Microsoft has released two types of feature updates in the past. Those that require just a small enablement patch for the upgrade and those that require a lengthy installation as they make fundamental changes to the underlying system.
The current feature update, Windows 11, version 24H2, belongs to the latter category. Users who have bypassed Windows 11 requirements now that these can be difficult to install, as the installation via Windows Update is blocked in this case.
Good news is that the coming feature update, Windows 11, version 25H2, will likely fall into the first category. Means, it is installed via a small enablement package.
News comes from Windows enthusiast Xeno, who discovered that the new feature update is based on the same base as version 24H2. This is a strong indicator that Windows 11, version 25H2 will install nicely and quickly on the majority of devices.
Note that this is only the case for upgrades from Windows 11, version 24H2. If you upgrade an older version of Windows, say version 23H2, then you will have to go through the lengthy installation process.
Microsoft has not announced Windows 11, version 25H2 officially, but it is certain that it will be released later this year (likely a bit earlier than last year’s feature update due to the smaller nature of it).
Anyway, that is good news for Windows users who have bypassed system requirements. While methods continue to be available to bypass the requirement checks, it is easier to not be bothered by them at all.
It is highly unlikely that Microsoft is going to release Windows 12, or whatever the next version of Windows will be called, this year. It would be the perfect time to get more Windows 10 customers to buy new PCs with the new version of Windows, but hey, what do I know.
Now You: do you have any expectations for Windows 11, version 25H2?
I expect it will reduce privacy and introduce new problems as has become the norm for M$ these days.
I’ve twice installed 24H2, only to have to roll it back both time. File Explorer would hang again and again, and was unusable. And I use it all the time
I think I was not alone in this. Do we know if this has been fixed?