Slashdot Mirror

← Back to Stories (view on slashdot.org)

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

Posted by samzenpus on from the back-to-the-old dept.

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.

12 of 304 comments (clear)

  1. It isn't only Windows 8 by cosmin_c · · Score: 5, Informative

    I'm using Windows 7 and I was affected by this. I can't fathom the depths of ineptitude required to release such an update, to be perfectly honest.

    1. Re:It isn't only Windows 8 by BarbaraHudson · · Score: 5, Informative

      I can't fathom how slashdot fall to the point where people with ignorance on your level get modded up instead of into oblivion. Whats better is that you're claiming that Windows 8 drivers that don't work on Windows 7 caused the same problem for you. This is an ID10T or PBKAC error I think.

      Before jumping on the previous poster for mentioning Windows 7, you might have wanted to read the linked article, or better yet Microsoft's own description of one of the updates that states it affects a LOT more than just Win8x, and it has nothing to do with drivers

      Update to support the new currency symbol for the Russian ruble in Windows

      ... Windows 8.1, Windows RT 8.1, Windows Server 2012 R2, Windows 8, Windows RT, Windows Server 2012, Windows 7, and Windows Server 2008 R2.

      Buffer overflow in a character set table?

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    2. Re:It isn't only Windows 8 by jones_supa · · Score: 5, Funny

      The scary thing about Linux is that they can do sometimes platform updates which suddenly break fundamental things like keyboard or ACPI fan control.

      But then again, the bleeding-edge development process also allows to get all the new cool features quickly into the kernel.

    3. Re:It isn't only Windows 8 by LesFerg · · Score: 5, Insightful

      I can usually find some way to boot into a repair mode and get things running again in Linux (I usually go with Debian) without having to follow the Microsoft approach of restoring my whole O/S from the install disk - which some people have been forced to do with these recent update bugs as they can't even get a boot into Windows safe mode.

      I have never had an update hose my Linux system so badly that I cannot get in there and replace or remove the offending driver or whatever.

      --
      If I had a DeLorean... I would probably only drive it from time to time.
    4. Re:It isn't only Windows 8 by chipschap · · Score: 5, Insightful

      I've never, ever had the severe kinds of problems you mention, and I've been on Ubuntu or its derivatives (most recently Mint) for years and years. And this is across maybe a dozen machines of all descriptions, and with all sorts of graphics cards, including the dreaded nvidia, which works just fine and only required a little patience.

      That is not to say I take the position that Linux is completely golden and Windows is purely trash. There are always bugs and problems. However, given what I paid for my Linux distros, I think I got a really good deal which far exceeds expectations.

      The problem is that some vocal Windows people will jump on Linux bugs as "proof" that Linux is not "ready" and so on. But Microsoft's latest antic convinces me that Windows, after how many years, is less ready.

  2. Forget TFA by Anonymous Coward · · Score: 5, Informative

    Here is the better workaround for the problem from Microsoft: https://support.microsoft.com/kb/2982791

  3. I've learned the hard way by msobkow · · Score: 5, Insightful

    I've learned the hard way over the years. Never let Windows Update install a driver of any kind. Ever.

    I've had them blow out network cards, video cards, sound cards, and low level on-board devices. I've had them completely bork systems to the point where they were unbootable.

    Go to the vendor and get the official updates.

    I don't know how they do it, but Windows Update perpetually mis-identifies hardware and installs the wrong drivers, delivers broken drivers, and otherwise screws up when it comes to drivers. Yet the official vendor's drivers (such as Intel) work just fine.

    Go figure. One would think Microsoft is just redeploying those same drivers, but years of being burned have taught me that's not the case.

    --
    I do not fail; I succeed at finding out what does not work.
  4. Connected to mass layoff of Windows SDETs? Maybe? by xeno · · Score: 5, Insightful

    One of the bits of logic used for recent layoff and reorgs has been something like 'component/security/etc testing had become so mature at Microsoft (!) and ingrained into normal dev processes, that such a large population of SDETs (testers) across OS and key office products is unecessary.' Just chew on that for a second, and ponder how intensely stupid that seems.

    But nevermind my opinion; I guess we're getting some at-scale empirical testing of whether getting rid of testers en masse was a good idea.

    --
    I think not...(*poof*)
  5. It's pretty hard to roll back automated updates by Brulath · · Score: 5, Informative

    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. At which point a second System Restore decided it would fail to modify a file and thus refused to work. Four hours later, I had to format to get Windows back.

    One thing I learned: Disable fast boot, if it's enabled, on your Windows machine (powercfg -h off will disable hibernation entirely). 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). You can mount it as read-only and get your data, but if you run into a problem that could be fixed by modifying or deleting files then you're out of luck if fast boot is enabled and the action required cannot be performed from the windows boot environment (you can't disable fast boot from it, the required services aren't loaded).

    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.

    1. Re:It's pretty hard to roll back automated updates by danknight48 · · Score: 5, Interesting

      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.

  6. never update windows on patch day, wait a week by Nyder · · Score: 5, Insightful

    One thing I have learned over the course of MS OS's lives, is to NEVER update the computer at within a week of the updates being released. MS had a nice reputation for putting out crappy patches every now and then.

    You are the product tester and you get to pay for it. So be smart, let the stupid people get the BSOD's so you don't have to.

    --
    Be seeing you...
  7. They fired 30% of their testers by Anonymous Coward · · Score: 5, Interesting

    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.