WSUSUpdateAdmin wrote:Hi.
boco wrote:[...]
- Set Windows Update to "Never search for updates". This is NOT the same as disabling the Update service, don't do that!
- Reboot (or restart - NOT disable - the WU service)
[...]
Exactly this is what should have been done automatically by the installation routine (see ":AdjustWUSvc" in "DoUpdate.cmd").
The implementation manipulated two registry values under "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU", according to
Microsoft's documentation.
However, this was obviously insufficient for several systems, so I took a look inside a freshly installed W7 and found out that the Control Panel GUI switched "AUOptions" under "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" instead of the documented values above, so I now added this.
Cheers,
Torsten
The problem with this is that the behavior has been changed by MS (with the latest WUClients, I suppose). Now Windows Update is "Never search for updates" only if BOTH of the following conditions are met:
1. NoAutoUpdate must be 1, AND
2. The AUOptions value must be deleted completely.
The old behavior was, indeed, controlled by AUOptions, entirely. AUOptions=1, to be exact, which now doesn't exist anymore.
_____
moconnell wrote:I apologize, but I too am stuck here. I initially had Windows Update set to never run before I even attempted to run WSUSOU, yet I let it run almost 36 hours over the weekend and nothing happened. I am a little torn as to what to do at this point, as some people above are saying they disabled wuauserv service completely after starting the updateinstaller, but then an admin is saying to absolutely NOT do that a few posts later, only restart the service. I am going on 4 days working on this and am starting to panic, as I have never had an issue with this before. I am wondering what the reasoning behind even needing the wuauserv running if the offline installer is doing all the updates on its own anyways? Thanks for any feedback, this is really frustrating when I don't have a WSUS server available to me, and this has always worked in the past.
*EDIT*
I can confirm that running an elevated command prompt and using the 'net stop wuauserv' (no quotes) command, AFTER the initial updateinstaller executable has started. It took 10 minutes or so, but then all of a sudden the updates started running and are still going strong. I am just impatient, sorry.
While CAB-based updates install using the DISM (servicing) utility and do not need wuauserv, the MSU-based updates install using WUSA, which needs wuauserv.
Essentially, there are two issues disabling or stopping the service:
1. MSU-based install will restart the service, or, if disabled, fail.
2. Stopping the service mid-term will abort the scan and some required updates might not be detected and thus skipped.