Closed celengbalap closed 10 months ago
Managed to found the cause, closing.
Managed to found the cause, closing.
hey, I'm having a similar issue, what was the cause and how did you fix it?
Managed to found the cause, closing.
hey, I'm having a similar issue, what was the cause and how did you fix it?
i don't exactly remember, i've fully migrated to linux now, but it's related to some system service that must be started automatically and i had to find it by comparing original registry and registry after applying the tweak then.
Description
After applying the "apply tweaks", command prompts/cmd.exe would always pauses itself when opening the "OpenTerminalHere.cmd" and requires me to press enter to spawn UAC request after this
was shown the instead of automatically spawning it like the first time. I've tried to figure out what causes this, first suspect was this line. https://github.com/LeDragoX/Win-Debloat-Tools/blob/ba3d655a9a45c995baf3bac4ad0a015469254ce8/src/scripts/Optimize-Security.ps1#L71 https://github.com/LeDragoX/Win-Debloat-Tools/blob/ba3d655a9a45c995baf3bac4ad0a015469254ce8/src/scripts/Optimize-Security.ps1#L72 but changing them according to this docs https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-gpsb/341747f5-6b5d-4d30-85fc-fa1cc04038d4 https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-gpsb/9ad50fd3-4d8d-4870-9f5b-978ce292b9d8 Doesn't revert the behavior, i wonder, are you aware of what might be causing this behavior? searching on stackoverflow yields irrelevant answer like this https://stackoverflow.com/questions/13599822/command-prompt-gets-stuck-and-continues-on-enter-key-press when in reality a fresh windows 10 installs, quick edit is indeed enabled by default and does not introduce this behavioral changes to command prompt and UAC.
Reason
Examples
No response