Windows 11 24H2 Update: 12 Major Bugs and User Frustrations

  • Thread Author
Microsoft’s rollout of the Windows 11 24H2 update, which was designed to enhance features like Copilot AI, improve File Explorer, and deliver a smoother user experience, has faced significant turbulence since its official release on October 1, 2024. The much-anticipated update intended to refine performance and stability is turning into a nightmare for many users due to a burgeoning list of bugs and compatibility issues.
While Microsoft continues to address these problems by pushing patches, several serious glitches remain unresolved, and new ones seem to be cropping up. If you’ve been eyeing the update for your system, you might want to hit pause. Here’s a breakdown of 12 major bugs currently plaguing Windows 11 24H2 and why waiting this one out could save you a lot of frustration.

1. Ubisoft Game Crashes: Assassin’s Creed Fans Beware

Trying to dive into your favorite Ubisoft games like Assassin’s Creed Origins or the much-anticipated Avatar: Frontiers of Pandora? You might hit a wall—or rather, a black screen or hard crash. Ubisoft has issued some temporary hotfixes for their newer titles (Star Wars Outlaws and Avatar), but performance issues persist across others.
This appears to stem from compatibility problems with underlying game-engines or DirectX interplay with Windows 11 24H2’s code. Gamers may need to wait for permanent resolutions, currently being worked on by Ubisoft and Microsoft.

2. Auto HDR Glitches: Gaming’s Visuals Gone Wrong

Auto HDR, the feature that dynamically converts SDR graphics to HDR for richer visuals, is causing some games to display wildly incorrect colors—or worse, fail to function entirely. For those who rely on HDR for immersive gaming, this is a critical issue.

Quick Fix:​

Disabling Auto HDR seems to alleviate the issue. This can be done directly in Display Settings—though it’s a frustrating workaround for a feature intended to enhance gaming graphics.

3. Easy Anti-Cheat and BSOD: Competitive Gamers Hit a Snag

If you’re into multiplayer gaming, you’ve likely run into Easy Anti-Cheat—a tool designed to thwart cheaters. Unfortunately, on systems with Intel’s Alder Lake or newer processors, the combination of Easy Anti-Cheat and Windows 11 24H2 can lead to the nightmarish Blue Screen of Death (BSOD).
For now, affected users are at the mercy of patches from Easy Anti-Cheat developers and Microsoft.

4. General BSOD Mayhem: Intel Drivers to Blame (Again)

Intel’s Smart Sound Technology drivers, specifically for 11th Gen Core processors, are clashing with Windows 11 24H2, leading to system crashes and blue screens. This issue also extends to Western Digital SSDs and MSI motherboards equipped with Xe-LPG graphics.
Until stable driver updates are distributed, Microsoft has paused updates on some of these systems, but if you’re already impacted, be prepared for disruptions.

5. Ghostly Mouse Pointer in Chromium Apps

If you’ve updated and noticed your mouse cursor disappearing while using Edge or Chrome, you’re not alone. The glitch comes into play when users interact with text input fields, making web browsing a tedious task.
For now, users can implement clunky workarounds or wait for an official fix to restore smooth browsing.

6. Internet Connectivity Fails

A number of users have reported their internet connection mysteriously vanishing post-update—Ethernet, Wi-Fi, or both. Even connected devices don’t get assigned proper IP addresses, severing access to the web.

Possible Solution:​

Switching to a static IP configuration resolves the issue for some, but this is hardly intuitive for the average user. Dynamic addressing continues to pose challenges for others.

7. Time Zone Restrictions

Out of administrative privileges? You might not be able to update the system’s time zone—an oddly specific but significant bug that’s already drawing ire. The option to change time zones simply vanishes from Setting’s Date & Time utility.

Workaround:​

Dive back into the old-school Date & Time settings via the Control Panel (yes, it’s still there) to manually set the correct time zone.

8. Clipboard History Broken

Since its debut in 2018, Clipboard History has been a handy feature for power users, allowing quick access to saved clips across devices. Unfortunately, the 24H2 update is leaving clipboard data mysteriously “empty” for an unlucky subset of users.
Microsoft testers flagged this oversight during beta testing, but it seems to have slipped through the cracks. For many users, what was once a productivity booster is now a broken feature.

9. Network Sharing Kaput

Got shared files or printers? Think again. Some updated PCs no longer appear on network lists, making file or device sharing nearly impossible. This bug may relate to a glitch in how Function Discovery Resource Publication (FDResPub) operates in the 24H2 ecosystem.
Switching the startup mode from "automatic" to "manual" has provided relief for certain affected users.

10. Printer Problems on ARM Copilot+ Systems

Owners of ARM-based PCs, such as those leveraging Microsoft’s Copilot+, are reporting a complete inability to use common printer models, including those from HP, Canon, and Brother.
Microsoft has acknowledged the issue with common peripherals and even published workarounds. Still, robust long-term fixes remain elusive.

11. Audio Output Fails

PCs equipped with Dirac Audio drivers (cridspapo.dll) have reported that, after upgrading, their audio solutions—including Bluetooth wireless connections—are essentially dead. First-party hardware cannot detect available output sources, let alone output sound.
Microsoft has temporarily blocked the update for PCs with this configuration.

12. MAPI Errors Blocking Outlook and Google Workspace Sync

Imagine logging into Outlook, only to be greeted with a fatal error message. Users leveraging Google Workspace Sync tools—which integrate Google services into Microsoft’s ecosystem—are finding Outlook outright refusing to launch due to incompatibilities with the 24H2 update.
Updating Google Workspace Sync has solved the issue for some, while others continue to experience ongoing challenges.

The Bigger Picture: Why Windows 11 24H2 Feels Rushed​

With three patch cycles (October, November, and December), Microsoft clearly recognizes the breadth of the issues. Yet, the perpetual introduction of new bugs with successive updates signals potential QA bottlenecks in their deployment process. Could Microsoft’s fervent push for innovation with AI-powered Copilot and enhanced gaming features have left quality assurance an afterthought?
For now, the best advice for everyday users—even power users—is to hold the line on 22H2 or previous stable releases. New features and visual embellishments rarely justify system instability or interruptions to productivity.

What Should You Do?​

  • Pause Updates. If you see the Windows 24H2 update on your system but haven’t installed it, hold off until further resolutions emerge.
  • Temporary Fixes. Follow Microsoft’s Known Issues page for workarounds where applicable.
  • Backup Backup Backup. Always ensure your critical files are backed up before performing any major update, no matter how promising it sounds.

Final Thought:​

Windows 11 24H2 has inadvertently reinforced the old adage: if it ain’t broke, don’t fix it. While software evolution is necessary, Microsoft’s latest test seems more like a beta than a polished public release. Unless these critical issues are resolved swiftly, 24H2 could further alienate users still based on Windows 10 or earlier Windows 11 versions.
Forum Community: Have you installed 24H2 and survived (bugs and all)? Let us know your experience—or bug horror stories—below!

Source: ZDNET New Windows 11 24H2 bug list: 12 reasons to avoid this update for now