Microsoft auto-updates consumer PCs to Windows 11 24H2 — you can defer the update for five weeks

Windows 11
(Image credit: Shutterstock)

In a new blog post, Microsoft reports that it has reached a new phase in the gradual rollout of Windows 11 24H2. Compatible systems will be automatically updated to the latest release. Launched in October, Windows 11 24H2 has been plagued by a handful of jarring problems, including game-breaking bugs, persistent caches, and broken HDR. Recent patches have addressed most of these issues, and Microsoft is now confident enough to initiate automatic 24H2 updates for mainstream consumers. Note that this does not apply to managed systems.

The initial rollout began for Copilot+ PCs in June of last year. If you don't own an "AI PC," 24H2 launched as early as October but was marred by bugs and glitches, most of which have been fixed per Microsoft's blog. So, if your PC wasn't on the latest release, it will automatically be updated to 24H2. Note that this only applies to eligible devices running Windows 11 Pro/Home on the 23H2/22H2 builds, which no organization can manage.

After checking Microsoft's bug log, we found that many problems had been resolved. However, the potential for newer bugs still exists. Users can defer the update by up to five weeks using the "Pause Updates" feature in the "Windows Update" tab in "Settings." If you're eager to update, select the "Check for updates" option in the same tab to see if the update is available for your device.

Microsoft is aware of issues that have not been resolved, such as the Failure to install 24H2 on specific Asus devices, the camera's unresponsiveness on a handful of systems, unexpected behavior with wallpaper applications, etc. Note that affected devices will be put on a "safeguard hold" until these issues have been resolved.

Copilot PCs will get the most out of this update with the infamous Recall feature and other AI goodies. Sadly, these features will continue rolling out in phases for select devices under the Windows Insider Program. The good news is that Windows 11 24H2 promises faster update times and better performance for AMD's Ryzen CPUs. Intel mandates the installation of specific Windows 11 24H2 patches for optimal performance with Arrow Lake processors, even though our testing shows little to no improvements.

Hassam Nasir
Contributing Writer

Hassam Nasir is a die-hard hardware enthusiast with years of experience as a tech editor and writer, focusing on detailed CPU comparisons and general hardware news. When he’s not working, you’ll find him bending tubes for his ever-evolving custom water-loop gaming rig or benchmarking the latest CPUs and GPUs just for fun.

  • USAFRet
    Just to preclude the obvious comments...your PC almost certainly is NOT CoPilot/Recall capable.
    Reply
  • Gururu
    Been using it for at least a month now, nothing noticeable has changed.
    Reply
  • Alvar "Miles" Udell
    Installed it via ISO in November, haven't noticed any difference or issues, but that's to be expected on a well maintained non-OEM system from a build that doesn't have any major changes, and my 5950X still caps at 4.49ghz multi-core boost...piece of junk...
    Reply
  • USAFRet
    Alvar Miles Udell said:
    Installed it via ISO in November, haven't noticed any difference or issues, but that's to be expected on a well maintained non-OEM system from a build that doesn't have any major changes.
    Both my Win 11 systems updated naturally last month. Zero issues.
    1 non-OEM, 1 Surface.
    Reply
  • Dr3ams
    Have the 24H2 update since the 13th of December. No isssues with it yet.
    Reply
  • thestryker
    I've purposely avoided it due to having an ARL platform and manually installed 23H2 when I built it. Still not terribly enthusiastic about this update and really wish Microsoft wouldn't keep taking control out of users hands. I have zero issues with automatic updates and pushing people to do so it's the not letting them opt out part.
    Reply
  • OldAnalogWorld
    Fortunately for people, in the fall of 2024, the long-term construction project from MS - W11 LTSC - finally appeared.

    By the way, an interesting thing - modern versions of OS become obsolete, not when Microsoft says that it is all over, but when browser makers (the last of them) stop supporting this system and changes in the sites code are so great that the latest versions of browsers for this OS version can no longer cope with their tasks. Because for ordinary people, this support is key. As long as all sites work fine - they don't care about new versions of OS, only if there is something that will definitely force them to make some movements...

    This is conveniently able to bypass "long-term formal support". For example, W10 1809 LTSC formally has support until 2029. But if it has, then who will develop browsers for this version until 2029? But no. Browser makers will intentionally stop supporting it from 2026 for all versions W10, although they formally must support W10 1809 LTSC up to 2029 year... Moreover, this will be the first experience in history with such a throw, since before W10 did not exist a LTSC (LTSB) channel.
    Reply
  • Dr3ams
    thestryker said:
    I've purposely avoided it due to having an ARL platform and manually installed 23H2 when I built it. Still not terribly enthusiastic about this update and really wish Microsoft wouldn't keep taking control out of users hands. I have zero issues with automatic updates and pushing people to do so it's the not letting them opt out part.
    If you have the Pro version of Windows 11, you can refuse the update.
    Reply
  • OldAnalogWorld
    Dr3ams said:
    If you have the Pro version of Windows 11, you can refuse the update.
    This can be done in many ways and Home versions, but M$, as always, is counting on the ignorant majority, who, as usual, will accept their fate as another guinea pig (free alpha testers) for their own money...
    Reply
  • Notton
    I expect this forced update will brick 5~10% of PCs running Win11 and require a complete reinstall.
    Brickings will be 70% driver related. 20% firmware related and 10% other, my guess.
    Reply