Share via

Microsoft Surface Device - Reset Failed - Local Install - After March / April 2026 Update with Hotpatch

Veera Ragavan 56 Reputation points
2026-04-29T15:31:06.19+00:00

Dear Experts,

We are in the Requirement to "Reset the Device" to the Factory Default with User Action as Self Service. We have Created the Script which helps the Users to Start the Reset, Without any Prompt and use the "Local Download" and make the Reset.

The Reset was working until the March / April 2026 Update. We have Validated this approach on the Surface Laptop 5 as Model with the Build Number as 26200.8246

We have noticed that out of 5 Devices - Only on 2 Devices it worked, and the Other 3 the Reset failed, but there is no data loss.

KB5083769 was the Hot fix was recommended in few MS Forums, We have tried to install the Updates and Hot fix as per the Intune and Manually and upgrade the Build Number from 8116 to 8246. But the Reset is always failing with the Local Download.

User's image

Security Updates which we trigger from Intune gets install - 04/14/2026 - 2026.04 B Security Update for Windows 10 and later - But the Reset were not Successful.

We want to know if there is any official statement or known issue from Microsoft. If So - Is this Part of May 2026 update to Cover? :)

We do not want to use

  1. Cloud Download - Because of time taken
  2. Device Wipe / Reset from Intune - Because its not Self Service and User Flexibility

With Same Model, Same Build worked for 2 Devices and not for 3 Devices is strange. Any ideas Experts?

Surface | Surface Laptop | Install and update
0 comments No comments

1 answer

Sort by: Most helpful
  1. S.Sengupta 30,501 Reputation points MVP Volunteer Moderator
    2026-05-02T13:26:10.3933333+00:00

    Verify WinRE Health on the 3 Failing Devices

    Run this in an elevated CMD on each device:

    reagentc /info

    Check that Windows RE status shows Enabled and the path points to a valid partition. If it shows Disabled or a broken path, the Local Download will always fail.

    To re-enable:

    reagentc /enable

    Deploy KB5079471 (March Safe OS Dynamic Update) — this is the dedicated targeted fix, separate from the monthly CU. Push it via Intune or manually from the Update Catalog.

    Open Command Prompt as Admin and run:

    DISM /Online /Cleanup-Image /RestoreHealth

    sfc /scannow

    reagentc /disable

    reagentc /enable

    KB5083769 alone is not enough — KB5079471 + WinRE repair is the complete fix for the 3 broken devices.


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.