If they are already impacted, please I'm just saying that this is indeed the way to showcase that there's impacted numbers out here. Forum posts do not have the same impact as a support case. Again please, I can't do this without help.
Recieve a BSOD after KB2859537.
When I install KB2859537 on my Windows 7 X64 machine I get a BSOD during reboot either trying to boot normally or trying to boot in safe mode. Had to restore the primany disk three times now to get the PC bac. Can someone report to MS tech please.Anyone else seen this
Windows for home | Previous Windows versions | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
216 answers
Sort by: Most helpful
-
Anonymous
2013-08-16T06:28:02+00:00 -
Anonymous
2013-08-16T06:24:19+00:00 That doesn't solve it. Please, with that many impacted machines you would be a fantastic resource of log files. Please, it won't cost you a dime and you'll help us all here. Please?
I know but I don't think Bill will send me a check for my travel expenses, must go by car to at least 20 clients to uninstall. Don't have the time to do it more then once.
-
Anonymous
2013-08-16T04:48:27+00:00 Furthermore when I set up these cases it does INDEED prove numbers. Phone calls/support engineers cost Microsoft more. So they notice more.
-
Anonymous
2013-08-16T04:47:25+00:00 That doesn't solve it. Please, with that many impacted machines you would be a fantastic resource of log files. Please, it won't cost you a dime and you'll help us all here. Please?
-
Anonymous
2013-08-16T04:27:41+00:00 What you and I consider to be widespread, isn't widespread in their view. If their enterprise folks are not screaming their heads off, it won't be pulled. Would you be willing to have me set up a support case for you? If so email susan-at-msmvps.com (change the -at- to a @) and I'll need your phone number to set up a call back from Microsoft.
Thanks Susan but I "solve" the problem by uninstalling and hiding KB2859537, don't have the time to be involved in this. Just hope MS will admit the problem and stop denying they have released a bad update!