Recieve a BSOD after KB2859537.

Not without exact images of the systems to understand what's going on.  "English" - the first person in this thread is the reason why we have info on those registry key problems.  They only repro'd once they got his complete machine to fully understand the issue.  They didn't repro at will.  They needed  - what I refer to - as a "crusty" box as it was not in the plain RTM code of Windows that this occurs.

Beleive me I understand, but I don't want people to blow these issues out of proportion.  The Office updates this month we had repros coming out of our ears.   These issues are not comparable in magnitude.

Thanks Susan.

I do understand your points, and the risks of not patching. I generally wait a few weeks after the monthly updates are released before installing the updates (to allow Microsoft to find and fix bugs ... it seems that lately the monthly updates are initially buggy and have to be recalled and fixed ... Microsoft is not inspiring confidence in their quality).

I've had BSODs that have taken the good part of a day to recover from. So, I hope you can understand my reluctance to install these updates that are known to cause BSODs (even if only in a few cases).

I am familiar with System File Checker ... but I am skeptical that by running SFC and getting a clean report, Microsoft can give me a 100% guarantee that I will not get a BSOD when installing these kernel updates.

Has Microsoft been unable to reproduce these BSODs in-house?

But that's the thing, 1% of customers are not being impacted.  Look on the headlines and they all point back to this thread in the forums.  In this thread there's only a couple of clear cut cases.  The majority of impacted customers hit the 0xc00000005 issue which was caused by using pirated operating system. It it was truly 1% then I'd be seeing lots more systems hitting this issue including many under my personal control.

I understand that you are concerned here, but I don't want anyone to place more emphasis on the risks of patching than the risk of not patching.  These kernel code updates are used in blended attacks that 'walk' up the system and gain control.  While these two may not have specific widespread attacks today, they will in the future. 

(btw this was meant as a response to you ---

http://support.microsoft.com/kb/929833/en-us

Use that to scan your system ahead of time. It will perform repairs on the system and registry to ensure your system is fine.

http://support.microsoft.com/kb/929833/en-us

Use that to scan your system ahead of time.  It will perform repairs on the system and registry to ensure your system is fine.

If you have any issues all I need from you is your name/email address/phone number and I'll set up a support case with Microsoft.

100% perfection in any technology is not guaranteed.  There is a greater probability that you will get nailed by malware.  I think it's more unreasonable that we continue to have to deal with malware.

Yes it does supercede the August update on 64bit system.  Again, we're not seeing a ton of bsod's.  And if you do get one, it's a sign your system needs to get looked at and investigated.

You assume a user can do all the things you ask if they get a BSOD.  I consider myself somewhat knowledgeable yet I don't even know if I could get my computer started if I experienced some of the issues reported related to these (now) two updates, let alone provide you the info you need to get it repaired.

I'm told to go ahead and install the updates even though there are known (albeit rare) issues?  I think that is an unreasonable request from MS.