Talk:User Account Control

Is UAC really first appeared on Longhorn 4029?[edit source]

Because builds from 3683 to 4002 features Avalon Trust Manager, a UAC but only for Avalon applications. Later builds, such as 4015 contains Trust Advisor and of course, its only for Avalons. The UAC featured in 4029 is still for Avalons. Someone (talk) 09:18, 20 April 2022 (UTC)

Add more images[edit source]

Well can you add prompts for blocked programs Someone (talk) 02:03, 21 April 2022 (UTC)

UAC Debut Prediction[edit source]

UAC probably debuted in Windows Longhorn build 3683. --Brennan1234567890 (talk) 19:31, 4 July 2022

The debut of UAC

I think this need to be corrected.[edit source]

There is a sentence named "although Windows does not have an equivalent of a root user". That is incorrect. We have SYSTEM/TrustedInstaller that can do any modifications of system files. SYSTEM can be accessed by running cmd in login screen. TrustedInstaller can't be accessed normally and need special softwares to access under cmd. Someone (talk) 15:28, 7 July 2022 (UTC)

Neither SYSTEM nor TrustedInstaller is intended to be used by the end user. Furthermore, a regular administrator account can do most of the stuff that would require logging in as root under Unix. That includes modifying system files, assuming you take ownership of them first. So no, they are not really equivalent to a root user. Not to mention you can't spawn a command prompt on the login screen without modifying the system first, so I would hardly call that "normally accessible". --Ryuzaki (talk | contribs) 18:40, 5 August 2022 (UTC)