KB5075906 for Windows Server 2022 – What the Fixes Mean and How to Enable DNS Shuffle
The latest cumulative update (OS Build 20348.4773) bundles a handful of long‑standing annoyances and a tiny new networking tweak. This article explains which problems actually get resolved, why they matter to a production server, and how to turn on the random DNS record shuffling without digging through a mountain of documentation.
File Explorer rename glitch
A subtle bug in Explorer ignored the LocalizedResourceName entry inside desktop.ini files, so folders that were supposed to show a friendly name kept displaying the raw folder name. The issue only shows up when custom language packs or third‑party themes rewrite folder labels—something many admins have run into after deploying a localized resource pack on a shared file server. After installing KB5075906 the rename operation respects the desktop.ini setting, meaning those prettily named folders finally appear as intended in every user’s view.
Chinese font update
The update expands the GB18030‑2022A character set for Simplified Chinese fonts. In practice this stops odd “tofu” squares from appearing when legacy documents contain rare glyphs introduced by recent Unicode revisions. Companies with multilingual content pipelines have reported fewer rendering complaints after applying the patch, so it’s a straightforward win if any Chinese text is served from the server.
GPU driver crash fix
Servers that run heavy graphics workloads—think remote desktop farms or AI inference nodes—have occasionally hit a KERNEL_SECURITY_CHECK_FAILURE because the dxgmms2.sys component mis‑handled certain GPU configurations. The root cause was a race condition in the driver’s memory manager, and it manifested as an instantaneous reboot under load. KB5075906 patches the driver layer, so the kernel check no longer trips on those edge‑case GPU setups.
VSM shutdown bug
Virtual Secure Mode (VSM) is great for isolating secrets, but a recent security update introduced a regression where machines with VSM would refuse to power down or hibernate; instead they performed an abrupt restart. The behavior broke scheduled maintenance scripts that rely on graceful shutdowns. This cumulative update restores the proper shutdown path, letting admins keep their automated tasks intact.
Enable random DNS shuffling
A brand‑new feature lets Windows Server shuffle the order of resource records in a DNS response. By rotating which A or AAAA record appears first, traffic is spread more evenly across load‑balanced backends that otherwise suffered from “first‑record bias.” To activate it, create a DWORD value named RandomShuffle under
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters
and set the data to 1. After the change, restart the DNS Server service or reboot the host for the setting to take effect. If the shuffling causes unexpected client behavior—unlikely but possible in tightly scripted environments—simply revert the value to 0 or delete it entirely and reload the service.
Known side‑effects
Two quirks linger after the update. First, Windows Server Update Services (WSUS) no longer shows detailed synchronization error messages; this was a deliberate trade‑off to close CVE‑2025‑59287, a remote code execution flaw in the WSUS reporting pipeline. Administrators who rely on those details will need to consult the event logs directly for deeper diagnostics. Second, the DNS shuffle feature may expose legacy applications that hard‑code expectations about record order; testing before rollout is advisable.
That’s the gist of what KB5075906 brings to a Windows Server 2022 box. Apply it when you can—most of the fixes address real pain points that have been surfacing for months, and the DNS tweak offers a low‑effort way to balance traffic without touching your load balancer configuration.
February 10, 2026—KB5075906 (OS Build 20348.4773)
February 10, 2026—KB5075906 (OS Build 20348.4773) - Microsoft Support
