- New Update for Windows 11 24H2 Packing Gaming Fixes were paused for some PCs
- These devices had a ‘compatibility problem’ which means they needed a revised update
- Microsoft said this fine -tuned update should be out for all Windows 11 users now but some are still reporting they don’t have patch
Windows 11’s latest update has arrived, packing important corrections to PC players running version 24h2 of us, but it has suffered an unusual technical error that causes some confusion.
Windows most recently noted that Microsoft hit the break button with the roll -out of the June update (formally known as KB5060842), at least for some users after it started to be implemented yesterday.
As Microsoft let us know via Windows Message Center: “Note: This update is gradually rolled out to devices running Windows 11, Version 24H2 throughout the day. We have identified a compatibility problem affecting a limited set of these devices. If your device is affected, you will receive a revised update with all June 2025 security improvements at the end of the day.”
Microsoft did not specify what the compatibility problem is, but given the language used in the form of a ‘limited’ amount of units affected, the problem is being played down.
But when you look at a couple of Reddit threads – primarily the official announcement of the patch from Jen Gentleman from Windows Engineering Team – there are quite a few confused Windows 11 users wondering where their update is. There are also people with several PCs that indicate that you have received June -Patch, but others do not have it.
In theory ended yesterday yesterday a few hours ago (based on American Pacific Time, as used in Microsoft’s post at the Message Center) – and therefore all should have the patch now. (Either the original or fine -tuned update to solve the compatibility roll, which apparently has a slightly different version number).
However, there are comments on the above -mentioned Reddit wire towards: “Isn’t it over midnight now? Still no update yet. What happens to this ‘compatibility problem.'”
Analysis: What happens – and what is it anyway?
Microsoft may have slipped with its deadline here. I would hardly be surprised if this is the case and it could just be a minor delay. What is a little more worrying, however, are some scattered reports of Reddit of people ending up with broken operating systems (frozen on green screens or black screens) after using this June update. There are not enough of these complaints to be really concerned yet, but this is something to keep an eye on.
Could it be people who accidentally got the update to a PC that is vulnerable to the compatibility error before Microsoft put the brakes on? Maybe, but it’s just guesswork. Still, if you become impatient – and players may be in particular – I will strongly advise against manually installing the June update if not led to your PC via Windows update automatically. Mainly because you may not receive it for a good reason, and by forcing the upgrade through, you may have encountered a showstopping problem.
In particular, players will be eager for the KB5060842 because this patch uses some crucial adjustments as mentioned at first. It includes the correction to problems with some PC games that lock together in Windows 11 24h2 and improvements with stability for NVIDIA GPUs (as well as a possible resolution for problems with mouse or keyboard delay). All this was seen in the preview version of this patch last month.
Another new feature that was introduced with this patch is CV devices across devices. This allows you to seamlessly resume work on OneDrive files between your PC and smartphone (and it will develop into a larger vision of this functionality in the end).
There are also a lot of exclusive forces for Copilot+ PCS, including an ASK Copilot setting for clicks to the DO feature, and a change that has come in from the left field that was not in the preview update in May. This is a limit of 60 days that are imposed on system recovery points, so from now on, restore points that are older than two months will disappear into the ether.
For the uninitiated, System Restore is a feature that allows you to take a snapshot of the current configuration of your PC in a working state, so if some kind of bug breaks destruction of your device, you can in theory (provided you can access desktop) return time back to that point. Not that there is any guarantee that it will work, mind, but it is an option worth trying when troubleshooting.
This is a feature that Microsoft has not affected for a long time, so why mess with it this way now? That’s a good question and I can’t think of a good answer, really. If I had to guess, System Restore may not be able to use as much these days so it will be scaled back.
