Alright.. this is just ridiculous....
I just spent half a day of work fixing Windows on my work computer, which Windows Update broke. Apparently, somewhere along the line, the automatic update got some corrupted install files. Every time I started up my computer, it attempts to run itself, then crashes svchost.exe with some memory error.
If you looked into your task manager, you'll probably see several entries by svchost.exe. This is a process that Windows uses to execute DLL's, thus an integral process of the system that just can't be allowed to fail by any extent. After my svchost.exe took a dump (and not all of them, just one of the many processes), my XP-styled UI disappeared, reverting back to "classic style". I couldn't run certain applications, Internet Explorer hung & crashed, and I could not access any networked drives.
The solution was, to turn off automatic Windows Update completely. Reboot the computer so it no longer tries to run the Windows Update process. Then manually go to the Windows Update site to get my updates. After wasting a few hours figuring out what's going on, and fixing it... now my computer is up and running again. Still, isn't this the type of thing that should *never* happen with an automatic update process? Now I'm leaving my automatic update off permanently to prevent any future occurrences of this issue.
Wednesday, December 20, 2006
Windows Update broke my Windows
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment