wojtek109 0 Posted August 9, 2013 I Trying this script RegWrite("HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionPoliciesSystem", "EbableLUA","REG_SZ", "0") i have win 8 but this script not disable UAC if you knot how to turn it off tell me !!! Share this post Link to post Share on other sites
orbs 201 Posted August 9, 2013 you copy/paste from MSDN blog without reading? that's awful. even one of the posts in the article you copied from mentioned the typo - yet the author did not fix it. read your line, man. also, Win 8 UAC can not be fully disabled without crippling your Metro apps. there are many articles on this - most of them, like the one you copied from, are mistaken because they are not aware of this (written too early when Win 8 was just released). for myself, i do not disable UAC on Win 8 (or Win 7 for that matter). this is a lost battle. i just plan my scripts to not tackle UAC in the first place. Share this post Link to post Share on other sites
Bert 1,430 Posted August 9, 2013 The whole point of UAC is to keep users from doing stupid stuff. You can disable it on your PC manually ...but scripting it - why do you want to do that? The Vollatran project My blog: http://www.vollysinterestingshit.com/ Share this post Link to post Share on other sites
0xdefea7 10 Posted August 9, 2013 RegWrite("HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System", "EnableLUA","REG_SZ", "0") Notice the "n" in "Enable" as orbs pointed out. Again everyone else in here is right, it is a bad idea to disable UAC, it has adverse effects. Share this post Link to post Share on other sites
AdamUL 98 Posted August 9, 2013 If I need a script to have full admin rights, and to be rerun multiple times to complete a series of tasks, I set the "ConsentPromptBehaviorAdmin" value on first run of the script, and then have the script reset it when the script is finished. As others have said, I would not fully disable UAC. There are examples on the forum for working with UAC, depending on what you are trying to do. Adam Share this post Link to post Share on other sites
BlueBoden 0 Posted August 9, 2013 (edited) . Edited July 27, 2016 by BlueBoden Share this post Link to post Share on other sites
Queener 1 Posted August 9, 2013 I have not tried, but you possibly want to try it out first before code it Got it from HowToGeek Disable UAC C:\Windows\System32\cmd.exe /k %windir%\System32\reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f Enable UAC C:\Windows\System32\cmd.exe /k %windir%\System32\reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 1 /f retstart needed Msgbox(0, "Hate", "Just hate it when I post a question and find my own answer after a couple tries. But if I don't post the question, I can't seem to resolve it at all.") Share this post Link to post Share on other sites
orbs 201 Posted August 9, 2013 I set the "ConsentPromptBehaviorAdmin" value on first run of the script, @Adam, but that first change will trigger the UAC anyway, no? Share this post Link to post Share on other sites
AdamUL 98 Posted August 9, 2013 Yes, that is true. It all depends on what you are trying to with your script. If you want to disable UAC for admin only, you can set "ConsentPromptBehaviorAdmin" to 0, and admins will not be prompted, but non admins will. Adam Share this post Link to post Share on other sites
0xdefea7 10 Posted August 10, 2013 (edited) The reason why people want to disable it – the reason that i want to disable it anyway – is that it drastically slows down installers and setup programs. I've personally had these things freeze up for several seconds, just waiting for UAC to show its dialogs. Run your process as admin and create the installer processes from your process. Any child process will run with the same access and should not trigger UAC. I use several installers (MSI and other) in my scripts this way and it works fine, only the first UAC (the prompt to start my own script) ever fires. Edited August 10, 2013 by 0xdefea7 1 BlueBoden reacted to this Share this post Link to post Share on other sites
Chimaera 144 Posted August 10, 2013 Run your process as admin and create the installer processes from your process. Any child process will run with the same access and should not trigger UAC. I use several installers (MSI and other) in my scripts this way and it works fine, only the first UAC (the prompt to start my own script) ever fires. Thats how i run my installers etc deal with it once and thats it (unless you close the tool ) If Ive just helped you ... miracles do happen. ChimaeraCopyRobo() * Hidden Admin Account Enabler * Software Location From Registry * Find Display Resolution * _ChangeServices() Share this post Link to post Share on other sites