Recieve a BSOD after KB2859537.

It might be wise if as these kernel updates come out that they first check for "Redmond code" and fail to install, or check the servicing stack and fail as well. 

 

[...]

There are times that due to third party programs, or just hard drive hiccups, the servicing stack doesn't have the bits lined up like it should. 

Thanks for the info on servicing stack.

Now I understand how the problem could occur (especially due to third parties).

I think the "fix" for KB2859537 should (at the very least) insure that if corruption exists, the update exits and does not subsequently cause a BSOD. Hopefully by now, Microsoft has enough feedback from customers (such as EnglishM45) to "fix" KB2859537 in that way and then unthrottle it.

The potential of a BSOD is probably keeping many people from attempting to install KB2859537.

http://technet.microsoft.com/en-us/library/cc749534(v=ws.10).aspx

Servicing stack.  How Windows now updates/deploys patches. 

http://blogs.technet.com/b/joscon/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx

Read that blog post to get an idea of what's going on in the background when an update is installed.  A LOT of moving parts gets shuffled around and laid down where they are supposed to be.  So files move around and get lined up to be in a certain place at a certain time needed for updating.  If stuff happens and the bits are not in the right place then issues with updating occur.  Periodically Microsoft releases servicing stack updates that go through systems looking for the big windows updating errors they see.

A few years back when the Alereon root kit was hot and heavy a kernel update came out that was a really good indicator of a root kit.  It might be wise if as these kernel updates come out that they first check for "Redmond code" and fail to install, or check the servicing stack and fail as well. 

A servicing stack update is available for Windows RT, Windows 8, and

Windows Server 2012: September 2013:

http://support.microsoft.com/kb/2871777/en-us There's a servicing stack update out today for Windows 8 in fact.

Since Vista, Windows now uses a different engine to install updates.  CBS or component based servicing.  A bit more info below:

http://blogs.technet.com/b/joscon/archive/2012/09/26/fixing-component-store-corruption-in-windows-8-and-windows-server-2012.aspx

There are times that due to third party programs, or just hard drive hiccups, the servicing stack doesn't have the bits lined up like it should.

Hmmm, ok, like 'langware' I would like to understand what 'servicing stack corruption' actually means. I understand each word individually but not together. I could guess at a queue of actions that need to be performed for installation, but I'm probably wrong!

You do have Redmond code, you aren't getting the 0xc0000005 application error which is a sign of the non genuine bits.  Again, as I understand it, you do have servicing stack corruption that they are still trying to figure out the best plan of action for... ergo the silence. 

It's 100% reproducible for if there are certain servicing stack issues, but not everyone has these servicing stack issues.