DevCon disables the device even if the device is already disabled. Before and after disabling a device, use the DevCon Status operation to verify the device status. Before using an ID pattern to disable a device, determine which devices will be affected. To do so, use the pattern in a display command, such as devcon status USB. or devcon hwids. However, when I try to the same, I get the message 'devcon failed' with no further elaboration. I provided following commands but none of them works. Devcon install 'C: Program Files (x86) Molecular Imaging MI Application Drivers pixciwin7x64 epixxcw6.inf' 'PCI VEN165A&DEVEB01&CCFF00' or after installing through device manager. Devcon Failed Windows 10 Wilcom To turn off or turn on service in windows but there are also some risks using devcon.exe. In Microsoft Windows 10 you can also enable and disable several programs and application using command lines. Hardware/software information Windows Version: 10 Tablet Driver version: V0.1.5 Tablet model: Wacom CTL 490DW-S. 'devcon.exe failed' i get this issue, everytime i. I build sysvad solution and got tabletaudiosample on a windows 10, 64 bit virtual machine. I copied.inf,.sys. Cat and package files to a folder inside target computer. 1.Hardware ID will be found in respective inf file, open inf with notepad,ctrl+f HardwareIds 2.bcdedit /set TESTSIGNING ON. Go to devcon.exe folder. Devcon listclass usb 1394. Remove all USB devices. Devices that are removed are listed with their removal status. Devcon remove @usb. Rescan for new Plug and Play devices. List the resources that are used by all devices in the ports setup class. Devcon resources =ports. Restart the loopback adaptor ROOT.MSLOOP 0000.

• Devcon Failed Windows 10 Wilcom
• Devcon Failed Windows 10 64-bit
• Devcon Remove Failed Windows 10

I'm having trouble installing OpenVPN - the TAP driver simply refuses to install.
I've tried 5 different versions of the installer - including v2.1 RC19 which, according to a Google search, seems to be everyones solution.
I've tried v2.1.3, which supposedly should have the driver signing solved, v2.1.1, v2.1.4 and even v2.2 beta5 - all run as administrator.
I've tried running the installers in compability mode set to Vista, aswell.
I've tried downloading the x64 driver (tap0801), from openvpn.se, and installing it manually (from a dos prompt, run as administrator, from a destination folder that isn't named with troublesome characters like space), and between the installs, i've even made sure to uninstall the 'unknown' TAP network adaptor, the installations leaves behind.
I've tried extracting the driver (tap0901) from the installer and manually install it, using same procedure as above.
.. I'm fresh out of ideas on how to get OpenVPN running on Windows 7 Ultimate x64, please help.
Regards
Mads Jensen

Although this article mainly targets OpenVPN TAP driver installation issue, The problem is likely not limited to that specific driver.

Devcon Failed Windows 10 Wilcom

You may want to continue reading and give the very easy solution at the end of the article a try.

Recently I had to install OpenVPN on a system running Windows XP (Don’t ask). The installation went smoothly up until TAP driver installation and then suddenly things went haywire:

The yellow marked status with the code of 28 in the device manager was not promising either:

In Windows XP, to install its inf file, TAP driver installation uses the built-in Windows Device Console (Devcon.exe). Pretty simple stuff, you just use devcon.exe with the install argument, supply the inf file and then provide the device’s Hardware ID.

This is the command being used to install each TAP NIC:
'C:Program FilesTAP-Windowsbindevcon.exe' install 'C:Program FilesTAP-WindowsdriverOemWin2k.inf' tap0901

Which gave a mundane error:

devcon.exe failed.

Devcon Failed Windows 10 64-bit

Devcon however, leaves a log file of its operation behind in %windir%setupapi.log which included these lines:

#E122 Device install failed. Error 2: The system cannot find the file specified.
#E154 Class installer failed. Error 2: The system cannot find the file specified.
#I060 Set selected driver.
#I125 Installing NULL driver for “ROOTNET0000”.
#E122 Device install failed. Error 2: The system cannot find the file specified.

Now that’s our first clue. There seems to be a file missing somewhere. So after ensuring it’s not an obvious one (like a .sys file required by the inf), I was getting prepared to go deeper to debug the issue.

Luckily, turned out DaveBurnett had already done that and has shared his findings. I thank him for this as he’s possibly saved me couple of hours of struggle.

As it’s been mentioned in that post, if RunOnce key is missing in the registry (Which could easily happen by a program with a not a very well tested uninstall system), for some unknown reason devcon.exe dislikes it. So much in fact that it decides to leave the installation in half-state and complain about a missing “specified” “file”.

Just for the fun of it, lets fire up the amazing Process Monitor:

Almost right before failing, you can see the failed accesses to the RunOnce key.

The fix is utterly simple, just open cmd.exe as an administrator and use this command to create the missing key again:
reg ADD HKLMSOFTWAREMicrosoftWindowsCurrentVersionRunOnce

Before reinstalling TAP driver however, first remove all the half-installed ones from the Device Manager. For each failed driver installation attempts, you will likely find different entries, some of which labeled as “Unknown device” Windows sdk 8.1 download.

To see if either of the Unknown devices are really a malfunctioning TAP driver, check their Hardware ID first:

Then just right-click on each and uninstall them.

And then you can just install TAP virtual NICs again by simply using the batch script provided in the TAP driver’s installation folder which defaults to:
C:Program FilesTAP-Windowsbinaddtap.bat

Devcon Remove Failed Windows 10

Oh, You might also want to consider upgrading your OS. It’s been ages for heaven’s sake!