Microsoft has released an optional preview update for Windows 11 version 23H2 that targets a set of high-impact reliability bugs, including a sign-in freeze when using a SIM PIN, abrupt shutdowns during Remote Desktop sessions with multiple monitors, and a recently introduced break in SMBv1 connectivity over NetBIOS. The KB5065790 update, pushed to the Release Preview channel on September 24, 2025, also corrects issues with Chinese IME character rendering and shared printer queue crashes. With consumer editions of Windows 11 23H2 reaching end of servicing on November 11, 2025, this patch offers a timely opportunity for affected users to resolve pressing problems before the platform’s support window closes.

What’s Inside the KB5065790 Update

KB5065790 (build 22631.5984) is a compact, non-security quality rollup. It brings no new features—only fixes for specific regressions that the September 2025 Patch Tuesday updates either caused or left unresolved. Here are the concrete changes:

  • SIM PIN sign-in freeze: Users who authenticate via a mobile broadband SIM PIN no longer face an unresponsive login screen. The sign-in process completes normally after entering the PIN.
  • Remote Desktop multi-monitor shutdown: RDP sessions using two or more displays are no longer at risk of abruptly terminating the host machine. Previously, disconnecting a dock or external monitor during an active remote session could force an unexpected shutdown.
  • Chinese IME rendering glitches: The Input Method Editor now displays characters correctly. Empty boxes or garbled text in text fields and administrative tools have been eliminated.
  • SMBv1 NetBT connectivity regression: Access to SMBv1 file shares over NetBIOS over TCP/IP (NetBT) is restored. The September security updates had broken this path, causing “network path not found” errors. KB5065790 fixes it for 23H2 clients.
  • Shared printer queue crash: Opening the print queue in Settings for a shared printer no longer crashes the user interface.
  • COSA profile updates: Country and Operator Settings Asset profiles for mobile broadband are refreshed, improving eSIM and WWAN provisioning.
  • Service metadata: The “McpManagement” service now shows a proper description in the Services snap-in.

Microsoft also fixed an Internet Explorer mode problem in Edge affecting same-domain redirects, though that item is not prominently listed in the official release notes.

What This Update Means for You

KB5065790’s fixes are narrow but targeted at genuine pain points. Who benefits most?

Remote workers and multi-monitor users
If you regularly connect to a corporate desktop via RDP and depend on multiple screens, the fix for unexpected shutdowns is a must. The bug could lose unsaved work and force a reboot mid-session. Installing KB5065790 removes that risk, even before October’s Patch Tuesday.

Users with cellular-capable tablets or laptops
The SIM PIN hang affected any device using mobile broadband for sign-in. If you’ve been forced to bypass PIN entry or use a different authentication method, this patch restores normal behavior.

Anyone relying on legacy SMBv1 shares
Organizations with older NAS devices or industrial equipment that speak only SMBv1 regained connectivity to those shares after the September update broke NetBT lookups. This patch fixes the regression, but it’s a short-term tactical move. Microsoft still urges migrating off SMBv1 entirely; the protocol is insecure and deprecated.

IT administrators and deployment teams
Because KB5065790 is an optional “C” release, you can test and validate it in a pilot ring now. The same fixes will be bundled into the mandatory October Patch Tuesday cumulative update. Use this window to confirm the patch doesn’t introduce new regressions with your specific driver stacks, docking stations, or WWAN modules.

The 23H2 end-of-servicing clock is ticking
Home and Pro editions of Windows 11 23H2 stop receiving security updates on November 11, 2025. This optional preview may be one of the last quality rollups you can install on that version before the servicing channel goes dark. If you remain on 23H2 after that date, your device will be vulnerable to future exploits. For most users, the strategic move is to plan an upgrade to 24H2 (or a later release) before the deadline.

How We Got Here

Windows 11 23H2 launched in October 2023 as a scoped feature update. By September 2025, it’s in its final months of full support. Microsoft had already shifted the bulk of development energy to versions 24H2 and 25H2, leaving 23H2 with maintenance-only updates.

The bugs fixed in KB5065790 emerged from two converging timelines. First, the September 2025 cumulative security update (KB5046621) inadvertently broke SMBv1 access when NetBT was in play. Microsoft quickly acknowledged the regression in its release health dashboard, promising a fix “in an upcoming release.” Second, reports of the RDP shutdown and SIM PIN freeze surfaced after earlier cumulative updates, prompting Microsoft to earmark corrections for the September optional preview.

Optional “C” releases have been a standard part of Windows servicing for years. They appear in the third or fourth week of each month and serve as a test bed for changes that will be folded into the next month’s mandatory “B” Patch Tuesday release. For organizations, this preview period is a chance to spot compatibility issues before they hit production machines.

Notably, while 23H2 receives this relief, the 24H2 channel got an out-of-band emergency patch (KB5068221) on the same day to fix Office app crashes in App-V environments. However, that OOB update did not address the DRM playback regression that has been plaguing some 24H2 users since August. The DRM issue remains “confirmed” on Microsoft’s health dashboard, meaning a separate fix is still in the works.

What to Do Now

1. Determine if you’re affected

Review the list of bugs above. If none apply to your workflow, you can safely skip KB5065790 and wait for the October Patch Tuesday rollup, which will include these fixes automatically.

2. For affected users: install manually or via Windows Update

Optional updates won’t download automatically unless you’ve opted into the Release Preview channel. You can:
- Go to Settings > Windows Update and choose “Download and install” under the optional update banner.
- If that fails, download the standalone installer from the Microsoft Update Catalog.

Manual installation steps:
- Verify you’re running Windows 11 23H2 (build 22631.xxx) by typing winver in Run.
- Go to the Microsoft Update Catalog, search for “KB5065790,” and select the .msu file matching your system architecture (x64 or ARM64) and edition (Home/Pro vs. Enterprise/Education).
- Optionally, check the file’s SHA-256 hash against published values to ensure integrity.
- Double-click the .msu to install interactively, or use an elevated command prompt for silent installation:
wusa.exe C:\Path\To\windows11.0-kb5065790.msu /quiet /norestart
- For image servicing, use DISM:
Dism /Online /Add-Package /PackagePath:C:\Path\To\windows11.0-kb5065790.msu
- Reboot when ready. The build number should change to 22631.5984.

3. Administrators: stage a controlled rollout

  • Deploy the patch to a pilot ring of representative devices for 48–72 hours.
  • Monitor event logs, app reliability, and user reports, paying special attention to systems with multiple monitors, cellular modems, or legacy SMB connections.
  • If you depend on SMBv1/NetBT, test share access thoroughly after applying the update.
  • Plan your migration away from SMBv1 in parallel—the fix is a stopgap, not a long-term solution.

4. Address the 23H2 end-of-life timeline

  • Mark November 11, 2025 as the deadline for Home and Pro editions. If your fleet still run 23H2 after that date, you’ll lose security patching.
  • Start evaluating compatibility with Windows 11 24H2 or newer. Many organizations are using the months between now and November to stage upgrades.
  • For users on 24H2 who experience DRM issues, continue to expect a separate fix from Microsoft. The OOB update KB5068221 does not cover that.

What to Watch Next

KB5065790’s fixes will be rolled into the mandatory October 2025 Patch Tuesday update. If you skip this optional release, you’ll get the same corrections automatically in two weeks—provided you haven’t deferred updates.

On the servicing front, the approaching end-of-life for 23H2 means Microsoft may soon begin nudging consumer devices toward 24H2 through its phased rollout machinery. While KB5065790 itself contains no migration triggers, the shrinking support window makes the upgrade path more urgent. Keep an eye on health dashboards for any new regressions, particularly around DRM playback and network connectivity, that could affect both 23H2 and 24H2 in the next cycle.

For now, KB5065790 is a pragmatic, surgical fix for a handful of stubborn bugs. If you’re impacted, it’s worth installing. Everyone else can wait for Patch Tuesday—but come November, staying on 23H2 won’t be an option.