KB5127936 Adds Windows 11 Restore Summary for Settings and Microsoft Store Apps

This is not a new backup engine, and it is not a substitute for system-image recovery. It is a confirmation layer for something that used to happen without much feedback. IT admins who handle PC refreshes will probably find that more useful than it sounds.

What KB5127936 actually is​

Microsoft's support notice lists KB5127936 as an optional non-security update [that] will upgrade Windows 11 25H2 and 26H2 devices to builds 26200.9818 and 26300.9818, respectively. NinjaOne's KB catalog notes it was released October 28, 2026, and that it is delivered through a gradual rollout phase and a normal rollout phase, so availability varies by device.

The Restore Summary is part of the gradual rollout group. Installing the update does not guarantee you will see the feature right away.

Microsoft's own description of the change reads: "This update introduces a Restore Summary that appears after you restore a backup profile to a new device. The summary gives a clear overview of what was successfully restored, including Windows settings and the list of Microsoft Store apps."

Version scope, in brief:

One wrinkle: Microsoft Learn's Windows settings backup and restore overview says the restore summary experience applies "starting with Windows 11, version 24H2." The KB5127936 servicing notice, however, covers only 25H2 and 26H2. If you manage a mixed fleet, check against the specific servicing release for each version rather than assuming every device gets the feature at the same time.

Section summary: KB5127936 is an optional preview for Windows 11 25H2 and 26H2. The Restore Summary rolls out gradually, so some eligible PCs will get it later than others.

First, a reminder of what Windows settings backup and restore does​

Many people hear "backup" and picture their files being saved. That is not what this feature does.

Microsoft renamed Windows Backup for Organizations to Windows settings backup and restore. The Learn overview warns that some policy names and documents may still use the old name during the transition. The feature is built for managed device transitions: Windows 10 to Windows 11 moves, PC refresh cycles and new-hardware rollouts. Admins configure it through Intune, Policy CSP or Group Policy.

According to Microsoft's FAQ, the feature backs up:

• Windows settings (personalization and preferences)
• The list of installed Microsoft Store apps

It does not:

• Back up user files. Microsoft recommends OneDrive for that.
• Back up or reinstall apps in general. It covers only the list of Store apps.
• Back up app settings
• Handle Edge favorites and settings. Microsoft points to Edge enterprise sync for those.

Desktop backgrounds have their own rule. System images stored under %windir%\Web\ are not restored by design. Custom backgrounds set by a user or admin come back only if OneDrive Picture folder sync is enabled.

So the Restore Summary reports on a fairly narrow set of items. That is fine, as long as nobody expects it to list Documents or line-of-business apps.

Section summary: This feature restores settings plus a Store-app list. It is not a file backup, and the Restore Summary only reports on that scope.

What the Restore Summary shows, and when​

Microsoft Learn's overview gives more operational detail than the KB note:

• Contents: Personalization settings restored from the user's backup profile, plus the Microsoft Store app list tied to that profile.
• Default values may appear: In some cases the summary also lists settings that kept their default values (ones the user never changed). Microsoft says this is by design, so it is not a bug to report.
• Timing: The summary becomes available about one hour after a successful restore.
• Expiry: It stays accessible for seven days after device setup. After that, you can't view it.
• Where it appears: As a Windows notification once restore completes, or under Settings > Accounts > Windows backup.

Independent coverage describes the benefit the same way. Pureinfotech wrote that the improvement makes switching to a new Windows 11 device more transparent by showing which settings and apps were restored.

How to view the Restore Summary​

According to Microsoft Learn:

1. During device setup (OOBE) or first sign-in, sign in with the same Microsoft Entra ID work or school account used for the backup, then select a backup profile from the previous device.
2. Let the restore and any remaining setup steps finish until you reach the desktop.
3. When the restore summary notification appears, select View.
4. Or go to Settings > Accounts > Windows backup and select the link icon next to Restore summary.

What success looks like: a list of restored personalization settings and Store apps from the selected profile.

If you don't see it:

• Less than an hour has passed. Wait. The summary isn't instant.
• More than seven days have passed since setup. The summary has expired.
• Gradual rollout. The device may not have the feature turned on yet, even with KB5127936 installed.
• No restore happened. If the user chose "set up as new," there is nothing to summarize.

Section summary: Check within the one-hour-to-seven-day window, either from the notification or under Settings > Accounts > Windows backup.

Prerequisites admins can't skip​

Here is where Microsoft's documentation is most useful. Backup and restore have separate requirements, and mixing them up is a common source of failed restores.

Backup​

• Supported minimum builds per Microsoft Learn: Windows 10 22H2 build 19045.6216; Windows 11 22H2 build 22621.5768; 23H2 build 22631.5768; 24H2 build 26100.4946 (or later).
• The device must be Microsoft Entra joined or hybrid joined, and the user signs in with Entra ID.
• Backups run automatically every eight days. Users can also start one manually from the Windows Backup app.

About "default on" in 26H2: Microsoft says backup is enabled by default on eligible Windows 11 26H2 devices. That only applies when the backup policy is Not Configured, the device is not in a privacy-sensitive region, and it is not in a sovereign or restricted cloud. Existing explicit admin policies, enabled or disabled, are still honored. The change covers backup only.

Restore​

• Restore is disabled by default. An admin has to turn it on.
• OOBE restore requires Entra join and at least one backup profile. If you use Autopilot, it must be in user-driven mode, not self-deploying.
• First-sign-in restore applies to devices that have already completed enrollment, starting with Windows 11 24H2 build 26100.7922 and 25H2 build 26200.7922.
• The feature is unavailable in GCCH, sovereign clouds and China.
• Backups are tenant-bound, and cross-tenant migration isn't supported.

Turning restore on in Intune (tenant-wide, at enrollment)​

1. Sign in to the Microsoft Intune admin center.
2. Go to Devices > Enrollment > Windows Backup and Restore.
3. Set Show restore page to On.
4. Select Save.

This step requires the Intune Service administrator or Global administrator role. It affects devices enrolled after the change, not devices already enrolled. For those, use a Settings catalog policy with Windows Backup And Restore > Enable Windows Restore set to Enabled, or the CSP path ./Device/Vendor/MSFT/WindowsBackupAndRestore/EnableWindowsRestore set to True.

Common failure points​

• Mixing GPO and CSP. Microsoft says to pick one, because combining them can cause unexpected results.
• Disabled dependency policies. EnableActivityFeed, PublishUserActivities, UploadUserActivities, EnableCDP and AllowConnectedDevices must not be set to Disabled. If they are, backup doesn't apply.
• Conditional Access blocks. "You can't get there from here" errors usually mean a Conditional Access policy is blocking the token. Microsoft's fix is a custom policy that allows app ID d32c68ad-72d2-4acb-a0c7-46bb2cf93873.
• VDI and shared Cloud PCs. Microsoft recommends excluding non-persistent VDI and Windows 365 Flex shared Cloud PCs from both backup and restore policies, and using FSLogix or User Experience Sync instead.

Section summary: Backup may turn itself on in 26H2, but restore never does. Most failures come down to policy conflicts, disabled dependencies or Conditional Access.

Why this matters, and where to temper expectations​

The case for the feature is simple. Before this, verifying a restore meant opening Settings pages and checking whether dark mode and taskbar choices had come across. A summary turns that into a single check. For a help desk handling dozens of refreshes a week, that probably means fewer "my PC doesn't look right" tickets. That is our reading of Microsoft's stated goal, not a figure Microsoft has published.

The limits are just as clear:

• The summary shows what was successfully restored. Microsoft does not describe it as a per-item error report for what failed.
• It disappears after seven days, so it doesn't work as an audit record.
• It covers only settings and the Store-app list. Files, Win32 apps and app settings still need their own tools.

The headline calls this a "much needed backup recovery feature," which oversells it somewhat. It is useful, but it adds visibility, not new recovery capability. The bigger recovery news in KB5127936 is elsewhere in the same update: Cloud rebuild and WinRE's ability to reuse saved Wi-Fi profiles.

How to get KB5127936​

• Windows Update: Settings > Windows Update > Advanced options > Optional updates, then install the update from the Optional updates list.
• Microsoft Update Catalog: Download the standalone MSU packages and install them as described in Microsoft's x64 or Arm64 instructions.
• Known issue: Microsoft is still investigating USB Audio Class 1.0 devices that fail with Code 10 after the September 8, 2026 security update. Test before deploying widely if your users rely on such devices.

As with any preview, the cautious approach is to put it on a pilot ring first. The changes will reach the broader fleet with the next security update anyway.

Bottom line: The Restore Summary doesn't change what Windows settings backup and restore can save, but it finally shows what was restored. If you're planning 26H2 migrations, keep the one-hour wait and seven-day window in mind. Also make sure restore is actually enabled, because Microsoft leaves it off by default.