Windows 8.1 consumers: It's time to move to Update 1

Windows 8.1 consumers: It's time to move to Update 1

Summary: June 10 is the Microsoft-imposed deadline for Windows 8.1 consumers to move to the Windows 8.1 Update in order to continue to receive future fixes and patches from Microsoft.


Today, June 10, is Microsoft Patch Tuesday. It's also the deadline for consumers running Windows 8.1 to install the Windows 8.1 Update if they want to continue to receive patches and fixes from Microsoft.


Microsoft originally imposed a deadline of May 13 on consumer users to move to the Windows 8.1 Update. On May 12, Microsoft announced a deadline extension to June 10.

Business users still have until August 12 to move to the Update for Windows 8.1 and Windows Server 2012 R2. Microsoft extended the deadline for those updating using Windows Server Update Services (WSUS), Windows Intune, and/or System Center Configuration to update users' machines. Microsoft execs unveiled the new deadline in mid-April after outcry from some that Microsoft wasn't giving them enough lead-time to apply the update.

Consumers running Windows 8.1 who have Automatic Updates turned on don't need to do anything; they should have received the Update automatically via Windows Update by now.

Users who are on Windows 8, not Windows 8.1, are not subject to the requirement to move to Windows 8.1 Update by June 10. (Microsoft has set January 2016 as the end support date for Windows 8 users who haven't moved to 8.1.) Those running Windows 8 who are interested in moving to Windows 8.1 Update do not need to move to Windows 8.1 first, as these updates are cumulative. 

The Update for Windows 8.1 included a number of new features designed to make Windows 8.1 more easily navigable by those using keyboards and mice. 

Here's an early look at what's in today's Patch Tuesday pipeline.

Topics: Windows 8, IT Priorities, Microsoft, Security, IT Policies


Mary Jo has covered the tech industry for 30 years for a variety of publications and Web sites, and is a frequent guest on radio, TV and podcasts, speaking about all things Microsoft-related. She is the author of Microsoft 2.0: How Microsoft plans to stay relevant in the post-Gates era (John Wiley & Sons, 2008).

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • About time

    I've been using 8.1 for so long I forgot how bad Windows 8 actually was until I got a new PC recently that came with it installed.
    • Funny, I just installed 8.1...

      ... and haven't noticed anything different.
  • I wonder if they are considering changing

    windows to a "rolling distribution" with subscription or something? Instead of just patching a windows version, its considered a new windows version, maybe every month. This would be like chrome OS, for example.
    • Microsoft has always ended support for each service pack shortly after ...

      ... its successor service pack has been released. Nothing new at all.
      M Wagner
      • But, a Windows SP traditionally gets support for 2 years

        After the next SP is released. So, Windows 7 RTM stops being supported two years after Windows 7 SP1 is released, and SP1 looses support two years after SP2 is released.

        This is a much more aggressive schedule. But, then again, if you are using Windows 8.1, I'm not quite sure why you'd hesitate moving to 8.1 Update, no real changes in functionality, only in overall "fitness"
        • You may find

          At some point Microsoft will need to "re-work" their sunset or cycling policy. No more of this "is good for 5 years kind of thing" you'd get with typical versions, service packs or R# releases. There is no way any Company on the planet would be able to keep up with something like this for that long a period. In other words as Microsoft increases their release cadence, which they obviously have, this will, at some point mean they will end up with a myriad of versions of each of their products - they simply will not be able to support that many versions like the "old days" where they had a big release every few (or more) years. Again at some point this sunset/cycling schedule will need to change. Gone are the days of supporting a version for 10 years. With an accelerated release schedule which MS has obvioulsy adopted, they will only be able to support a few versions back because they will simply have too many versions of that particular software, as most of their competitors also have experienced. Simply the way the industry has and is headed.
          • Then MSFT may find

            That the industry moves away from them. People don't just upgrade systems the way they used to. I understand that MSFT can't support OS versions indefinitely. They took care of XP for a long time beyond any reasonable cycle. Still, how many months is this for 8.1? Not even a year. At work, we didn't go from XP SP2 to SP3 on a number of machine for well over a year. Because doing so broke some systems. And we're big enough to go to MSFT directly for support.

            But I've heard that some machines that worked fine with 8.1 can't be updated past that. The update simply won't install. Not a large percentage to be certain, but still serviceable systems. For a .1.1 release? So now, no new fixes? Correct me if I'm wrong, but I don't ever recall anything beyond an integer number version change causing that. Even then it would typically still install, even if it ran poorly. So MSFT finally does something right about bloat and makes an OS that has less system requirements than the previous version. Then they turn around and make it so you can't run it anyway?

            If this is just a chance event and not a harbinger for things to come, all well and good. But if it becomes more frequent or even common, that isn't going to help their adoption rate for the new OS and its successors.

            I was thinking recently that if MSFT really wanted to move XP users to 8, they should offer an limited edition upgrade for only XP. Say for $20-25. Something that wouldn't eat much into upgrade/new PC sales for people who wouldn't do it otherwise. A concrete way of helping some of those stranded with XP (good PR). I have a couple of Core 2 Duo machines that could run 8 pretty well, since my last gen dual core Atom tablet does a decent job of it. Except now, maybe that isn't an option.
          • Then the Industry will have no where to move to...

            ...Everyone is moving this way. This isn't unique to Microsoft. Historically lazy IT departments who languish on outdated patches can't sit on their hands anymore in this dynamic age of BYOD.
          • That said.

            I agree with your idea of giving XP squatters some incentive to move up.
          • People have to decide

            they moan that Android doesn't get updates.

            OS X users get pretty much force-upgraded on a very quick cycle, until their hardware gets left behind, then they are SOL unless they buy a new machine, but hardly anyone complains. The same with iOS.

            And yet they moan that Windows is getting updated at a similar pace to the other operating systems now...
        • reasons not to upgrade

          not all machines function with the upgrade. my friends computer crashed after the update and the manufacture sent her a thumb drive she has to have in at boot up and leave in for the computer to work.
      • Arggghh, you MS apologists.....

        drwrong was making a suggestion to improve the MS update/upgrade process. The fact that "it's always been done that way" has been the biggest impediment to progress throughout human history. There's always room for improvement, particularly at MS.
  • Windows 8.1 consumers: It's time to move to Update 1

    I've been upgrading everyone to Microsoft Windows 8.1 Update 1 whenever I come across their computers. I can't see many reasons why anyone would have turned auto update off especially on the consumer side.
    • Too many people have had their systems destroyed

      and work lost.

      Good administrators either test it out themselves first...

      It is not good for a business to be bricked for a day or two while MS gets around to recalling a bad patch...
    • Sure you have, Lovey

      You've been running down to Microcenter and picking up the win8 install disks for all your "friends". Didn't realize how charitable you could be, particularly since living on your minimum wage job at Mickey D's must put a strain on your IT budget. Good thing your Mom's not charging you rent for the room in the basement behind the laundry room. Isn't that her now, calling you up for dinner?
  • About that automatic update

    One of several example threads of folks impacted by the inability to get KB2919355 installed.

    Mary Jo, let me introduce you to those folks who should have KB2919355 and because of system corruption of unknown origin (mostly due to merely using their computers) can't get the @#$!@# patch installed.

    These are the minority that Microsoft is trivializing. Support cases are not working to fix the problems, the only thing that is a repair install. However because these are consumers they don't have proper media so they have to roll back to whatever media they have - Windows 8, go through the store again to get back to a working machine.

    This is one of several threads of folks impacted. It's making these folks feel like Microsoft doesn't care about them.

    It should be a concern for all of us that 8.1 can get into a state that no amount of DISM commands are working to repair the machines. It's great that the majority have it installed. However the impacted minority should have us all concerned that something is wrong with the installation process.
    • re:About that automatic update

      If someone can corrupt a computer simply by using it then you have to ask the are they using it and what are they using it they update they have virus protection etc stuff thats often ignored. An example..I experienced update trouble in the past but thats only because i uxthemed windows 8..looked great but stuffed would be more concerning i would have thought if the minority had no trouble updating.
      • It's not the user here...

        Most of these customers have antivirus software, some report the corruption even occurs with the OEM recovery media.

        Microsoft support points to antivirus as being one cause of system corruption in fact.
        • Then perhaps they should be using Microsoft's built-in AV protection.

          Besides, users are notorious for ignoring AV nags to update - and to renew their AV licenses.

          Often AV software interferes with software installs and needs to be disabled first.

          All this to say that, if all else fails, following Microsoft's recommendations is often the best advice you can take.
          M Wagner
          • Cases I've opened

            In the cases I've opened, it's not out of date antivirus. And last I checked, Microsoft supported an ecosystem of software.