System *Still* hangs when Automatic Updates is On

Ok, I installed WU 3.0 and ran the hotfix 927891. I set Auto Update to
“Automatic� and rebooted my system. I logged in, let the desktop come up
until everything loaded, and just like before, as soon as I try to launch any
application; the system hangs solid. I have to reboot into safe mode and
disable Auto Updates in order to keep my system form hanging. So what’s my
next step?

Thanks


"TaurArian" wrote:

> Please install the the WU 3.0 client and the associated hotfix - see article
> for links
>
> When you use Automatic Updates to scan for updates or to apply updates to
> applications that use Windows Installer, you experience issues that involve
> the Svchost.exe process
> http://support.microsoft.com:80/kb/932494
>
>
> "Mitch" wrote:
>
> > For that last two weeks I have been fighting this issue; I finally narrowed
> > it down to the Automatic Update service. If I have the Automatic Update
> > service enabled, my system will hang shortly after I log in. The only way to
> > use my system right now is to disable the Automatic Update service. Not sure
> > what caused this to happen; any and all help would be greatly appreciated!
> >
> > Thanks
> >

Mitch wrote:
> Ok, I installed WU 3.0 and ran the hotfix 927891. I set Auto Update
> to "Automatic" and rebooted my system. I logged in, let the desktop
> come up until everything loaded, and just like before, as soon as I
> try to launch any application; the system hangs solid. I have to
> reboot into safe mode and disable Auto Updates in order to keep my
> system form hanging. So what's my next step?

1) Reboot and logon as a user with Administrative Privs...
2) Immediately run the following batch script (You will have to create it by
cutting/pasting as directed.)

- Click Start, Run, type: notepad C:\register.bat and press Enter. Choose
Yes when you are prompted.
- Copy the following commands and then paste them into the opened Notepad
window:

regsvr32 comcat.dll /s
regsvr32 shdoc401.dll /s
regsvr32 shdoc401.dll /i /s
regsvr32 asctrls.ocx /s
regsvr32 oleaut32.dll /s
regsvr32 shdocvw.dll /I /s
regsvr32 shdocvw.dll /s
regsvr32 browseui.dll /s
regsvr32 browseui.dll /I /s
regsvr32 msrating.dll /s
regsvr32 mlang.dll /s
regsvr32 hlink.dll /s
regsvr32 mshtmled.dll /s
regsvr32 urlmon.dll /s
regsvr32 plugin.ocx /s
regsvr32 sendmail.dll /s
regsvr32 scrobj.dll /s
regsvr32 mmefxe.ocx /s
regsvr32 corpol.dll /s
regsvr32 jscript.dll /s
regsvr32 msxml.dll /s
regsvr32 imgutil.dll /s
regsvr32 thumbvw.dll /s
regsvr32 cryptext.dll /s
regsvr32 rsabase.dll /s
regsvr32 inseng.dll /s
regsvr32 iesetup.dll /i /s
regsvr32 cryptdlg.dll /s
regsvr32 actxprxy.dll /s
regsvr32 dispex.dll /s
regsvr32 occache.dll /s
regsvr32 occache.dll /i /s
regsvr32 iepeers.dll /s
regsvr32 urlmon.dll /i /s
regsvr32 cdfview.dll /s
regsvr32 webcheck.dll /s
regsvr32 mobsync.dll /s
regsvr32 pngfilt.dll /s
regsvr32 licmgr10.dll /s
regsvr32 icmfilter.dll /s
regsvr32 hhctrl.ocx /s
regsvr32 inetcfg.dll /s
regsvr32 tdc.ocx /s
regsvr32 MSR2C.DLL /s
regsvr32 msident.dll /s
regsvr32 msieftp.dll /s
regsvr32 xmsconf.ocx /s
regsvr32 ils.dll /s
regsvr32 msoeacct.dll /s
regsvr32 inetcomm.dll /s
regsvr32 msdxm.ocx /s
regsvr32 dxmasf.dll /s
regsvr32 l3codecx.ax /s
regsvr32 acelpdec.ax /s
regsvr32 mpg4ds32.ax /s
regsvr32 voxmsdec.ax /s
regsvr32 danim.dll /s
regsvr32 Daxctle.ocx /s
regsvr32 lmrt.dll /s
regsvr32 datime.dll /s
regsvr32 dxtrans.dll /s
regsvr32 dxtmsft.dll /s
regsvr32 WEBPOST.DLL /s
regsvr32 WPWIZDLL.DLL /s
regsvr32 POSTWPP.DLL /s
regsvr32 CRSWPP.DLL /s
regsvr32 FTPWPP.DLL /s
regsvr32 FPWPP.DLL /s
regsvr32 WUAPI.DLL /s
regsvr32 WUAUENG.DLL /s
regsvr32 ATL.DLL /s
regsvr32 WUCLTUI.DLL /s
regsvr32 WUPS.DLL /s
regsvr32 WUWEB.DLL /s
regsvr32 wshom.ocx /s
regsvr32 wshext.dll /s
regsvr32 vbscript.dll /s
regsvr32 scrrun.dll mstinit.exe /setup /s
regsvr32 msnsspc.dll /SspcCreateSspiReg /s
regsvr32 msapsspc.dll /SspcCreateSspiReg /s
regsvr32 /s urlmon.dll
regsvr32 /s mshtml.dll
regsvr32 /s shdocvw.dll
regsvr32 /s browseui.dll
regsvr32 /s jscript.dll
regsvr32 /s vbscript.dll
regsvr32 /s scrrun.dll
regsvr32 /s msxml.dll
regsvr32 /s actxprxy.dll
regsvr32 /s softpub.dll
regsvr32 /s wintrust.dll
regsvr32 /s dssenh.dll
regsvr32 /s rsaenh.dll
regsvr32 /s gpkcsp.dll
regsvr32 /s sccbase.dll
regsvr32 /s slbcsp.dll
regsvr32 /s cryptdlg.dll
regsvr32 /s schannel.dll
regsvr32 /s oleaut32.dll
regsvr32 /s ole32.dll
regsvr32 /s shell32.dll
regsvr32 /s initpki.dll
regsvr32 /s msscript.ocx
regsvr32 /s dispex.dll
regsvr32 jscript.dll /s
del %temp% /Q /F
net stop wuauserv
ren %windir%\system32\catroot2 catroot2.old
cd /d %windir%\SoftwareDistribution
rd /s DataStore /Q
regsvr32 wuapi.dll /s
regsvr32 wups.dll /s
regsvr32 wuaueng.dll /s
regsvr32 wucltui.dll /s
regsvr32 wuweb.dll /s
regsvr32 msxml.dll /s
regsvr32 msxml2.dll /s
regsvr32 msxml3.dll /s
regsvr32 urlmon.dll /s
net start wuauserv
exit

- After you paste the above commands, please close the Notepad window.
Choose Yes when you are prompted to save the file.
- Click Start, Run, type:
C:\register.bat and press Enter to run the commands I have pasted.
The Process may take sometime.

3) Download/Install Windows Update v3.
http://go.microsoft.com/fwlink/?LinkID=91237

4) Download/Install the 927891 patch.
http://www.microsoft.com/downloads/d...9-404327772E5A

5) Reboot.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Okay, I'm puzzled. Mitch is saying the "fix" for windows update freezing
didn't work, and so you're basically cleaning a bunch of stuff out of the
registry and suggesting he try again. What it is that you see that the other
MVP haven't?

(I have the same problem as Mitch...my workaround is to set my display to
640x480-256 colors and then the update will work. However, when I set the
display back to normal, update hangs again. Will your patch address this?)

"Shenan Stanley" wrote:

> Mitch wrote:
> > Ok, I installed WU 3.0 and ran the hotfix 927891. I set Auto Update
> > to "Automatic" and rebooted my system. I logged in, let the desktop
> > come up until everything loaded, and just like before, as soon as I
> > try to launch any application; the system hangs solid. I have to
> > reboot into safe mode and disable Auto Updates in order to keep my
> > system form hanging. So what's my next step?
>
> 1) Reboot and logon as a user with Administrative Privs...
> 2) Immediately run the following batch script (You will have to create it by
> cutting/pasting as directed.)
>
> - Click Start, Run, type: notepad C:\register.bat and press Enter. Choose
> Yes when you are prompted.
> - Copy the following commands and then paste them into the opened Notepad
> window:
>
> regsvr32 comcat.dll /s
> regsvr32 shdoc401.dll /s
> regsvr32 shdoc401.dll /i /s
> regsvr32 asctrls.ocx /s
> regsvr32 oleaut32.dll /s
> regsvr32 shdocvw.dll /I /s
> regsvr32 shdocvw.dll /s
> regsvr32 browseui.dll /s
> regsvr32 browseui.dll /I /s
> regsvr32 msrating.dll /s
> regsvr32 mlang.dll /s
> regsvr32 hlink.dll /s
> regsvr32 mshtmled.dll /s
> regsvr32 urlmon.dll /s
> regsvr32 plugin.ocx /s
> regsvr32 sendmail.dll /s
> regsvr32 scrobj.dll /s
> regsvr32 mmefxe.ocx /s
> regsvr32 corpol.dll /s
> regsvr32 jscript.dll /s
> regsvr32 msxml.dll /s
> regsvr32 imgutil.dll /s
> regsvr32 thumbvw.dll /s
> regsvr32 cryptext.dll /s
> regsvr32 rsabase.dll /s
> regsvr32 inseng.dll /s
> regsvr32 iesetup.dll /i /s
> regsvr32 cryptdlg.dll /s
> regsvr32 actxprxy.dll /s
> regsvr32 dispex.dll /s
> regsvr32 occache.dll /s
> regsvr32 occache.dll /i /s
> regsvr32 iepeers.dll /s
> regsvr32 urlmon.dll /i /s
> regsvr32 cdfview.dll /s
> regsvr32 webcheck.dll /s
> regsvr32 mobsync.dll /s
> regsvr32 pngfilt.dll /s
> regsvr32 licmgr10.dll /s
> regsvr32 icmfilter.dll /s
> regsvr32 hhctrl.ocx /s
> regsvr32 inetcfg.dll /s
> regsvr32 tdc.ocx /s
> regsvr32 MSR2C.DLL /s
> regsvr32 msident.dll /s
> regsvr32 msieftp.dll /s
> regsvr32 xmsconf.ocx /s
> regsvr32 ils.dll /s
> regsvr32 msoeacct.dll /s
> regsvr32 inetcomm.dll /s
> regsvr32 msdxm.ocx /s
> regsvr32 dxmasf.dll /s
> regsvr32 l3codecx.ax /s
> regsvr32 acelpdec.ax /s
> regsvr32 mpg4ds32.ax /s
> regsvr32 voxmsdec.ax /s
> regsvr32 danim.dll /s
> regsvr32 Daxctle.ocx /s
> regsvr32 lmrt.dll /s
> regsvr32 datime.dll /s
> regsvr32 dxtrans.dll /s
> regsvr32 dxtmsft.dll /s
> regsvr32 WEBPOST.DLL /s
> regsvr32 WPWIZDLL.DLL /s
> regsvr32 POSTWPP.DLL /s
> regsvr32 CRSWPP.DLL /s
> regsvr32 FTPWPP.DLL /s
> regsvr32 FPWPP.DLL /s
> regsvr32 WUAPI.DLL /s
> regsvr32 WUAUENG.DLL /s
> regsvr32 ATL.DLL /s
> regsvr32 WUCLTUI.DLL /s
> regsvr32 WUPS.DLL /s
> regsvr32 WUWEB.DLL /s
> regsvr32 wshom.ocx /s
> regsvr32 wshext.dll /s
> regsvr32 vbscript.dll /s
> regsvr32 scrrun.dll mstinit.exe /setup /s
> regsvr32 msnsspc.dll /SspcCreateSspiReg /s
> regsvr32 msapsspc.dll /SspcCreateSspiReg /s
> regsvr32 /s urlmon.dll
> regsvr32 /s mshtml.dll
> regsvr32 /s shdocvw.dll
> regsvr32 /s browseui.dll
> regsvr32 /s jscript.dll
> regsvr32 /s vbscript.dll
> regsvr32 /s scrrun.dll
> regsvr32 /s msxml.dll
> regsvr32 /s actxprxy.dll
> regsvr32 /s softpub.dll
> regsvr32 /s wintrust.dll
> regsvr32 /s dssenh.dll
> regsvr32 /s rsaenh.dll
> regsvr32 /s gpkcsp.dll
> regsvr32 /s sccbase.dll
> regsvr32 /s slbcsp.dll
> regsvr32 /s cryptdlg.dll
> regsvr32 /s schannel.dll
> regsvr32 /s oleaut32.dll
> regsvr32 /s ole32.dll
> regsvr32 /s shell32.dll
> regsvr32 /s initpki.dll
> regsvr32 /s msscript.ocx
> regsvr32 /s dispex.dll
> regsvr32 jscript.dll /s
> del %temp% /Q /F
> net stop wuauserv
> ren %windir%\system32\catroot2 catroot2.old
> cd /d %windir%\SoftwareDistribution
> rd /s DataStore /Q
> regsvr32 wuapi.dll /s
> regsvr32 wups.dll /s
> regsvr32 wuaueng.dll /s
> regsvr32 wucltui.dll /s
> regsvr32 wuweb.dll /s
> regsvr32 msxml.dll /s
> regsvr32 msxml2.dll /s
> regsvr32 msxml3.dll /s
> regsvr32 urlmon.dll /s
> net start wuauserv
> exit
>
> - After you paste the above commands, please close the Notepad window.
> Choose Yes when you are prompted to save the file.
> - Click Start, Run, type:
> C:\register.bat and press Enter to run the commands I have pasted.
> The Process may take sometime.
>
> 3) Download/Install Windows Update v3.
> http://go.microsoft.com/fwlink/?LinkID=91237
>
> 4) Download/Install the 927891 patch.
> http://www.microsoft.com/downloads/d...9-404327772E5A
>
> 5) Reboot.
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>
>

OriginalGorrilla wrote:
> Okay, I'm puzzled. Mitch is saying the "fix" for windows update
> freezing didn't work, and so you're basically cleaning a bunch of
> stuff out of the registry and suggesting he try again. What it is
> that you see that the other MVP haven't?
>
> (I have the same problem as Mitch...my workaround is to set my
> display to 640x480-256 colors and then the update will work.
> However, when I set the display back to normal, update hangs again.
> Will your patch address this?)

Re-registering the DLLs, clearing out the old software distribution/patch
directories and stopping/starting the service makes sure that everything
needed to run the Windows Updates services are presented and accounted for
and 'like new'. Installing the lastest Windows Update executable insures
that things wrong with the old version (known issues) have been resolved and
the final patch fixes specific issues with Windows Update in relation to
SVCHOST.EXE.

I *see* nothing that the other MVP hasn't - it is experience with doing
things the way I laid out vs. just applying the patch and/or the update and
then the patch...

Previously when there were problems with the update services - I would run
the batch script I laid out. That would fix it completely in some cases -
only partially (it would come back again some time later - sometimes a
month - sometimes many months) in other cases.

Then they came out with a newer version of the Windows Update client and the
932494 patch. I had similar experiences when trying just one or both of
those. Sometimes the problem would go away - sometimes it would not.
However - I have yet to have the problem *not* go away if I did things as I
laid out in the post you are discussing - if done in that order.

There's something to be said for starting out with a clean house in order to
keep a clean house - and essentially - that is what you are doing if you
follow the steps I laid out. Making sure everything is cleaned up/available
and then updating the software and patching.

You have nothing to lose but 20 minutes trying it. Seems like changing your
resolution should do nothing - what do you know that the rest of us don't?

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Understood. I'll give the clean sweep approach a try.

I've got another thread going that talks about my workaround. The replies
so far point out that my system with its onboard Intel 82810e display
controller actually shares ram with the CPU. It was mentioned that by
dropping the resolution back to 640x480, the display is using a minimum
amount. Okay, I'll buy that. But, I'm still wondering if the update agent
hasn't got a memory leak or a pointer problem when its loaded higher than
some memory limit. The machine I'm having trouble with originally had
128meg...the difficulties only started when I bumped it to 512meg.

"Shenan Stanley" wrote:

> OriginalGorrilla wrote:
> > Okay, I'm puzzled. Mitch is saying the "fix" for windows update
> > freezing didn't work, and so you're basically cleaning a bunch of
> > stuff out of the registry and suggesting he try again. What it is
> > that you see that the other MVP haven't?
> >
> > (I have the same problem as Mitch...my workaround is to set my
> > display to 640x480-256 colors and then the update will work.
> > However, when I set the display back to normal, update hangs again.
> > Will your patch address this?)
>
> Re-registering the DLLs, clearing out the old software distribution/patch
> directories and stopping/starting the service makes sure that everything
> needed to run the Windows Updates services are presented and accounted for
> and 'like new'. Installing the lastest Windows Update executable insures
> that things wrong with the old version (known issues) have been resolved and
> the final patch fixes specific issues with Windows Update in relation to
> SVCHOST.EXE.
>
> I *see* nothing that the other MVP hasn't - it is experience with doing
> things the way I laid out vs. just applying the patch and/or the update and
> then the patch...
>
> Previously when there were problems with the update services - I would run
> the batch script I laid out. That would fix it completely in some cases -
> only partially (it would come back again some time later - sometimes a
> month - sometimes many months) in other cases.
>
> Then they came out with a newer version of the Windows Update client and the
> 932494 patch. I had similar experiences when trying just one or both of
> those. Sometimes the problem would go away - sometimes it would not.
> However - I have yet to have the problem *not* go away if I did things as I
> laid out in the post you are discussing - if done in that order.
>
> There's something to be said for starting out with a clean house in order to
> keep a clean house - and essentially - that is what you are doing if you
> follow the steps I laid out. Making sure everything is cleaned up/available
> and then updating the software and patching.
>
> You have nothing to lose but 20 minutes trying it. Seems like changing your
> resolution should do nothing - what do you know that the rest of us don't?
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>
>

Okay, ran the register.bat file, did the downloads...same results. Windows
update freezes on the scrolling green bar screen. Reset video adapter to
640x480 - 256 colors and it works. I'm thinking that in addition to gobbling
up cpu cycles, that svchost guy is spraying itself all over memory...

"OriginalGorrilla" wrote:

> Understood. I'll give the clean sweep approach a try.
>
> I've got another thread going that talks about my workaround. The replies
> so far point out that my system with its onboard Intel 82810e display
> controller actually shares ram with the CPU. It was mentioned that by
> dropping the resolution back to 640x480, the display is using a minimum
> amount. Okay, I'll buy that. But, I'm still wondering if the update agent
> hasn't got a memory leak or a pointer problem when its loaded higher than
> some memory limit. The machine I'm having trouble with originally had
> 128meg...the difficulties only started when I bumped it to 512meg.
>
> "Shenan Stanley" wrote:
>
> > OriginalGorrilla wrote:
> > > Okay, I'm puzzled. Mitch is saying the "fix" for windows update
> > > freezing didn't work, and so you're basically cleaning a bunch of
> > > stuff out of the registry and suggesting he try again. What it is
> > > that you see that the other MVP haven't?
> > >
> > > (I have the same problem as Mitch...my workaround is to set my
> > > display to 640x480-256 colors and then the update will work.
> > > However, when I set the display back to normal, update hangs again.
> > > Will your patch address this?)
> >
> > Re-registering the DLLs, clearing out the old software distribution/patch
> > directories and stopping/starting the service makes sure that everything
> > needed to run the Windows Updates services are presented and accounted for
> > and 'like new'. Installing the lastest Windows Update executable insures
> > that things wrong with the old version (known issues) have been resolved and
> > the final patch fixes specific issues with Windows Update in relation to
> > SVCHOST.EXE.
> >
> > I *see* nothing that the other MVP hasn't - it is experience with doing
> > things the way I laid out vs. just applying the patch and/or the update and
> > then the patch...
> >
> > Previously when there were problems with the update services - I would run
> > the batch script I laid out. That would fix it completely in some cases -
> > only partially (it would come back again some time later - sometimes a
> > month - sometimes many months) in other cases.
> >
> > Then they came out with a newer version of the Windows Update client and the
> > 932494 patch. I had similar experiences when trying just one or both of
> > those. Sometimes the problem would go away - sometimes it would not.
> > However - I have yet to have the problem *not* go away if I did things as I
> > laid out in the post you are discussing - if done in that order.
> >
> > There's something to be said for starting out with a clean house in order to
> > keep a clean house - and essentially - that is what you are doing if you
> > follow the steps I laid out. Making sure everything is cleaned up/available
> > and then updating the software and patching.
> >
> > You have nothing to lose but 20 minutes trying it. Seems like changing your
> > resolution should do nothing - what do you know that the rest of us don't?
> >
> > --
> > Shenan Stanley
> > MS-MVP
> > --
> > How To Ask Questions The Smart Way
> > http://www.catb.org/~esr/faqs/smart-questions.html
> >
> >
> >