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

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.

Comments

For some it was just a plain black screen

[yakumo.unr]

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

http://answers.microsoft.com/e...

Re:For some it was just a plain black screen

[innerweb]

Windows is my gaming system, from which I browse when I have been gaming (as I just finished a bit ago).

Linux is actually where I do most of my work already.

Re:For some it was just a plain black screen

[Anonymous Coward]

Boot into safe mode and restore. Windows automatically creates a restore point before updates are applied. If the boot process is too quick to hit F8 or shift-F8, hard power your PC on and off a few times and Windows 8 will automatically go into a recovery mode where you can choose to reboot into safe mode.

Re:For some it was just a plain black screen

[Anonymous Coward]

Linux would have to start working on the Desktop.

With Android and ChromeOS added to traditional Linux DEs, it's already there.

Windows is only useful for about 1% of business use-cases now.

Thing is, it's so maintenance-heavy, it costs way more to provision and admin than just about everything else around. With that sort of $ savings available, it's only a matter of time before smart companies transition.

Re: For some it was just a plain black screen

[Anonymous Coward]

Foresooth. I tried Linux again when I got my first Vista laptop and have never looked back. Gnome on OpenSuse has worked way better than friends' Windows machines.

Re: For some it was just a plain black screen

[Anonymous Coward]

Uu, the classic desktop environment flame wars. I like it!

Re: For some it was just a plain black screen

[ozmanjusri]

I'm pretty sure casual computer users still need to pay tax.

Then use MyTax. That'll work for Android as well as Linux computers. E-Tax is a dinosaur.

https://www.ato.gov.au/Individ...

Re: For some it was just a plain black screen

[Anonymous Coward]

Indeed. Balmer knew this - which is why he tried to use Windows 8 to shepherd everyone into the Windows Store.

Re:For some it was just a plain black screen

[Anonymous Coward]

Thing is, it's so maintenance-heavy, it costs way more to provision and admin than just about everything else around.

Nonsense. On the desktop (and ONLY on the desktop), Windows consistently has lowest TCO. Apple systems have some very decent software in certain markets, and should be chosen where this platform makes the worker more productive, but base costs are slightly higher and (more importantly) administrative tools are severely lacking. A competent admin may be needed to automate deployment, but once that's done, you have everyone else in the building being more productive than with some half-assed Open Source offering or inefficient, insecure joke of a cloud offering.

It is an utterly false economy to regard the cost of an Office license or the time taken to install it as significant compared to the continual productivity loss from second rate solutions. Anyway, even if you're paying minimum wage with no benefits and no overheads (i.e. imagination), the "software licensing and maintenance" cost is still a teeny part of overall monthly expenditure associated with each employee.

Re:For some it was just a plain black screen

[robsku]

Linux has worked fine for most peoples needs on desktop for ages. I dont see much additional benefit for it from android, which is really for mobile devices, or Chrome OS, which is mostly good for lightweight netbooks.

People just need to get over whatever it is keeping them for believing it don't work on desktops. Please, no quoting ones special needs cases as rebbutals.

Re: For some it was just a plain black screen

[robsku]

I can haz games fine on linux too - especially as there's a well knows FOSS software to provide Windows API for, and run large set of Windows applications. Sure, I can't get every/any game to work, but I consider myself a hardcore gamer and yet don' need to have all of them. There's way more good games that work on it for me to ever play all of them. And I've run linux almost extensively since 02 - when I switched I first thought I'd keep windows as dual boot for games, but after 2 weeks in linhx I never went back.

Re:For some it was just a plain black screen

[gfxguy]

Yeah... but Woolworth's is still in business? That's what's newsworthy... every Woolworths store I've ever known has been shutdown for ages.

I work for television production, and luckily those creative types keep Macs persistent in our computer inventory, but most desktops are still Windows; we still use Maya on Windows, and even those lucky enough to get MacBooks get Windows installed (one of our VPs called his MacBook the best Windows computer he ever had).

It's not happening enough to matter. I'm glad I can choose what to work on... yes, I dual boot and select Linux most of the time, but I do have to use Windows for some things, still, and yes, even at home we have Windows boxes (and out of four people, I'm the only one who dual boots).

Re:For some it was just a plain black screen

[Espectr0]

Huh? F8 doesn't exist anymore on Windows 8.x

Re:For some it was just a plain black screen

[richy freeway]

It's not by default, but can be re-enabled easily enough.

I know, it's a bit late for that once the machine doesn't boot, but for future reference : http://www.bleepingcomputer.co...

Re:For some it was just a plain black screen

[Zero__Kelvin]

Did I mention that for 99% of the business use cases Libre Office is actually a better tool than Office? For the few who absolutely need Office, and they are few indeed, there is Crossover.

Re:For some it was just a plain black screen

[Bacon Bits]

Actually, it does. It just boots too fast for you to press the key.

Re:For some it was just a plain black screen

[udippel]

No astroturfing, please! ;-)

For me the free wine is doing just fine. sudo apt-get install wine; that is. For MS Office 2007, at least. And who needs newer?

Re:For some it was just a plain black screen

[Zero__Kelvin]

I agree that WINE is great, but I mentioned Crossover since it comes with support. This will hopefully quell the cries of ... but you haz ta be da expert geek, and rely on da forumz where da peoplez is meanz!.

Re:For some it was just a plain black screen

[hawkinspeter]

He's referring to Australian Woolworths which is a big supermarket chain. Over here in the UK, Woolworths as a general/department store has been out of business for a few years. I believe the companies are unrelated, but I haven't looked into it.

Re:For some it was just a plain black screen

[david_thornley]

My son said that, the more he uses his Windows 8 laptop, the more he likes Linux. I'm proud of him.

Re:For some it was just a plain black screen

[david_thornley]

That depends entirely on what you're doing. Depending on what you're doing with Office, you may or may not find LibreOffice or OpenOffice suitable. Depending on what else you're doing, you may find Windows, Linux, or MacOSX as best on the desktop.

Now, the safe thing to do for typical office workers is to give them a MS Windows box with MS Office, but that does come with some problems, such as retraining every time MS has a "bright" idea.

Re: For some it was just a plain black screen

[david_thornley]

If a vendor doesn't think it's worth producing a Linux version of some software you need, I'm happy with calling that Linux's fault. If a place you have to deal with requires Windows, I'm blaming it on the place that requires proprietary software. Governments in particular have no business mandating the purchase of particular proprietary products.

Re:For some it was just a plain black screen

[demonrob]

Different woolworths. This is the australian one. There's even a seperate South Aftican one too I believe,

Re:For some it was just a plain black screen

[Espectr0]

thank you, i knew about the legacy bootloader but i didn't know it enabled F8

It isn't only Windows 8

[cosmin_c]

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.

Re:It isn't only Windows 8

[fustakrakich]

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

Re:It isn't only Windows 8

[Anonymous Coward]

If it was just one update I might agree with you, but deciding to release four different bad updates at the same time is just ridiculous. All of my friends that worked in QA there have been laid-off, but even that doesn't justify the decision to release known bad updates.

Re:It isn't only Windows 8

[BarbaraHudson]

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?

Re:It isn't only Windows 8

[jones_supa]

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.

Re:It isn't only Windows 8

[Anonymous Coward]

In 5 years, I never had a Linux update break anything, no BSOD's or lockups either. The "other" PC, we'll call that "Windows" locks up at least once per day, BSOD's, nags about everything, loses its LAN connection configuration, won't do this or that, etc. Two identical PC's, one Linux, one Windows, only one is stable and trusted.

Re:It isn't only Windows 8

[Ol Olsoc]

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.

Re: It isn't only Windows 8

[exomondo]

No it doesn't seem "more like that" at all, testing the millions of configurations is objectively impossible with the different types, brands and revisions of hardware all mixed and matched as well as the myriad of different versions of drivers for that hardware.

Re:It isn't only Windows 8

[mvdw]

I like linux, I run linux exclusively at home, but I don't believe that this could be purely Windows' fault. If the computers truly are identical, swap hard drives and see if the 'good' computer now suddenly develops faults while running windows, or if it's a hardware problem.

Re:It isn't only Windows 8

[EvilJoker]

You've apparently never had to deal with buggy Linux drivers. I've been fighting with a buggy nVidia implementation ever since I switched it to be my Linux server. It has never quite worked right on Linux (Fedora, Ubuntu), but since it's a server, it's not a big deal.

I DID find out the hard way when they changed mdadm to HALT BOOT when *ANY* array is degraded, and then not give a useful error message.

If your Windows PC is getting BSODs, either it's hardware fault, or it's a bad driver. (Or possibly a driver-level virus). If the hardware is actually supported by that version of Windows, you should investigate further. There may not be a good driver, but you should be able to at least identify the issue I would start with the NIC driver. I had a D-Link DUB-E100 USB NIC. The Win7 x64 driver would cause the same issues you're having now.

Re: It isn't only Windows 8

[exomondo]

It isn't really a question of money, you simply cannot test anything even close to that many configurations. No other vendor supports anywhere near that many. The could leave it up to the OEM to test but that would probably end up like the state of Android updates.

OS X is supported on a relatively small amount of configurations and they bundle driver updates for the core hardware so it is generally much more stable across its available hardware platforms.
iOS is a comparatively very narrow set of configurations.
We all know the story with the disparate availability of Android updates and even custom distros like Cyanogen only support a handful of handsets and they don't have customizable internals or various driver versions for those internals unlike desktops/laptops.

Re:It isn't only Windows 8

[bigfinger76]

I don't believe you.

Re:It isn't only Windows 8

[Anonymous Coward]

Nope, I turned mine off and have never had to update. 7 at least. I learned the hard way that the new default behavior of Winblows is now to force an automatic reboot regardless of what programs are running.

Re:It isn't only Windows 8

[Anonymous Coward]

Then you didn't disable updates. I always set Windows to manual update only and have never had any patches force installed.

Re:It isn't only Windows 8

[ozmanjusri]

The scary thing about Linux

There's more than one Linux, and it's very easy to choose a stable distro that doesn't live on the bleeding edge.

Re:It isn't only Windows 8

[jones_supa]

Are you aware that the fan bug slipped right into the main kernel of Ubuntu 14.04 LTS. It was finally fixed in July in Ubuntu kernel 3.13.0-31.

Re:It isn't only Windows 8

[Anonymous Coward]

In 5 years, I never had a Linux update break anything, no BSOD's or lockups either. The "other" PC, we'll call that "Windows" locks up at least once per day, BSOD's, nags about everything, loses its LAN connection configuration, won't do this or that, etc. Two identical PC's, one Linux, one Windows, only one is stable and trusted.

If you have Win7 or Win8 locking up once a day or BSODs etc, then the problem is you.
Seriously, it's you.

Re:It isn't only Windows 8

[jenningsthecat]

There's more than one Linux, and it's very easy to choose a stable distro that doesn't live on the bleeding edge.

Do you mean like Debian Testing, (Jessie), that broke both my sound and my ability to suspend during the last dist-upgrade? Or do you mean like Debian Stable, (Wheezy), which won't work with my wired network hardware so I can't even install it in my new machine without a bunch of CD's and a few prayers? Or perhaps you mean Ubuntu, (I moved to Xubuntu when I got fed up with trying to get Debian working), which prompts me to reboot after updates a couple of times a week like some crappy Windows box?

I don't think I could ever really go back to Windows, (especially given my recent experiences with 8.1 on my GF's new laplet), but recently there have been days when I've toyed with the idea...

Re:It isn't only Windows 8

[_merlin]

I had persistent bluescreens that I tracked down to an overheating SAS controller. It was not a pleasant experience. It's been pretty stable since then, though.

Re:It isn't only Windows 8

[Anonymous Coward]

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.

My Windows XP computer is still working fine.

Re:It isn't only Windows 8

[techno-vampire]

Or perhaps you mean Ubuntu...

...which is based on Debian. Maybe you might consider trying a distro that's based on something else, such as Fedora, based on RedHat. Right now, I'm running Fedora 20 on my laptop and 19 on my desktop because I just haven't had time to upgrade it. Normally, my desktop runs 24/7, only rebooting for kernel updates. Current uptime is a little over 9.25 days and I can't remember the last time an update broke anything. Of course, I'm not foolish to run anything that's as bloated as Gnome, preferring Xfce with Compiz, but It Just Works.

Re:It isn't only Windows 8

[phantomfive]

Isn't it sad that in 2014, font processing on Windows still happens in the kernel? Wouldn't it be nice if, instead of shifting around their UI, Microsoft spent time moving font processing out of the kernel?

Here is Microsoft's workaround. Notice how it involves fonts and the registry. The registry: another 'gift' that keeps on giving.

Re:It isn't only Windows 8

[LesFerg]

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.

Re:It isn't only Windows 8

[chipschap]

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.

Re:It isn't only Windows 8

[LesFerg]

Even with a non-functional kernel, you can boot from a rescue disk and add other kernel versions in there, can't you?
My Debian install usually has a couple of kernels to choose from in the boot menu.
Graphics driver problems shouldn't stop you from getting a working command prompt, allowing you to fix or replace the driver.

Re:It isn't only Windows 8

[LesFerg]

In 5 years, I never had a Linux update break anything, no BSOD's or lockups either. The "other" PC, we'll call that "Windows" locks up at least once per day, BSOD's, nags about everything, loses its LAN connection configuration, won't do this or that, etc. Two identical PC's, one Linux, one Windows, only one is stable and trusted.

If you have Win7 or Win8 locking up once a day or BSODs etc, then the problem is you.
Seriously, it's you.

Have to agree with that sentiment. I have not had any major problems with win7 since replacing old outdated hardware. The last big problem I had was the AMD software which kept prompting me to update to the latest drivers, advice which I stupidly accepted; the AMD driver developers dropped support for 'old' chipsets but never modified the updaters to advise against installing drivers that were no longer compatible.

At the time I believed I was doing the right thing by keeping up with the suggested updates, this is not necessarily true all of the time. Sometimes you are trying to be too cheap instead of updating your old hardware. Also you should usually be able to track the cause of the BSOD and work out what hardware, driver etc. is being reported. Thats why the BSOD has all those scary numbers on it. So you can fix it. Instead of complaining about your daily BSOD.

Re:It isn't only Windows 8

[jones_supa]

GP's claim was that it is "very easy to choose a stable distro that doesn't live on the bleeding edge". For many people Ubuntu LTS is an obvious choice. If there suddenly comes a rule that Ubuntu cannot be used, then the choice is obviously not very easy.

Re:It isn't only Windows 8

[Anonymous Coward]

I can...it's Microsoft, after all.

They basically jumped the shark at Vista, salvaged it quite a bit with Win7- and then burned all but a smidgen of their goodwill with 8.0, having really jumped the shark with that and RT (Seriously, Microsoft? Didn't you learn that lesson with CE in it's early days?).

There's not really anybody at the helm. I daresay a symptom that's prevalent throughout the industry these days. It's all about placating the Sharesellers long enough to bumble and stumble to the next set of profits to keep the farce rolling forward.

Just try not to be the bagholder when they are forced to turn the lights off there.

Re:It isn't only Windows 8

[Anonymous Coward]

Luckily, neither Gnome nor systemd run in kernel space. What's even better, you can have a fully functional syste without either of those as well.

Typing this on Linux with Gnome, and no systemd. Imagine that!

Re:It isn't only Windows 8

[Cutterman]

Confirm Windows 7 affected. System fonts wouldn't display resulting in illegible system.
Did a restore and then cautiously installed update one by one, with reboots in between each.
Running OK now
Seems the problem was Windows installing all those updates in one big bunch.

The Cutter

Re:It isn't only Windows 8

[SuperTechnoNerd]

As an additional measure I block micro$oft in my firewall so im not "forced" to do anything..

Re:It isn't only Windows 8

[simplypeachy]

Yesterday I had mod points :-(

Guess I'll join you down here at 0 Troll for discussion of a sensible, unprejudiced manner. Shall we start with Heartbleed?

Re:It isn't only Windows 8

[simplypeachy]

I'm taking collections for a Karma Self-Destruction Fund, to support people who accidentally held up logic and sane discussion towards a Microsoft subject, and get themselves mutilated by the prejudicial horde. Care to donate?

Re:It isn't only Windows 8

[AmiMoJo]

Windows doesn't do font processing in the kernel. This update changes the way the kernel handles the Russian code page, which Russian versions of Windows use instead of ASCII since the American Standard Code for Information Interchange doesn't support Cyrillic characters.

Re:It isn't only Windows 8

[AmiMoJo]

It isn't hard to imagine at all. Consider how many versions of Windows there are and how many different hardware configurations it runs on.

Windows 8 Home and Pro
x86, x64 and ARM versions of both
50+ languages for each

I'm sure there are more variations than that. It's the same with IE. Every time they release an update it has to be testing on a few hundred configurations minimum, and even then there will be cases they didn't test.

Re:It isn't only Windows 8

[TheDarkMaster]

Welcome to the new world where using a computer became so easy that any ignorant can use. But do not worry, someday - maybe - he will learn that problems can happen however much you try to avoid them.

Re:It isn't only Windows 8

[TheDarkMaster]

Maybe because do it in the kernel is much faster than doing it in user space, and being a function where performance is critical? Do not take hasty conclusions without knowing why the original decision was made.

Re:It isn't only Windows 8

[ruir]

Cant compute what you are saying nVidia bug and "server"? You are not supposed to run a graphical environment in a server...

Re:It isn't only Windows 8

[Ol Olsoc]

As an additional measure I block micro$oft in my firewall so im not "forced" to do anything..

That's quite the indictment when you have to do that. Sorta like taking out a PFA against your parents.

Re:It isn't only Windows 8

[c]

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.

I've seen all sorts of similar stuff. Mind you, it's not as bad as the GP suggests. If you're running Debian testing, you *will* get bit on the ass inevitably. And Ubuntu prompts you to boot more than any other distro largely because the others don't really prompt you to boot at the GUI layer after a kernel update.

I've seen some updates that render a system unbootable (the one that comes to mind was that /dev/hd* to /dev/sd* migration a while back), and there's been some pretty boneheaded small glitches too (Ubuntu recently updated to show a pretty background image at boot rather than the far more useful prompt for my whole-disk decryption password). And things like drivers can be a pain (nvidia graphics and anything involving the name "Broadcom" in particular).

The main difference from Windows, though, is that I've never, *ever* had to solve a Linux distro issue by reformatting. I've had to boot into rescue to edit files, sure, but in over 20 years of running Linux, I've never had to completely nuke a system in order to "save it" from a broken update. In fact, I think the only time I've had to do so was way back when I had to tweak my own storage drivers.

Re:It isn't only Windows 8

[phantomfive]

That may have been a consideration in the 80s, but it's not a good reason to do so now.

Re:It isn't only Windows 8

[phantomfive]

Windows doesn't do font processing in the kernel

then where did this come from?

Re:It isn't only Windows 8

[Ol Olsoc]

Do you have any proof of this? I actually run Windows 8.1 Update 2 (x64) with Windows Update set to only notify me of updates. No updates from Microsoft have been installed without me explicitly installing them.

Well, only that I had updates turned completely off, and on several occasions my wife told me the computer was sluggish and acting weird. I shut it down, and lo, an update. The only update I ever purposely allowed was to 8.1.

I'm not the only one, and this link was regarding Windows 7:

http://superuser.com/questions...

It certainly isn't a new phenomenon, here's one from 2007

http://blog.seattlepi.com/micr...

Hey - maybe we're all just kooks? http://answers.microsoft.com/e...

Install an update when you have them turned off? No Problem Microsoft turns them back on.I've had this happen several times. Apparently Microsoft doesn't do this - it's always the customers fault:

http://social.technet.microsof...

Windows 7 users have noted:

http://www.sevenforums.com/win...

Windows 7 users have been having a big problem with some sotfware I regularly ue. They have an update that breaks the software, and they roll it back, and turn the auto update feature off, but next black tuesday, it reinstalls the offending update.

Re:It isn't only Windows 8

[Espectr0]

I only reboot windows once a month after patch tuesday.
Crappy experiences are mostly gone since 7 (and in my case, since Vista as well. I experienced only one major bug in vista, slow file copying which was fixed in SP1)

Re:It isn't only Windows 8

[Ravaldy]

I honestly haven't found a Linux distro outside Ubuntu that is easy to install on just about any hardware. So for 99% of users with Windows systems, they will just have to deal with this rare failed update scenario. It's really not the end of the world as some may picture it to be.

Re:It isn't only Windows 8

[Zero__Kelvin]

"Then you know absolutely nothing about software development ... Whats better is that you're claiming that Windows 8 drivers that don't work on Windows 7 caused the same problem for you.

Perhaps the OP doesn't know about software development, but unlike you, he can actually read.

Re:It isn't only Windows 8

[Zero__Kelvin]

"which Russian versions of Windows use instead of ASCII since the American Standard Code for Information Interchange doesn't support Cyrillic characters"

Holy Shit! How do people from England use Windows if it only works in America!!!?? Code pages are based on another American standard, the American National Standards Institute. But fear not my antiquated friend, for even in America we've heard of other countries! That's why the ANSI committee did the unthinkable and created code pages for all kinds of languages including the ruskies! There's even this new-fangled thing called UTF now!

Re:It isn't only Windows 8

[Algae_94]

I've had many computers. TRS-80 (No Problems) DOS 4 to 8 (No Problems) Linux (No Problems). Now we get to Windows. Win95, Win98, Win98SE, WinXP Pro, Win7, Win8 all on different hardware and legal. All of them freeze up, BSOD's, hardware/driver problems, generally a peace of $hit. Friends and family report the same problems. Anyone that says that they don't have problems with windows must be working for M$. When you get tired of paying for malware, try Linux.

Well, then I expect my check any day now. I've had problems with XP, but everything I've used with 7 or 8 have not had any BSODs, or other major problems. I skipped Vista so I can't say where that compared.

That's not to say everything is perfect with Windows, but these regular and common freeze ups and BSODs do not occur for me anymore.

Re:It isn't only Windows 8

[SuperTechnoNerd]

Windows is always talking to MS. For example, do a local file search, it opens a connection to microsoft servers. I haven't looked deep into what it sends, but why connect at all?

Re:It isn't only Windows 8

[Ol Olsoc]

Those people were not disabling updates (ie. option #4).

One universal truth in all of Microsoft's updates or any problem. It is the users fault no exceptions, Microsoft has never been at fault ever.

Are you also sure that your wife didn't inadvertently reenable them?

Very unlikely, unless you can re-enable Windows update from Firefox, Thunderbird, or solitaire.

When updates are disabled, the Windows action centre will pop-up a security notification from time to time from the system tray unless you explicitly tell it to ignore the status of the auto update mechanism.

She's been told to ignore popups of any sort. And does

And it of course continues.

Some of us have our limits though. I am a fucking idiot, and all the problems I've ever had with Microsoft are of my own doing, I am responsible, not them.

Which is exactly why I switched to OS's where I am not an idiot.

Re:It isn't only Windows 8

[jones_supa]

It is serious bug. It makes big amount of laptops overheat.

Re:It isn't only Windows 8

[sjames]

Missing a driver for new hardware is hardly limited to Linux. In fact, I have run into that problem FAR more often with Windows even though I've done far fewer Windows installs. Unlike Windows, in Linux I can generally get around the problem by loading the relevant non-distro driver onto a flash drive (or my phone) and manually insmoding it at the start of an advanced install. An alternative approach is to use a well supported USB network adapter to complete the install, then load an out of tree driver for the network hardware.

As for Jessie, it's called testing for a reason :-)

Re:It isn't only Windows 8

[Ravaldy]

I wasn't talking about Ubuntu. I was saying that people can deal with the one time occurrence of a Windows Update bug. It's much less trouble than to get onboard with any Linux distro.

Re:It isn't only Windows 8

[dotwhynot]

That may have been a consideration in the 80s, but it's not a good reason to do so now.

NT3.x was on the right path as a fairly well implemented micro-kernel OS, with graphic subsystem completely in user space. This was changed with NT4 for performance and compatibility reasons. (or, what we asked for, where we=market). There was a reason a lot of us clinged to our NT3.51 and refused to "update", like others cling to Win7 now.

Re:It isn't only Windows 8

[beastofburdon]

Do you know what site it connects to and the protocol? If they are different from the update site or a different protocol it could be easily blocked while still allowing you to update. I would really like to know if you can find out.

Re:It isn't only Windows 8

[jenningsthecat]

I had already long-ago banished Pulse from my system - I've never liked it and always had problems with it. (Not surprising that systemd and pulseaudio are from the same developer). Anyway, I actually got desperate enough to ADD pulseaudio to try to fix the audio. It restored functionality in some programs but not others, and I was unable to sort out the 'default device' problems. (Not that I was too motivated - having broken two critical functions with one update had soured me on Jessie).

And now I'm on Xubuntu, which comes with Pulse installed by default. I don,t love it, but sound works now so I'm inclined not to dick with it.

Re:It isn't only Windows 8

[jenningsthecat]

Missing a driver for new hardware is hardly limited to Linux... An alternative approach is to use a well supported USB network adapter to complete the install, then load an out of tree driver for the network hardware.

I considered doing that so I could install Wheezy, but I didn't really want to jump through hoops to install an older version that would have required me to try backporting for the newer versions of Kicad. And in Wheezy, Suspend functionality didn't even work on my old box, so I wasn't keen to try it on a new one.

As for Jessie, it's called testing for a reason :-)

I know, I know... But I ran what became Squeeze and Wheezy when they had only spent a few months in Testing, and I only ever had minor issues, so I came to think of Testing as being pretty solid. I guess I got complacent...

Re:It isn't only Windows 8

[jenningsthecat]

...If only there was a Debian based distribution which did not force the systemd into their users.

Ubuntu doesn't use systemd. Yes, I know it might be a stretch these days to call it "Debian based", but at least it still uses Debian packages, and I've even pulled stuff in from Debian repos with no trouble so far. I've uninstalled the cutesy 'Software Center', and I either use apt/aptitude from the command line, or Synaptic, depending on what I'm doing. My Xubuntu setup 'feels' very 'Debian' to me, without the downside of systemd.

Re:It isn't only Windows 8

[sjames]

It is easy to get complacent about that since even testing is usually quite stable, it's just not promised to be.

It is worth considering though that it is nice that installing stable and backporting is even an option. For an individual perhaps it's not worth it, but in a corporate environment it might work out to be reasonable.

some 19 years on...

[Anonymous Coward]

"Windows 95 will get rid of all Unrecoverable Application Errors"

Re:some 19 years on...

[BitZtream]

Chicago pretty much did (ignoring driver flaws) ... until they added backwards compatibility.

Misleading article

[Anonymous Coward]

Its a new feature they're introducing.

LOL windows restore

[Anonymous Coward]

good luck with restore as you cant boot into "safe" mode, so if you didnt create a rescue disc or bootable usb (nobody does and you fucknig know it) you are up shit creek (moreso if you have a software RAID)

The state of engineering in PC recovery is awful, shame on software devs

Re:LOL windows restore

[bill_mcgonigle]

The state of engineering in PC recovery is awful, shame on software devs

What? You just power off your vm, roll back the storage to the appropriate snapshot, and turn it on again.

Wait - you let Windows touch your hardware? Oh, my.

In other news...

[djupedal]

Microsoft announced they will change from calling their software 'software' to 'cute puppy' in bid to distance themselves from their reputation as they have now run out of feet to shoot and stick in their mouth.

Re:In other news...

[SeaFox]

I wonder if Microsoft has considered changing their name to distance themselves from their reputation for the software they produce.

Re:In other news...

[Tablizer]

This latest puppy is shittin' all over the carpet.

This update deleted my "All Programs" list

[PilotKnob]

I'm going to have to reinstall Windows 7, and I can't tell you how excited I am about this.

Re:This update deleted my "All Programs" list

[ElderKorean]

I'm going to have to reinstall Windows 7, and I can't tell you how excited I am about this.

What about your backup, restore to that.

Re:This update deleted my "All Programs" list

[Anonymous Coward]

Use System Restore in Windows 7. Start up the pc and when you see the first text on the screen, press the F8 button and then choose Safe Mode with Command Prompt. Type: rstrui.exe

For XP users:
%systemroot%\system32\restore\rstrui.exe

Now you can use your mouse and choose a date to go back to before the problem.

Re:This update deleted my "All Programs" list

[Cutterman]

Unfortunately rstrui.exe is a GUI rather than a console app so if your GUI fonts are messed up it is unusable.
rstrui needs to be a console app

The Cutter

 

Re:This update deleted my "All Programs" list

[Nimey]

Heh. Back in the day there was a certain group of users who'd disable System Restore out of concern that all it did was back up viruses.

Forget TFA

[Anonymous Coward]

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

Re:Forget TFA

[Anonymous Coward]

What does that say that the article doesn't?

Re:Forget TFA

[sa1lnr]

"If you do not have media, you should use the power button to restart your computer during the startup process three times. This should start the Windows Recovery Environment. "

In fact not so much horse shit as you assumed.

Re:Forget TFA

[David_W]

"If you do not have media, you should use the power button to restart your computer during the startup process three times. This should start the Windows Recovery Environment. "

Oh yeah, THAT's gotta be good for the hardware. Definite improvement over F8. Thanks Microsoft...

Re:Forget TFA

[benjymouse]

"If you do not have media, you should use the power button to restart your computer during the startup process three times. This should start the Windows Recovery Environment. "

Oh yeah, THAT's gotta be good for the hardware. Definite improvement over F8. Thanks Microsoft...

It is actually quite clever: If the system barks 3 times in a row when trying to start, the operating system *should* infer that something is preventing an orderly startup. In that case, dropping into the recovery console is a perfectly good choice.

NTFS has volume shadow copy on by default for the system drive. It records changes to the *system* (Windows/** and Program Files/**) and lets you roll back those changes without rolling back any user/data files.

So even if you f***** up so royally as to make the system unbootable (e.g. a bad disk driver), the system will boot into the recovery console with a minimal number of known "basic" drivers.

Re:Forget TFA

[robsku]

And who the hell is this General Failure anyway, and why is he reading my floppy drive!?

their new motto

[slashmydots]

Microsoft: "Where we don't really give a shit until Windows 9 comes out"

Re: their new motto

[Anonymous Coward]

Windows 9 "You have no choice but to upgrade".

Solid marketing move there.

Re: their new motto

[Anonymous Coward]

Windows 9 "You have no choice but to upgrade".

Solid marketing move there.

Perfect marketing for Linux: Windows keeps crashing and Microsoft says the only fix is to upgrrade, so I upgraded to Linux and now everything works perfectly and is far faster then it was on Windows and I can keep right on gaming as Steam, GOG, Desura and Humble are all providing the latest titles!

Re: their new motto

[robsku]

FUD Reichmeister strikes again. Nothing works perfectly for every(one|thing) when it comes to OS's, so your partly right, although when the comparison is with MS Bullshit...

I've learned the hard way

[msobkow]

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.

Re:I've learned the hard way

[kesuki]

"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. "

thats not a bug, thats a feature... you've heard of vendor lockin and planned obsolescence...

Re:I've learned the hard way

[jones_supa]

The nice thing about Windows Update drivers is that they sometimes allow you to install the the sole driver instead of the 300MB garbage pack from the vendor. :)

Re:I've learned the hard way

[mrprogrammerman]

I generally avoid driver updates unless I know there is a specific problem I am experiencing that is fixed. Got burned too many times.

Re:I've learned the hard way

[jones_supa]

It's a bit amateurish to dismiss the parent with the classic "it works for me, there must no problem". For example, maybe your university machines were mostly the same brand of conservative desktop machines which had quite basic hardware with well-tested interoperability with Windows Update? I mean, if you have a bunch of HP or Dell machines with Intel integrated graphics, the chances of things exploding are probably lower than with some more hot rod hardware.

Re:I've learned the hard way

[phantomfive]

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

That's a good strategy, but one of the offending patches was a change to include the new symbol for ruble. It wasn't a driver update.

Re:I've learned the hard way

[symbolset]

No, it has always been this way. And their internal documentation is also crap.

Re:I've learned the hard way

[Ravaldy]

I bet you also believe those self proclaimed scientist that swear the pyramids were made by aliens.

Those conspiracies are as true as those stories of me having big dick The H/W manufacturers have had it figured out for a long time by simply not releasing drivers for the next OS that comes out. The last thing H/W manufacturers want is your call to support or a RMA request.

Re:I've learned the hard way

[Ravaldy]

I have supported Microsoft workstations for over 10 years and have never experienced a hardware failure due to an automatic update. Heck, I had maybe 3-5 problems related to auto updates that were caused by security enhancements and they didn't actually break anything, rather they defaulted values that I just wouldn't have set for my environment.

I suspect you are an isolated case because if that's how poor MS products were, they would not be trusted by any IT department.

Re:I've learned the hard way

[X0563511]

I've never seen that happen, even when accidentally installing the wrong drivers back in Windows 98, when shit could actually catch fire instead of just crashing!

Re:I've learned the hard way

[phantomfive]

Um, I have?

is this BETA?

[the_fat_kid]

I thought for sure that I had missed the [Satire] tag

Connected to mass layoff of Windows SDETs? Maybe?

[xeno]

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.

It's pretty hard to roll back automated updates

[Brulath]

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.

Re:It's pretty hard to roll back automated updates

[danknight48]

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:It's pretty hard to roll back automated updates

[benjymouse]

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.

Wrong. Fastboot hibernates the kernel but not the userland processes. It depends on drivers being capable of quickly re-initializing hw devices, but what it does is it brings up the kernel from a hibernated image and skips most of the usual hardware detection and device initialization.

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.

Really, really stupid advice. System restore has N previous versions of your driver setup. You can reliably go back in time for the operating system but retain any changes to user files. It is stupid to NOT use system restore. Whenever you install a new driver, the system *will* retain the old files, registry settings etc as shadow copies. It is a well-tested and stable way to go back in time with your os.

Re:It's pretty hard to roll back automated updates

[danknight48]

System restore has N previous versions of your driver setup. You can reliably go back in time for the operating system but retain any changes to user files. It is stupid to NOT use system restore. Whenever you install a new driver, the system *will* retain the old files, registry settings etc as shadow copies. It is a well-tested and stable way to go back in time with your os.

I love how even you had to highlight "reliably". Its a known issue with windows system restore, hence why you should never use it.

If you want reliable system restore:
- Ghost or DD your HDD.
Ideally a fresh install on your system, to ensure you get a clean OS to start with.
If you image the drive without installed drivers, you can quickly install fresh/updated ones if you restore. Preventing any old drivers causing issues (cough AMD+CCC)

- When shit hits the fan, or, you cant be bothered to fix it, or, you just want a fresh install,
simply restore the backed up image. Boot with a USB linux disk to recover any files before hand if required.

Thats the method i used for many many years, at home and at work.
Not only does it improve windows performance (by disabling system restore), its alot quicker and reliable method of restoring your system.

Re:It's pretty hard to roll back automated updates

[Trogre]

For a FLOSS alternative to Ghost I now use and highly recommend Clonezilla.

Pending Restart..

[craznar]

So - my system has installed KB2982791 and is pending a restart.

How on earth do I remove it now, before restarting a system that may never restart ?

Re:Pending Restart..

[djdanlib]

You can't always, but you can prepare a recovery disk and also burn a copy of HBCD before your inevitable power cycle or reboot.

Re:Pending Restart..

[dwywit]

There were some posts in one of the microsoft support forums that indicated removing %system%\FNTCACHE.DAT resolved the problem. That led to discussions that it might have been systems with a large number of installed fonts that were vulnerable.

Windows will automatically replace FNTCACHE.DAT, so removing it won't hurt.

Re:Pending Restart..

[craznar]

I suspect you don't understand what 'pending restart' means in the context of updates.

For some it was just a plain black screen

[Anonymous Coward]

Windows not working at all. It seems like the right time for Linux on the Desktop to make some headway.

never update windows on patch day, wait a week

[Nyder]

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.

Re:never update windows on patch day, wait a week

[E-Rock]

Or, there's a lot of different windows configurations and they can't test them all. We updated a few hundred machines last week, zero problems. Sounds like we got lucky, but it's not as if these problems nuke every machine.

Reference?

[jamesl]

This post and the linked article say, "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."

I note that neither this post nor the linked article reference or link to a specific instruction from Microsoft. Is this a joke?

Re:Reference?

[pslytely psycho]

http://support.microsoft.com/kb/2982791

Reference Known issue number 3.

The linked report is rather dull, lacking all of the OMG DEAD COMPUTERS EVERYWHERE, aspect.
It does confirm the problem, and states downloads were removed, followed by what appears to be (only glanced at and did not actually read) detailed instructions for 7/8 to remove the updates if you were negatively affected.

This is why I always wait one week and do my updates manually on the advice of a wizened old computer guru I knew years ago.

Field day for hackers.

[whoever57]

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.

Re:How about win 7?

[50000BTU_barbecue]

Yes I can confirm that on my Windows 7 Home Premium SP1, the 2982791 update was present and it's removable.

10 LET M$ = "Microsoft"

[tepples]

It's been M$ since the 1970s, back when Microsoft was a publisher of BASIC interpreters and names of string variables in BASIC ended with $.

Re:10 LET M$ = "Microsoft"

[phantomfive]

Well you got downmodded for that one. I guess people around here don't remember BASIC anymore.

Killer apps

[tepples]

"App" has been short for "application" before the introduction of OS X, let alone iOS. The definition of "killer app", for instance, came up during the Microsoft antitrust trial.

Developers remix

[tepples]

But the old boss is BOSS.

They fired 30% of their testers

[Anonymous Coward]

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.

Re:They fired 30% of their testers

[symbolset]

I suppose if you wanted a font of information about disastrous bugs marked "ship anyway" and unreported faults, you could do worse than a suddenly terminated tester.

Re:They fired 30% of their testers

[david_thornley]

Of the remaining 70%, the competent ones are updating their resumes and checking out other employment, although it's a bit early to do so after the layoffs. Remember, Nadella said layoffs would continue for about a year, in one of the stupidest moves I've seen a CEO not named Elop make recently (assuming Elop was acting out of incompetence rather than malice).

How many people will do this?

[tsa]

Since most people on this planet are not tech-savvy and don't read sites like /., I wonder what percentage of Windows 8 users will actually do the things Microsoft recommends.

delete fntcache.dat fixed some people

[clovis]

It appears that booting into recovery, or using a standalone Linux distro, and deleting C:\windows\system32\fntcache.dat solved the problem for some people, if not all of the ones who tried it.
There are other problems with the patches regarding fonts, but at least you'll be able to boot.

a case of the Mondays

[slashmydots]

One of the Window 7/8 glitches basically went like this. I changed the kernel mode drivers and now I'm going to reboot. Hey, it looks like a glorified temp file called fntcache.dat that's a cache for font-related stuff is corrupt. Should I keep loading the OS? OH HELL NO! Fuck everything! I quit! *blue screens*
Mega case of the Mondays. Seriously, who coded it to crash the entire OS if a font cache seems to be a bit off instead of regenerating or renaming it?

Re:a case of the Mondays

[phantomfive]

Seriously, who coded it to crash the entire OS if a font cache seems to be a bit off instead of regenerating or renaming it?

The same people who decided font processing in the kernel is a good idea.

Re:a case of the Mondays

[gtall]

You cannot just move font processing out of the kernel. To do remove kernel stuff piecemeal is asking for a system slower than Steve Ballmer's thought processes. The thing has to be designed from the get-go to be a lightweight kernel or else the machine spends all its time process swapping.

Re:a case of the Mondays

[phantomfive]

You cannot just move font processing out of the kernel.

Yes, yes you can.

Re:a case of the Mondays

[robsku]

windows: where only way to make font processing fast was to do it in kernel spacen. What a crappy OS.

Upcoming fix?

[Animats]

Will this be fixed on the next Patch Tuesday? I haven't been using the Windows macines much lately, but one is powered up, idle, and accepting updates. Will it fix itself?

Re:Upcoming fix?

[symbolset]

If it machine checks its performance as a space heater will be slightly reduced, as the lack of spam zombie workload will leave it in an idle state.

For Win9, MS should go back to Service Packs...

[BUL2294]

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...

Re:For Win9, MS should go back to Service Packs...

[simplypeachy]

At least with Service Packs you knew that it was complicated and had a lot of updates to install, and were aware it could hose the machine. I've come to expect Microsoft's monthly updates be trouble-free, because they are almost every single occasion.

Re:For Win9, MS should go back to Service Packs...

[BUL2294]

Generally speaking, old-school Service Packs were both the bundling of hotfixes and new kernel-level features (e.g. USB 3.0, 4K drive sectors, UEFI support, etc.). In the world of Win7 and lower, Patch Tuesday was generally limited to security fixes and parameter changes (e.g. daylight savings time changes). Microsoft would also make available optional updates to Windows components (Internet Explorer, Media Player, etc.) that you could apply as desired.

This model isn't true with Win8.x. They're putting out kernel/feature updates every few months, trying to appear more Agile. A few months back, there was a mini-furor over Update 1 in that you had 30 days to test & apply it to your systems, or get no new updates. There was no beta of the release code that administrators could test ahead of time, as was customary with Service Packs. Some users flipped--specifically companies. Microsoft backed down a teeny bit, but only offered to create a branch for those who wanted to hold off on Update 1--for one extra Patch Tuesday cycle (4-5 weeks).

Re:For Win9, MS should go back to Service Packs...

[BUL2294]

In addition, the "monthly updates" are generally security fixes that exists to solve a security hole--where proper interaction with the component shouldn't cause problems before or after the applied fix. They generally solve one security problem within the component (e.g. buffer overflow at xxxxxxxxxxxxxx when called by yyyyyyyyyyyyyyy). That's why they've generally been trouble-free. Microsoft has recently gone on-record stating that Patch Tuesday will now be getting more such non-security feature updates, and they won't be optional.

Re:For Win9, MS should go back to Service Packs...

[OfficeSupplySamurai]

I find it ironic that you say Microsoft should not try to be Apple and talk about how old-fashioned it is to release service packs, when in fact that's how Apple does OS updates. Apple tends to release large updates to OS X all together (10.x.y releases) rather than a lot of smaller updates with individual security and bug fixes and so forth.

Re:How about

[Anonymous Coward]

Because Gnome is better than KDE.

Re:Wait until SP1/SP2 before buying ?

[DingerX]

They don't do SPs any more. Calling them "Mandatory Updates" allows them to get around any promises they made regarding SPs. Oh yeah, and this update? I'm not affected, since my machine is still unable to install the mandatory update.
WTG Microsoft. You should be glad that platforms are not part of your core mission.

Problem analysis

[lskovlund]

A 'softie has posted a reasonable-looking problem analysis here (look for the screenshot) and corroborated later in the thread. So, it's a problem with shortcuts to OpenType font files... which impacts e.g. Photoshop users. Nice.

Best Fix

[Murdoch5]

Upgrade to Linux and don't look back.

Mostly trouble-free

[swb]

Which is kind of the problem, because it is trouble free so it's kind of easy to get complacent about them.

I kind of wish they would create cumulative update bundles that could be installed the old way or to machines with limited online capability. It's just not practical to track individual updates and I've found third party software that creates offline repositories to be kind of hit and miss.

Who uses auto update?

[gelfling]

Seriously, who? You should be about 90 days behind the curve with updates if you want to have a hope of not getting Satan Fucked.

Re:Who uses auto update?

[robsku]

Some of us prefer getting satan fucked, you insensitive clod!

Re:Am I the only around here

[Zaiff Urgulbunger]

Yes. NT6 was the turning point when Windows became more useful than Linux for me.

Vista? Really? I mean, if you'd said 6.1 then that would seem more plausible!

Re:How about

[michael_rendier]

I use fluxbox, because both gnome and kde are bloated and eat my processor just to sit there and do nothing...

Easy to avoid...

[mr_resident]

I only upgrade to versions which end in a even number. Works every time!

But then again, I only upgrade after taking my left shoe off, so that might be a factor too.

Re:Easy to avoid...

[steak]

In the past, for me, it was odd numbered versions of fedora; for what ever fedora core 2, 4, 6, etc. never worked right. 1, 3, 5 perfect. That seems to have changed though as just about every linux distro I have tried recently works right out of the gate.

Or the backlight

[phorm]

My current favourite is laptop backlight support. I haven't figured out if it's an issue with recent kernels or the recent fglrx drivers, but the last update gave me a blank screen after X starts. Several people have reported it, mostly Asus laptops but also some Toshiba I believe.
Or at least it looked blank, until I took it into a room with good light and discovered that - hey - the backlight is just dialed down to zero. So now my choice is no vendor-accelerated driver, or no using the LCD :-(

Re:Am I the only around here

[robsku]

I have lately ran win 7 on one of my system and still get annoyed of it's lackings. Even though it's best of windows systems so far, that really does not mean much.

We just can't win...

[iq145]

i doubt we ever will

Re:How about

[beastofburdon]

(readies bucket of gasoline)
You're full of shit! KDE is by far the superior desktop!!!!!

Re:How about

[beastofburdon]

I'll give you that one, but KDE is getting much better about its overhead. It will obviously never get down to the point of fluxbox, but should be entirely useable even on 5 - 10 year old hardware.

Re:Go back to Debian stable...

[jenningsthecat]

why I haven't addressed your specific issue with networking? I have no idea what it might be and without lots more detail -totally out of the purview of this forum- no one would.

Thanks, but I wasn't looking for that anyway. I used to love doing things TO my computer, but I've gotten to the stage where I'd rather concentrate on doing stuff WITH it, and I no longer have much patience for tracking down this kind of problem. Changing to Xubuntu was simpler, and aside from the Windows-like rebooting after updates, it's been pretty good.