All posts

Update known issues: what changed on October 22, 2026

October 22, 2026 · Senserva Patch Tracker

Senserva Watch

Join Senserva Watch and get Three Free Unlimited Audits with our full Claude MCP, a fresh audit credit every quarter, alerts when a CVE or KB you follow changes, critical security updates when they land, the Patch Tuesday wire on release day, and 20% off when you buy.

Join Senserva Watch

One email address. No tenant connection, no agent, no call.

What Microsoft changed in update known issues, October 22, 2026

Each day we read the Known issues section of Microsoft's support article for every recent Windows and Office update and record what changed. Since our last post, Microsoft changed that section on 24 updates. Every quote below is Microsoft's own text, from the article linked beside it.

Known issues Microsoft updated

"Known Issues: After installing the August 2026 .NET Framework cumulative update, some WPF applications may fail with a System.IO.FileFormatException when printing or generating PDF/XPS content that uses certain fonts, including Calibri."

Microsoft changed the text of this known issue for:

  • KB5120698 (Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 and Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019), Microsoft's article
  • KB5120699 (Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012), Microsoft's article
  • KB5120700 (Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 R2), Microsoft's article
  • KB5120701 (Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 and Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 22H2), Microsoft's article
  • KB5120702 (Microsoft .NET Framework 4.8 on Windows Server 2016 and Microsoft .NET Framework 4.8 on Windows 10 Version 1607), Microsoft's article
  • KB5120703 (Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 and Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019), Microsoft's article
  • KB5120704 (Microsoft .NET Framework 4.8 on Windows Server 2012), Microsoft's article
  • KB5120705 (Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022), Microsoft's article
  • KB5120706 (Microsoft .NET Framework 4.8 on Windows Server 2012 R2), Microsoft's article
  • KB5120708 (Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2025 and Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 25H2), Microsoft's article
  • KB5120709 (Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 22H2), Microsoft's article
  • KB5120710 (Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 24H2), Microsoft's article
  • KB5120711 (Microsoft .NET Framework 4.8.1 on Windows 11 version 26H1 and Microsoft .NET Framework 4.8.1 on Windows 11 Version 26H1), Microsoft's article
  • KB5120713 (Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 23H2), Microsoft's article
  • KB5120714 (Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022), Microsoft's article

The new text, in Microsoft's words:

Status: This issue is resolved in the October 2026 .NET Framework cumulative update and later updates.

"|"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

Although Windows updates released January 14, 2025, conflict with the initialization of this service, no impact to performance or functionality should be observed. There is no change to the security level of a device resulting from this issue. This service has already been disabled in other supported versions of Windows, and SgrmBroker.exe presently serves no purpose.Note: There is no need to manually start this service or configure it in any way (doing so might trigger errors unnecessarily). Future Windows updates will adjust the components used by this service and SgrmBroker.exe. For this reason, please do not attempt to manually uninstall or remove this service or its components. | This issue is addressed in KB5055612 . | After installing this security update, you might experience issues with USB audio devices. You are more likely to experience this issue if you are using a USB 1.0 audio driver based DAC (Digital to Analog converter) in your audio setup. This issue might cause USB audio devices to stop working, preventing audio playback.DACs (Digital-to-Analog Converters) are commonly used in scenarios where users need to improve the quality of their audio systems. A few scenarios where they are used are home audio systems, professional music studios and portable music players.Resulting from this issue, the Device Manager might display the error ‘This device cannot start. (Code 10) Insufficient system resources exist to complete the API’. | This issue is addressed in KB5050081 . | After installing this security update, you might experience issues with USB cameras. Your device might not recognize the camera is on. | This issue is addressed in KB5050081 .

"|"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

| After installing this security update, you might experience issues with USB cameras. Your device might not recognize the camera is on.

"Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

Navigate to: Computer Configuration > Administrative Templates > Windows Components > BitLocker Drive Encryption > Operating System Drives . Set Configure TPM platform validation profile for native UEFI firmware configurations to Not Configured . Run the following command on affected devices to propagate the policy change: gpupdate /force Run the following command to suspend BitLocker (if BitLocker is enabled on the C: drive): manage-bde -protectors -disable C: Run the following command to resume BitLocker (if BitLocker is enabled on the C: drive): manage-bde -protectors -enable C: This updates the BitLocker bindings to use the Windows-selected default PCR profile. If you do not wish to remove this Group Policy configuration, you can install the new Windows Boot Manager by temporarily suspending BitLocker and installing the Secure Boot update. To do this: Run the following command to suspend BitLocker (if BitLocker is enabled on the C: drive): manage-bde -protectors -disable C: Run the following command: Start-ScheduledTask -TaskName \\Microsoft\\Windows\\PI\\Secure-Boot-Update Restart the device. Once the new Windows Boot Manager is successfully installed, enable BitLocker by running the command: manage-bde -protectors -enable C:

"Domain-joined devices might lose their secure trust relationship with the domain"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

MII enforcement will be prevented regardless of the MII configuration.

"File History might stop working after installing September 2026 Windows update"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

File History, available through Control Panel > System and Security > File History , is used to back up files to an external drive or network location. Affected devices might incorrectly display a "Reconnect your drive" message even when a compatible backup drive is connected and functioning properly. Additionally, the "Last Backup" timestamp might not update, and previously backed up files might show "No previous version available." In some cases, Event Viewer might record application crash events referencing FileHistory.exe and KERNELBASE.dll . This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5126657 .

"File History might stop working after installing September 2026 Windows update"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

After installing the September 2026 Windows security update KB5124008 , some customers using File History, might be unable to create or update backups. File History, available through Control Panel > System and Security > File History , is used to back up files to an external drive or network location. Affected devices might incorrectly display a "Reconnect your drive" message even when a compatible backup drive is connected and functioning properly. Additionally, the "Last Backup" timestamp might not update, and previously backed up files might show "No previous version available." In some cases, Event Viewer might record application crash events referencing FileHistory.exe and KERNELBASE.dll . This issue is resolved in Windows updates released on and after September 22, 2026 such as KB5124010 .

"File History might stop working after installing September 2026 Windows update"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

After installing the September 2026 Windows security update KB5124008 , some customers using File History, might be unable to create or update backups. File History, available through Control Panel > System and Security > File History , is used to back up files to an external drive or network location. Affected devices might incorrectly display a "Reconnect your drive" message even when a compatible backup drive is connected and functioning properly. Additionally, the "Last Backup" timestamp might not update, and previously backed up files might show "No previous version available." In some cases, Event Viewer might record application crash events referencing FileHistory.exe and KERNELBASE.dll . This issue is resolved in Windows updates released on and after October 13, 2026 such as KB5126653 . We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.

"File History might stop working after installing September 2026 Windows update"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

After installing the September 2026 Windows security update KB5124008 , some customers using File History, might be unable to create or update backups. File History, available through Control Panel > System and Security > File History , is used to back up files to an external drive or network location. Affected devices might incorrectly display a "Reconnect your drive" message even when a compatible backup drive is connected and functioning properly. Additionally, the "Last Backup" timestamp might not update, and previously backed up files might show "No previous version available." In some cases, Event Viewer might record application crash events referencing FileHistory.exe and KERNELBASE.dll . This issue is resolved in Windows updates released on and after September 22, 2026 such as KB5124006 .

"Host folder shares might be unavailable in Hyper-V-based Linux VMs"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

​​​​​​​​​ After installing the September 2026 security update (KB5124008), applications that use HCS-managed virtual machines might experience issues when sharing host folder with Linux VMs using Plan9. Affected virtual machines start normally, but folders shared from the Windows host using Plan9 do not appear or cannot be accessed in the guest environment. Applications or sandbox environments that depend on these shared folders might display an error indicating that no Plan9 drive shares were mounted. Claude Cowork and the Windows Subsystem for Linux (WSL) are two of the applications affected by this issue. Standard Hyper-V virtual machines that do not use the Plan9 feature are not affected by this issue. Resolutions This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129195 .

"Host folder shares might be unavailable in Hyper-V-based Linux VMs"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

​​​​​​​​​ After installing the September 2026 security update (KB5124012), applications that use HCS-managed virtual machines might experience issues when sharing host folder with Linux VMs using Plan9. Affected virtual machines start normally, but folders shared from the Windows host using Plan9 do not appear or cannot be accessed in the guest environment. Applications or sandbox environments that depend on these shared folders might display an error indicating that no Plan9 drive shares were mounted. Claude Cowork and the Windows Subsystem for Linux (WSL) are two of the applications affected by this issue. Standard Hyper-V virtual machines that do not use the Plan9 feature are not affected by this issue. This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129194 .

"Print to PDF might not work"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

To address this, try enabling the Printing-PrintToPDFServices-Feature using one of the following options: Option 1: Press Windows + R , type optional features, and enable Microsoft Print to PDF in the Windows Features dialog. Option 2: Open PowerShell as Administrator and run the following commands: Disable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices-Features Enable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices-Features Note The final command might encounter an error with code 0x800f0922 . This issue is addressed in KB5060829 .

"Remote Desktop Services might stop responding after September 2026 security update"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.

"Remote Desktop Services might stop responding after September 2026 security update"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

After installing the September 2026 Windows security update, some organizations might experience issues with Remote Desktop Services (RDS). In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator. Note This issue does not affect Windows 365 or Azure Virtual Desktop. This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129195 .

"Remote Desktop Services might stop responding after September 2026 security update"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator. Note This issue does not affect Windows 365 or Azure Virtual Desktop. This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129242 . We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.

"Remote Desktop Services might stop responding after September 2026 security update"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

After installing the September 2026 Windows security update, some organizations might experience issues with Remote Desktop Services (RDS). In some environments, RDS might become unstable, resulting in RDP connections failing after several minutes, sign-in issues, or servers hanging at "Please wait for the Remote Desktop Configuration". Related tools, including Microsoft Management Console (MMC), RDS Licensing Diagnoser, and File Explorer might also become unresponsive. Additionally, the Windows Update page might stop responding and continuously display a loading indicator. Note This issue does not affect Windows 365 or Azure Virtual Desktop. This issue is resolved in Windows updates released on and after September 14, 2026 such as KB5129194 .

"USB audio devices might fail to start or produce no sound"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

​​​​​​​​​ After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: ​The device displays an error in Device Manager: "This device cannot start (Code 10).” ​ No audio output. ​ Volume controls are unresponsive or remain at zero. ​ Sound settings are unresponsive or unavailable. ​ Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices. This issue is partially resolved in the out-of-band (OOB) update released on September 14, 2026, (KB5129195) . This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. Microsoft is working to address the other symptoms and will provide more information when it is available. IT administrators who need an immediate workaround for the symptoms not addressed yet by the OOB update should contact Microsoft Support for Business for assistance.

"USB audio devices might fail to start or produce no sound"

Microsoft changed the text of this known issue for:

The new text, in Microsoft's words:

​​​​​​​​​ After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms: ​The device displays an error in Device Manager: "This device cannot start (Code 10).” ​ No audio output. ​ Volume controls are unresponsive or remain at zero. ​ Sound settings are unresponsive or unavailable. ​ Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode. This issue is limited to USB Audio Class 1.0 devices. This issue is partially resolved in the out-of-band (OOB) update released on September 14, 2026, (KB5129194) . This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. Microsoft is working to address the other symptoms and will provide more information when it is available. IT administrators who need an immediate workaround for the symptoms not addressed yet by the OOB update should contact Microsoft Support for Business for assistance.

Every recent update and its known issues are on our Microsoft patch tracker.

Compiled automatically by the Senserva Patch Tracker from Microsoft's support articles. No AI writes this post: every quote is copied from the article it links, and an issue counts as changed only when Microsoft's text changed. Sources and their terms are on our Data sources & thanks page. Facts as of 2026-10-22.

All posts

Patching across Intune, Windows Autopatch, Defender, Azure, and your endpoint managers: see Senserva patching in action.