Urgent — How to safely cancel a staged Windows 11 26H2 upgrade in Pending restart state without upgrading?

There is no documented Microsoft-supported command or UI operation that withdraws a Windows 11 feature upgrade after Windows Setup has completed staging and reached Pending restart; do not restart, delete $WINDOWS.~BT, or manually modify CBS, BCD, registry pending-operation data, or servicing queues.

Protect the current running session

Until Microsoft Support assesses the staged transaction, use supported restart controls to reduce—but not indefinitely eliminate—the chance of an automatic restart:

1. Open Settings → Update & Security → Windows Update → Change active hours.
2. Select Change, set the longest suitable period, and save it. Windows 10 versions later than 1607 support an active-hours range of up to 18 hours. Automatic update restarts normally occur outside active hours.^1^
3. Keep the workstation signed in and monitor restart notifications. Do not select Update and restart, Update and shut down, or Schedule the restart: scheduling merely chooses when the staged upgrade starts; it does not cancel it.

Active hours are a delay mechanism, not a cancellation guarantee. A configured compliance deadline can eventually force a restart, including during active hours.^2^

Conditional Group Policy protection

The following applies only if Windows Update is configured for scheduled installation:

1. Run gpedit.msc.
2. Go to Computer Configuration → Administrative Templates → Windows Components → Windows Update.
3. Open Configure Automatic Updates.
4. Verify that it is Enabled with option 4 — Auto download and schedule the install.
5. Only if step 4 is true, enable No auto-restart with logged on users for scheduled automatic updates installations.

That no-restart policy applies only with option 4, and a user-scheduled restart overrides it. Microsoft also warns that the policy does not work exactly as its name suggests and recommends modern compliance-deadline controls for managed environments.^1^ Conflicting management or deadline policies can change the resulting behavior, so this is not an indefinite block.

Why Setup switches cannot cancel this staging

Windows Setup’s /NoReboot option only suppresses the first reboot when specified as Setup is launched. It does not document cancellation or reversal of an already-completed down-level phase, and it cannot be retroactively applied to the Windows Update process now waiting for restart.^3^

Consequently, there is no supported “cancellation verification” procedure for this state. Seeing Windows 10 in winver only confirms that the first reboot has not occurred; it does not prove that the pending Setup transaction was withdrawn.

Prevent another Windows 11 offer

After the current transaction has been resolved, configure the target feature-update policy:

1. Run gpedit.msc.
2. Go to Computer Configuration → Administrative Templates → Windows Components → Windows Update → Manage updates offered from Windows Update.
3. Enable Select the target Feature Update version.
4. Set the product to Windows 10 and the target version to 22H2.
5. Reopen the policy and confirm that it remains enabled with those values.

The policy is supported on Windows 10 Pro and requires both the product and target-release version values.^4^ It controls future feature-update offers; it is not documented as cancelling an upgrade that is already pending restart.

Do not rely on this policy as an unlimited Windows 10 servicing guarantee. Microsoft’s policy guidance says a device pinned beyond its edition’s end of service can eventually be updated automatically. The cited documentation does not establish whether enrollment in your particular Windows 10 ESU program changes that behavior, so confirm that point with Microsoft before relying on the policy long term.^5^

Supported escalation and recovery boundaries

Open the Get Help app and request Windows Update/Setup support while the machine is still running Windows 10. Provide:

• Current build and edition
• Windows 11 26H2 shown as Pending restart
• RebootRequired state
• SetupHost.exe exit code 0x0
• Presence of staged SafeOS and NewOS
• Confirmation that no restart has occurred

The 26H2 release-health page directs users to Get Help for immediate update assistance.^6^ Support can assess the specific staged state and advise which supported options remain; the documentation does not establish that Support has a mechanism to clear it.

If the upgrade ultimately completes, DISM provides /Initiate-OSUninstall for reverting during the available uninstall window.^7^ That is a post-upgrade rollback, not pre-restart cancellation, and it does not guarantee preservation of every application, license, driver, WSL configuration, or customization.

A restore from a pre-staging system image would avoid completing this staged transaction, but it is available only if such an image already exists. Creating an image now remains valuable for recovery, but it captures the current pending state rather than a pre-staging state.

References

1. Manage device restarts after updates
2. Enforce compliance deadlines for updates
3. Windows Setup Command-Line Options
4. Policy CSP - Update
5. Walkthrough: Use Group Policy to configure Windows Update client policies
6. Windows 11, version 26H2 known issues and notifications
7. DISM operating system uninstall command-line options