Updating drivers for devcon failed


28-Jul-2019 22:20

The Dev Con command we used was tells us that the hardware's driver hasn't been loaded yet.

After loading the driver, this will read Card Man 3x21.

Because we had nearly 500 computers, manually installing the drivers wasn't practical.

To save a lot of time and manpower, we used Dev Con (devcon.exe).

If you want to remove that device driver you can create a task containing the following command: parameters specifies all or part of a hardware ID, compatible ID, or device instance ID of a device.

When specifying multiple IDs, type a space between each ID.

After some testing we discovered that if you plug in an unknown USB device (such as a smart card reader), click Cancel to close the New Hardware Found wizard, then run Dev Con, you can obtain its device ID.Anyway, I have copied the to the package directory and copied that to a freshly installed Win10 (build 10240) virtual machine. ndv: No drivers were found that are better matching drivers for device instance ROOT\MEDIA

After some testing we discovered that if you plug in an unknown USB device (such as a smart card reader), click Cancel to close the New Hardware Found wizard, then run Dev Con, you can obtain its device ID.Anyway, I have copied the to the package directory and copied that to a freshly installed Win10 (build 10240) virtual machine. ndv: No drivers were found that are better matching drivers for device instance ROOT\MEDIA[[

After some testing we discovered that if you plug in an unknown USB device (such as a smart card reader), click Cancel to close the New Hardware Found wizard, then run Dev Con, you can obtain its device ID.

Anyway, I have copied the to the package directory and copied that to a freshly installed Win10 (build 10240) virtual machine. ndv: No drivers were found that are better matching drivers for device instance ROOT\MEDIA\0000 (Error 0x00000103) ! dvi: .006 dvi: Class installer: Enter .006 dvi: Class installer: Exit dvi: Default installer: Enter .006 dvi: Default installer: Exit dvi: .022 has a Device Install32 section so you can use "-a tabletaudiosample.inf" to install it; the physical device object is created by Windows when the driver is added to the store.

||

After some testing we discovered that if you plug in an unknown USB device (such as a smart card reader), click Cancel to close the New Hardware Found wizard, then run Dev Con, you can obtain its device ID.Anyway, I have copied the to the package directory and copied that to a freshly installed Win10 (build 10240) virtual machine. ndv: No drivers were found that are better matching drivers for device instance ROOT\MEDIA\0000 (Error 0x00000103) ! dvi: .006 dvi: Class installer: Enter .006 dvi: Class installer: Exit dvi: Default installer: Enter .006 dvi: Default installer: Exit dvi: .022 has a Device Install32 section so you can use "-a tabletaudiosample.inf" to install it; the physical device object is created by Windows when the driver is added to the store.

]]00 (Error 0x00000103) ! dvi: .006 dvi: Class installer: Enter .006 dvi: Class installer: Exit dvi: Default installer: Enter .006 dvi: Default installer: Exit dvi: .022 has a Device Install32 section so you can use "-a tabletaudiosample.inf" to install it; the physical device object is created by Windows when the driver is added to the store.

00 (Error 0x00000103) ! dvi: .006 dvi: Class installer: Enter .006 dvi: Class installer: Exit dvi: Default installer: Enter .006 dvi: Default installer: Exit dvi: .022 has a Device Install32 section so you can use "-a tabletaudiosample.inf" to install it; the physical device object is created by Windows when the driver is added to the store.