It’s already answered here stackoverflow but I want to take note for later usage in case I forget it again 🤣.
Unfortunately we couldn’t address all cases of the command line issue for this release as we’re still investigating the appropriate way to address them. What we do have is a workaround that we believe will work for almost all of them.
If you are still suffering this issue then you can try to change the DWORD value for the following registry value
If this doesn’t exist you can create it as a DWORD.