With the official release of Windows 11 24H2, Microsoft has begun sharing information about known issues.
This is important for users who have already upgraded, or for those interested in upgrading but aren’t seeing the update in Windows Update.
In the initial phase, the distribution is controlled, starting with a small percentage of Windows 11 devices. Some systems are intentionally excluded from the rollout for a time due to known issues identified during the distribution on similar devices.
These problems often involve drivers or programs that don’t function as expected under certain conditions. This is common with new operating system releases since not all hardware configurations can be tested beforehand. That’s why Microsoft relies on a phased distribution.
The broader rollout of Windows 11 version 24H2 started on October 1st, and a few issues have already been identified:
- Safe Exam Browser won’t launch: This affects versions 3.7 and earlier. Version 3.8 is available, and updating the program resolves the issue.
- Easy Anti-Cheat causes system crashes: Anti-cheat software used in multiplayer games can cause issues when there are system changes. This problem is reported with versions of Easy Anti-Cheat released before April 2024, particularly on Intel Alder Lake processors and newer, as well as processors with vPro.
- Fingerprint readers may not work after device lock: Some users are unable to log back in using fingerprint authentication after locking their device. This issue affects a small number of devices, but updating the firmware may help.
- Wallpaper customization tools don’t work: Microsoft has noted issues with certain wallpaper customization tools that could block the upgrade to version 24H2, although specific tools are not named. Updating these programs should resolve the problem.
- Intel Smart Sound Technology driver issues: If you have an 11th-generation Intel Core processor, drivers with versions 10.29.0.5152 or 10.30.0.5152 may cause system crashes.
- Asphalt 8 crashes: The game may become unstable, but no fix is currently available.
