Windows 11 Update 25H2 is trying to install itself again.

Question

I've already successfully installed Windows Version 25H2. Why is it again on my list of recommended updates? What should I do?I tried partially before, to install it (again) and it then tried to undo what it had done.

Answer 1

Open the Settings App.

Go to System - Recovery.

Click the 'Reinstall Now' button in the 'Fix problems with Windows Udpates' section, then wait for that process to complete.

This process should resolve any problems with Windows udpates, and this process will not affect your files, settings or installed software.

Answer 2

It wasn't a glitch. The update HAD been installed in January. But as for solutions in paragraphs numbers 3 and 4, they're beyond my ability to understand. I must tell you that I've already resolved to buy a Chromebook for simpler updates, so I will not welcome any attempt to talk me through the more technical solutions. I'll keep an eye on the answers page, but I'm not going to invest to much effort into this. Sorry.

Answer 3

Windows 11, version 25H2 can appear again in Windows Update even after it is installed when there are known issues or follow‑up fixes associated with that feature update.

For 25H2, there is a known issue where updates installed via the Windows Update Standalone Installer (WUSA) or .msu files can behave unexpectedly and still show restart or update requirements in Settings, even though the update actually completed. This is a display/state issue in Update History and can make Windows Update think the feature update still needs attention.

Actions to take:

1. Confirm that Windows 11, version 25H2 is actually installed:
   • Open Settings > System > About and check Windows specifications for Version: 25H2.
   • If 25H2 is shown there, the feature update itself is already in place.
2. If 25H2 is installed but Windows Update still offers it:
   • This is typically a transient state issue. Restart the device once or twice and then wait at least 15 minutes before re‑opening Settings > Windows Update and Update history. The status often corrects itself after the system finishes processing the update state.
3. If the update was installed using a .msu or WUSA from a network share and you saw failures or rollbacks:
   • There is a known problem when multiple .msu files are on the same share, which can cause failures and odd behavior.
   • Work around this by downloading/saving the .msu locally on the PC and running it from there, or by letting Windows Update handle the feature update directly instead of using WUSA.
4. For managed/enterprise devices (if applicable):
   • IT administrators can deploy the special Known Issue Rollback (KIR) Group Policy for Windows 11 24H2/25H2 to correct the WUSA behavior on managed devices. The policy MSI and configuration steps are documented under How to use Group Policy to deploy a Known Issue Rollback and in the 25H2 release health notes.

If 25H2 shows as installed in About and the PC is working normally, no additional action is required beyond ensuring the device is restarted and allowing Windows Update to refresh its status.

---

References:

• Windows 11, version 25H2 known issues and notifications
• Windows 11, version 25H2 update history
• KB5054156: Feature update to Windows 11, version 25H2 by using an enablement package