Yes, sssssssssssorry, I've got the KBnumbers mixed up...
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-09-13T15:27:50+00:00 -
Anonymous
2013-09-13T15:15:28+00:00 Hi!
"KB2589275 is messing up Office file associations on Windows 7, with no official fix available for the time being."
"At this point, it appears that running MS Word with the /r parameter is the only way to fix the problem, as update removal isn’t yet recommended. To do this, click on Start, hit Run and type “winword.exe /r” to launch the application and temporarily fix file associations."
Hope that's helpful...
Cheers
Julia
No, that won't be helpful. That one is another kind of update for another, different, Microsoft product.
-
Anonymous
2013-09-13T08:40:21+00:00 Hi!
"KB2589275 is messing up Office file associations on Windows 7, with no official fix available for the time being."
"At this point, it appears that running MS Word with the /r parameter is the only way to fix the problem, as update removal isn’t yet recommended. To do this, click on Start, hit Run and type “winword.exe /r” to launch the application and temporarily fix file associations."
Hope that's helpful...
Cheers
Julia
-
Anonymous
2013-09-13T08:13:40+00:00 Take care with KB2876315 - it caused BSOD immediately after login on my Dell 7010. Even BSOD in safe mode with networking. If it happens, boot in safe mode and uninstall the update.
-
Anonymous
2013-09-12T18:00:31+00:00 I did not install KB2859537 (due to potential of BSOD), and have been following this thread.
It appears that KB2859537 has been superseded by KB2872339 ??
However, the description for KB2872339 states that there are some known issues with that update that can result in a STOP 0x6B if the following registry entries are missing.
Really Microsoft? How many people know enough to check their registry before installing an update that MS sends and will install automatically if that's how you have it set (luckily I don't).
I am not going to install KB2872339 until I do some checking.