Updating drivers for devcon failed

Windows offers to automatically detect the driver that should be installed. If you got the "you will need to restart" message, Windows helpfully offers to restart right away.

No thanks, we want to pick a particular driver: Windows asks where we want to look - do we have a set of driver files, or is the driver already in the list of installed drivers? Make sure you're ready for a restart (no unsaved documents or anything) and restart either by clicking "Yes" or by using the Start menu.

I found about 50 devices that need drivers and I clicked one-by-one right-click and update driver software and everything except coprocessor was clean (which I manually installed).

Than I installed desired state: windows 2016 core which is, I must say, working like a charm on 8 years old IBM server (who is not even on microsoft HCL for server 2012).

Try configuring windows (with the help of sconfig.cmd) to search windows updates for device drivers.

Check the following linkshttps://docs.microsoft.com/en-us/windows-server/get-started/sconfig-on-ws2016https://technet.microsoft.com/en-us/library/cc753091(v=ws.11).aspxsecond question: how can I do that on core?

Occasionally, for troubleshooting purposes, it is useful to switch from one driver to the other... Type "devmgmt.msc" (without the quotes) to launch Device Manager.

either to get the additional functionality provided by the vendor-supplied driver, or to see what happens if the class driver is installed. Expand the "Sound, video and game controllers" node and note the list of audio devices.

In Windows this generally means that a device driver for the hardware is installed.Most on-the-motherboard audio devices support the Intel High Definition Audio standard.Windows Vista (and later) includes a "class driver", hdaudio.sys, which should work with any such audio device.Yes, you can use access the device manager of your core server from other computers MMC snap-in.Check the following link (section 1.3) https://technet.microsoft.com/en-us/library/jj574205(v=ws.11)Please let us know about your experience here.

Search for updating drivers for devcon failed:

updating drivers for devcon failed-29updating drivers for devcon failed-10updating drivers for devcon failed-37

The top one is the most specific identifier, and going down, the identifiers are more generic.

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “updating drivers for devcon failed”