Share via

MS_Idd_Bus_0x keeps reappearing

Bison 0 Reputation points
2026-05-03T20:26:30.02+00:00

In honor of a previous topic here that was never answered, this is a copy paste to provide HELP since the other topic has been locked:

So, I recently bought a USB 3.0 to HDMI adapter. I hooked it up to my laptop and it installed 3 devices: MS_Idd_Bus_01, MS_Idd_Bus_02 and MS_Idd_Bus_03. The adapter didn't work with my laptop, since my onboard graphics didn't support it. Now I've uninstalled the drivers for the old adapter, but the MS_Idd_Bus_0x devices weren't removed with them, so I removed them manually using the Device manager.

Now the problem I'm having, is that they keep reappering. I uninstall them, restart my laptop and boom... there they are again. It's specially annoying, since then Windows looks for new drivers, but fails to find them.

My question is: how do I abolish these devices, so that they are completely removed?

Windows for home | Windows 10 | Devices and drivers
0 comments No comments

2 answers

Sort by: Most helpful
  1. Bison 0 Reputation points
    2026-05-03T20:34:23.3266667+00:00

    The answer is that you have to delete the drivers. First, you have to look for them with this command in CMD as ADMIN:

    pnputil /enum-drivers > drivers.txt
    

    Check the generated text (it will be generated wherever you are positioned in the command line when you execute the command and search for "Provider: MS" which is EXTREMELY suspicious. in my case the .inf files were these:

    1. oem57.inf → indirectdisplaybus.inf
      • Provider: MS
      • Class: System devices
      • This is the Indirect Display Bus driver that spawns the ms_idd_bus_01 virtual hardware.
    2. oem56.inf → msusbdisplay.inf
      • Provider: MS
      • Class: MSDisplay
      • This is the Microsoft USB Display driver, often bundled with USB‑to‑HDMI adapters. It can also leave behind virtual display entries.

    Now start your PC in safe boot mode and run this replacing the names of the .inf files that were generated on your PC:

    pnputil /delete-driver oem57.inf /uninstall /force
    pnputil /delete-driver oem56.inf /uninstall /force
    

    Deactivate Safe Boot, restart and you are done.

    0 comments No comments

  2. Q&A Assist
    2026-05-03T20:26:47.37+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    MS_Idd_Bus_0x entries are phantom (non‑present) device instances that remain in the registry even after the physical device or its main driver is removed. Windows Plug and Play can keep re‑creating or re‑enumerating them, which is why they reappear after a reboot.

    To remove or at least stop seeing them, use these steps:

    1. Show non‑present devices in Device Manager
      1. Open a Command Prompt.
      2. Run:
              set devmgr_show_nonpresent_devices=1
              start devmgmt.msc
        
      3. In Device Manager, select View > Show hidden devices.
      4. Locate the MS_Idd_Bus_0x devices (likely under Display adapters or System devices), right‑click each, and select Uninstall device.
      5. Close Device Manager and the Command Prompt.
      This exposes and lets Device Manager remove phantom devices that are not currently connected to the computer.
    2. If they continue to reappear and are only cluttering Device Manager (not causing functional issues), hide them instead of relying on removal Windows supports marking devices as hidden so they do not normally appear in Device Manager. Devices with the DN_NO_SHOW_IN_DM devnode status bit set, or that belong to a NoDisplayClass, are not shown unless hidden devices are explicitly requested. For end users, the practical effect is:
      • When Show hidden devices is not enabled, hidden devices (including phantom ones) will not be visible.
      • Only when Show hidden devices is turned on will such devices appear.
      Driver or firmware changes from the adapter vendor would be required to mark these devices as hidden at the driver level (for example, by responding to IRP_MN_QUERY_PNP_DEVICE_STATE or IRP_MN_QUERY_CAPABILITIES with the appropriate flags). Without such a driver update, Device Manager will continue to show them when hidden devices are displayed.
    3. If registry buildup from many non‑present storage‑class devices is a concern (for example, large numbers of phantom disks/volumes), use DevNodeClean For disk and volume classes specifically, Microsoft provides the DevNodeClean utility to remove registry information for devices that will never be used again. The documented pattern is:
      • Enumerate devices in a class (for example, disk or volume) with SetupDiGetClassDevs and SetupDiEnumDeviceInfo.
      • Check each device’s status with CM_Get_DevNode_Status to see if it is absent.
      • For absent devices, remove them via SetupDiCallClassInstaller(DIF_REMOVE, ...).
      This approach is intended for storage classes (GUID_DEVCLASS_DISKDRIVE, GUID_DEVCLASS_VOLUME) and for scenarios where many phantom devices accumulate in the registry.

    In summary: use Device Manager with non‑present devices shown to uninstall the MS_Idd_Bus_0x entries; if they still reappear, they are being re‑enumerated by the system and can be effectively ignored or hidden by not enabling Show hidden devices. For large‑scale cleanup of phantom storage devices, DevNodeClean is the supported tool.


    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.