compatibility hold Archives

Winsage

February 12, 2025

Microsoft finally fixes some of Windows 11’s most annoying problems with new patch

Windows 11 released its February 2025 cumulative update, identified as KB5051987 for Windows 11 24H2 and KB5051989 for 23H2. This update fixes several bugs, including an Auto HDR issue that caused color distortion and game crashes, a bug affecting digital-to-analog converters (DACs), and a 'This device cannot start' audio error. It also resolves USB webcam detection issues. The compatibility hold for certain PCs to receive the 24H2 update has been lifted, allowing more users to access the latest features.

Winsage

December 20, 2024

Microsoft blocks Windows 11 24H2 update on more PCs due to new gaming issues

Many users view Windows 11 as a reimagined version of Windows 10, but it includes exclusive features for gamers. Microsoft has restricted access to the latest Windows 11 update due to complications with the Auto HDR feature, which enhances visuals by converting SDR content to HDR. A bug in Auto HDR has caused games to display incorrect colors or freeze. Microsoft has not specified which devices or games are affected and has implemented a compatibility hold on devices using Auto HDR, preventing them from installing Windows 11 version 24H2. Users are advised to disable Auto HDR to proceed with the update. Additionally, there have been other gaming-related issues with Windows 11 version 24H2, including crashes in games using Easy Anti-Cheat and responsiveness issues in titles like Asphalt 8, along with compatibility challenges with certain Ubisoft games.

Winsage

December 20, 2024

Gamers beware: Windows 11 24H2 update could wreck your colors and crash your games

Windows 11's 24H2 update has introduced a bug affecting users with the Auto HDR feature, causing incorrect color displays and potential game crashes. Microsoft has acknowledged the issue, which impacts both gaming and desktop environments. Users have reported crashes in popular games like Call of Duty, Assassin’s Creed, and Far Cry. To address the problem, Microsoft suggests disabling Auto HDR or staying on the previous version, 23H2. A compatibility hold has been placed on devices with Auto HDR enabled, preventing them from receiving the 24H2 update until a fix is available. Users can turn off Auto HDR in the Settings menu under Display and Graphics.

Winsage

December 20, 2024

Microsoft says Auto HDR causes game freezes on Windows 11 24H2

Microsoft has implemented a block on Windows 11 24H2 upgrades for systems with Auto HDR enabled due to reports of game freezes and graphical anomalies. Auto HDR enhances gaming visuals but has caused concerns among users regarding high-contrast and oversaturated visuals. Microsoft warned that enabling Auto HDR could lead to incorrect color representation and unresponsive games. Users experiencing issues are advised to disable Auto HDR through the 'Settings' app. A compatibility hold has been placed on devices with Auto HDR enabled, tagged with safeguard ID 55382406. Additionally, Microsoft has lifted a previous compatibility hold related to Ubisoft game bugs and blocked upgrades on systems with outdated Google Workspace Sync installations and incompatible Intel Smart Sound Technology audio drivers.

Winsage

December 19, 2024

Windows 11 24H2 upgrades blocked on some PCs due to audio issues

Microsoft has implemented a safeguard hold on the Windows 11 24H2 upgrade for systems using Dirac audio enhancement software due to compatibility issues that disrupt sound output. The problem is associated with the cridspapo.dll software component, which affects integrated speakers, Bluetooth speakers, and headsets, rendering them non-functional after the upgrade. Users are advised not to manually upgrade their devices until Dirac releases a fix for their audio driver. The safeguard hold will remain until the issue is resolved. Affected users can check for safeguard holds in Windows Update settings. Additionally, Microsoft has introduced another upgrade block for Windows 11 24H2 concerning systems with Auto HDR due to compatibility issues causing game freezes.

Winsage

December 19, 2024

Microsoft Stops Updates For Millions Of Windows Users—Here’s What You Do Now

Windows users are experiencing issues with the Windows 11 24H2 update due to a compatibility problem with the AutoHDR feature, which causes incorrect color display in games and applications. Microsoft has acknowledged this issue and implemented a compatibility hold, preventing devices with Auto HDR enabled from receiving the update. Users can resolve the issue by disabling Auto HDR in the settings. Microsoft is working on a fix and advises against manually updating to version 24H2 until the problem is resolved.

Winsage

December 19, 2024

Microsoft confirms even more Windows 11 24H2 bugs: audio output is now affected

Windows 11 version 24H2 has two notable bugs affecting gamers and audio functionality. One issue involves the Auto HDR feature for gamers, while the other affects sound output across devices due to complications with the cridspapo.dll file, which is part of Dirac Audio technology. Microsoft has implemented a temporary update block for certain devices from a specific manufacturer due to these audio issues, preventing sound through integrated speakers, Bluetooth devices, and headsets. Users can check for updates to see if their devices are impacted, and currently, no workarounds exist. Microsoft plans to release an updated driver to resolve the issue and lift the upgrade block. Additionally, another audio bug in this version causes systems to output sound at 100% volume, which Microsoft is also addressing.

Winsage

December 14, 2024

Microsoft will still let Windows 11 users send a fax, should they ever want that

Microsoft resolved a connectivity issue affecting eSCL devices, including USB-connected scanners and fax machines, for users who upgraded to Windows 11, version 24H2. A compatibility hold was implemented to prevent complications, which was first reported on November 22. On December 10, Microsoft announced that the hold (ID 54762729) would be lifted, allowing users to upgrade without concerns, with some devices receiving the update within 48 hours. As of now, Windows 11 accounts for approximately 34.9% of all Windows installations, while Windows 10 holds a 61.8% share.

Winsage

December 12, 2024

Microsoft releases KB5048667 update, removing another Windows 11 24H2 block and introducing a questionable change

Microsoft has updated Windows 11 to version 24H2 with the KB5048667 update, removing a compatibility block for USB scanners using the eSCL scan protocol. This change allows affected systems to install the update more smoothly. The update also modifies the date format on the taskbar, includes critical security fixes, and introduces several new features such as: - Rebranding of "Tailored Experiences" to "Personalized offers." - A shortened date and time format in the system tray, with an option to revert to the traditional format. - Access to jump lists for pinned apps in the Start menu. - Customizable touchscreen edge gestures. - Hiding of the IME toolbar in full-screen mode for Chinese or Japanese typing. - Sharing content directly to Android devices from File Explorer. - New placeholder messages in Dynamic Lighting Settings when no compatible device is connected. - Enhancements to speech-to-text and text-to-speech functionalities. - New functions in Narrator scan mode for improved accessibility. The update can be accessed via Windows Update or downloaded from the Microsoft Update Catalog.

Winsage

December 12, 2024

Microsoft fixes scanner discovery glitch in Windows 11 24H2

Microsoft has resolved compatibility issues related to the Scanner Communication Language (eSCL) protocol that affected device discovery for scanners and fax machines on Windows 11 systems. The problem, which prevented devices from being discovered, was acknowledged by Microsoft and addressed in the KB5048667 security update released on December 10. Affected users may need to wait up to 48 hours to receive the upgrade to Windows 11 24H2, although restarting the device may expedite this process. The issue was caused by devices failing to transition from eSCL mode to USB mode, necessary for proper driver matching. The compatibility hold impacted various devices using the eSCL protocol, including printers and modems. Users were advised against manually bypassing the hold to ensure adherence to safeguards. With the fix, devices should now be recognized correctly during the discovery process.