Requirement of Upgrade Patch for Windows 23H2 to 25H2
发布时间:2026-09-22 | 浏览:1
Required Update Patch to upgrade windows 23H2 to Windows 25H2
AI answer 2026-05-04T07:45:41.2766667+00:00 To upgrade from Windows 11, version 23H2 to Windows 11, version 25H2, the required mechanism is the 25H2 enablement package . Key points from the available information: Windows 11, version 25H2 is delivered as a feature update (the “Windows 11 2025 Update”). For systems already on Windows 11, version 24H2, the move to 25H2 is done via the 25H2 enablement package (KB5054156). The enablement package has prerequisites: The device must already be running Windows 11, version 24H2 . It must have August 29, 2025—KB5064081 (OS Build 26100.5074) Preview or a later cumulative update installed before applying the enablement package. Therefore, for a device currently on 23H2 : First update the device from 23H2 → 24H2 using normal Windows Update or supported deployment tools. Ensure the device has KB5064081 or a later cumulative update for 24H2. Then apply the 25H2 enablement package (KB5054156) to move from 24H2 → 25H2 . If no updates are showing for a 23H2 device that is at or near end of servicing, use standard upgrade paths (Windows Update, Windows 11 Installation Assistant, or ISO-based in-place upgrade) to move to a supported version such as 24H2 or directly to media that already contains 25H2, then ensure the above prerequisites are satisfied. References: Windows 11, version 23H2 known issues and notifications March 25, 2025—KB5053657 (OS Builds 22621.5126 and 22631.5126) Preview May 31, 2025—KB5062170 (OS Builds 22621.5415 and 22631.5415 Out-of-band What's new in Windows 11 IoT Enterprise, version 25H2 How to install 25H2 enablement package? - Microsoft Q&A win end of life update - Microsoft Q&A AI-generated content may be incorrect. Read our transparency notes for more information.
To upgrade from Windows 11, version 23H2 to Windows 11, version 25H2, the required mechanism is the 25H2 enablement package .
Key points from the available information:
Windows 11, version 25H2 is delivered as a feature update (the “Windows 11 2025 Update”).
For systems already on Windows 11, version 24H2, the move to 25H2 is done via the 25H2 enablement package (KB5054156).
The enablement package has prerequisites: The device must already be running Windows 11, version 24H2 . It must have August 29, 2025—KB5064081 (OS Build 26100.5074) Preview or a later cumulative update installed before applying the enablement package.
The device must already be running Windows 11, version 24H2 .
It must have August 29, 2025—KB5064081 (OS Build 26100.5074) Preview or a later cumulative update installed before applying the enablement package.
Therefore, for a device currently on 23H2 :
First update the device from 23H2 → 24H2 using normal Windows Update or supported deployment tools.
Ensure the device has KB5064081 or a later cumulative update for 24H2.
Then apply the 25H2 enablement package (KB5054156) to move from 24H2 → 25H2 .
If no updates are showing for a 23H2 device that is at or near end of servicing, use standard upgrade paths (Windows Update, Windows 11 Installation Assistant, or ISO-based in-place upgrade) to move to a supported version such as 24H2 or directly to media that already contains 25H2, then ensure the above prerequisites are satisfied.
Windows 11, version 23H2 known issues and notifications
March 25, 2025—KB5053657 (OS Builds 22621.5126 and 22631.5126) Preview
May 31, 2025—KB5062170 (OS Builds 22621.5415 and 22631.5415 Out-of-band
What's new in Windows 11 IoT Enterprise, version 25H2
How to install 25H2 enablement package? - Microsoft Q&A
win end of life update - Microsoft Q&A
Jason Nguyen Tran • 26,170 Reputation points • Independent Advisor 2026-05-13T03:28:18.48+00:00 Hi Vipul More , I’m following up to check whether the issue has been resolved. Feel free to reply if you need further information. If the information provided was helpful, please click "Accept Answer" to help others in the community. Thank you! 0 comments No comments Sign in to comment Add comment
Hi Vipul More ,
I’m following up to check whether the issue has been resolved. Feel free to reply if you need further information. If the information provided was helpful, please click "Accept Answer" to help others in the community. Thank you!
Jason Nguyen Tran • 26,170 Reputation points • Independent Advisor 2026-05-04T08:33:27.2333333+00:00 Hi Vipul More , The official path involves first updating your devices to 24H2, ensuring they have cumulative update KB5064081 or later , and then applying the 25H2 enablement package (KB5054156) . This enablement package unlocks the new 25H2 features without a full reinstall, since 24H2 and 25H2 share the same servicing baseline. If you prefer, you can also perform a direct upgrade using ISO media or the Installation Assistant, but Microsoft recommends the staged approach to ensure prerequisites are satisfied. Please note that 23H2 has already reached end of servicing for Home and Pro editions, so moving forward is necessary to continue receiving security updates. I suggest testing the upgrade in a pilot group first, backing up data, and then rolling out broadly using your preferred management tools. I hope this gives you a clear roadmap. If you find this answer helpful, please consider clicking Accept Answer so others can benefit too. Jason. 0 comments No comments Sign in to comment Add comment
Hi Vipul More ,
The official path involves first updating your devices to 24H2, ensuring they have cumulative update KB5064081 or later , and then applying the 25H2 enablement package (KB5054156) . This enablement package unlocks the new 25H2 features without a full reinstall, since 24H2 and 25H2 share the same servicing baseline.
If you prefer, you can also perform a direct upgrade using ISO media or the Installation Assistant, but Microsoft recommends the staged approach to ensure prerequisites are satisfied. Please note that 23H2 has already reached end of servicing for Home and Pro editions, so moving forward is necessary to continue receiving security updates.
I suggest testing the upgrade in a pilot group first, backing up data, and then rolling out broadly using your preferred management tools. I hope this gives you a clear roadmap.
If you find this answer helpful, please consider clicking Accept Answer so others can benefit too.