-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
windows 11 CmDiag DevelopmentMode -On
invalid
#4
Comments
Windows 11 was not tested. What is the output of the command? |
no output |
And what about |
PS C:\Users\Chord> CmDiag DevelopmentMode -On
PS C:\Users\Chord> CmDiag Debug -On -Net
PS C:\Users\Chord> CmDiag DevelopmentMode -On
PS C:\Users\Chord> CmDiag DevelopmentMode -On
PS C:\Users\Chord> CmDiag DevelopmentMode -On
PS C:\Users\Chord>
PS C:\Users\Chord>
PS C:\Users\Chord>
PS C:\Users\Chord> CmDiag Debug -On -Net
PS C:\Users\Chord> CmDiag DevelopmentMode -On
PS C:\Users\Chord> CmDiag Debug -On -Net
PS C:\Users\Chord> CmDiag Debug -On -Net
PS C:\Users\Chord>
PS C:\Users\Chord> CmDiag -h
CmDiag
PS C:\Users\Chord> CmDiag
PS C:\Users\Chord> |
And Windows Sandbox is working correctly? |
yep |
Maybe Microsoft removed the CmDiag functionality. You can try to use procmon and filter on Which version of windows 11 are you on exactly? |
windows 11 21H2 22000.856 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
windows 11
CmDiag DevelopmentMode -On
invalidThe text was updated successfully, but these errors were encountered: