Microsoft Known Issue

Free Trial
Known issues in Microsoft Patches:
 
Microsoft often releases patches to address security and reliability issues. Sometimes, patches itself will introduce unprecedented issues after installing them. Here's the updated list of all the known issues in Microsoft patches and possible workaround for them.

Oops! No results for your search.

workaround
Mar 12, 2025
KB5053995
2025-03 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5053995) (ESU) (CVE-2025-24991) (CVE-2025-24985) (CVE-2025-24993) (CVE-2025-24983) (CVE-2025-26633)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the How to get this update section of this article.
workaround
Mar 12, 2025
KB5053888
2025-03 Security Monthly Quality Rollup for Windows Server 2008 for x86-based Systems (KB5053888) (ESU) (CVE-2025-24991) (CVE-2025-24985) (CVE-2025-24993) (CVE-2025-24983) (CVE-2025-26633)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the "How to get this update" section of this article.
workaround
Mar 12, 2025
KB5053598
2025-03 Cumulative Update for Windows 11 Version 24H2 for arm64-based Systems (KB5053598) (CVE-2025-24991) (CVE-2025-24984) (CVE-2025-24985) (CVE-2025-24993) (CVE-2025-26633)
"We’re aware of an issue where players on Arm devices are unable to download and play Roblox from the Microsoft Store on Windows."
Roblox is working on a resolution to address this issue. Please refer to the Roblox support site for updates. Until the resolution is available, players on Arm devices can play Roblox by downloading the title directly from www.Roblox.com.
workaround
Mar 12, 2025
KB5053598
2025-03 Cumulative Update for Windows 11 Version 24H2 for arm64-based Systems (KB5053598) (CVE-2025-24991) (CVE-2025-24984) (CVE-2025-24985) (CVE-2025-24993) (CVE-2025-26633)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Mar 12, 2025
KB5053602
2025-03 Cumulative Update for Windows 11 Version 23H2 for arm64-based Systems (KB5053602) (CVE-2025-24991) (CVE-2025-24984) (CVE-2025-24985) (CVE-2025-24993) (CVE-2025-26633)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Mar 12, 2025
KB5053606
2025-03 Cumulative Update for Windows 10 Version 21H2 for x86-based Systems (KB5053606) (CVE-2025-24991) (CVE-2025-24984) (CVE-2025-24985) (CVE-2025-24993) (CVE-2025-26633)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Mar 12, 2025
KB5053606
2025-03 Cumulative Update for Windows 10 Version 21H2 for x86-based Systems (KB5053606) (CVE-2025-24991) (CVE-2025-24984) (CVE-2025-24985) (CVE-2025-24993) (CVE-2025-26633)
"The Windows Event Viewer might display an error related to SgrmBroker.exe, on devices that have installed Windows updates released January 14, 2025 or later. This error can be found under Windows Logs > System as Event 7023, with text similar to ‘The System Guard Runtime Monitor Broker service terminated with the following error: %%3489660935’. This error is only observable if the Windows Event Viewer is monitored closely. It is otherwise silent and does not appear "
No specific action is required, however, the service can be safely disabled in order to prevent the error from appearing in Event Viewer. To do so, you can follow these steps: Open a Command Prompt window. This can be accomplished by opening the Start menu and typing cmd. The results will include “Command Prompt” as a System application. Select the arrow to the right of “Command Prompt” and select “Run as administrator”. Once the window is open, carefully enter the following text: sc.exe config sgrmagent start=disabled A message may appear afterwards. Next, enter the following text: reg add HKLMSystemCurrentControlSetServicesSgrmBroker /v Start /d 4 /t REG_DWORD Close the Command Prompt window. This will prevent the related error from appearing in the Event Viewer on subsequent device start up. Note that some of these steps might be restricted by group policy set by your organization. We are working on a resolution and will provide an update in an upcoming release.
workaround
Mar 12, 2025
KB5053596
2025-03 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5053596) (CVE-2025-24991) (CVE-2025-24984) (CVE-2025-24985) (CVE-2025-24993) (CVE-2025-26633)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Mar 12, 2025
KB5053599
2025-03 Cumulative Update for Microsoft server operating system version 23H2 for x64-based Systems (KB5053599) (CVE-2025-24991) (CVE-2025-24984) (CVE-2025-24985) (CVE-2025-24993) (CVE-2025-26633)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Feb 14, 2025
KB5052072
2025-02 Security Only Quality Update for Windows Server 2008 for x86-based Systems (KB5052072) (ESU) (CVE-2025-21418)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the How to get this update section of this article.
workaround
Feb 14, 2025
KB5052038
2025-02 Security Monthly Quality Rollup for Windows Server 2008 for x86-based Systems (KB5052038) (ESU) (CVE-2025-21418) (CVE-2025-21377)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the "How to get this update" section of this article.
workaround
Feb 14, 2025
KB5052000
2025-02 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5052000) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Feb 14, 2025
KB5052000
2025-02 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5052000) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Feb 14, 2025
KB5051987
2025-02 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5051987) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"We’re aware of an issue where players on Arm devices are unable to download and play Roblox from the Microsoft Store on Windows."
Players on Arm devices can play Roblox by downloading the title directly from www.Roblox.com.
workaround
Feb 14, 2025
KB5051987
2025-02 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5051987) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Feb 14, 2025
KB5051987
2025-02 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5051987) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Feb 14, 2025
KB5051989
2025-02 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5051989) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Feb 14, 2025
KB5051989
2025-02 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5051989) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Feb 14, 2025
KB5051974
2025-02 Cumulative Update for Windows 10 Version 21H2 for x86-based Systems (KB5051974) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Feb 14, 2025
KB5051974
2025-02 Cumulative Update for Windows 10 Version 21H2 for x86-based Systems (KB5051974) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Feb 14, 2025
KB5051974
2025-02 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5051974) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"The Windows Event Viewer might display an error related to SgrmBroker.exe, on devices that have installed Windows updates released January 14, 2025 or later. This error can be found under Windows Logs > System as Event 7023, with text similar to ‘The System Guard Runtime Monitor Broker service terminated with the following error: %%3489660935’. "
No specific action is required, however, the service can be safely disabled in order to prevent the error from appearing in Event Viewer. To do so, you can follow these steps: Open a Command Prompt window. This can be accomplished by opening the Start menu and typing 'cmd'. The results will include “Command Prompt” as a System application. Select the arrow to the right of “Command Prompt” and select “Run as administrator”. Once the window is open, carefully enter the following text: sc.exe config sgrmagent start=disabled A message may appear afterwards. Next, enter the following text: reg add HKLM\System\CurrentControlSet\Services\SgrmBroker /v Start /d 4 /t REG_DWORD Close the Command Prompt window. This will prevent the related error from appearing in the Event Viewer on subsequent device start up. Note that some of these steps might be restricted by group policy set by your organization. We are working on a resolution and will provide an update in an upcoming release.
workaround
Feb 14, 2025
KB5051980
2025-02 Cumulative Update for Microsoft server operating system version 23H2 for x64-based Systems (KB5051980) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Feb 14, 2025
KB5051979
2025-02 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5051979) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"The Windows Event Viewer might display an error related to SgrmBroker.exe, on devices that have installed Windows updates released January 14, 2025 or later. This error can be found under Windows Logs > System as Event 7023, with text similar to ‘The System Guard Runtime Monitor Broker service terminated with the following error: %%3489660935’. "
No specific action is required, however, the service can be safely disabled in order to prevent the error from appearing in Event Viewer. To do so, you can follow these steps: Open a Command Prompt window. This can be accomplished by opening the Start menu and typing 'cmd'. The results will include “Command Prompt” as a System application. Select the arrow to the right of “Command Prompt” and select “Run as administrator”. Once the window is open, carefully enter the following text: sc.exe config sgrmagent start=disabled A message may appear afterwards. Next, enter the following text: reg add HKLM\System\CurrentControlSet\Services\SgrmBroker /v Start /d 4 /t REG_DWORD Close the Command Prompt window. This will prevent the related error from appearing in the Event Viewer on subsequent device start up. Note that some of these steps might be restricted by group policy set by your organization. We are working on a resolution and will provide an update in an upcoming release.
workaround
Feb 14, 2025
KB5051979
2025-02 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5051979) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Feb 14, 2025
KB5051979
2025-02 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5051979) (CVE-2025-21391) (CVE-2025-21418) (CVE-2025-21377)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Feb 10, 2025
KB5052819
2025-01 Cumulative Update Preview for Microsoft server operating system version 21H2 for x64-based Systems (KB5052819)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Feb 10, 2025
KB5052819
2025-01 Cumulative Update Preview for Microsoft server operating system version 21H2 for x64-based Systems (KB5052819)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Feb 10, 2025
KB5052819
2025-01 Cumulative Update Preview for Microsoft server operating system version 21H2 for x64-based Systems (KB5052819)
"The Windows Event Viewer might display an error related to SgrmBroker.exe, on devices that have installed Windows updates released January 14, 2025 or later. This error can be found under Windows Logs > System as Event 7023, with text similar to ‘The System Guard Runtime Monitor Broker service terminated with the following error: %%3489660935’. This error is only observable if the Windows Event Viewer is monitored closely. It is otherwise silent and does not appear "
No specific action is required, however, the service can be safely disabled in order to prevent the error from appearing in Event Viewer. To do so, you can follow these steps: Open a Command Prompt window. This can be accomplished by opening the Start menu and typing cmd. The results will include “Command Prompt” as a System application. Select the arrow to the right of “Command Prompt” and select “Run as administrator”. Once the window is open, carefully enter the following text: sc.exe config sgrmagent start=disabled A message may appear afterwards. Next, enter the following text: reg add HKLMSystemCurrentControlSetServicesSgrmBroker /v Start /d 4 /t REG_DWORD Close the Command Prompt window. This will prevent the related error from appearing in the Event Viewer on subsequent device start up. Note that some of these steps might be restricted by group policy set by your organization. We are working on a resolution and will provide an update in an upcoming release.
workaround
Feb 10, 2025
KB5050094
2025-01 Cumulative Update Preview for Windows 11 Version 24H2 for x64-based Systems (KB5050094)
"We’re aware of an issue where players on Arm devices are unable to download and play Roblox via the Microsoft Store on Windows."
Players on Arm devices can play Roblox by downloading the title directly from www.Roblox.com.
workaround
Feb 10, 2025
KB5050094
2025-01 Cumulative Update Preview for Windows 11 Version 24H2 for x64-based Systems (KB5050094)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Feb 10, 2025
KB5050094
2025-01 Cumulative Update Preview for Windows 11 Version 24H2 for x64-based Systems (KB5050094)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Feb 10, 2025
KB5050081
2025-01 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5050081)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Feb 10, 2025
KB5050081
2025-01 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5050081)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Feb 10, 2025
KB5050081
2025-01 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5050081)
"The Windows Event Viewer might display an error related to SgrmBroker.exe, on devices that have installed Windows updates released January 14, 2025 or later. This error can be found under Windows Logs > System as Event 7023, with text similar to ‘The System Guard Runtime Monitor Broker service terminated with the following error: %%3489660935’. This error is only observable if the Windows Event Viewer is monitored closely. It is otherwise silent and does not appear "
No specific action is required, however, the service can be safely disabled in order to prevent the error from appearing in Event Viewer. To do so, you can follow these steps: Open a Command Prompt window. This can be accomplished by opening the Start menu and typing cmd. The results will include “Command Prompt” as a System application. Select the arrow to the right of “Command Prompt” and select “Run as administrator”. Once the window is open, carefully enter the following text: sc.exe config sgrmagent start=disabled A message may appear afterwards. Next, enter the following text: reg add HKLMSystemCurrentControlSetServicesSgrmBroker /v Start /d 4 /t REG_DWORD Close the Command Prompt window. This will prevent the related error from appearing in the Event Viewer on subsequent device start up. Note that some of these steps might be restricted by group policy set by your organization. We are working on a resolution and will provide an update in an upcoming release.
workaround
Feb 3, 2025
KB5050092
2025-01 Cumulative Update Preview for Windows 11 Version 23H2 for arm64-based Systems (KB5050092)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Feb 3, 2025
KB5050092
2025-01 Cumulative Update Preview for Windows 11 Version 23H2 for arm64-based Systems (KB5050092)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Feb 3, 2025
KB5050008
2025-01 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5050008) (CVE-2025-21308)
"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 w"
Users can avoid this issue by avoiding the use of an external DAC in the connection process and directly plugging your audio device to your PC. We are working on a resolution and will provide an update in an upcoming release.
workaround
Feb 3, 2025
KB5050009
2025-01 Cumulative Update for Windows 11 Version 24H2 for arm64-based Systems (KB5050009) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"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 w"
This issue is addressed in KB5050094.
workaround
Feb 3, 2025
KB5050009
2025-01 Cumulative Update for Windows 11 Version 24H2 for arm64-based Systems (KB5050009) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"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 KB5050094.
workaround
Feb 3, 2025
KB5050021
2025-01 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5050021) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"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 w"
This issue is addressed in KB5050092.
workaround
Feb 3, 2025
KB5050021
2025-01 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5050021) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"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 KB5050092.
workaround
Feb 3, 2025
KB5049981
2025-01 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5049981) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"The Windows Event Viewer might display an error related to SgrmBroker.exe, on devices that have installed Windows updates released January 14, 2025 or later. This error can be found under Windows Logs > System as Event 7023, with text similar to ‘The System Guard Runtime Monitor Broker service terminated with the following error: %%3489660935’. This error is only observable if the Windows Event Viewer is monitored closely. It is otherwise silent and does not appear "
No specific action is required, however, the service can be safely disabled in order to prevent the error from appearing in Event Viewer. To do so, you can follow these steps: Open a Command Prompt window. This can be accomplished by opening the Start menu and typing cmd. The results will include “Command Prompt” as a System application. Select the arrow to the right of “Command Prompt” and select “Run as administrator”. Once the window is open, carefully enter the following text: sc.exe config sgrmagent start=disabled A message may appear afterwards. Next, enter the following text: reg add HKLMSystemCurrentControlSetServicesSgrmBroker /v Start /d 4 /t REG_DWORD Close the Command Prompt window. This will prevent the related error from appearing in the Event Viewer on subsequent device start up. Note that some of these steps might be restricted by group policy set by your organization. We are working on a resolution and will provide an update in an upcoming release.
workaround
Feb 3, 2025
KB5049981
2025-01 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5049981) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"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 w"
This issue is addressed in KB5050081.
workaround
Feb 3, 2025
KB5049981
2025-01 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5049981) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"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.
workaround
Feb 3, 2025
KB5049993
2025-01 Cumulative Update for Windows 10 Version 1607 for x86-based Systems (KB5049993) (CVE-2025-21308)
"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 w"
Users can avoid this issue by avoiding the use of an external DAC in the connection process and directly plugging your audio device to your PC. We are working on a resolution and will provide an update in an upcoming release.
workaround
Feb 3, 2025
KB5049983
2025-01 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5049983) (CVE-2025-21275) (CVE-2025-21308)
"The Windows Event Viewer might display an error related to SgrmBroker.exe, on devices that have installed Windows updates released January 14, 2025 or later. This error can be found under Windows Logs > System as Event 7023, with text similar to ‘The System Guard Runtime Monitor Broker service terminated with the following error: %%3489660935’. This error is only observable if the Windows Event Viewer is monitored closely. It is otherwise silent and does not appear "
No specific action is required, however, the service can be safely disabled in order to prevent the error from appearing in Event Viewer. To do so, you can follow these steps: Open a Command Prompt window. This can be accomplished by opening the Start menu and typing cmd. The results will include “Command Prompt” as a System application. Select the arrow to the right of “Command Prompt” and select “Run as administrator”. Once the window is open, carefully enter the following text: sc.exe config sgrmagent start=disabled A message may appear afterwards. Next, enter the following text: reg add HKLMSystemCurrentControlSetServicesSgrmBroker /v Start /d 4 /t REG_DWORD Close the Command Prompt window. This will prevent the related error from appearing in the Event Viewer on subsequent device start up. Note that some of these steps might be restricted by group policy set by your organization. We are working on a resolution and will provide an update in an upcoming release.
workaround
Feb 3, 2025
KB5049983
2025-01 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5049983) (CVE-2025-21275) (CVE-2025-21308)
"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 w"
Users can avoid this issue by avoiding the use of an external DAC in the connection process and directly plugging your audio device to your PC. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jan 16, 2025
KB5050061
2025-01 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5050061) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the How to get this update section of this article.
workaround
Jan 16, 2025
KB5050063
2025-01 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5050063) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the "How to get this update" section of this article.
workaround
Jan 16, 2025
KB5050008
2025-01 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5050008) (CVE-2025-21308)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Jan 16, 2025
KB5050008
2025-01 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5050008) (CVE-2025-21308)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Jan 16, 2025
KB5050009
2025-01 Cumulative Update for Windows 11 Version 24H2 for arm64-based Systems (KB5050009) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"We’re aware of an issue where players on Arm devices are unable to download and play Roblox via the Microsoft Store on Windows."
Players on Arm devices can play Roblox by downloading the title directly from www.Roblox.com.
workaround
Jan 16, 2025
KB5050009
2025-01 Cumulative Update for Windows 11 Version 24H2 for arm64-based Systems (KB5050009) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Jan 16, 2025
KB5050009
2025-01 Cumulative Update for Windows 11 Version 24H2 for arm64-based Systems (KB5050009) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Jan 16, 2025
KB5050021
2025-01 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5050021) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Jan 16, 2025
KB5050021
2025-01 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5050021) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Jan 16, 2025
KB5049981
2025-01 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5049981) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Jan 16, 2025
KB5049981
2025-01 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5049981) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275) (CVE-2025-21308)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Jan 16, 2025
KB5049984
2025-01 Cumulative Update for Microsoft server operating system version 23H2 for x64-based Systems (KB5049984) (CVE-2025-21333) (CVE-2025-21334) (CVE-2025-21335) (CVE-2025-21275)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Jan 16, 2025
KB5049983
2025-01 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5049983) (CVE-2025-21275) (CVE-2025-21308)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Jan 16, 2025
KB5049983
2025-01 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5049983) (CVE-2025-21275) (CVE-2025-21308)
"Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with Citrix Session Recording Agent (SRA) version 2411. The 2411 version of this application was released in December 2024. Affected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when rest"
Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix’s documentation. Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.
workaround
Dec 23, 2024
KB5048744
2024-12 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5048744)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the How to get this update section of this article.
workaround
Dec 23, 2024
KB5048710
2024-12 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5048710)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the How to get this update section of this article.
workaround
Dec 18, 2024
KB5048685
2024-12 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5048685)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Dec 18, 2024
KB5048667
2024-12 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5048667) (CVE-2024-49138)
"We’re aware of an issue where players on Arm devices are unable to download and play Roblox via the Microsoft Store on Windows."
Players on Arm devices can play Roblox by downloading the title directly from www.Roblox.com.
workaround
Dec 18, 2024
KB5048667
2024-12 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5048667) (CVE-2024-49138)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Dec 18, 2024
KB5046740
2024-11 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5046740)
"We’re aware of an issue where players on Arm devices are unable to download and play Roblox via the Microsoft Store on Windows."
Players on Arm devices can play Roblox by downloading the title directly from www.Roblox.com.
workaround
Dec 18, 2024
KB5046740
2024-11 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5046740)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Dec 18, 2024
KB5046613
2024-11 Cumulative Update for Windows 10 Version 22H2 for x86-based Systems (KB5046613) (CVE-2024-43451) (CVE-2024-49039)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Dec 18, 2024
KB5046617
2024-11 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5046617) (CVE-2024-43451) (CVE-2024-49039) (CVE-2024-49019)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Dec 18, 2024
KB5046618
2024-11 Cumulative Update for Microsoft server operating system version 23H2 for x64-based Systems (KB5046618) (CVE-2024-43451) (CVE-2024-49039) (CVE-2024-49019)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Dec 11, 2024
KB5048661
2024-12 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5048661)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Dec 11, 2024
KB5048654
2024-12 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5048654)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Nov 14, 2024
KB5046615
2024-11 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5046615) (CVE-2024-43451) (CVE-2024-49039) (CVE-2024-49019)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Nove 14, 2024
KB5046616
2024-11 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5046616) (CVE-2024-43451) (CVE-2024-49039) (CVE-2024-49019)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:ProgramDatassh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Nov 14, 2024
KB5046639
2024-11 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5046639) (ESU) (CVE-2024-43451) (CVE-2024-49019)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the How to get this update section of this article.
workaround
Nov 13, 2024
KB5046661
2024-11 Security Monthly Quality Rollup for Windows Server 2008 for x86-based Systems (KB5046661) (ESU) (CVE-2024-43451) (CVE-2024-49019)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the "How to get this update" section of this article.
workaround
Nov 13, 2024
KB5046633
2024-11 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5046633) (CVE-2024-43451) (CVE-2024-49039)
"Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process. This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro "
Customers can temporarily resolve the issue by updating permissions (ACLs) on the affected directories. Follow these steps: Open PowerShell as an Administrator. Update the permissions for C:ProgramDatassh and C:ProgramDatasshlogs to allow full control for SYSTEM and the Administrators group, while allowing read access for Authenticated Users. You can restrict read access to specific users or groups by modifying the permissions string if needed. Use the following commands to update the permissions: $directoryPath = "C:\ProgramData\ssh" $acl = Get-Acl -Path $directoryPath $sddlString = "O:BAD:PAI(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;0x1200a9;;;AU)" $securityDescriptor = New-Object System.Security.AccessControl.RawSecurityDescriptor $sddlString $acl.SetSecurityDescriptorSddlForm($securityDescriptor.GetSddlForm("All")) Set-Acl -Path $directoryPath -AclObject $acl. Repeat the above steps for C:ProgramDatasshlogs. Microsoft is actively investigating the issue and will provide a resolution in an upcoming Windows update. Further communications will be provided when a resolution or additional workarounds are available.
workaround
Nov 13, 2024
KB5046617
2024-11 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5046617) (CVE-2024-43451) (CVE-2024-49039) (CVE-2024-49019)
"We’re aware of an issue where players on Arm devices are unable to download and play Roblox via the Microsoft Store on Windows."
Players on Arm devices can play Roblox by downloading the title directly from www.Roblox.com.

Disclaimer:This webpage is intended to provide you information about patch announcement for certain specific software products. The information is provided "As Is" without warranty of any kind. The links provided point to pages on the vendors websites. You can get more information by clicking the links to visit the relevant pages on the vendors website.

 

Was this article helpful?

Thank you for your feedback!

Sorry about that!

By clicking "Submit", you agree to processing of personal data according to thePrivacy Policy.

Trusted by

Back to Top