Windows Release Preview Round: Fixes for Windows 11 22631.5982 and Windows 10 19045.6388

Microsoft has pushed fresh Release Preview updates for both Windows 11 and Windows 10 this week, delivering targeted reliability fixes for real‑world scenarios and a terse Windows 10 rollup aimed at keeping late‑life devices stable while organizations complete migration plans.

Background / Overview​

Microsoft uses the Release Preview Channel to deliver low‑risk cumulative updates and final validation builds before a wider distribution; these updates are intentionally focused on quality and reliability rather than major new features. The most recent Release Preview deliveries include a Windows 11 package listed under KB5065790 that raises OS build numbers in the 22631 family, and a small Windows 10 rollup listed as KB5066198 for the 19045 branch. Both shipments aim to resolve device- and workflow-specific issues observed in field telemetry and Insider feedback.
One point worth flagging up front: third‑party reporting briefly referenced a Windows 11 revision as build 22631.5984 in some summaries, while the official Windows Insider announcement and related community documentation identify the package as build 22631.5982 (KB5065790). Where independent outlets and community threads diverge on the final build suffix, the Windows Insider Blog is the authoritative reference; discrepancies should be treated cautiously until Microsoft updates the record.

---

What Microsoft shipped (quick summary)​

• Windows 11 (Release Preview) — Build 22631.5982 (KB5065790): a cumulative quality update that fixes a set of reliability issues including SIM‑PIN sign‑in hangs, multi‑monitor Remote Desktop crashes, Chinese IME rendering problems, and a Print Queue UI crash.
• Windows 10 (Release Preview) — Build 19045.6388 (KB5066198): described by Microsoft as a “small set of general improvements and fixes” for Windows 10 version 22H2; the Release Preview post is intentionally brief and does not provide an itemized changelog in the initial announcement.
• Companion Canary/Beta notes in community reporting mention additional quality fixes in Dev/Canary channels that address storage cleanup scanning, HDR toggling behavior and UI thumbnail duplication — items that often precede Release Preview validation. These Canary/Beta fixes show the multi‑ring approach Microsoft uses to triage regressions.

---

Windows 11 Release Preview: Build 22631.5982 (KB5065790)​

What the update fixes​

The Windows Insider blog lists several specific reliability items addressed in this KB:

• Authentication — resolves an issue where the Windows sign‑in screen could stop responding after a user entered a SIM PIN while signing in with a mobile broadband connection. This was a potentially serious blocker for WWAN/eSIM users who authenticate during the sign‑in flow.
• Country and Operator Settings Asset (COSA) — updates mobile operator profiles. COSA updates are small but critical for cellular tethering, carrier‑specific settings, and WWAN device interoperability. Administrators managing fleets with cellular connectivity should note these profile updates.
• Display/Remote Desktop — fixes an issue where display configuration changes during Remote Desktop Protocol (RDP) sessions with multiple monitors could cause a system shutdown when a docking station was disconnected mid‑streaming. This addresses a class of hard failures impacting remote/hybrid workers who use docking stations and RDP‑based workflows.
• Input/IME — corrects character‑rendering errors for certain Chinese IMEs where characters either didn’t display or appeared as empty boxes in text fields that impose character limits. Localization and IME regressions have outsized user impact in affected locales, so these fixes matter to multinational organizations and Chinese‑language users.
• Printer UI — prevents the Print Queue user interface in Settings from crashing when viewing the queue for a shared printer. Printer UI crashes, particularly for shared printers in mixed environments, can derail simple admin tasks and end‑user printing workflows.
• System services — ensures the McpManagement service shows a proper description rather than appearing as an undocumented service entry. This is a small but tidy reliability/management fix that helps administrators identify service behavior correctly.

Why these fixes matter​

These are pragmatic, targeted fixes that reduce friction in important day‑to‑day workflows:

• Remote workers and IT administrators get higher confidence when docking/undocking and using RDP across multiple monitors — a scenario common in hybrid workplaces.
• Cellular‑first devices (laptops with eSIM/WWAN) regain a reliable sign‑in experience, which is crucial where mobile broadband is the primary network path.
• Improved IME behavior directly benefits users in Chinese language environments and lowers support tickets related to text input and display.

Taken together, the patch is a classic Release Preview candidate: not flashy, but materially useful to specific user cohorts.

Deployment considerations​

• Pilot before wide deployment: Although Release Preview builds are low‑risk by design, IT teams should validate fixes in representative pilot rings, focusing tests on docking station workflows, multi‑monitor RDP use, WWAN/eSIM authentication paths, and printers that are shared across domains.
• Check driver and firmware compatibility: Display and docking station regressions often interact with vendor drivers and firmware. Confirm vendor‑supplied dock and GPU driver compatibility before broad rollout.
• Monitor for rollbacks: If your environment uses combined SSU/LCU packages, uninstallation may be nontrivial; plan for recovery mechanisms (disc images, system snapshots) in case rollback is needed.

---

Windows 10 Release Preview: Build 19045.6388 (KB5066198)​

What Microsoft says​

Microsoft’s Windows Insider announcement is intentionally concise: the update contains a “small set of general improvements and fixes” for Windows 10, version 22H2. There is no extended line‑item changelog in the initial post beyond that summary, which is common for Release Preview posts that focus on lower‑risk servicing.

What community reporting and forums add​

Industry reporting and community threads observed that the Windows 10 preview appeared to be a stability‑focused rollup with emphasis on device compatibility, IME and localization touches, and other non‑feature quality improvements. Because the formal Microsoft Support KB page for KB5066198 may lag Insider announcements, administrators should treat community‑listed specifics as provisional and validate empirically in a controlled pilot.

Why this matters now​

Windows 10’s servicing horizon is constrained: Microsoft has scheduled the end of servicing for Windows 10 on October 14, 2025. These last Release Preview pushes act as stopgap measures to keep remaining Windows 10 devices stable while organizations plan migrations to Windows 11 or enroll in Extended Security Updates (ESU). For devices that must stay on Windows 10, these preview quality updates still provide meaningful reliability value — but they are not a long‑term substitute for a migration strategy.

Deployment guidance for IT​

• Validate functionality that matters to your fleet: printer sharing, IME behavior, custom device drivers, and enrollment wizards (e.g., ESU enrollment) have historically been affected by late servicing updates; confirm these flows in a staging ring.
• Plan migrations: With end‑of‑servicing looming, use this window to accelerate migration projects for eligible hardware or confirm ESU enrollment if devices must remain on Windows 10.
• Treat Release Preview as pre‑production: Apply the same pilot discipline you use for monthly cumulative updates — test, measure, and escalate only after representative hardware and workloads pass validation.

---

Canary / Dev Channel context and adjacent fixes​

While the Release Preview updates are specifically targeted, recent Canary/Dev channel activity provides useful context for the kinds of regressions Microsoft is chasing across channels. Canary builds in the days surrounding these Release Preview pushes included fixes for temporary files scanning getting stuck, an HDR toggle regression that caused momentary HDR toggle off behavior, duplicate taskbar thumbnail previews after switching desktops, and other quality items. These fixes often originate in Canary/Beta and then cross into Release Preview once sufficiently validated. The pattern highlights Microsoft’s multi‑ring approach to regression triage.

---

Critical analysis — strengths, limitations, and risks​

Strengths​

• Targeted fixes reduce immediate friction: The Windows 11 items directly address high‑impact scenarios — sign‑in hangs on SIM PIN entry, abrupt shutdowns when disconnecting docks mid‑RDP session, and IME display problems. Fixes like these have an outsized impact on daily productivity for affected users.
• Release Preview remains a sensible low‑risk ring: Microsoft’s channeling ensures fixes reach a testable audience before broad rollout, allowing administrators to validate updates against their specific device mixes.
• Short, conservative Windows 10 rollup fits the timeframe: Given the October 14, 2025 servicing deadline for Windows 10, small stability fixes are operationally useful until migration paths are complete.

Limitations and risks​

• Sparse public documentation for some preview KBs: The Windows 10 announcement for KB5066198 is intentionally terse. The initial lack of a formal Microsoft Support KB article means file‑level changes, root cause detail and uninstall guidance may not be immediately available, complicating risk assessments for IT teams. Treat community writeups as provisional until Microsoft publishes the KB.
• Potential for hardware/driver regressions: Display and docking‑related fixes interact with GPU drivers and dock firmware. Even though Release Preview is lower risk than Canary, these updates can surface driver‑specific regressions on a small subset of hardware. Vendors should be engaged in pilot validation.
• Version/build numbering confusion: Discrepancies in reported build suffixes across outlets (e.g., 22631.5982 vs 22631.5984) create noise for administrators tracking specific revisions. Always cross‑check with the Windows Insider Blog or Microsoft Support KB when precision matters.
• Short window for Windows 10 organizations: Organizations delaying migration risk exposure after October 14, 2025 if they assume preview fixes are a long‑term approach. The Release Preview updates are not a substitute for security servicing after end‑of‑support.

---

Practical recommendations for users and administrators​

For individual power users and Insiders​

• Check Windows Update and the Windows Insider Blog for the official post before installing preview builds.
• If you rely on WWAN/eSIM, multi‑monitor RDP, or Chinese IMEs, consider installing the Windows 11 Release Preview build in a controlled way to verify the specific fixes.
• Maintain regular backups and create a system restore point or full image before applying any preview updates; preview channels are lower risk but not risk‑free.

For IT administrators and device managers​

• Run a focused pilot on representative hardware (docks, GPUs, printers, WWAN modems) before broad deployment. Emphasize the workflows addressed by the KB — sign‑in flows, RDP sessions, printer queue management, and IME input scenarios.
• Track Microsoft’s Support KB pages and the Windows Insider Blog closely — these are the authoritative sources for build numbers and documented fixes. If the KB for a preview build is delayed, treat community-sourced specifics as provisional.
• Coordinate with hardware vendors for driver and dock firmware updates during pilots; regressions often arise from vendor driver interactions.
• For Windows 10 devices, prioritize migration planning or ESU enrollment; rely on preview fixes only as temporary mitigation until the end‑of‑servicing milestone has passed.

---

How to verify and instrument post‑update behavior​

• Use targeted telemetry: monitor reliability metrics for RDP sessions, docking/undocking events, print queue errors, and authentication failures involving SIM PIN paths.
• Validate IME rendering: for locales using complex input methods (Chinese, Japanese, Korean), run automation that exercises IME input across typical enterprise applications (SharePoint, Outlook, enterprise line‑of‑business apps).
• Log and triage driver failures: add monitoring for driver errors and kernel‑level bugchecks on test devices; if driver regressions appear, capture memory dumps and engage hardware vendors with Windows Error Reporting traces.

---

What we still don’t know (and what to watch)​

• The Windows 10 preview’s itemized changelog in the Microsoft Support KB: Microsoft sometimes posts a fuller KB article later; administrators should watch the Support site for KB5066198’s detailed entry. Until that appears, exact file changes and uninstall guidance remain partly unverifiable.
• Any latent interactions with third‑party imaging/management solutions: Release Preview updates can interact unexpectedly with endpoint management stacks; watch for reports from Intune, SCCM, and third‑party management vendors during pilots.
• Whether the Windows 11 build suffix discrepancy reported in some outlets reflects a post‑release revision or a reporting error: Microsoft’s Insider Blog and support pages remain the authoritative record for build numbers. Confirm against those sources if build suffix precision matters for deployment gating.

---

Conclusion​

This round of Release Preview releases is typical of Microsoft’s ongoing servicing rhythm: focused, pragmatic fixes that don’t make headlines but materially reduce friction in real‑world workflows. Windows 11’s KB5065790 (build 22631.5982) patches a set of high‑impact reliability issues that will matter most to remote/hybrid workers, WWAN/eSIM device owners, and users requiring Chinese IME fidelity. Windows 10’s KB5066198 follows the expected conservative path for late‑life servicing — a short, stability‑focused rollup that helps keep remaining 22H2 devices usable while migrations continue.
Administrators should pilot these updates on representative hardware, verify the specific customer‑facing workflows the KBs claim to fix, and maintain a clear migration plan for Windows 10 fleets ahead of the October 14, 2025 end‑of‑servicing milestone. Finally, when build suffixes or KB details differ across outlets, default to Microsoft’s Insider Blog and the official Support KB for the authoritative record — and treat third‑party summaries as a useful but secondary signal while you validate in your environment.

---

Source: Neowin Microsoft releases new Windows 11 and 10 Release Preview builds with bug fixes

 

[ChatGPT]

Microsoft has pushed fresh Release Preview cumulative updates for both Windows 11 and Windows 10 this week, delivering a set of targeted reliability fixes for 23H2 and a small stability-focused rollup for 22H2 that are intended for validation before broader distribution.

Background​

Microsoft uses the Release Preview Channel to stage cumulative quality updates and final validation builds before they flow to general customers. These pushes are typically conservative: they focus on stability, localization, driver compatibility, and servicing reliability rather than introducing new consumer features. That posture is especially visible now because Windows 10 is nearing its end-of-support milestone, while Windows 11 continues to receive maintenance and feature work on parallel branches.

• Windows 11 in these updates is being serviced on the 23H2 (22631) baseline.
• Windows 10 remains on the 22H2 (19045) baseline for the final servicing window before its support end date of October 14, 2025.

This article summarizes the observable changes in the latest Release Preview deliveries, explains the practical impact for users and IT teams, flags inconsistencies reported by secondary outlets, and offers a conservative deployment checklist for administrators and advanced users.

---

Overview of what shipped​

Windows 11 — Build family and KB label​

Microsoft’s Windows Insider Blog documents a Release Preview push identified as Windows 11 Build 22631.5982 (KB5065790). The official entry lists a concise set of fixes spanning authentication, operator settings (COSA), display/kernel behavior in Remote Desktop sessions, Input/IME rendering, printer-queue stability, and a system service description issue. These changes are framed as reliability corrections rather than new features.
Note: several third‑party outlets and community captures briefly referenced a closely related suffix — 22631.5984 — when reporting the same KB label. Those differences appear to be minor revision-number variances in preview feeds and packaging rather than differences in the documented symptom fixes. Treat the Windows Insider Blog entry as the authoritative Microsoft record for the itemized list of fixes.

Windows 10 — Build family and KB label​

For Windows 10, Microsoft published a terse Release Preview announcement identifying Build 19045.6388 (KB5066198) and describing the update as “a small set of general improvements and fixes” for version 22H2. The public notice intentionally omits a granular, line-item changelog in favor of a short quality-focused summary. Community and industry reporting has echoed this characterization.
Some outlets briefly reported a follow-up revision (for example, 19045.6390) under the same KB label in parallel coverage. At the time of writing the Windows Insider Blog and Microsoft Support pages list the builds as 22631.5982 and 19045.6388; any alternate trailing-suffix numbers should be treated as packaging or telemetry artifacts until Microsoft updates the official record.

---

Windows 11: What the fixes address (deep dive)​

The Windows Insider note for the 22631 family spells out several concrete fixes. Each item is small on its face but can have outsized operational impact depending on hardware, work patterns, or language settings:

Authentication: SIM PIN hang during mobile‑broadband sign‑in​

• What was happening: On devices that sign in via a WWAN/mobile broadband connection, the sign-in UI could stop responding after a user entered a SIM PIN.
• Why it matters: Laptops and tablets relying on eSIM or WWAN modems — particularly those used in field or mobile-first scenarios — can be blocked at sign-in. This is a critical usability regression for cellular-first devices.
• Fix summary: The update resolves that hang condition in the Windows sign-in flow.

Country and Operator Settings Asset (COSA) updates​

• What it is: COSA packages provide per‑operator configuration (APN, roaming rules, operator policy) used by built‑in cellular stacks.
• Why it matters: Outdated operator profiles can cause connectivity, provisioning, or SIM behavior inconsistencies. The update refreshes profiles for certain mobile operators to improve WWAN interoperability. Administrators who manage fleets with cellular connectivity should consider validating WWAN provisioning after installation.

Display kernel / Remote Desktop multi‑monitor shutdowns​

• Symptom: Systems could unexpectedly shut down when display configuration changes occur during RDP sessions using multiple monitors — notably when disconnecting a docking station during streaming or active remote sessions.
• Impact: Remote and hybrid workers who use RDP with docking stations and multiple displays were most exposed. Unexpected shutdowns during remote sessions can cause lost work and decreased trust in remote workflows.
• Fix: The update addresses the display-kernel interaction that could trigger the shutdown scenario. Given the historically sensitive interplay between GPU drivers, docking firmware, and display stacks, administrators should pilot this in representative hardware.

Chinese Input Method Editor (IME) rendering errors​

• Symptom: Certain Chinese characters either failed to render or appeared as empty boxes in apps with character‑limit fields (for example, in the Connection Manager Administration Kit).
• Impact: This is a localization/IME regression impacting users typing in Chinese; it can be a show‑stopper for localized business apps and for users who rely on accurate character composition.
• Fix: The IME rendering behavior has been corrected. Organizations operating in Chinese locales should validate critical input-heavy flows after applying the update.

Printer queue crashes for shared printers​

• Symptom: Viewing a shared printer’s queue in Settings could cause the Print Queue UI to stop responding.
• Impact: Environments that rely on network-shared printers (mixed enterprise/home office setups) could see printing disruptions or increased help-desk calls.
• Fix: The update prevents the Print Queue UI from crashing when inspecting shared print queues.

McpManagement service description missing​

• Symptom: The McpManagement service appeared without a human‑readable description in Services, which is a small but important manageability bug.
• Fix: The update restores the proper service description so administrators can identify the service reliably.

---

Windows 10: What the release contains (what we know and what we don’t)​

Microsoft’s announcement for Build 19045.6388 (KB5066198) is intentionally minimal: the update contains a “small set of general improvements and fixes” to improve device stability. That statement is consistent with Microsoft’s pattern for Release Preview pushes to Windows 10 late in the life cycle: servicing-oriented, low risk, and often lacking a long public changelog.

• Typical contents of these small rollups include reliability fixes for Explorer, IME/localization, SMB or RDS behaviors, update/servicing stability, and packaging/installation fault corrections.
• Microsoft’s terse wording means the update is low‑risk by intent, but it also means administrators must validate empirically because root causes and file‑level changes often aren’t disclosed in the brief Insider post. Community reporting and next-day KB articles (when published) usually fill in additional details if there are substantive items to call out.

Given Windows 10’s approaching end-of-support date, these updates act as last-mile stabilization steps for devices that will remain on 22H2 longer than planned. If your estate depends on Windows 10 beyond October 14, 2025, plan for Extended Security Updates (ESU) or migration to Windows 11.

---

Discrepancies and verification — what to watch for​

Several community posts and third‑party outlets briefly reported build suffixes of 22631.5984 and 19045.6390 under the same KB labels. Those minor variant numbers show up in certain feeds and package manifests, which can happen when Microsoft issues incremental packaging tweaks (e.g., metadata repackaging or CDN variant deployments). However, the Windows Insider Blog entries and Microsoft Support remain the authoritative sources for the documented fixes and published build identifiers; they list 22631.5982 and 19045.6388 for the KB labels referenced. Treat the alternate trailing-suffix numbers as potential packaging/telemetry artifacts until Microsoft formally amends the official release notes.
Flagging an unverifiable claim: if you see coverage stating 22631.5984 or 19045.6390 without corroboration on Microsoft’s official channels (Windows Insider Blog or Microsoft Support KB), consider that coverage provisional. Administrators requiring absolute auditability should wait for a formal KB article or the Microsoft Update Catalog entry before broad rollout.

---

Practical guidance: who should install, and how​

These Release Preview updates are low‑risk by design, but prudent validation is still required. The following guidance balances the Release Preview intent with enterprise caution.

Quick recommendations​

• Individual users enrolled in Release Preview who want earlier fixes for the specific scenarios described (WWAN sign-in, RDP multi‑monitor/dock behavior, Chinese IME issues, shared‑printer queue crashes) may install the update via Windows Update.
• Enterprises and organizations should pilot the update in a representative ring (10–50 devices) that includes docking station models, GPU drivers, WWAN/eSIM devices, and shared‑printer configurations before broad deployment.

Deployment checklist (numbered)​

• Inventory and scope: Confirm devices running Windows 11 version 23H2 (22631.x) or Windows 10 version 22H2 (19045.x). Use winver or your management inventory tool.
• Capture baselines: Create system images or reliable restore points for pilot devices. Ensure backups are tested.
• Pilot group (1–2 weeks recommended): Deploy to a small set that represents the major hardware/driver combinations in your environment—especially docking stations, GPU models, and WWAN modems.
• Test scenarios:
• WWAN/eSIM sign‑in flows with SIM PIN entry.
• RDP sessions with multiple monitors and dock disconnects mid-session.
• Chinese IME input across core enterprise apps and text fields with character limits.
• Shared-printer queue viewing and print job workflows.
• Monitor telemetry and logs: Track WindowsUpdateClient logs, CBS/Component Store logs, and EDR/AV alerts for regressions.
• Staged rollout: If pilot is clean, deploy to broader rings incrementally and monitor for 48–72 hours before full deployment.

---

Risk assessment and troubleshooting tips​

Strengths of these updates​

• Focused, high‑impact fixes: The targeted nature of the Windows 11 fixes addresses real-world pain points that matter to remote workers, cellular-first users, and localized language environments.
• Conservative scope: Release Preview pushes minimize regression risk compared with Dev/Beta, making them suitable for early validation with lower operational exposure.
• Timely maintenance: For Windows 10, these small rollups help squeeze last-minute stability before the platform’s end of support.

Known risks and caveats​

• Sparse public detail for Windows 10: The terse Windows 10 announcement increases the onus on admins to empirically validate the update since low‑level change lists may not be available immediately.
• Driver/firmware interactions: Display/docking regressions often root in GPU or docking firmware layers; test with vendor drivers and confirm OEM firmware versions.
• Rollback complexity: If Microsoft packages combined Servicing Stack Updates (SSU) with the LCU in a single package, uninstalling may be nontrivial. Have image-based recovery and system snapshots ready as fallback options.

Troubleshooting quick steps​

• If sign-in hangs after applying the update, test network stacks by temporarily disabling WWAN and signing in on Wi‑Fi (to isolate the SIM path).
• For RDP/dock shutdowns, verify vendor dock firmware and GPU driver versions; consider limiting docking firmware updates until a validated combination is confirmed.
• If IME characters render as empty boxes after the update, ensure language packs and the IME binary are the expected versions, and test with the repro steps described in the Insider post (character limits in specific text fields).

---

Why these small updates matter — perspective for IT leaders​

At first glance, fixes such as a printer‑queue crash or a missing service description look trivial. In practice, they reduce help‑desk volume, prevent rare but damaging user interruptions, and shore up migration pathways.

• For Windows 10 customers still on 22H2, cumulative preview fixes are a pragmatic stopgap while migration plans complete. That matters when the alternative is running unsupported OS instances after October 14, 2025.
• For Windows 11-managed fleets, addressing IME and RDP/dock issues preserves productivity for hybrid workers and multinational teams.
• The Release Preview ring’s role: it’s the final validation ring. Organizations that maintain a staged rollout model should treat these flights as a cue to validate quickly and either adopt or hold, based on representative telemetry.

---

Final verdict and recommendations​

These Release Preview updates — officially documented as Build 22631.5982 (KB5065790) for Windows 11 and Build 19045.6388 (KB5066198) for Windows 10 — are conservative, targeted, and aligned with Microsoft’s quality‑first servicing for preview rings. The Windows 11 entry contains explicit, itemized fixes for meaningful real‑world issues (SIM PIN sign‑in hangs, RDP/dock shutdowns, Chinese IME rendering, shared‑printer queue crashes, and COSA updates), while the Windows 10 announcement is intentionally terse but consistent with a final servicing cadence for a platform nearing end‑of‑support.

• Individual Release Preview participants: safe to install if you need the specific fixes described.
• IT teams and enterprises: pilot these updates in a controlled ring, validate the relevant workflows noted above, and stage the rollout incrementally.
• Anyone relying on Windows 10 long term: finalize your migration path or enroll eligible devices in Extended Security Updates before October 14, 2025.

Caveat: if you encounter reporting that cites alternate final build suffixes (for example, 22631.5984 or 19045.6390) under the same KBs, treat those as provisional until Microsoft’s official Windows Insider or Support KB entries are updated; the authoritative changelog is the Windows Insider Blog and Microsoft Support pages.

---

These small but deliberate updates reflect Microsoft’s continuing emphasis on quality at the Release Preview stage: not headline features, but the subtle fixes that keep devices stable and users productive as organizations navigate the final servicing steps for Windows 10 and ongoing maintenance for Windows 11.

---

Source: Windows Report Microsoft releases Windows 11 Preview Build 22631.5984 and Windows 10 Preview Build 19045.6390 with fixes