Windows 11 KB5132061: Cloud Rebuild, File Explorer Changes and 24H2 Eligibility

There are two separate packages. KB5132061 covers Windows 11 versions 24H2, 25H2 and 26H2. KB5132059 covers version 26H1, the Arm-only branch. Microsoft's release history for 26H2 lists the update as November 10, 2026—KB5132061 (OS Builds 26300.9974, 26200.9974 and 26100.9974), which means 26H2, 25H2 and 24H2 respectively.

Which Windows 11 PCs get KB5132061​

Version 24H2 needs some care. Microsoft's support page says KB5132061 applies to Windows 11 26H2 and 25H2 in all editions, but only the Enterprise and Education editions of 24H2. Windows Latest says the same thing from the consumer side: Windows 11 24H2 Home and Pro won't get the November 2026 update. The outlet adds that if you're on 24H2, moving to Windows 11 26H2 takes only a small enablement package and one restart.

So the idea that the new features "roll out to 24H2" only fits managed Enterprise and Education machines. Even there, Microsoft's October preview notes say 24H2 Enterprise and Education will keep getting monthly security updates but no longer get non-security preview updates. Home and Pro users on 24H2 should plan to move to a newer release.

Microsoft also says there will be no December 2026 non-security preview update, because of reduced staffing over the holidays. Normal servicing resumes in January 2027. For many PCs, this means November's features are the last new ones of the year.

Summary: 25H2 and 26H2 get everything. 24H2 gets security updates only on Enterprise and Education. 26H1 has its own package.

Security and reliability changes that affect admins​

Microsoft lists several changes in KB5132061 that IT administrators should check before approving the update.

• NTLM signing on by default. Clients will now offer NTLM message signing by default for non-anonymous connections. Microsoft says this reduces exposure to NTLM relay attacks and adds auditing so admins can find connections that don't use signing. If you have old appliances or NAS boxes, test them before deploying widely.
• Stricter PowerShell signature checks. Script signing and signature verification now validate encoding more strictly. Signed scripts that contain invalid UTF-8 may now fail validation even if they passed before. Microsoft's fix is to re-save the affected scripts as valid UTF-8 with a byte-order mark (BOM) and sign them again. If you have a folder of old signed scripts, check it before your scheduled tasks start failing.
• Remote Desktop. RDP connections that could fail on the client with a certificate mismatch after the October preview update should now work.
• Printing. Adding a printer published in Active Directory through Settings > Bluetooth & devices > Printers & scanners > Add device could fail with error 87, "The parameter is incorrect." This is fixed. Microsoft says the October update caused the problem and that it generally didn't affect existing printers.
• Audio. USB Audio 1.0 devices that wouldn't start, showing error code 10 in Device Manager, are fixed. So is HDMI and DisplayPort audio that failed on some AMD graphics cards.
• Cuba's time zone rules. Updated daylight saving time rules keep Cuba on UTC−04:00 through the November 2026 and March 2027 transitions. Cuba goes back to UTC−05:00 in November 2027 and returns to its normal seasonal schedule in 2028.
• Secure Boot certificates. Microsoft added more device-targeting data so that more PCs automatically receive the new Secure Boot certificates as the older ones expire.

Prerequisites and deployment details​

• 26H2: Requires an update released on or after September 22, 2026 (such as KB5124010) and servicing stack version 26100.9539 or later.
• 24H2 and 25H2: Require an update released on or after June 10, 2025 (such as KB5060842) and servicing stack version 26100.4193 or later.
• Check your servicing stack version: From an elevated prompt, run DISM /Online /Get-Packages | findstr /i "ServicingStack".
• Updating install media: If you apply dynamic updates to an existing Windows image, make sure boot.stl is on the media. Without it, devices may fail to boot from that media with error 0xc0430001.

Microsoft says it knows of no issues with KB5132061. Some users disagree. Several posters on ElevenForum reported Installation Failure: Windows failed to install the following update with error 0x800F0989: 2026-11 Security Update (KB5132061) (26300.9974). These are individual forum reports, not a confirmed known issue, but watch for it if you manage a lot of machines. Windows Latest had no trouble in its own test. The update showed up as "2026-11 Security Update (KB5132061) (26300.9974)" and installed automatically within a few minutes.

Summary: Test NTLM-dependent devices and signed PowerShell scripts before broad deployment, confirm the servicing stack version, and keep an eye out for 0x800F0989.

The features: what actually changes​

According to Microsoft's notes for the October preview (KB5127936), several of these features arrive through a gradual rollout. Installing the update doesn't guarantee you'll see them right away.

File Explorer gets a better right-click menu​

The new context menu opens faster and can be customized. Right-click and choose Customize menu to:

• Choose whether app extensions appear in the main menu or in a submenu, or hide that submenu entirely
• Show Cut, Copy, Paste, Rename, Delete and Share as text commands instead of a row of icons
• Move Properties to the bottom of the menu

Shift + right-click on the desktop still shows more options. The Folder Options dialog also gets dark mode support. The preview added a few other things too: a consistent layout for file search results, and support for ~ in the address bar to jump to your user profile folder (for example, ~\AppData).

Edge opens faster​

Microsoft's Edge team says Edge is the first browser to support Windows' accelerated app launch feature. Normally, when you click Edge on the taskbar or open a link, Windows starts a helper process to find the copy of Edge that's already running. With this feature, Edge registers with Windows, and Windows sends the request straight to the running process.

Microsoft says most users will see launches about 15% faster, and up to 33% faster under heavy multitasking. Those are Microsoft's own numbers, measured against an already-running Edge without the feature. The feature needs Edge 150 or later and Windows 11 25H2, 26H1 or 26H2 with KB5127936 or later. Other app developers can use it as well. Microsoft says it is also contributing the work to Chromium. Windows Latest reports that accelerated app launches let Edge, and soon Firefox, open links without starting an extra process.

Xbox Mode, Magnifier and Phone Link​

• Xbox Mode: Gaming Task View has a new navigation bar with quick buttons for Exit to Desktop and Power Options.
• Magnifier:
  • A contrast theme toggle reduces glare while keeping the original colors in photos and videos.
  • Each monitor can have its own zoom level. This is on by default and requires your displays to be set to Extend. Use Windows key + Plus or Minus, or Ctrl + Alt with the mouse wheel.
  • Viewport locking keeps one display's magnified view in place while you move to another. Press Ctrl + Windows key + K to lock or unlock a display, and Windows key + Esc to release all locked displays.
• Phone Link in Start: Hover over a recent message or notification to preview it without opening it. You can manage this under Phone Link > Settings > Start menu personalization.

Summary: The context menu change is the one you'll notice every day. The Edge speedup only matters when Edge is already running.

Cloud Rebuild: a reinstall without USB media​

Cloud Rebuild reinstalls Windows 11 using a fresh image and drivers downloaded from Windows Update. You don't need a USB drive or a local recovery image, and it works even if the Windows files on the PC are badly damaged.

This wipes everything. Unlike Reset this PC, which can keep your files, Cloud Rebuild always removes personal files, accounts, apps and settings. Files stored in OneDrive or another cloud service aren't affected.

How to run Cloud Rebuild​

1. Back up your files and plug the PC into power.
2. If Windows starts: Go to Settings > System > Recovery, and next to Rebuild this PC, select Rebuild PC.
3. If Windows won't start: In the Windows Recovery Environment (WinRE), choose Troubleshoot > Cloud rebuild. WinRE opens automatically after several failed boots.
4. Connect to the internet with Ethernet or Wi-Fi. The October preview also lets WinRE reuse eligible Wi-Fi profiles already saved in Windows.
5. Choose how to remove your files:
   • Remove files is faster and fine if you're keeping the PC.
   • Remove & sanitize asks the drive's hardware to erase the data, which makes recovery much harder. Use it if you're recycling, returning or giving away the PC.
6. Confirm the target build, edition and language, then accept the warning. The PC may restart several times and then opens Windows setup as if it were new.

If it fails​

Microsoft notes that sanitization depends on the storage hardware, and Windows can't independently confirm what the drive actually did. If you need certified data destruction, ask your PC maker. If sanitization fails, don't skip it on a PC you're getting rid of. Use the manufacturer's erase tool instead.

Summary: Cloud Rebuild is a full reinstall, not a quick fix. Try less disruptive recovery options first.

Windows 11 26H1: KB5132059​

KB5132059 brings 26H1 to build 28000.3501. Microsoft lists the same NTLM signing, PowerShell encoding, audio, printing, RDP, Cuba time zone and Secure Boot changes as for the other versions. It also updates AI components (Image Search, Content Extraction, Semantic Analysis and the Settings Model) to version 1.2610.1071.0. The update needs servicing stack version 28000.1575 or later, has no required checkpoint cumulative update, and ships only as Arm64 packages. Microsoft reports no known issues.

That Arm64-only packaging matches the version history, which shows 26H1 on build 28000 | ARM | February 10, 2026. Thurrott describes 26H1 as the release for PCs with Qualcomm Snapdragon X2 or Nvidia RTX Spark chips. Thurrott also says this update adds File Explorer improvements, more touchpad gestures, new remapping options for the Copilot key and Emoji 17.0 support. Microsoft's November KB page doesn't list those features individually. It only points back to the October 26H1 releases (KB5127646, the out-of-band KB5134134 and the KB5127653 preview). So treat those specific features as Thurrott's reporting rather than something confirmed in the November release notes.

The bottom line​

On 25H2 or 26H2, install the update. You get real fixes for audio, RDP and printing, plus a context menu you can finally configure. Admins should test NTLM signing and signed PowerShell scripts before rolling it out widely. If you're still on 24H2 Home or Pro, you won't get this update, and a short enablement package will move you to 26H2.