|
|
Hating Microsoft After Update Breaks My Computer With svchost.exe Error
I'm three hours into a marathon session of trying to get my computer to work again the way it used to before Microsoft shoved a ton of security updates at me. System Restore, my old trusty friend, hasn't been able to help. That makes me think Microsoft has done some things to override how System Restore is supposed to work. If so, you suck, Microsoft -- you suck big time.
Last Friday, I installed Internet Explorer 7. I had it on my system once several months ago, just to see how it works. I'm a dedicated Firefox user, so IE is more a curiosity for me. I removed it because one particular site I wanted to access required IE6 -- and IE7 wouldn't work with it. I put IE7 back on because of the mandatory upgrade that's supposed to happen later this month. I dislike the idea that Microsoft, among other things, hopes to shore up it search share by shoving IE7 at people. The search integration is tighter in IE7, and some assume this will generate more queries for Microsoft. Since it's coming, I need to look at IE7 more closely. My system was working fine on Sunday, when I next used it. But when I shut down, I was informed that I had updates ready for install. Usually, I review and approve these. In this case, I couldn't get that option to work. I might be wrong, but it seemed as if I had no choice but to take these updates. The computer flashed a message that it was installing update 1 of 15. Then it sat like that for the next 1/2 hour. I pondered leaving it to waste electricity all night long but concluded the update procedure must have had a problem. I shut it off. This morning, I booted up and soon received this message:
The system then hung. I rebooted, several times, and eventually the system let me work for about an hour or so before the message came up and froze things once again. Fine. Time for System Restore (you'll find it at Start, Accessories, System Tools). System Restore is awesome. It has saved me time and again in these situations. Windows automatically saves various "checkpoints" for you over time. If your system breaks, you can go back to an earlier checkpoint before whatever caused an error. It has worked flawlessly for me four or five times to get my up and running quickly. It largely restored my faith in Windows as an operating system. This time, System Restore didn't help. I went back a day, a week, two weeks. No matter what, I kept getting the error. Further more, I noticed the Internet Explorer was reporting itself as if it was IE7 rather than IE6, if System Restore was working properly. I can only conclude that either IE7 or the updates messed up my system. In either case, something made changes so permanent that it overrode the protection System Restore is supposed to provide. And that's ticked me off immensely. I'm doing this post up on my laptop while I've been working a solution to the svchost.exe error hitting my desktop. I found that here: Windows Update Broke My Machine (svchost.exe -- application error), and How to Fix It. So far, Scott Swigart's solution seems to have worked. The desktop seems stable, so I'm going back on to it. Then eventually, I let Windows install each of the updates one by one selective, to see if the system doesn't crash. Joy. Note that Scott suggests the error isn't happening because a particular update overrides System Restore. Instead, he thinks the update procedure itself sometimes goes wonky, causing trouble. Still, that's something System Restore ought to take care of. By Danny Sullivan on Oct. 16, 2006 | PermalinkSee related posts in: Computers, Rants
Next Post: Google Logos At Google Kirklandplex Comments Comment by SearchRank SearchRank: Yes, because having an OS full of security holes is preferable to having to do a little debugging. "Working fine" is great until your systems are compromised maybe isn't so great after all. Comment by amped Hey Danny, were you able to get everything patched ok this time around? I've seen this sort of thing before on my son's computer, I didn't want to call MS either (that is just a pain) luckily he doesn't have any data on there so I re-formatted and started from scratch. If you do find the culprit let the rest of us know!! Comment by Josh Maher M.O updates sometimes do alot more harm than good, I updated mine on a Friday came in on Monday and there it was svchost.exe - Application Error : The instruction at "0x745f2780" referenced memory at "0x00000000". The memory could not be "read". I did a system restore worked for a few weeks and had to reformat my PC at the end of it all. What can we do re these updates, you just don't know if you will be affected. Comment by gennsearch | October 16, 2006 9:09 PM So far, that procedure that Scott Swigart covered (link above in story) has been solid. I've been up and running all day. I really suggest anyone having this issue try it. Comment by Danny Sullivan Danny, I would like to say I have had similar problems but I haven't. I have a Mac. I have it to stay away from M$ and that particular kind of problem/s. Sorry to hear you are so frustrated. What is a .exe file any way? Comment by garypool I've been in the same boat. I always keep updates set to prompt me before downloading and installing, because I'm often on a slow connection or don't want my computer to start a reboot in the middle of a presentation (MS will do an automatic restart after some updates - you have to be watching the screen to cancel it) Twice now, 'some' update has reset the settings to automatically download, install and reboot, causing me to lose unsaved work and then causing problems with the laptop. Not happy, not happy at all. Comment by Joining Dots | October 17, 2006 9:38 AM Quote "The computer flashed a message that it was installing update 1 of 15. Then it sat like that for the next 1/2 hour. I pondered leaving it to waste electricity all night long but concluded the update procedure must have had a problem. I shut it off." --> Why do you blame Microsoft? I would assume that one should know that it might not be the best idea to turn off a computer while in the middle of an update scenario. Seriously! When changing the tires of your car yould you consider it to be smart to kick the car-jack away simply because dinner is ready??? It's always easy to blame somebody else! Think about! Comment by Hans | October 17, 2006 10:44 AM Hans, after a half hour, the update had shown no progress. It hadn't moved to step 2 at all. That's unusual. It's a sign that the update wasn't happening but instead that the computer froze. It's sort of like putting that new tire on, lowering the car and discovering the tire is flat anyway. Shutting off a computer before the operating system itself has closed is always a dangerous move, so I gave it a hard think before doing so. I did it in the end only because I was very confident something was wrong with the update situation. Comment by Danny Sullivan Have you considered moving to the other side? Comment by grnidone David Weinberger put it well a few days ago: "Unless Mac hardware never fails, please do not tell me to get a Mac. Thank you." Meanwhile, Dave Winer's struggles with his Macbook have gone on so long that I'm to the point of unsubscribing from his feed, I'm so tired of hearing about it. But his saga underscores that it's all not happy Mac, either. Whatever the platform, we all just want our systems to work. Honestly, I'd move to Ubuntu if I thought that would give me stability. But I suspect it would give me a host of other problems. Windows is far, far from perfect -- but I know what I'm getting with it, and XP has been so, so much better than any version that came before it. Comment by Danny Sullivan If you have a SP2 update CD, you could simply reinstall SP2. That should fix any corrupted files. Some say you'll need to d/l all MS security installs etc but I've never had to do that. Comment by Super Des It's really going to be funny to watch the chaos if Microsoft actually makes this an automatic update. There are SO many sites out there that will just flat break. Microsoft is going to take a lot of heat over this if it happens. Comment by Scott Johnson Hmm - few people moaning here about Windows Update causing their desktop machine to fail. Sounds bad, but wait until it brings down your Windows 2003 server and you get to explain, one by one, to each employee of the company, why you are frantically wiring them to a direct net connection so they can get at least some work done, and slowly & carefully explaining how they can read their emails through a web browser because Exchange aint where it should be today. Then, and only then, shall you know true hatred of the upadte mechanism and it's devilish plans for your day. Comment by taekwondo | October 28, 2006 2:45 AM Danny, you're displaying a pretty poor quality of thinking in your earlier comment. To recap: Comment by Scramblejams | November 6, 2006 5:43 AM > Implicit in your response is the notion that Apple hardware is somehow so much less reliable than whatever your PC brand of choice is that Macs are unworthy of the slightest consideration. Not at all. Macs are certainly worth consideration. I'm simply saying that I don't expect that a Mac experience is going to be a flawless one, whether it's a hardware or software problem. For the most part, Windows XP has worked very, very well for me. System Restore has been absolutely wonderful for getting out of the occasional problem. I like Windows. I want Windows to be better, and this was a serious issue. I'd rather Windows solve it instead of me having to switch to an entire new platform. I'm not there yet :) Also, as a postscript, I've since applied all the updates and IE7. The problem hasn't come back and seems to have been specific not to the updates or IE7 but a glitch with the actual update process. Comment by Danny Sullivan Want to comment? If you are signed into TypeKey, you'll see a form below. No form? Click on the sign-in link below, and you can sign-in or sign-up for a free account. Sorry you have to use TypeKey, but I use it to avoid comment spam. All comments currently appear automatically after posting.
|
Subscribe! Search
|
That is the very reason why I haven't done an update on any of my computers for.... I don't know how long now. Update a computer that is working fine only to have it break. Microsoft is quite famous for that.