Recieve a BSOD after KB2859537.

Given that my understanding is the root cause is servicing stack corruption

I am not familiar with "servicing stack corruption".

Do you think it would be possible for the patch to detect if corruption exists, and if so then exit ...  with perhaps a notification to user that update will not be installed .... thus avoiding a subsequent BSOD?

 

"Some users may experience issues...." is a polite way of saying "if you have a machine who's kernel code isn't genuine Redmond code, this patch is going to cause a problem".

 

The fact that there isn't a clear cut response at this time indicates there's no clear cut problem with the patch.

 I agree with most of what you say, but let me assure you the kernel on my machine is genuine Redmond code. That doesn't mean some sort of corruption hasn't occured, but as this issue is 100% reproducible, I doubt it.

There isn't a clear cut response to me either at present so I suspect MS are still not sure if the patch causes the issue on some installations or not, which is why they continue to be cautious. I've asked for an update on progress.

Given that my understanding is the root cause is servicing stack corruption - not a problem with the patch - I don't anticipate them rereleasing the update. 

I am personally still opening up cases but if this was a widespread issue I would have hit this problem on a machine I personally have.  I have not. 

As the KB says "there are limited reports".  There are indeed just that.

"Some users may experience issues...." is a polite way of saying "if you have a machine who's kernel code isn't genuine Redmond code, this patch is going to cause a problem".

I fully anticipate that they will 'unthrottle' the update and monitor to ensure that the issues are indeed limited.

They can only respond if they understand the issue.  If people don't open support cases ....ergo my ask that if you do see issues, help all of us by opening a case.

The fact that there isn't a clear cut response at this time indicates there's no clear cut problem with the patch.

I too am confused by Microsoft's lack of response.

The article for KB2859537 (http://support.microsoft.com/kb/2859537) says this (underlining is mine):

"Some users may experience issues with certain programs after they install security update 2859537. In some cases the programs may not successfully start. We are also aware of limited reports that certain users may encounter difficulties restarting their computers after applying this security update.  Microsoft is researching this problem and will post more information in this article when the information becomes available."

The date of the article is this:  "Article ID: 2859537 - Last Review: August 16, 2013 - Revision: 3.0" ... that's almost 4 weeks ago and we are still waiting for Microsoft to "post more information".

Here's an interesting article on the issue from Infoworld:  http://www.infoworld.com/t/microsoft-windows/microsoft-needs-your-help-fix-botched-patch-kb-2859537-225314

 

But bottom line, I do not expect a new fix, nor should you.

Confused. 

The update which was listed as Important was issued due to a vulnerability.  Due to some users having issues it was unchecked (throttled) but still listed as Important. So in theory users can not have this update installed and be subject to the vulnerability.  MS doesn't plan to reissue (unthrottle) it and again check it for installation?