Stop Windows 10 Updates Properly and Completely

Have you found a way to stop the osrss? I have found that the newest wub can disable it and that process hacker 2 can kill it. But it takes three terminates to do so since the failure needs to be three times.

pf100 said:

May 5, 2018
WUMT Wrapper Script 2.2.8 (Download link from Major Geeks)
Updated for Windows 10 1803
Now uninstalls and removes Windows 10 Update Assistant.
Disables new WaasMedic components introduced in 1803
Update Orchestrator service disabled permanently (UpdateOrchestrator tasks can't run)
WaasMedic permanently disabled (WaasMedic tasks can't run)
WindowsUpdate *optionally* permanently disabled using Configurator (default is always disabled unless checking updates with script, can be left on for automatic app updates and to use Store and Defender at any time at the expense of a possible forced update. Or just use it to temporarily enable the update service to use the store and then disable it afterwards which is what I do using a third party antivirus. Your choice.)
Sihclient (I call it Silent Install Helper) permanently disabled (sih tasks can't run.)
*All changes can be reversed with uninstaller script.

I understand the concern about Windows Update Blocker (wub.exe) and I'll stop using it and replace it's functionality in the script at some point but it hasn't been a priority for me since it works; however, I've gotten a lot of requests to stop using it and I will. It's really harmless though. This is what wub does:
Wub.exe works by dealing with the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv registry key.
Wub /e sets the value of "Start" to 2
Wub /d /p sets the value of "Start" to 4 and changes the registry key permissions. System has only read access, hence Windows Update process is disabled permanently (unless an update reenables it which is what the task wub_task is for. It keeps the update service off after a reboot.)

Why is it putting the code on one line? Am I retarded?
You can see the code here or here.

This is the script:

Code:

@echo off & goto startWUMT Wrapper Script version 2.2.8Original script by pf100 @ MDL with special thanks to rpo and abbodi1406 @ MDL for code improvements.https://forums.mydigitallife.net/threads/72203-WUMT-Wrapper-script-controls-windows-update-service******************************************************************You may freely modify this script as you wish, I only request that you leave the credits and thelink to the original script.******************************************************************This script provides manual updates.Update Windows 10 on your schedule, not Microsoft's!I originally wrote this script for personal use because of the lack of update options with theoriginal RTM release of Windows 10 Pro. I wanted to update Windows 10 when I had the free timeto manually update, just like I did with previous versions of Windows that allowed me toset updates to manual, not when Microsoft forced it on me while I was busy using my computer.When my computer rebooted in the middle of the night after a forced update I swore it would bethe last time I would let that happen. With the Windows 10 Anniversary Edition, increased lackof control and arbitrary removal of registry options only got worse. Microsoft removed previouslyworking Group Policies and registry tweaks on Windows 10 Pro and Windows 10 Home and I expectthings may only get worse with future major updates. The methods that may or may not work nowsuch as update notifications, metered network connections, Windows 10 Pro Group Policy edits,and other workarounds implemented to control automatic updates are not guaranteed to work foreveron Windows 10 if the past is any indicator. This script will always allow fullymanual updates no matter what Microsoft does to force automatic updates, including Windows 10 Home.*******************************************************************Installation: Save this script, the Windows Update MiniTool (WUMT), and Windows Update Blocker in the same folder, i.e."X:\Windows Update", then make a shortcut to this script and use it to run windows updatesmanually from now on. You only have to make the shortcut run as administrator if you have an elevation problem since it auto-elevates.WUMT is available here: https://forums.mydigitallife.net/threads/64939-Windows-Update-MiniTool*It is recommended to keep the Windows Update Minitool (WUMT) updated to the latest version.*Windows Update Blocker is available here: http://www.sordum.org/9470/windows-update-blocker-v1-0/*******************************************************************How it works: This script auto-elevates, uninstalls and removes the Windows 10 Update Assistant, renames the rempl folder (disabling remsh.exe), resets and removes permissions from and disables UsoClient.exe, WaaSMedic.exe, WaasMedicSvc.dll, WaaSMedicPS.dll, WaaSAssessment.dll and SIHClient.exe,makes sure the task "wub_task" is installed (keeps updates off after reboot), runs wub and enables and starts the windows update service (wuauserv) if disabled,then runs the correct version of the Windows Update MiniTool in "auto search for updates" mode for your OS version's architecture (x86 or x64),then disables and stops wuauserv giving you full control. No more forced automatic updates or surprise reboots in the middle of the night. This waswritten for Windows 10 Pro and Home, but works with all versions of Windows 10.********************************************************************If you need to install .Net 3.5 or use the Windows 10 Store or something that needs wuauservrunning, run the script and after it enables wuauserv and starts WUMT, install what you needafter WUMT checks for updates, before closing WUMT. If you ran the Configurator to "leavethe Windows Update Service running at all times" you can ignore this note as the store willwork at any time and Windows Defender will get updates.*******************************************************************:start::::::::::::::::::::::::::::::::::::::::::: Automatically check & get admin rights:::::::::::::::::::::::::::::::::::::::::Title WUMT Wrapper Script 2.2.8Color 1FCLS:: ECHO.:: ECHO =============================:: ECHO Running Admin shell:: ECHO =============================:: Check Privileges:: Get Privileges:: and:: Invoke UAC for Privilege Escalation:: Notify if error escalating:: and prevent looping if escalation fails::::::::::::::::::::::::::::set "params=Problem_with_elevating_UAC_for_Administrator_Privileges"&if exist "%temp%\getadmin.vbs" del "%temp%\getadmin.vbs"fsutil dirty query %systemdrive%  >nul 2>&1 && goto :GotPrivileges::    The following test is to avoid infinite looping if elevating UAC for Administrator Privileges failedIf "%1"=="%params%" (echo Elevating UAC for Administrator Privileges failed&echo Right click on the script and select 'Run as administrator'&echo Press any key to exit...&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::::::::::::::::::::::::::::::START::Uninstall and remove Windows 10 Update assistant.::Disable Windows Update Service until script menu screen.::Reset (in case of wrong Permissions), remove Permissions from and Disable UsoClient.exe,::WaaSMedic.exe, WaasMedicSvc.dll, WaaSMedicPS.dll, WaaSAssessment.dll, and SIHClient.exe.::Kill remsh.exe if it's running.::Rename the folder %ProgramFiles%\rempl to %ProgramFiles%\rempl-backup if it exists.::Install wub_task (prevents Windows Update service from starting after installing updates and rebooting).::Enable and start the Windows Update Service (wuauserv).::Run the correct version of WUMT for your architecture.::Start WUMT in "auto-check for updates" mode.::After updates are completed and WUMT is closed and/or the "reboot"::button in WUMT is pressed, silently run wub.exe and disable and stop wuauserv::::::::::::::::::::::::::::echo.echo Please wait...::::::::::::::::::::::::::::@echo offclsif exist "%systemdrive%\Windows10Upgrade\Windows10UpgraderApp.exe" ( echo Windows 10 Update Assistant detected. Preparing to uninstall. ) else ( goto noevil )echo The "Windows 10 Update Assistant has stopped working" dialog box may pop up. If so, just close it.echo Press a key to acknowledge this and please wait 15 seconds for the uninstall to finish.echo Script will continue after uninstall and removal is completed...pause > nulecho Uninstalling Windows 10 Update Assistant...%systemdrive%\Windows10Upgrade\Windows10UpgraderApp.exe /forceuninstalltimeout /t 15 /nobreak >nul 2>&1del %systemroot%\UpdateAssistant\*.* /f /q >nul 2>&1rmdir %systemroot%\UpdateAssistant /s /q >nul 2>&1del %SystemDrive%\Windows10Upgrade\*.* /f /q >nul 2>&1rmdir %SystemDrive%\Windows10Upgrade /s /q >nul 2>&1clsecho Windows 10 Update Assistant removed.echo Press a key to continue...pause > nul:noevildel %systemroot%\UpdateAssistantV2\*.* /f /q >nul 2>&1rmdir %systemroot%\UpdateAssistantV2 /s /q >nul 2>&1::::::::::::::::::::::::::::"%~dp0wub.exe" /d /p >nul 2>&1::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\UsoClient.exe" /a >nul 2>&1icacls "%systemroot%\System32\UsoClient.exe" /reset >nul 2>&1icacls "%systemroot%\System32\UsoClient.exe" /inheritance:r /remove *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaaSMedic.exe" /a >nul 2>&1icacls "%systemroot%\System32\WaaSMedic.exe" /reset >nul 2>&1icacls "%systemroot%\System32\WaaSMedic.exe" /inheritance:r /remove *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaasMedicSvc.dll" /a >nul 2>&1icacls "%systemroot%\System32\WaasMedicSvc.dll" /reset >nul 2>&1icacls "%systemroot%\System32\WaasMedicSvc.dll" /inheritance:r /remove *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaaSMedicPS.dll" /a >nul 2>&1icacls "%systemroot%\System32\WaaSMedicPS.dll" /reset >nul 2>&1icacls "%systemroot%\System32\WaaSMedicPS.dll" /inheritance:r /remove *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaaSAssessment.dll" /a >nul 2>&1icacls "%systemroot%\System32\WaaSAssessment.dll" /reset >nul 2>&1icacls "%systemroot%\System32\WaaSAssessment.dll" /inheritance:r /remove *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\SIHClient.exe" /a >nul 2>&1icacls "%systemroot%\System32\SIHClient.exe" /reset >nul 2>&1icacls "%systemroot%\System32\SIHClient.exe" /inheritance:r /remove *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1::::::::::::::::::::::::::::taskkill /im remsh.exe /f >nul 2>&1if exist "%ProgramFiles%\rempl" rmdir /s /q "%ProgramFiles%\rempl-backup" >nul 2>&1ren "%ProgramFiles%\rempl" rempl-backup >nul 2>&1::::::::::::::::::::::::::::set "Task_Name=wub_task"schtasks /delete /tn "%Task_Name%" /f 1>nul 2>nulschtasks /query /tn "%Task_Name%" >nul 2>&1 || (echo.&echo Creating Windows Update Blocker Auto-Renewal task %Task_Name%.(echo ^<?xml version="1.0" encoding="UTF-16"?^>echo ^<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task"^>echo ^<RegistrationInfo^>echo ^<Date^>2018-02-18T08:29:39^</Date^>echo ^<Author^>pf100\rpo^</Author^>echo ^<URI^>\wub_task^</URI^>echo ^</RegistrationInfo^>echo ^<Triggers^>echo ^<BootTrigger^>echo ^<StartBoundary^>2018-02-18T08:29:00^</StartBoundary^>echo ^<Enabled^>true^</Enabled^>echo ^</BootTrigger^>echo ^</Triggers^>echo ^<Principals^>echo ^<Principal id="Author"^>echo ^<RunLevel^>HighestAvailable^</RunLevel^>echo ^</Principal^>echo ^</Principals^>echo ^<Settings^>echo ^<MultipleInstancesPolicy^>IgnoreNew^</MultipleInstancesPolicy^>echo ^<DisallowStartIfOnBatteries^>false^</DisallowStartIfOnBatteries^>echo ^<StopIfGoingOnBatteries^>false^</StopIfGoingOnBatteries^>echo ^<AllowHardTerminate^>true^</AllowHardTerminate^>echo ^<StartWhenAvailable^>false^</StartWhenAvailable^>echo ^<RunOnlyIfNetworkAvailable^>false^</RunOnlyIfNetworkAvailable^>echo ^<IdleSettings^>echo ^<StopOnIdleEnd^>true^</StopOnIdleEnd^>echo ^<RestartOnIdle^>false^</RestartOnIdle^>echo ^</IdleSettings^>echo ^<AllowStartOnDemand^>true^</AllowStartOnDemand^>echo ^<Enabled^>true^</Enabled^>echo ^<Hidden^>false^</Hidden^>echo ^<RunOnlyIfIdle^>false^</RunOnlyIfIdle^>echo ^<WakeToRun^>false^</WakeToRun^>echo ^<ExecutionTimeLimit^>PT72H^</ExecutionTimeLimit^>echo ^<Priority^>7^</Priority^>echo ^</Settings^>echo ^<Actions Context="Author"^>echo ^<Exec^>echo ^<Command^>"%~dp0wub.exe"^</Command^>echo ^<Arguments^>/d /p^</Arguments^>echo ^</Exec^>echo ^</Actions^>echo ^</Task^>) >"%~dp0%Task_Name%.xml"schtasks /create /tn "%Task_Name%" /ru "SYSTEM" /xml "%~dp0%Task_Name%.xml" >nul 2>&1)::::::::::::::::::::::::::::clsecho ***********************************************echo Welcome to manual updates!echo Automatic updates are now turned offecho (unless overriden with Configurator).echo This script automates the update processecho It automatically disables a range of useless junkecho that bypasses windows update, such as:echo remsh, UsoClient, WaaSMedic, SIHClient, and Update Assistant.*echo Enables and starts only the Windows Update Service.echo Runs the Windows Update MiniTool (WUMT).echo After updates, stops and disables the Windows Update service.echo *The included uninstaller undoes script changes.*echo Closing WUMT at any time disables updates again;echo however, if WUMT is already offering updates, youecho need to hide them and/or install them one-by-oneecho before closing WUMT or it may install them withoutecho asking next time. Don't change WUMT settings whileecho running this script. If an update requires a reboot,echo re-run the script and just close the first screenecho to make sure the useless junk that forces updatesecho stay off.echo Run Configurator.cmd to enable running store and defenderecho ***********************************************echo. & echo Press any key to check for updates, orecho close this screen to cancel and leave updates turned offecho (unless overridden with configurator) & pause > nul"%~dp0wub.exe" /e:: Check OS and run correct version of WUMTfor /f "tokens=2 delims==" %%a in ('wmic cpu get AddressWidth /value') do (set arch=%%a)IF %arch% == 32 (set "wumt=%~dp0wumt_x86.exe") else (set "wumt=%~dp0wumt_x64.exe")Start "" "%wumt%" -update "-onclose %~dp0wub.exe /d /p"

Configurator:

Code:

@echo offColor 1FTitle WUMT Wrapper Script Configurator 2.2.8::::::::::::::::::::::::::::set "params=Problem_with_elevating_UAC_for_Administrator_Privileges"&if exist "%temp%\getadmin.vbs" del "%temp%\getadmin.vbs"fsutil dirty query %systemdrive%  >nul 2>&1 && goto :GotPrivileges::    The following test is to avoid infinite looping if elevating UAC for Administrator Privileges failedIf "%1"=="%params%" (echo Elevating UAC for Administrator Privileges failed&echo Right click on the script and select 'Run as administrator'&echo Press any key to exit...&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::::::::::::::::::::::::::::echo Welcome to WUMT Wrapper Script Configuratorecho [D]isable Update Service and only allow to run during manual updates (default)echo.echo [K]eep the Update Service always running to allow Defender Updates and Store at any timeecho.CHOICE /C DK /M "YOUR CHOICE ?:"if %errorlevel%==2 goto enablewubif %errorlevel%==1 goto disablewub:enablewub"%~dp0wub.exe" /e >nul 2>&1ren "%~dp0wub.exe" wub.exe-backup >nul 2>&1clsecho Windows Update Service now enabled and running and it won't be manipulated by wrapper script.echo To reverse changes just run script again.echo Press any key to exit...pause > nulgoto end:disablewubren "%~dp0wub.exe-backup" wub.exe >nul 2>&1"%~dp0wub.exe" /d /p >nul 2>&1clsecho Windows Update Service disabled except for manual update checks with script.echo To reverse changes just run script again.echo Press any key to exit...pause > nul:end

Uninstaller:

Code:

@echo offColor 1FTitle WUMT Wrapper Script 2.2.8 uninstallerset "params=Problem_with_elevating_UAC_for_Administrator_Privileges"&if exist "%temp%\getadmin.vbs" del "%temp%\getadmin.vbs"fsutil dirty query %systemdrive%  >nul 2>&1 && goto :GotPrivileges::    The following test is to avoid infinite looping if elevating UAC for Administrator Privileges failedIf "%1"=="%params%" (echo Elevating UAC for Administrator Privileges failed&echo Right click on the script and select 'Run as administrator'&echo Press any key to exit...&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:GotPrivilegesecho Press a key to uninstall WUMT Wrapper Scriptecho or close window or ctrl-c to cancel.pause > nul@echo onren "%ProgramFiles%\rempl-backup" remplren "%~dp0wub.exe-backup" wub.exeschtasks /delete /tn "wub_task" /f::::::::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\UsoClient.exe" /aicacls "%systemroot%\System32\UsoClient.exe" /reseticacls "%systemroot%\System32\UsoClient.exe" /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464::::::::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaaSMedic.exe" /aicacls "%systemroot%\System32\WaaSMedic.exe" /reseticacls "%systemroot%\System32\WaaSMedic.exe" /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464::::::::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaasMedicSvc.dll" /aicacls "%systemroot%\System32\WaasMedicSvc.dll" /reseticacls "%systemroot%\System32\WaasMedicSvc.dll" /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464::::::::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaaSMedicPS.dll" /aicacls "%systemroot%\System32\WaaSMedicPS.dll" /reseticacls "%systemroot%\System32\WaaSMedicPS.dll" /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464::::::::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaaSAssessment.dll" /aicacls "%systemroot%\System32\WaaSAssessment.dll" /reseticacls "%systemroot%\System32\WaaSAssessment.dll" /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464::::::::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\SIHClient.exe" /aicacls "%systemroot%\System32\SIHClient.exe" /reseticacls "%systemroot%\System32\SIHClient.exe" /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464::::::::::::::::::::::::::::::::::"%~dp0wub.exe" /e@echo offecho ::::::::::::::::::::::::::::::::::::echo :WUMT Wrapper Script changes undone:echo ::::::::::::::::::::::::::::::::::::echo Press any key to exit...pause > nul

pf100 said:

I just now submitted version 2.5.2 to Major Geeks and it's up now. Please use 2.5.2 as it's vastly improved. I can't imagine it working any better.
This script is basically like Windows 7 manual update mode. No notifications or update checks unless you run the script. No drivers or any other update you don't want from Windows Update can install unless you allow it, because you can hide them.

This looks like an amazing tool. Sorry for all these questions, but I'm not an expert & I'm completely lost.
1. I'm confused about the preinstall warning. Do I have to uninstall WUMT every time I want to run sfc & then reinstall it, or can I just ignore those errors (EOSNotify.exe, osrss.dll,UsoClient.exe, WaaSMedic.exe, WaasMedicSvc.dll, WaaSMedicPS.dll,WaaSAssessment.dll, MusNotificationUx.exe, MusNotification.exe, and SIHClient.exe) or should I run findstr /c:"[SR] Cannot" %windir%\logs\cbs\cbs.log|more to see if there are problems?

2. I saw this message above. Is the store the same as allowing WU to run normally? i.e. I don't know what the store has to do with WU. "Afterwards you can run the Configurator to allow the store at any time but it's a tradeoff. For the Store to work at any time the update service must be on. I leave it off and use Configurator to set it to [E]nable to run Store and then set [D]isable again with Configurator after I'm through with the Store. You can leave it [E]nabled and the Store will always work. At least you have a choice."
3. Will the WU Assistant reinstall after I close WUMT? If not, how do I get it back? Can I make a change to the configurator or will this defeat the entire purpose of WUMT?

4. Since I'm not sure what the "store" is, I don't know what "E" does? If I exit now by pressing "C", will I not be notified of any Windows Updates?
5. I don't know where the "configurator" comes into play. But at this point, if I run WUMT, is the only way to get updates is to rerun WUMT in the future...i.e. I won't be notified of updates otherwise? If I hide certain updates, will they show up the next time I run WUMT so I can unhide them? What happens if I select one & click the recycle icon...is it gone forever or can I undo this?
6. When I ran WUMT, I got a message about invalid data type & don't know if there's a problem.

7. If I choose notification mode, does this mean I'll be notified whenever there's an update & can choose to download & install?If so, will this show up in the "Action Center"? I don't know what all the options really do. I saw something about if I don't select or exclude (I can't remember which), it will install automatically. Is this true even if I've chosen to delay install, as I've shown below.

Again, I apologize for all the questions! I appreciate your time & expertise.

bryantjopplin said:

Have you found a way to stop the osrss? I have found that the newest wub can disable it and that process hacker 2 can kill it. But it takes three terminates to do so since the failure needs to be three times.

v2.5.2 permanently disables osrss until you uninstall the script. Don't use WUB v1.1 with this script because if you do you need to "enable" with v1.1, then never use it again with this script. The whole premise of WUB v1.1 makes no sense to me. It disables more things than v1.0, but the things it disables are completely unnecessary. Why would you disable a lot of services and then when you want to check for updates you turn all that stuff back on again? I told the author of WUB as much and received no answer.

phrab said:

This looks like an amazing tool. Sorry for all these questions, but I'm not an expert & I'm completely lost.
1. I'm confused about the preinstall warning. Do I have to uninstall WUMT every time I want to run sfc & then reinstall it, or can I just ignore those errors (EOSNotify.exe, osrss.dll,UsoClient.exe, WaaSMedic.exe, WaasMedicSvc.dll, WaaSMedicPS.dll,WaaSAssessment.dll, MusNotificationUx.exe, MusNotification.exe, and SIHClient.exe) or should I run findstr /c:"[SR] Cannot" %windir%\logs\cbs\cbs.log|more to see if there are problems?

2. I saw this message above. Is the store the same as allowing WU to run normally? i.e. I don't know what the store has to do with WU. "Afterwards you can run the Configurator to allow the store at any time but it's a tradeoff. For the Store to work at any time the update service must be on. I leave it off and use Configurator to set it to [E]nable to run Store and then set [D]isable again with Configurator after I'm through with the Store. You can leave it [E]nabled and the Store will always work. At least you have a choice."
3. Will the WU Assistant reinstall after I close WUMT? If not, how do I get it back? Can I make a change to the configurator or will this defeat the entire purpose of WUMT?

4. Since I'm not sure what the "store" is, I don't know what "E" does? If I exit now by pressing "C", will I not be notified of any Windows Updates?
5. I don't know where the "configurator" comes into play. But at this point, if I run WUMT, is the only way to get updates is to rerun WUMT in the future...i.e. I won't be notified of updates otherwise? If I hide certain updates, will they show up the next time I run WUMT so I can unhide them? What happens if I select one & click the recycle icon...is it gone forever or can I undo this?
6. When I ran WUMT, I got a message about invalid data type & don't know if there's a problem.

7. If I choose notification mode, does this mean I'll be notified whenever there's an update & can choose to download & install?If so, will this show up in the "Action Center"? I don't know what all the options really do. I saw something about if I don't select or exclude (I can't remember which), it will install automatically. Is this true even if I've chosen to delay install, as I've shown below.

Again, I apologize for all the questions! I appreciate your time & expertise.

1. If you want no sfc errors, uninstall the script first. The reason for the errors is that the disabled files cannot be read from or written to until the script is uninstalled even during a major update like from 1709 to 1803. I included the command to check for script-caused sfc errors. But no, you don't have to uninstall the script first.

2. The Store won't work without the Windows Update Service running. You can, a) temporarily enable it to use the store, then disable it, or b) leave it running (enabled) all the time. I use option "a" but like it says you at least have a choice. No matter what you choose, enabled or disabled, it'll stay that way permanently until you change it with the script.

3. A future update can reinstall the Update Assistant. That's why you should run the script again after any updates to the first screen (Configurator), then just close the window.

4. "E" enables the Windows Update Service. "D" disables it. You will never be notified of updates using this script because it never checks on its own which is the whole point of the script. Pressing "C" continues the script to the info screen and then runs WUMT.

5. The Configurator allows you to enable or disable the windows update service. That's all it does. And yes, you have to run the script every time you want to check for updates because you will never be notified.
Hidden updates can unhide themselves. That doesn't happen often but if it does you can just re-hide them again.
Your hidden updates are in the hidden updates button in WUMT. You can hide or unhide them all you want as many times as you want.
I assume by recycle button you mean the refresh button. If you select an update and click the refresh button it'll just show the same update(s) again. Refreshing just checks for updates.

6. I've never heard of the "invalid data type" WUMT error. I would uninstall the script and run the windows update troubleshooter. It sounds like a corrupted update or catroot folder unrelated to the script.

7. Don't change any of the settings in the lower left of WUMT while using the script. Setting it to notify, automatic, etc. will do nothing. And nothing, not even drivers, can automatically install while using the script except for windows defender updates. And if windows defender is disabled it won't even do that.

I hope that answered your questions. Let me know if you have any more.
Also, for some reason my email notifications of responses to this thread sometimes takes 3 days or more to notify me.

pf100 said:

v2.5.2 permanently disables osrss until you uninstall the script. Don't use WUB v1.1 with this script because if you do you need to "enable" with v1.1, then never use it again with this script. The whole premise of WUB v1.1 makes no sense to me. It disables more things than v1.0, but the things it disables are completely unnecessary. Why would you disable a lot of services and then when you want to check for updates you turn all that stuff back on again? I told the author of WUB as much and received no answer.

Thank you so much for your excellent response. I don't know what WUB is, but what do you do to avoid using it with this script?

pf100 said:

4. "E" enables the Windows Update Service. "D" disables it. You will never be notified of updates using this script because it never checks on its own which is the whole point of the script. Pressing "C" continues the script to the info screen and then runs WUMT. 5. The Configurator allows you to enable or disable the windows update service. That's all it does. And yes, you have to run the script every time you want to check for updates because you will never be notified.

If I run the script twice, the first time pressing C & then making choices & then run it again & choose "E", will WU now be enabled again...i.e. it will run automatically to notify me of updates, & then I can run WUMT again to hide those updates that I don't want?

pf100 said:

I assume by recycle button you mean the refresh button. If you select an update and click the refresh button it'll just show the same update(s) again. Refreshing just checks for updates.

I don't have the script running right now, but the icon looked like a trash can, not a refresh button.

pf100 said:

6. I've never heard of the "invalid data type" WUMT error. I would uninstall the script and run the windows update troubleshooter. It sounds like a corrupted update or catroot folder unrelated to the script.

Thank you. I've done that, but it only shows there's a pending update (that I hid with the WUshowhide.diacab.)

pf100 said:

7. Don't change any of the settings in the lower left of WUMT while using the script. Setting it to notify, automatic, etc. will do nothing. And nothing, not even drivers, can automatically install while using the script except for windows defender updates. And if windows defender is disabled it won't even do that.

What are those options for then? Thank you again for all your time & work!

Thank you so much @pf100 for your complete explanation. I have a much better understanding of how to use WUMT!

Yes I am looking to fill disable and most likely never enable updates ever again lol. We control around 3k machines for customers for specific needs and windows keeps breaking then due to them replacing custom drivers and programs installed.

pf100 said:

v2.5.2 permanently disables osrss until you uninstall the script. Don't use WUB v1.1 with this script because if you do you need to "enable" with v1.1, then never use it again with this script. The whole premise of WUB v1.1 makes no sense to me. It disables more things than v1.0, but the things it disables are completely unnecessary. Why would you disable a lot of services and then when you want to check for updates you turn all that stuff back on again? I told the author of WUB as much and received no answer.


1. If you want no sfc errors, uninstall the script first. The reason for the errors is that the disabled files cannot be read from or written to until the script is uninstalled even during a major update like from 1709 to 1803. I included the command to check for script-caused sfc errors. But no, you don't have to uninstall the script first.

2. The Store won't work without the Windows Update Service running. You can, a) temporarily enable it to use the store, then disable it, or b) leave it running (enabled) all the time. I use option "a" but like it says you at least have a choice. No matter what you choose, enabled or disabled, it'll stay that way permanently until you change it with the script.

3. A future update can reinstall the Update Assistant. That's why you should run the script again after any updates to the first screen (Configurator), then just close the window.

4. "E" enables the Windows Update Service. "D" disables it. You will never be notified of updates using this script because it never checks on its own which is the whole point of the script. Pressing "C" continues the script to the info screen and then runs WUMT.

5. The Configurator allows you to enable or disable the windows update service. That's all it does. And yes, you have to run the script every time you want to check for updates because you will never be notified.
Hidden updates can unhide themselves. That doesn't happen often but if it does you can just re-hide them again.
Your hidden updates are in the hidden updates button in WUMT. You can hide or unhide them all you want as many times as you want.
I assume by recycle button you mean the refresh button. If you select an update and click the refresh button it'll just show the same update(s) again. Refreshing just checks for updates.

6. I've never heard of the "invalid data type" WUMT error. I would uninstall the script and run the windows update troubleshooter. It sounds like a corrupted update or catroot folder unrelated to the script.

7. Don't change any of the settings in the lower left of WUMT while using the script. Setting it to notify, automatic, etc. will do nothing. And nothing, not even drivers, can automatically install while using the script except for windows defender updates. And if windows defender is disabled it won't even do that.

I hope that answered your questions. Let me know if you have any more.
Also, for some reason my email notifications of responses to this thread sometimes takes 3 days or more to notify me.