166718 messages in 18187 discussions
Latest 10/22/03 by [PC][Ch]amsalot (CHAMSALOT)
64590 messages in 4081 discussions
Latest Jul-21 by williams11
11370 messages in 1241 discussions
Latest Jul-17 by xSomeguyx
173546 messages in 18422 discussions
Latest Jul-8 by MEDDLY
Latest Jul-6 by gofer303(Windancer) (gofer303)
54195 messages in 4609 discussions
Latest Jul-28 by Buck Dharwin (Byff1)
Latest Jul-25 by Victor Varela (VictorVarela)
Latest Jul-10 by JustJudy (JUDYSCAMERON)
83238 messages in 7356 discussions
Latest Jul-31 by boxingguy
1040217 messages in 32512 discussions
Latest Jul-24 by [PC][Ch]amsalot (CHAMSALOT)
I think I got it started again. Cleared the registry entries except for the basic entries.
Also, ZA would have definitely affected it. I had a custom rule for svchost.exe that would only allow it to access my DNS servers for DNS.
Made sure to stop the AU service.
Then, got rid of extra registry entries in the AutoUpdates:
Kept AUOptions (set to 3)
Changed AUState (from 7 to 2)
Kept ODFFile Url.
Deleted anything else
Then, went into Control Panel and set AutoUpdates to Automatically Download and then notifiy me.
So far it connected yesterday after the fix and once today. I have ZA set to notify me when svchost wants to connect. Each time it did, the Windows_Update.log file was updated at that time, so it's working.
It runs as a service.