If you want to keep "::" for "cosmetic" reasons, use the following code : Code: fsutil dirty query %systemdrive% >nul 2>&1 && goto :GotPrivileges :: The following test is to avoid infinite looping if elevating UAC for Administrator Privileges failed If "%1"=="%params%" (echo Elevating UAC for Administrator Privileges failed...&echo Right click on the script and select 'Run as administrator'&echo Press any key for exiting&pause>nul 2>&1&exit) cmd /u /c echo Set UAC = CreateObject^("Shell.Application"^) : UAC.ShellExecute "%~0", "%params%", "", "runas", 1 > "%temp%\getadmin.vbs"&cscript //nologo "%temp%\getadmin.vbs"&exit :GotPrivileges
You didn't have to go to the trouble of doing that. The "rem" wasn't a problem. But since you did, I'll add the changed code to the script and make it v 2.1.4. Excellent work.
June 3,2017 Script updated to v2.1.4 Improved code by rpo Note: AUC elavation failure detection is testing well so far Send failure reports to this thread. So far, we've received none.
Your question is finally answered. Windows Defender updates using BITS, so you'll still get updates, even with windows update service disabled, if you have WD running.
Had mixed results using Defender GUI. Fortunately there's a powershell CMD-let which is very versatile, using MMPC as update source, works nicely here. Code: powershell "Update-MpSignature -UpdateSource MMPC -Verbose"
Interesting. Edit: I wish WUMT searched for defender updates. I never even thought about that when I started this project. I was just concentrating on full control of Windows Updates only and have never used defender. I could add code to check to see if Defender is running and if so, add a scheduled task to periodically run your code while windows updates are turned off. That might be the best approach. I don't even know how defender updates are scheduled. I'll study up on it and if enough people are interested I could incorporate that. So thanks for that.
I have been using the WUMT Wrapper script to run Windows Update MiniTool and this has enabled me to have full control of when my PC gets updated. Recently I have found that Windows 10 is changing the status of the Windows Update Service from Disabled to Manual (Trigger Start). Is there a way to stop this behavior and re-gain control of my PC. Overnight my PC installed an update and then forced a reboot which caused something I had been running over 3 days to get aborted when it was 96% finished. I am running Windows 10 Build 1607.
@thefly42: I have not been able to determine how the windows update service setting is being changed for some people. I wish I knew. Y̶o̶u̶ ̶c̶a̶n̶ ̶i̶n̶s̶t̶a̶l̶l̶ ̶t̶h̶e̶ ̶W̶i̶n̶d̶o̶w̶s̶ ̶1̶0̶ ̶U̶p̶d̶a̶t̶e̶ ̶D̶i̶s̶a̶b̶l̶e̶r̶ ̶a̶n̶d̶ ̶m̶a̶n̶u̶a̶l̶l̶y̶ ̶t̶u̶r̶n̶ ̶i̶t̶ ̶o̶f̶f̶ ̶b̶e̶f̶o̶r̶e̶ ̶r̶u̶n̶n̶i̶n̶g̶ ̶t̶h̶e̶ ̶w̶r̶a̶p̶p̶e̶r̶ ̶s̶c̶r̶i̶p̶t̶. You can modify the script to do that for you and then reenable the update disabler service. I've been thinking about incorporating it into the script. Maybe I'll do it. Edit: The Windows Update Disabler doesn't work to fix this problem.
Thanks for the quick reply but it seems that even with using the Windows 10 Update Disabler tool people are reporting that the update service was changed from disabled to manual. That was someone with build 1709 but it doesn't bode well. I will give it a try and see. Also others are reporting that it does not stop Windows 10 Update Assistant from downloading new build of Windows 10.
Yes, same results but again and just to make it clear: 1. Windows 10 Update Disabler not disables (stop running)) any Windows Update component. 2. Windows Updates components, namely Windows Update Agent and Service, two separate entities/programs are always running, as Microsoft likes them to be. 3. Windows 10 Update Disabler interferes with a undocumented system call so the Agent can't even start searching for updates.
Thanks for the info and links. I'll investigate and see what can be done to stop updates. The current situation is unacceptable.
Nah. As soon as more information is uncovered, I'll find a sure way to disable updates again and the wrapper script will be good as new. I just have to change tactics. Disabling wuaserv used to be enough. Now that it's not I'll find out what is and I'll adapt the script to the new changes. I'm keeping a close eye on this thread you showed me. Somebody will figure out a definitive solution and I'll update the script then to automate everything just like before. Hopefully it won't take long to find a working solution.
@ pf100 yep I trust on you always wumt is one awesome application, although I stuck with W10 1607 until 2019 and after no doubt open source O.S.