Code 56: Windows Is Still Setting Up the Class Configuration

What causes Code 56

• Some device classes need extra class configuration after the driver package is installed; network adapters are Microsoft's example.
• If a network adapter keeps this code, the driver's INF may contain invalid networking-specific entries, or the PC's network state may be corrupt and need to be reset (Microsoft Learn).

How to fix Code 56, safest step first

The steps follow Microsoft's recommended resolution for this code, in its order, with a reversible step first. Each one says how to put back what it changed.

1. 01

   Give it a moment, then restart

   Microsoft describes the code as frequently transient: when configuration completes, the device restarts and the code clears. If it does not, restart the PC with Start > Power > Restart.

   To undo: Nothing to undo: a restart changes no setting.

2. 02

   Before you change anything: note the driver and make a restore point

   Open the device's Properties > Driver tab and write down the driver provider, date and version. Then select Start, type Create a restore point, open it, and on the System Protection tab choose Create. Microsoft notes that System Protection is not turned on by default; if Create is greyed out, choose Configure and turn it on for the system drive first.

   To undo: A restore point changes nothing by itself. To go back later, run System Restore and pick it: Microsoft says it reverts system files, the registry and installed programs, and leaves your personal files alone.

3. 03

   For a network adapter that keeps the code: network reset

   Microsoft's fix for a network adapter stuck on Code 56 is the Network reset button in Settings (Network & internet > Advanced network settings > Network reset). It removes every network adapter and its settings, and reinstalls the adapters with default settings after a restart.

   To undo: There is no button to undo it. Afterwards reconnect to your Wi-Fi networks and, as Microsoft warns, reinstall or set up again VPN clients and virtual switches such as Hyper-V's; known networks may be switched to the public profile, so set the private profile again where you need it.

4. 04

   Get a driver from the hardware manufacturer

   Download the current driver for your exact model from the manufacturer's support page and install it. If the code survives a network reset, the driver's INF may be at fault, which only a different driver version fixes.

   To undo: Roll Back Driver on the Driver tab returns to the driver you had, or apply the restore point.

Check it yourself

1. 01

   List every device with this code (Command Prompt or PowerShell)

   Available from Windows 10, version 1903. Each device is listed with its instance ID and the problem code with its name, CM_PROB_NEED_CLASS_CONFIG. No administrator rights needed; nothing is changed.

   pnputil /enum-devices /problem 56

   cmdCopy
2. 02

   Or with PowerShell

   Device Manager shows the same code on the General tab of the device's Properties, in the Device status box.

   Get-PnpDevice | Where-Object { [int]$_.ConfigManagerErrorCode -eq 56 } |
     Format-Table Status, Class, FriendlyName, Problem

   PowerShellCopy