New
#11
" I opened regedit.exe and located: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Update Orchestrator\Scheduled Scan and backed up that key, then deleted and reboot."
That did the job, WU does not run in the background while pc boots and no errors or side-effects to report.
Thank you all.
Cheers,
I directly copied some of your code to use in my script, so yes. I was already inspired, but you showed me the way of instead of disabling tasks in a script, disable the related files instead so the tasks can't run. Far easier and far more reliable to implement and to be able to exactly reverse the changes, leaving no trace that any change ever took place, except for the event log of failed tasks. The chance of an update installing a new update forcer file and/or task is high; the difference is that the task will run soon if it hasn't already, before the dll or whatever, runs on it's own with no trigger, but the trigger from the task is more likely to fail if part of the waasmedic subsystem is still mostly disabled, giving me time to update the script with no ill effects. As time goes by, each failed forced update task makes me smile. I'm now truly free to update when I deem fit and hide the ones I don't want. That is, as long as I keep track of this exe/dll shell game, for example: 1803 has added waasmedic components ( specifically, MSFT removed one file and replaced it with 1 to 3 others depending on your build) , so now the list of update forcers including 1803 and earlier is: UsoClient.exe, WaaSMedic.exe(removed in 1803, now WaaSMedic uses only dll's, still disabled in script if it exists), WaasMedicSvc.dll, WaaSMedicPS.dll, WaaSAssessment.dll, and SIHClient.exe, Windows10UpgraderApp.exe (uninstall it with script), and whatever file is in X:\Windows\UpdateAssistantV2 that I delete and remove the folder which starts the whole Windows 10 Upgrade installer process shenanigans. I only delete files and folders when no other possible solution is found, never recklessly.
The script is a concept that's working better than I'd dreamed when I first started this, considering it's easily adaptable to all the changes Windows 10 is going through.
@muchomurka I always add-accepteula
so I don't get the EULA accept popup window. That only happens once. And here were are on the local system, so we'll see it and be able to click on it. But if we're doingpsexec
to a remote system, and we're re-invoking pstools on that system, and it's the first time any pstool is run there, then that GUI accept window can be a show-stopper.
I elaborated on your answer in a related, linked post: In Windows 10 v1709 how do I get Task Scheduler Credentials to work?
Good remark for remote systems.I always add -accepteula
Hasn't anyone discovered the hosts (or IPs) used by Windows update so that they can be blocked at the firewall ???
I've been waiting for that for years.
Yes, basically if you disable port 80 for HTTP and port 443 for HTTPS then Windows Update will probably not work. But the problem is this will disable access to your other websites or online gaming servers that require these ports.
The best thing to use is Windows Update Blocker tool. Windows Update Blocker v1.2
I can basically confirm that this tool does block Windows Update from starting up and will remain disabled. Windows will not be able to start-up this service on its own using scheduled task. You don't have to disable the task scheduler anymore as this tool with a click of a button will do all of that including the Updated Orchestrator service. And when you want to re-enable it to update you can click again inside the tool, restart the PC and Windows update will work again.
Obviously if it wasn't for this tool, I would've dumped Windows 10 by now. But it is only because of the Windows Update Blocker tool that I am still able to use this problematic operating system.
That code is run in an elevated command prompt or a batch file run as admin.
It removes permissions from the usoclient.exe file so that the Task scheduler task in question fails when it tries to use that file. The result is that scheduled checks for updates do not run. WU can still be run manually when desired.
The code / batch file normally needs to be run again after each Version update i.e. twice a year.
Denis