something didnt go as planned. No need to worry-Undoing changes. please keep your computer on

Question

something didnt go as planned. No need to worry-Undoing changes. please keep your computer on

Mukheeduddin Mohammed 0

when the updated is done after restart i'm getting the same issue in my organization, it s taking so much time for your productive work user's , kindly give me quick solution for this issue and open there laptop

0 comments

3 answers

Your answer

Answer 1

Domic Vo 25,675 Independent Advisor

Hi Mukheeduddin Mohammed,

Has your issue been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)

Domic V.

0 comments

Answer 2

Hi Mohammed,

If after a Windows update your laptops restart and then hang for a long time before reaching the desktop, the cause is usually a driver or startup service failing during the update. The fastest way to get the machines open is to boot into Safe Mode (Shift + Restart → Troubleshoot → Advanced Options → Startup Settings → Safe Mode), then update or roll back recent drivers, especially graphics and security. Running sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth can repair corrupted system files. If the freeze continues, uninstall the most recent update from Control Panel → Programs and Features → View installed updates so users can log in and work normally, then redeploy the patch after testing. You can try Safe_Mode or Uninstall_Update to restore productivity quickly.

If the above response helps answer your question, please hit "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

Domic V.

Answer 3

The message “Something didn’t go as planned. No need to worry – undoing changes. Please keep your computer on” with rollbacks after updates indicates the update installation is failing and Windows is reverting to the previous build.

For Windows 11 devices, this behavior with error 0x800F0922 is a known issue for the February 2024 updates (KB5034765 and KB5034848). The documented resolution is to install the later cumulative update that fixes the problem.

Action plan for the organization:

Identify affected update and error code
- On an affected device, open Event Viewer → Windows Logs → Setup and confirm if the failure shows error 0x800F0922 during the cumulative update installation.
- If the failure is for KB5034765 or KB5034848 and rolls back at ~96%, it matches the known issue.
Deploy the fixed cumulative update
- The issue with KB5034765/KB5034848 is addressed in the March 12, 2024 cumulative update KB5035853.
- In WSUS/ConfigMgr/Intune or your update management tool, approve/deploy KB5035853 (OS Builds 22621.3296 and 22631.3296) to the affected Windows 11 22H2/23H2 devices.
- Ensure problematic February updates are not forced again once KB5035853 is available, so devices move directly to the fixed build.
Retry update on clients
- On clients, run Windows Update again after KB5035853 is offered.
- Devices should now install successfully without the “undoing changes” loop.
If devices are stuck in a boot/update loop
- Boot into Windows Recovery Environment (WinRE): power on, interrupt boot 2–3 times to trigger Automatic Repair.
- In WinRE: Troubleshoot → Advanced options → Startup Repair or System Restore (if a restore point exists before the failed update).
- If repair/restore is not available or fails, use Troubleshoot → Reset this PC → Keep my files to restore a working OS while preserving user data, then rejoin the device to normal update management and apply KB5035853.
For future similar issues
- Monitor Windows release health and known issues for the specific Windows version in the environment and prioritize deployment of servicing updates that explicitly “address” known rollback problems.

References: