Excerpt from Windows 7 News

[Gloria E]

One Register reader, who has seen the errors appear on 15 machines had this to say:

"Basically, if you have an OEM machine connected to a server running WSUS [Windows Server Update Services] with the default settings it offers and installs SP1 automatically. This is killing machines and stopping them booting with a C00000034 fatal error

He also adds that Windows 7 SP1 deletes all restore points on your machine just before it begins to install, so you have no recovery points."

Some users have also reported falling into a reboot loop and encounter the error message Error C000009A applying update operation 120782 of 367890

The Microsoft forums and message boards have plenty to report on these issues which you can see here and here

Despite all these complaints, Microsoft still hadn’t figured out where it all went wrong until a couple of days ago. They’ve since issued a fix which will hopefully solve the error code 0xc0000034

Microsoft really wants to be careful with this situation. They really should have tested Windows 7 SP1 in all situations to make sure nothing like this would have occurred. I feel they may have been rushing it out and that could have caused some of these slip ups. There’s no point in rushing out a first service pack if it’s just going to cause trouble, but I believe that reports like this can often be blown out of proportion somewhat.
--------------------------------------------------------------------------------------------------------------------------

Someone may find this very helpful.

Gloria E

[JoeP]

WSUS is a Windows Server product to help with patch management and distribution in a small business. Seems as though a business has rolled out the same PCs with the same setup and therefore has the same problem. When there is a problem it is not unusual for it to appear in a situation where the same hardware & software are deployed.

Did the author provide a link to the Microsoft fix?

Writing something such as "They really should have tested Windows 7 SP1 in all situations to make sure nothing like this would have occurred" is idiotic. There is absolutely no way that Microsoft or any other vendor in the PC world can test all situations. There are just too many combinations of hardware and software.

With Windows 7 having sold somethine like 300,000,000 copies a 1% error rate in SP1 installs result in 3,000,000 failures. That is a big number but still very small compared to the sucessful updates.

Joe

[tedshemyers]

I have to agree with Joe. If a person or company has a successful install of SP1 they do not say anything about it. The only time you hear of anything is if something went wrong. Sorry, but a failure rate of less than 1% is fantastic. In fact many of the problems are related to additional apps running in the background causing conflicts with the installation. MS does say all running apps should be closed, including any AV or AM app (including MSE) during the update. I would be willing to bet most of those having a problem did not follow this advice.

[Gloria E]

WSUS is a Windows Server product to help with patch management and distribution in a small business. Seems as though a business has rolled out the same PCs with the same setup and therefore has the same problem. When there is a problem it is not unusual for it to appear in a situation where the same hardware & software are deployed.

Did the author provide a link to the Microsoft fix?

Writing something such as "They really should have tested Windows 7 SP1 in all situations to make sure nothing like this would have occurred" is idiotic. There is absolutely no way that Microsoft or any other vendor in the PC world can test all situations. There are just too many combinations of hardware and software.

With Windows 7 having sold somethine like 300,000,000 copies a 1% error rate in SP1 installs result in 3,000,000 failures. That is a big number but still very small compared to the sucessful updates.

Joe

Yes Joe and here it is:

http://blogs.technet.com/b/joscon/archi ... 00034.aspx" onclick="window.open(this.href);return false;

I hope the article and the fix will help someone.

Gloria E