random text

Winsage
March 28, 2025
Microsoft has addressed an issue affecting Remote Desktop Protocol (RDP) and Remote Desktop Services (RDS) connections for users connecting from Windows 11 24H2 to RDS hosts on earlier versions of Windows Server 2016, which arose after installing Windows updates since January 2025. Users reported disconnections after 65 seconds when establishing UDP connections. Affected users were advised to install the KB5053656 preview update to resolve the issue, which will be generally available with next month's cumulative updates. Additionally, Microsoft is working on fixing another issue causing Remote Desktop freezes on Windows Server 2025 and is investigating connection errors related to data restoration on Windows 11 24H2 systems. A bug causing USB printers to print random text has also been resolved.
Winsage
March 27, 2025
Microsoft released the KB5053657 update on Tuesday to address an issue in Windows 11 where certain USB printers were printing random text. This update is applicable only to Windows 11 23H2 and 22H2 versions, while users of Windows 11 24H2 do not have an equivalent update yet. The USB printer issue originated from a problematic update released in January 2025, which affected multiple patches. Microsoft clarified that the update fixes issues with USB connected dual-mode printers that might output incorrect text. Additionally, complications from the January update for Windows 11 24H2 have caused Remote Desktop Protocol (RDP) disconnections. Microsoft is implementing a Known Issue Rollback to revert the problematic changes, with a permanent solution expected in a future update for Windows 11 24H2.
Winsage
March 27, 2025
Microsoft has acknowledged a significant issue affecting Remote Desktop functionality on Windows Server 2025 systems, which arose after the installation of security updates released since February 2025. Users may experience freezes in Remote Desktop sessions shortly after connecting, with unresponsive mouse and keyboard inputs requiring a disconnect and reconnect to regain functionality. This issue also affects Windows 11 24H2 systems, but Microsoft addressed it for Windows 11 users with an optional update (KB5052093) released on February 25. A fix for Windows Server 2025 devices is planned for an upcoming update. Additionally, Microsoft has implemented Known Issue Rollback (KIR) to reverse problematic non-security updates related to Remote Desktop and Remote Desktop Services (RDS) connection issues from Windows 11 24H2 updates since January 2025. Users may experience Remote Desktop Protocol (RDP) disconnections lasting up to 65 seconds when connecting from Windows 11 24H2 devices to RDS hosts on Windows Server 2016 systems. A permanent fix for RDP disconnection issues is planned for next month's cumulative updates. Microsoft is also investigating connection errors on Windows 11 24H2 systems related to restoring data from SMB network shares or Backup & Replication servers.
Winsage
March 26, 2025
Microsoft has resolved an issue affecting USB printers that began after Windows updates in January 2025, which caused printers to produce random text. This fix is included in the March 2025 non-security preview updates KB5053643 and KB5053657 for Windows 10 (version 22H2) and Windows 11 (versions 22H2 and 23H2). The resolution will also be part of the cumulative updates for April 2025 Patch Tuesday. The problem was particularly noticeable when printers were powered on or reconnected, leading to erroneous outputs related to the Internet Printing Protocol (IPP). Microsoft acknowledged that the issue arose after the January 2025 preview update (KB5050092). Additionally, Microsoft has addressed another issue affecting Remote Desktop and RDS connections and is collaborating with Veeam to investigate connection errors on Windows 11 24H2 systems.
Winsage
March 26, 2025
Microsoft released an update, KB5053657, on March 25 to address printer issues caused by a previous patch in January that affected USB-connected dual-mode printers. Users reported printers producing random text and data, often starting with the header POST /ipp/print HTTP/1.1. The glitch was acknowledged in the March 11 update, which also unintentionally removed the Copilot application from some devices. Microsoft stated that the Copilot issue has been resolved without needing a patch. Additionally, users of version 2411 of the Citrix Session Recording Agent are still experiencing issues, and Microsoft is working with Citrix on a solution.
Winsage
March 20, 2025
Microsoft has released Windows 11 Build 27818 for users in the Canary Channel, enhancing File Explorer's performance for extracting zip files. The update includes general improvements and fixes, such as displaying additional details about Pluton TPM chips in the Windows Security app. The suggested actions feature for copying phone numbers or future dates is being deprecated. A critical fix addresses a d3d9.dll crash affecting application launches. Other improvements include enhanced performance for unzipping files, fixes for File Explorer Home loading issues, taskbar app window preview corrections, resolution of a ctmon.exe crash impacting typing, fixes for Settings launch errors, graphics performance improvements, resolution of Visual Studio Code installation issues with Admin Protection, and fixes for Remote Desktop freezing issues. Additionally, a fix addresses application opening failures related to a virtual machine component error.
Winsage
March 13, 2025
Users have reported that their printers are unexpectedly printing random text and IPP protocol headers instead of the intended document, primarily affecting USB-connected dual-mode printers. This issue is linked to Microsoft's K5050092 update released on January 29, 2025. The problem manifests when printers are powered on or reconnected after disconnection, impacting various Windows versions, including Windows 11 version 23H2, version 22H2, and Windows 10 22H2. A temporary workaround, Known Issue Rollback (KIR), has been provided for system administrators to revert affected machines to a previous state. A permanent fix is being developed by Microsoft.
Search