Follow Slashdot stories on Twitter


Forgot your password?
Bug Microsoft

Windows 8.1 Update Crippling PCs With BSOD, Microsoft Suggests You Roll Back 304

MojoKid writes Right on schedule, Microsoft rolled-out an onslaught of patches for its "Patch Tuesday" last week, and despite the fact that it wasn't the true "Update 2" for Windows 8.1 many of us were hoping for, updates are generally worth snatching up. Since the patch rollout, it's been discovered that four individual updates are causing random BSoD issues for its users, with KB2982791, a kernel-mode related driver, being the biggest culprit. Because of the bug's severity, Microsoft is recommending that anyone who updated go and uninstall a couple of the specific updates, or rollback using Windows Restore. You can uninstall these updates in much the same way you uninstall any app; the difference is that once you're in the "Programs and Features" section, you'll need to click on "View installed updates" on the left. While it's mostly recommended that you uninstall 2982791, you may wish to uninstall the others as well, just in case.
This discussion has been archived. No new comments can be posted.

Windows 8.1 Update Crippling PCs With BSOD, Microsoft Suggests You Roll Back

Comments Filter:
  • by yakumo.unr ( 833476 ) on Sunday August 17, 2014 @08:56PM (#47691811) Homepage

    For some it was just a plain black screen with no errors displayed (win 8.1 x64) , same fixes though: []

  • by Ol Olsoc ( 1175323 ) on Sunday August 17, 2014 @10:13PM (#47692157)

    Don't try to "fathom" anything. Just turn off automatic updates, and you'll be a bit safer.

    Microsoft doesn't pay attention to that any more. Before I nuked 8.1 and replaced it with Mint, they had at least 5 forced updates that wrecked my wife's laptop.

  • by whoever57 ( 658626 ) on Sunday August 17, 2014 @10:40PM (#47692283) Journal
    Since some of the updates were for security fixes, this gives hackers time to analyze and reverse engineer the original fault, then use it against systems before there is a fix available.
  • by Anonymous Coward on Sunday August 17, 2014 @11:51PM (#47692527)

    The Windows Serviceability team (dealing with updates) was decimated in the middle of last month, losing about 30% of their testers. This outcome is not surprising at all. Expect things to get much worse soon.

  • by BUL2294 ( 1081735 ) on Monday August 18, 2014 @02:35AM (#47692947)
    This is a perfect example of why Microsoft should go back to doing Service Packs and not these seemingly random "feature updates" that have become the norm with Windows 8.x and Office 2013 (non-MSI / "click to install"). There's no standard codebase anymore and feature updates are just being installed willy-nilly, with no real support window for delayed installations. (At least with a SP, you had a year to test & work around a problem before MS pulled the support plug). This is another reason why companies don't want Win8.x--kernel-level updates with only a few days warning. (Articles were still talking about "Windows 8.1 Update 2" as recently as 2 weeks prior to August's Patch Tuesday). I'd hate to be an NT administrator fretting over all my 2012R2 installations right now.

    Instead of getting a SP for Windows 8, we now have 8.1. Instead of getting SPs for Windows 8.1, we now have 8.1 Update 1 and 8.1 August Update. We have updates that come through the "Store" app. This is one of the reasons (granted, not the primary one) why the uptake of Windows 8.x is now slower than Vista's uptake [] some ~2 years post-RTM, and why Windows 7 is gaining market share, at the expense of XP and Vista. Companies don't want this model and the headaches that go along with it.

    So, for Win9, just go back to a Service Pack model and make everybody happy. Yes, SPs cost a lot of money to put out, and yes MS ends up looking old-school, but the rigor with testing is (presumed to be) significantly higher than some rushed, "little" update. Windows 8.x is broken, and Microsoft keeps pitching a newer, faster cycle of feature updates, but this just proves they are incapable of properly handling such a model... Microsoft: you are not Apple, and you don't have to try to emulate them.

    As for myself, so far my two Win8.1 installations (one x86, one x64) and one of 2012R2 in a VM are not showing problems from these updates... But I have only myself to blame for not waiting a few extra days. Of course, now MS will have to come up with an out-of-band fix (with even less testing) within the next ~3 weeks or will have to have 2 sets of patches for September's Patch Tuesday--one for those who haven't uninstalled these updates and one for those who have. Pure stupidity...
  • by Dan Askme ( 2895283 ) on Monday August 18, 2014 @03:49AM (#47693105) Homepage

    I hadn't realised it was an update which caused the error, so when I finally resorted to system restore it just auto-updated immediately and broke again.

    Rule number 1 = Dont use system restore
    Rule number 2 = Dont use system restore
    Rule number 3 = Google "Stop 0x0000000e" error code on your BSOD.
    Rule number 4 = Remember the last thing you did before the BSOD started happening, reverse the process. Job fixed.

    One thing I learned: Disable fast boot, if it's enabled, on your Windows machine. Your startup time will be a little slower, but you might just save that time if something ever goes wrong with your Windows install and system restore fails.

    All fastboot does is skip a few bios checks (eg: fast memory scan instead of full). It will not effect anything else, unless you have a hardware fault which can be detected at BIOS post.

    Apparently a Ubuntu boot dvd cannot mount an NTFS partition with write enabled if a hiberfile.sys is present (apparently windows leaves its mounts active and stored in said file, so modifying the file system would cause problems).

    Sounds like the Ubuntu DVD doesnt include NTFS-3G which is required for NTFS write ability on linux. Or simply its a safey feature to prevent you deleting the hibernation file.
    The only time you need to keep this file is if your machine is in hibernation and powered off. Only then will it contain possible data your working on that isnt technically saved. If you wernt in hibernation when you powered the machine off, the file is just a placeholder for the next hibernation.

  • Re:How about (Score:1, Interesting)

    by Anonymous Coward on Monday August 18, 2014 @03:58AM (#47693121)
    Because Gnome is better than KDE.

Make it myself? But I'm a physical organic chemist!