New Windows 11 install: essential USB drivers are "stopped"

byronhawkins · Jul 17, 2022

In my new Windows 11 install on a Tablet PC (Pipo W12), none of the USB-C devices on the dock are working, even though I installed from a USB drive over USB-C. When I boot from the USB drive on the dock, all the following drivers are in state "running". But when I boot into the Windows 11 desktop, these drivers are "stopped".

The machine has no network access without USB, so I manually downloaded and installed all the relevant updates. That didn't fix anything, presumably because these are standard components and the drivers have not changed for years. The tablet worked fine with its original Windows 10 install, but even if I install a fresh Windows 10, the USB-C devices are unavailable.

How can I get Windows to start the drivers for these components? I looked in the services list but couldn't find anything related.

Code:

UASPStor     USB Attached SCSI (UAS | Manual     Stopped    OK         FALSE       FALSE        4,096             61,440      0                                 C:\Windows\system32\drivers\uaspstor.sys         4,096
UrsChipidea  Chipidea USB Role-Swit | Manual     Stopped    OK         FALSE       FALSE        4,096             20,480      0                                 C:\Windows\system32\DriverStore\FileRepository\u 4,096
usbehci      Microsoft USB 2.0 Enha | Manual     Stopped    OK         FALSE       FALSE        0                 77,824      0                                 C:\Windows\system32\drivers\usbehci.sys          4,096
usbhub       Microsoft USB Standard | Manual     Stopped    OK         FALSE       FALSE        4,096             323,584     0                                 C:\Windows\system32\drivers\usbhub.sys  
USBSTOR      USB Mass Storage Drive | Manual     Stopped    OK         FALSE       FALSE        49,152            73,728      0                                 C:\Windows\system32\drivers\USBSTOR.SYS          4,096

iko22 · Jul 18, 2022

Hello,
It is a little difficult to interpret the results because you do not say what program you used to query the device store, plus there is no headings to the tabulated results.

What I wanted to know was, what was the "OK" column about? Something is clearly wrong witht the ports, but something is registering as "OK" - what is that?

Given something is wrong, you may want to run one of the Windows troubleshooters, and see if that can provide any useful information.

To run the Devices and Printers troubleshooter, press Windows Key + R and the Run box will appear.
Inside the Run box, type (or Copy and Paste) msdt.exe -id DeviceCenterDiagnostic, and then click OK.
The Devices and Printers troubleshooter will now open. Click Next to start the troubleshooter.

Sometimes the troubleshooter is able to fix problems automatically. If not, then report back with any results.

byronhawkins · Jul 18, 2022

The driver dump is generated by DriverQuery, and the headers are:

Code:

Module Name  Description            Driver Type   Start Mode State      Status     Accept Stop Accept Pause Paged Pool(bytes) Code(bytes) BSS(bytes) Link Date              Path                                             Init(bytes)

Apparently the forum does not allow edits to the original post, so I can't integrate this into the original table. Anyway, none of it is very informative. The "OK" is just the driver status.

I've run all the troubleshooters, only the network troubleshooter reports a problem, and it says there is no driver for my network adapter. In DeviceManager, the WAN Miniport elements are "hidden" and show error code 45: "device is not attached". But the components are soldered on the board, so this is not possible, and many people report the same error where physical disconnect is not a feasible diagnosis (so it's a bogus error message). The URS driver for the Synopsys controller is also "hidden" with error code 45.

Most of the USB devices appear as "Unknown Device" with no driver assigned.

I wonder if the Event Viewer might indicate how Windows is configuring the devices at startup, but there is so much stuff I'm not sure what to look for.

iko22 · Jul 18, 2022

You should be able to edit the Original Post (OP) on this Forum. If you cannot, that could be because you are still a New Member. Then a few more posts would unlock the feature.

"device is not attached" refers to the device attached to the computer, not the interface wiring. It suggests that it cannot detect any hardware present.
"hidden" device drivers are because the device is not attached, or the driver is obsolete.
-- Is it possible you manually installed the wrong device drivers?

Anyhow, you want to find Errors and Warnings in Event Viewer. I cannot predict which Event IDs they are. But it is likely that the source is Kernel-PnP. If you know how to filter events by source.

glasskuter · Aug 4, 2022

I read your thread on the MS forum where both you and the Microsoft agent had reached out to the manufacturer in China regarding this and where you were told by the company that drivers would soon be posted on a non-Chinese site. With no drivers available to you since you live outside of China, IMO there's nothing you can do until they are. Anyone here who wants to get caught up on what exactly is happening here can see this thread. Microsoft thread