- Download software for Zebra printers, mobile computers, scanners, RFID readers and interactive kiosks.
- Although the driver is loaded on the Windows system, Windows Plug and Play still needs to recognize the device and install it as well as assign the device a USB port (USB001, USB002, etc.) to allow for communication.
- The USB-A port on your monitor is a convenience feature for connecting devices like mice and keyboards, so you don’t have to dig around the back of your computer. The USB port on your monitor is likely USB 2.0, so it would work with a hard drive, but probably wouldn’t be ideal.
- Method 2 – Update Device Driver. If Windows is not able to recognize the device, you may also see in Device Manager that the device shows up as an “Unknown Device”. You can get to Device Manager by clicking on Start and typing in devmgmt.msc or by going to Control Panel and clicking on Device Manager.
- Moore Computer Consultants Port Devices Driver Jobs
- Moore Computer Consultants Port Devices Driver Windows 10
- Moore Computer Consultants Port Devices Driver Download
In this state, you can see in the Device Manager that there's an 'STM Device in DFU Mode.' Now I run Zadig and replace the driver with WinUSB. Here's the result. Note the SUCCESS and the changed Driver on the left. Here the STM32 Bootloader device now exists in Universal Serial Bus Devices in Device Manager. Now I can run dfu-util -list again.
I'm pretty happy with Windows 10 as my primary development box. It can do most anything I want, run a half-dozen Linuxes, and has a shiny new open source Terminal, and has great support for Docker now.
For years - YEARS I SAY - Windows has been a huge hassle when you want to flash the firmware of various devices over USB.
The term 'dfu' means Device Firmware Update and dfu-util is the Device Firmware Update Utility, natch.
Very often I'll find myself with a device like a Particle Photon, Wilderness Labs Meadow, or some STM32 device that uses the ST Bootloader.
The Mac and Linux instructions usually say something like 'plug it in and party on' but folks like myself with Windows have to set up a WinUSB Driver (libusb-win32 or libusbK) as dfu-util uses those libraries to speak to USB devices.
If you plug in a device, the vast majority of Windows users want the device to 'just work.' My non-technical parent doesn't want Generic USB drivers so they can flash the firmware on their mouse. I, however, as an aristocrat, sometimes want to do low-level stuff and flash an OS on a Microcontroller.
Today, the easiest way to swap the 'inbox' driver with WinUSB is using a utility called Zadig. Per their docs:
Zadig is a Windows application that installs generic USB drivers,
such as WinUSB, libusb-win32/libusb0.sys or libusbK, to help you access USB devices.
It can be especially useful for cases where:
- you want to access a device using a libusb-based application
- you want to upgrade a generic USB driver
- you want to access a device using WinUSB
If you follow the instructions when flashing a device and don't have the right USB driver installed you'll likely get an error like this:
That's not a lot to go on. The issue is that the default 'inbox' driver that Windows uses for devices like this isn't set up for Generic USB access with libraries like 'libusb.'
Install a generic USB driver for your device - WinUSB using Zadig
Run Zadig and click Options List All Devices.
Here you can see me finding the ST device within Zadig and replacing the driver with WinUSB. In my case the device was listened under STM32 Bootloader. Be aware that you can mess up your system if you select something like your WebCam instead of the hardware device you mean to select.
In this state, you can see in the Device Manager that there's an 'STM Device in DFU Mode.'
Now I run Zadig and replace the driver with WinUSB. Here's the result. Note the SUCCESS and the changed Driver on the left.
Here the STM32 Bootloader device now exists in Universal Serial Bus Devices in Device Manager.
Now I can run dfu-util --list again. Note the before and after in the screenshot below. I run dfu-util --list and it finds nothing. I replace the bootloader with the generic WinUSB driver and run dfu-util again and it finds the devices.
At this point I can follow along and flash my devices per whatever instructions my manufacturer/project/boardmaker intends.
NOTE: When using dfu-util on Windows, I recommend you either be smart about your PATH and add dfu-util, or better yet, make sure the dfu-util.exe and libusb.dlls are local to your firmware so there's no confusion about what libraries are being used.
I'd love to see this extra step in Windows removed, but for now, I hope this write up makes it clearer and helps the lone Googler who finds this post.
Sponsor: Develop Xamarin applications without difficulty with the latest JetBrains Rider: Xcode integration, JetBrains Xamarin SDK, and manage the required SDKs for Android development, all right from the IDE. Get it today
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
Click on your operating system below and follow the instructions to configure power management features on your computer. Note that your monitor may already enter a low-power sleep mode when the computer is inactive, but the computer itself may not. There are two separate settings: one for the monitor, and another for the computer.
Moore Computer Consultants Port Devices Driver Jobs
- Save $10-100 per computer annually in electricity costs
- Eliminate the need to boot up your computer each morning, saving time
- Help the environment by reducing air pollution associated with the burning of fossil fuels
Do you require remote access to your computer?
If you remotely access your desktop computer (via Remote Desktop, for instance), you may need to make some adjustments so that your sleeping computer can be awakened. For more details, see Remote Desktop for Sleeping Computers.
Situations That May Cause Windows Computers to Not Sleep
Under certain conditions, Windows-based computers may not drop into sleep mode despite being properly configured to do so. For example, the following conditions may prevent computers from entering sleep mode:
Moore Computer Consultants Port Devices Driver Windows 10
- The PC has a file open over the network – e.g., on a network server.
- The computer uses a graphics-intensive screen saver. (ENERGY STAR recommends disabling them.)
- A Microsoft PowerPoint file is in “presentation mode.”
- Processor activity is above a certain threshold, indicating that the computer is not idle.
Moore Computer Consultants Port Devices Driver Download
It is also possible for a network administrator to allow certain applications to 'veto' sleep mode. This setting cannot be configured via the computer’s Control Panel, but network administrators can use Group Policy to do so.