You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When in sysprep mode, we are only applying changes to the default user profile. There is no need to Restart Explorer in this case. Further, it can hamper cmd script execution.
Additional context
I just encoutered this. I wanted to call windebloat with -silent and -sysprep from another cmd script form OOBE Shift-F10-Console. My script terminates because RestartExplorer kills the CMD window as it is a subprocess from the running Explorer instance.
PR follows.
The text was updated successfully, but these errors were encountered:
helge000
added a commit
to helge000/Win11Debloat
that referenced
this issue
Feb 10, 2025
- Since Settings are applied to Default Profile, calling RestartExplorer
does nothing
- RestartExplorer also terminates all processes witch might have called
WinDebloat in the first place
Describe the bug
When in
sysprep
mode, we are only applying changes to the default user profile. There is no need to Restart Explorer in this case. Further, it can hamper cmd script execution.Additional context
I just encoutered this. I wanted to call windebloat with
-silent
and-sysprep
from another cmd script form OOBE Shift-F10-Console. My script terminates because RestartExplorer kills the CMD window as it is a subprocess from the running Explorer instance.PR follows.
The text was updated successfully, but these errors were encountered: