What Code Is 35 in Device Manager?

What Code Is 35 in Device Manager?

Device Manager code 35 means Windows cannot determine or read a device’s firmware or resource information, so the fix often starts with BIOS/UEFI, chipset, or device firmware. If you ignore it, the device may disappear, fail to start, or keep breaking after every reboot. This guide shows a device-by-device decision tree for USB, PCI, Bluetooth, audio, network, and chipset errors.

This guide is part of our Windows driver errors: full list and fixes series.

What code 35 means

In Windows Device Manager, code 35 usually means the device firmware does not include enough information for Windows to enumerate the hardware correctly. That is why the problem often points to firmware visibility first, not only to a bad driver. The device can be present in Windows, yet still fail to start because the system cannot read its configuration data.

Key points: What code 35 means

This code often shows up on USB controllers and devices, PCI devices such as network and audio adapters, Bluetooth radios, and some chipset-related hardware. The message usually means Windows can see the device path, but not enough details to build a working hardware instance.

Code 35 triage table

Device typeLikely causeFirst fixSecond fixEscalation path
USBPort, hub, power, or device firmware issueMove to a direct rear port and restartRemove the device, then rescan hardware changesUpdate the device firmware or USB controller driver; check Fast Startup
PCIMotherboard enumeration, slot, or device firmware issuePower off, reseat the card, then boot againInstall the motherboard vendor chipset packageUse vendor firmware or support; test in another slot if available
BluetoothOEM radio firmware or chipset driver mismatchRestart and rescan in Device ManagerReinstall the Bluetooth driver package from the PC makerUpdate BIOS/UEFI and the OEM Bluetooth package together
AudioAudio codec, onboard controller, or firmware visibility issueRestart and check device statusInstall the system audio driver from the OEMReset BIOS defaults; update motherboard firmware if the codec stays hidden
NetworkNIC firmware, PCIe enumeration, or chipset driver issueRescan hardware changes and rebootInstall the vendor network driver packageUpdate BIOS/UEFI and motherboard chipset drivers; contact the board maker if the NIC still fails

How do you confirm code 35?

Code 35 can be confirmed in Device Manager by opening the device’s Properties page and checking the status box on the General tab. Windows usually prints the code there, along with a short message about firmware or resource information. That check tells you whether you are dealing with code 35 or a different Device Manager error.

Open Device Manager, expand the affected category, and look for a yellow warning icon or a device that has vanished from its normal group. Then open Properties and read the Device status box. If the code is 35, use Scan for hardware changes before you move to deeper firmware checks.

  1. Press Win+X and open Device Manager.
  2. Expand the device category that shows the warning icon.
  3. Open Properties and read the Device status box.
  4. Choose Action and then Scan for hardware changes.
  5. If the code stays, note the device type before changing firmware or drivers.

Which fix should you try first?

Start with a restart, then do a full power cycle if the device is external or tied to a removable controller. If that does not clear the code, remove the device in Device Manager, rescan hardware changes, and then move to the correct driver or firmware path. Do not jump straight to random driver downloads.

A common first-timer mistake is to reinstall the same generic driver package three times and never check the firmware side. Suppose a USB capture device shows code 35 after a sleep resume; a reboot helps once, but the error returns. That pattern points to initialization or firmware visibility, not a simple driver corruption case.

Basic steps that still matter

  • Restart the PC once before deeper changes.
  • Shut down fully, unplug power for a short period if the device is external, then boot again.
  • Uninstall the affected device from Device Manager and rescan hardware changes.
  • Open Windows Update and install the latest driver or platform updates offered for the PC.
  • Get OEM driver and firmware packages from the PC maker, motherboard maker, or device maker when they provide them.

When is BIOS or chipset the fix?

BIOS or UEFI is often the main fix when the device is built into the motherboard path, the same code appears after reinstalling drivers, or the device depends on platform initialization. Chipset drivers matter because they help Windows interpret PCIe, USB, and onboard controller paths. If those layers are wrong, the device may never enumerate correctly.

Quick steps: When is BIOS or chipset the fix?

Update BIOS or UEFI from the PC or motherboard maker when the platform firmware is old or when the device was added support only in newer releases. Install the correct chipset package from the OEM after a firmware update, especially on laptops and prebuilt systems. Reset BIOS defaults if a custom setting, disabled controller, or unusual boot option may be blocking initialization.

Firmware and driver decision tree

  • Start with the device itself if the hardware is external and the maker offers its own firmware tool.
  • Move to chipset drivers if the device is built into the system, especially on PCIe, USB, or onboard audio paths.
  • Update BIOS/UEFI if the device stopped working after a platform update, or if support notes mention added hardware compatibility.
  • Reset BIOS defaults if settings were changed recently and the device no longer enumerates.

USB and PCI device checks

USB code 35 cases often come from port choice, hub problems, or power state issues. Start with a direct motherboard port, not a hub or front-panel extension. If the device is bus-powered, unplug it, shut the PC down, wait briefly, and boot again. Fast Startup can preserve a bad state, so check it if the error keeps returning.

Key points: USB and PCI device checks

PCI device cases need a different approach. Audio, network, and storage adapters on PCI or PCIe often rely on motherboard vendor packages and platform firmware to enumerate correctly. If the card is removable, reseat it and test another slot if the board supports one. If it is onboard, focus on chipset drivers and BIOS/UEFI first.

USB-specific checks

  • Try a different USB port, preferably one directly on the PC.
  • Remove hubs, docks, and pass-through adapters from the test path.
  • Disconnect other high-draw USB devices during the test.
  • Check whether Fast Startup is keeping the device in a bad state.

PCI-specific checks

  • Reseat the card if it is removable.
  • Try another PCIe slot if the motherboard provides one.
  • Install the motherboard vendor’s chipset and device package, not a random generic driver.
  • Check BIOS/UEFI settings for disabled onboard controllers or unusual lane sharing options.

When code 35 keeps coming back

When code 35 returns after every restart, the blocker is often firmware visibility rather than a bad Windows session. If the same device fails on multiple boots, and driver reinstalling does nothing, the device firmware or the motherboard firmware path is probably still wrong. That is the point where OEM support pages matter more than generic driver sites.

It can also mean the hardware is no longer supported by the older motherboard or laptop. Some devices need newer BIOS support, newer chipset code, or a board that exposes the right enumeration data. If the maker no longer offers firmware for that model, the realistic options are a supported replacement part, a different slot, or a newer system.

Say your desktop’s onboard network adapter shows code 35 after a BIOS update and a driver reinstall. If the maker’s notes mention newer LAN support, the fix may be a newer BIOS revision or the OEM LAN package, not another round of Windows Update. That is a firmware compatibility path, not a Windows-only path.

Keep reading

Frequently asked questions

What does code 35 mean in Device Manager?

Code 35 means Windows cannot read enough firmware or resource information to enumerate the device correctly. The problem usually points to BIOS/UEFI, chipset drivers, or device firmware before it points to a plain driver fault. The affected hardware may still appear in Device Manager, but it will not start normally.

How do I fix code 35 on Windows?

Start with a restart, then rescan hardware changes and remove-re-detect the device if needed. After that, install the OEM driver package, check Windows Update, and move to BIOS/UEFI or chipset updates when the device sits on an internal controller path. Use the device maker’s firmware only when it exists.

Why does code 35 keep coming back after restart?

If code 35 returns after restart, the underlying enumeration problem is still present. That often means the device firmware is incomplete, the motherboard firmware is outdated, or the chipset package is wrong for the hardware. A reboot can clear a temporary state, but it cannot fix missing firmware data.

Is code 35 a driver problem or a hardware problem?

It can be either, but it is often a firmware-enumeration problem first. If reinstalling the driver changes nothing, the next checks should be BIOS/UEFI, chipset drivers, and device firmware. If the device is unsupported on that older board or laptop, software fixes may not solve it.

Does code 35 mean my device is broken?

Not always. A healthy device can still throw code 35 if the system firmware cannot read its configuration data, or if the wrong chipset path is in place. But if the device keeps failing on a supported system after firmware and driver updates, hardware replacement becomes a reasonable next step.

What code is 353

That search usually means the reader should verify the exact Device Manager code shown on the screen, because different codes point to different failures. Code 353 is not the same as code 35, so the fix path may change completely. Open the device properties and confirm the exact number before acting.

What code is 351

That query should be treated as a code lookup, not a fix. Verify the number in Device Manager first, since 351 is not code 35 and may describe a different driver or resource problem. The safest next step is to read the Device status box and follow the code-specific guidance.

What code is 352

Code 352 is a different Device Manager result, so the correct response is to confirm the device’s exact status text before changing drivers or firmware. If you are actually seeing code 35, use the firmware-first path in this guide. If the code differs, the cause and fix can differ too.

What code is 358

That code search should end with verification inside Device Manager, because 358 is not code 35 and may point to another hardware or driver failure. Check the device’s Properties page, read the status box, and match the number exactly. The fix only makes sense after the exact code is confirmed.

Similar Posts