Hard Drive Error 'Invalid class name' – Fixed

Quick answer

Delete the corrupted class GUID from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\ under {4d36e967-e325-11ce-bfc1-08002be10318} and reinstall the disk driver from Device Manager.

What's going on here?

I ran into this one about six months ago with a Windows 11 Pro machine – an HP EliteDesk 800 G6. Client said the D: drive just vanished. Went into Disk Management, saw the drive but with no volume info. Device Manager showed the disk, but with a yellow bang and that error: Invalid class name. The machine had just installed a Windows Update for the storage controller. That update nuked the registry entry for the disk class driver. Windows has these GUIDs in the registry that point to the driver class – think of them as a phone book for the system to find the right driver. When that entry gets corrupted, Windows can't load the driver, and your drive goes invisible. It's not a hardware failure – it's a software hang-up. But if you don't know the fix, you might think the drive's dead. It's not.

Fix it in 5 steps

Back up your registry before touching it. One wrong delete and you're reinstalling Windows. Here's the path:

1. Open Regedit as admin (Win+R, type regedit, right-click and run as admin).
2. Navigate to:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}

3. Look for a subkey that has a Class value that's empty or Invalid class name. Delete that entire subkey – not the GUID key itself, just the subkey under it that's corrupt. If you're unsure, right-click the subkey, export it as a backup first.
4. Close Regedit. Open Device Manager. Expand Disk drives. Right-click your disk and select Uninstall device. Check the box to delete the driver software.
5. Restart your machine. Windows will reinstall the default disk driver on boot. Your drive should appear in This PC. Check Disk Management to assign a drive letter if needed.

What if that doesn't work?

Sometimes the registry fix alone doesn't stick because Windows has a cached bad driver. Try these in order:

• Run the DISM and SFC tools: Open an admin command prompt and run DISM /Online /Cleanup-Image /RestoreHealth, then SFC /SCANNOW. This can fix system file corruption that might be blocking the driver reload.
• Manually install the chipset driver: Go to your motherboard or PC manufacturer's site (e.g., Intel, AMD, Dell, HP) and download the latest chipset driver. Run it as admin. The disk class driver is part of the chipset package on many modern systems.
• Use a restore point: If you have one from before the issue started, roll back. This is the nuclear option – it'll revert registry and drivers. Windows System Restore works surprisingly well for this exact problem.

I've only seen this fail twice: once on a system with a failing motherboard where the SATA controller was physically dying, and once on a laptop that had a third-party storage driver that didn't play nice with a Windows update. In the hardware case, the drive eventually failed completely. For the third-party driver, we had to boot into Safe Mode, uninstall the custom driver, and let Windows use the in-box one.

Prevent it from coming back

Don't rely on Windows Update for storage drivers. It's the number one trigger for this error. Here's what I do on all my clients' machines: download the chipset and storage drivers directly from the manufacturer, install them manually, then disable driver updates via Windows Update. You can do that through Group Policy if you have Pro/Enterprise, or use the Show or hide updates troubleshooter from Microsoft on Home editions. Also, set a monthly reminder to check for manufacturer driver updates – I use a simple calendar alert. And keep a system restore point before any major update. Takes 30 seconds. Saves hours.

Had a client last month whose entire print queue died because of this – well, not the print queue, but the same registry corruption affected the disk driver. The fix was identical. This error is rarer than the typical "disk not initialized" or "driver error" messages, but when it hits, it's almost always the registry class entry. Don't chase hardware ghosts. Fix the registry.