DriverCove

Device not working after Windows 11 24H2

The 24H2 update changed more of Windows' internals than a usual update, and a noticeable share of machines came out of it with losses - sound, webcams, Bluetooth and fingerprint readers get hit most often. The hardware is fine. Laptop makers ship separate driver builds marked for 24H2, and installing one - or rolling the driver back - usually brings the device back.

Why this happens

  • 24H2 changed how Windows works with sound and cameras - old drivers for these devices break more often than others.
  • During the update Windows replaced the maker's driver with a generic one.
  • The driver carried over from the previous Windows version and was never built for 24H2.
  • The device froze mid-update and never re-initialized.

Quick checks first

1Shut down fully once, don't just restart

Shift + Shut down bypasses Fast Startup. After a major update some devices hang half-initialized until a true cold boot.

2Make sure 24H2 is actually the culprit

Settings → Windows Update → Update history: does the day the device died match the 24H2 install? If it broke later, the cause is likely elsewhere - see our general guide for devices that break after Windows updates.

3Look through Device Manager

Yellow warning icons on the usual 24H2 victims: sound, camera, Bluetooth, fingerprint reader.

4Check for a 24H2 driver build

Laptop makers publish separate versions marked “11 (24H2 or Later)” - Lenovo keeps them for audio, cameras and fingerprint readers, and the catalog lists them alongside the regular releases.

5Check optional updates

Windows Update → Advanced options → Optional updates → Driver updates: a fixed version sometimes already sits there.

If the device is still silent after these checks, its driver was not built for 24H2. The next step is to find a 24H2 build for the device, or roll back to the version that worked. The Hardware ID names the exact model even when Device Manager shows it nameless.

Drivers most often behind this problem

Fixing it manually

Install a 24H2 driver build

  1. Search the catalog for your device's driver marked “24H2 or Later” and pick the version for your model.
  2. Create a restore point before installing.
  3. Install following the instructions on the driver page, then reboot.

Roll back the driver

  1. Use this when the device broke right after the update and no 24H2 build exists for it yet.
  2. Device Manager → the device → Properties → Driver tab → Roll Back Driver.
  3. Rollback returns the version that worked before the update; reboot and test.

Reinstall cleanly by Hardware ID

  1. Uninstall the device in Device Manager and tick the driver removal option, then reboot.
  2. Open the device Properties → Details → Hardware Ids and copy the top value.
  3. Search it in the catalog and install a version that lists Windows 11 support.

Know the exact device model?

Search the driver database by device name, laptop model or Hardware ID - builds marked “24H2 or Later” show up next to the regular versions.

The Hardware ID pins the device even when 24H2 left it nameless: Device Manager → the device → Properties → Details → Hardware Ids, copy the top value - the search decodes it.

Try for example: 24H2 · read the Hardware ID guide

Frequently asked questions

▸Can I just roll back the whole 24H2 update?

Yes, within the first 10 days: Settings → System → Recovery → Go back. But that postpones the problem rather than solving it - the update will return. Fixing the driver is the reliable way.

▸Why did sound break after 24H2 specifically?

24H2 changed how Windows handles sound, and laptop drivers with maker-tuned sound effects are the first to break. The right cure is the laptop maker's build marked for 24H2, not a generic package.

▸The camera works in one app and not in another - is that 24H2?

More likely permissions: Settings → Privacy & security → Camera, per-app access. Blame the driver when the camera is gone everywhere, or sits in Device Manager with a warning icon.

▸Should I wait for Microsoft to fix it?

Microsoft patches some of it, but driver problems are usually fixed by device makers. If a 24H2 build for your device is already out, installing it is faster than waiting.

Other common problems