Make your Vista's admin account acts like in XP


Recommended Posts

First let me start by saying that one of the main features of Windows Vista is the new user accounts security enhancements, but sometimes, defaults don't meet everyone's taste when it comes to how we deal with our PCs. I for one, always used full administrator accounts since I first knew what a Windows user account is, and never been hit by a virus/spyware/crap, using common sense and updated AV software, so I don't want to give permissions to myself or face strange error messages every time I do a simple task on my computer.

We know UAC feature in Windows Vista, and we all know how to disable it, this is not the purpose of this thread, because even after you disable UAC, you'll have other prompts about folder/file permissions errors sometimes (I faced it in strange, unexpected occasions, like deleting an empty folder for a program left by the uninstaller), or you'll need to right click and select "Run as Administrator" for most applications to work/install correctly.

That's because Microsoft made the administrators accounts (in local administrators group) run as standard users, unless we give permissions for every and each administrative tasks, with a little difference when UAC is turned on/off

Enough introductions, lets get our hands dirty:

*************************************

Remember that cute "Administrator" account you see when you login to safe mode in XP? That's the built-in administrator account that's installed by default, and disabled by default too, after a little digging-in I made this tutorial that'll let you enable and use this account in normal mode, and with a little other tweak, enjoying an XP-like administrator experience, while UAC is left ON (or off, it doesn't matter), but with no prompts or right clicks.

For Windows Vista Ultimate/Business/Enterprise:

1- Click Start, and type "secpol.msc" in the search area and click Enter. (You may receive a prompt from UAC, approve/login and proceed)

2- In the left list, choose "Local Policies", then "Security Options"

3- Set "Accounts: Administrator account status" to Enabled.

4- Set "User Account Control: Admin Approval Mode for the Built-in Administrator account" to Disabled.

For Windows Vista Home Basic/Home Premium:

1- Click Start, and type "cmd" in the search area, right click on "Command Prompt" and select 'Run as Administrator".

2- In the command prompt type "net users Administrator /active:yes" (Note the capital "A" in Administrator) and press Enter, you will get a confirmation as "The command completed successfully".

3- Click Start, and type "regedit" in the search area and click Enter, navigate to: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]

Double click on "FilterAdministratorToken" and set it to ""

*************************************

Now log-off, and you'll see new account named "Administrator" is available, click on it to login.

Now you are the master of your domain! I recommend if you're going to use this method is to apply it as soon as you do a fresh install of Windows, so you can simply delete whatever administrator you've created in the setup process, and make this one the "real" administrator for your PC, also you can rename this new admin account or change its password like any other account from "User Accounts" in the Control Panel.

A last note/disclaimer:

Please note that disabling UAC and using the built in Adminstrator account will also disable IE7 "Protected Mode", fore more information and a work around please see this post.

Please apply this procedures only if you know what you're doing. Disabling security features in the operating system is not something recommended to the average Joe, and for sure I won't be held accountable for any damaging happens to your system or files resulting from running a full administrator account all the time.

Enjoy! :)

Special thanks to:

- Farstrider for providing the location of the relevant register keys that made applying this method to the home versions of Vista possible!.

- bradavon for his comment/solution of IE7 protected mode.

Edited by Tantawi
the built in admin account, iirc, has some perms that your normal admins dont, but it also lacks some perms that your normal admins do. at least in XP it was like this....anyone confirm?

By default the administrator account does not have permission to access the files of other users if the others users are configured to make their files private (I'm basing this on my domain controller setup but I believe its the same for local accounts)

But as an administrator, you can take ownership of the files and then change the permissions.

And of course if other users encrypt their files then the admin account can't access them.

Vista appears to be the same.

You can also use gpedit.msc

secpol.msc's items are a subset of gpedit.msc

You can also adjust the settings in the registry here:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Policies\System]

These are the main keys that affect UAC, equivalent to the secpol.msc

settings.

"ConsentPromptBehaviorAdmin"

"ConsentPromptBehaviorUser"

"EnableInstallerDetection"

"EnableLUA"

"EnableSecureUIAPaths"

"EnableVirtualization"

"PromptOnSecureDesktop"

"ValidateAdminCodeSignatures"

"FilterAdministratorToken"

You can also use gpedit.msc

secpol.msc's items are a subset of gpedit.msc

You can also adjust the settings in the registry here:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Policies\System]

These are the main keys that affect UAC, equivalent to the secpol.msc

settings.

"ConsentPromptBehaviorAdmin"

"ConsentPromptBehaviorUser"

"EnableInstallerDetection"

"EnableLUA"

"EnableSecureUIAPaths"

"EnableVirtualization"

"PromptOnSecureDesktop"

"ValidateAdminCodeSignatures"

"FilterAdministratorToken"

maybe someone could post some reg tweaks for the above keys, so that we can just copy and paste them into notepad and save them as .reg files, would be very handy:)!

Nice work, but why would someone use the Administrator account?

I've just turned off UAC and have my own user with Administrator privileges.

That was even less work then this solution...

because of some popup messages and some programs wont even run like the bios flash utility for my hp laptop, it wont even work when you choose "run as administrator".

Suppose i use this method. I currently don't have to log onto my computer, it just boots to windows. After doing this change will i be prompted choose a user to log in with as there would be 2 users and i would then have to log in?

If it does create a log in after i deleate the old admin account will the log in process go away (assuming that i don't use a password for the new admin)?

Suppose i use this method. I currently don't have to log onto my computer, it just boots to windows. After doing this change will i be prompted choose a user to log in with as there would be 2 users and i would then have to log in?

If it does create a log in after i deleate the old admin account will the log in process go away (assuming that i don't use a password for the new admin)?

Yes, that's why I recommend to do it as soon as you install a fresh window so you don't be worried about deleting the admin account you created in the setup process :) After you delete it, you'll login automatically as long as you don't set a password of course.

You can also use gpedit.msc

secpol.msc's items are a subset of gpedit.msc

You can also adjust the settings in the registry here:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Policies\System]

These are the main keys that affect UAC, equivalent to the secpol.msc

settings.

"ConsentPromptBehaviorAdmin"

"ConsentPromptBehaviorUser"

"EnableInstallerDetection"

"EnableLUA"

"EnableSecureUIAPaths"

"EnableVirtualization"

"PromptOnSecureDesktop"

"ValidateAdminCodeSignatures"

"FilterAdministratorToken"

Nice guide,but I can only access to this settings via registry in vista home basic.

I like to ask which one number we must past here in this lines?

), or you'll need to right click and select "Run as Administrator" for most applications to work/install correctly.

That makes absolutely no sense. There's no split token when you disable UAC via that dialog. The "Run As Administrator" option should have no effect at all.

The only time you'd have to do that would be if you disable UAC by setting admins to auto-elevate (as I suggested in another thread).

@ Brandon Live

I'm curious to know your opinion on:

Remember that cute "Administrator" account you see when you login to safe mode? That's the built-in administrator account that's installed by default, and disabled by default too, after a little digging-in I made this tutorial that'll let you enable and use this account in normal mode, and with a little other tweak, enjoying an XP-like administrator experience, while UAC is left ON (or off, it doesn't matter), but with no prompts or right clicks.

1- Click Start, and type "secpol.msc" in the search area and click Enter.

2- You may receive a prompt from UAC, approve/login and proceed.

3- In the left list, choose "Local Policies", then "Security Options"

4- Set "Accounts: Administrator account status" to Enabled.

5- Set "User Account Control: Admin Approval Mode for the Built-in Administrator account" to Disabled.

6- Now log-off, and you'll see a new account named "Administrator" will be available, click on it to login.

Now you are the master of your domain! I recommend if you're going to use this method is to apply it as soon as you do a fresh install of Windows, so you can simply delete whatever administrator you created in the setup process, and make this one the "real" administrator for your PC, also you can rename this new admin account or change its password like any other account from "User Accounts" in the Control Panel.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
    • AMD releases hotfix for driver install issues on Windows 10 PCs by Taras Buria Earlier this week, AMD released an important graphics driver update. Version 26.6.2 brought AMD FSR 4.1 support to the previous-gen Radeon lineup, the RX 7000 series, giving users better upscaling tech that was previously locked to the newest GPUs. However, the driver turned out to be a little buggy, with users reporting installation issues on systems still running Windows 10. AMD quickly acknowledged the bug and today released a hotfix to resolve the problem. The AMD 26.6.3 Hotfix update is now available for download from the official website. Given that it is a hotfix release, it has only one change in its release notes: AMD announced the update on its official X account and added that a WHQL driver update with the necessary fixes would be released next week. Meanwhile, users can apply the hotfix or roll back to the previous driver using the official AMD Cleanup Utility. You can download AMD Software: Adrenalin Edition 26.6.3 Hotfix Preview Driver from the official website here. It is compatible with all currently supported graphics cards and 64-bit Windows 10 and 11. Full release notes are available on the same page.
    • With Microsoft now listening to its core audience and acting upon received feedback, fans can finally expect a much better version of Windows 11 than what was available five years ago. Here is to five more years, Windows 11! I guess we all need a good laugh now and again...
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      466
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!