Welcome to the Microsoft Q&A forum.
From what you described, this behavior can occur when a device has been offline for an extended period and the system time was incorrect during early startup. In this state, Windows may believe it is already fully up to date, while required servicing components and app update metadata are no longer available locally. When this happens, update and repair tools may be unable to recover automatically, even though the system appears healthy on the surface.
When Windows reaches this condition, the supported way to return the device to a fully serviceable state is to back up your data and perform a clean reinstall of Windows 11 using current installation media. While this is not the outcome anyone hopes for, it ensures the system is rebuilt on a fresh, fully supported servicing baseline.
If you encounter this again on another device, these early checks may help reduce the risk:
1 - Before first Windows sign-in after long storage
- Set the correct date and time in BIOS/UEFI.
- Connect the device to the internet as soon as Windows starts.
2 - Early warning signs
- Windows Update reports “Up to date” but hasn’t updated for months.
- Microsoft Store apps request updates but cannot install them.
- DISM /RestoreHealth fails with “repair content not found.”
3 - When these signs appear together
- Standard reset and repair tools may not be able to restore the update servicing state.
- An in-place upgrade may also fail because it depends on the existing servicing baseline.
Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.