DefaultUser0 Error - Newly added UAC Warning

[bseklecki_ge]

Thank you for adding that; I had the problem earlier this year where I burned a hundred hours troubleshooting PANTHER.
I think I finally agreed not to adjust UAC during the OEM setup cmd.

Finally, to set the desired resulting setting of UAC that does not interfere with OEM Setup process, I have the OEM setup register a RunOnce script to change it at 1stLogin.



View attachment 10789

 

[garlin]

Disabling UAC is generally risky, because several Windows processes will assume they need to elevate and their code fails when rights have already been granted. Start All Back is another example, it won't run from Post-Setup (Machine).

If you play around with UAC, always look there first before blaming NTLite or Windows.

 

[chrcol]

I noticed this on the latest ntlite, when I previously had no warning, it confuses me as I have dont have any defaultuser0 problems, so is the warning being shown in instances when it shouldnt be shown?

For reference I do change the default UAC behaviour to disable the whitelisting (Vista behaviour).

Turns out I do have defaultuser0, and its still there with UAC left on defaults. I guess I am going to have to do step by step diagnosis on changes to find the culprit. Its so fragile and easy to break. (it does go away after a reboot now though, before it didnt on reboot.)