Windows 10: What is oem42.inf and why doesn't it install?

I still think there's a driver for you out there somewhere. If I can run it down, I'll package it up and post it here. OTOH, you might want to see if the driver management stuff inside the Windows Update Minitool can handle it for you. Download, install, and try it to see.
HTH,
--Ed--

 

Well, i've been looking for drivers and getting nowhere fast. Maybe EdTittel will have better luck then I.

• You said this was a clean re-install. Does that mean that controller was working before under Win 10?
• Have you tried just right click the controller in Device Manager, select Update Driver?
• Windows 10 comes with its own generic driver for the USB controller. Had you checked if the USB controllers and ports worked with the windows 10 generic driver?

As to your processor question, can't answer. I'm more of a software guy *Smile Maybe one of the others can

btw.... Don't think still needed at this point, but when I asked earlier about "Matching ID" that's an actual selection in the Details pull down menu. It tells you which one of the hardware IDs Windows used in selecting the driver it chose. Can tell you have specific or generic a driver Windows selected for a device.

 

One more thing, to be certain. Select one of the installed controllers->Properties->Details tab, select Inf Name on the pull down menu. Verify it does say oem26.inf .?

 

Not on mine. Perhaps because it didn't install?

 

There are 4 entries titled Universal Serial Bus (USB) Controller. All of them, including the one with the yellow triangle, have an entry described as Install Inf and it refers to oem26.inf. There is no entry titled ​Inf Name.

 

Re: No matching id on Details pull down"Not on mine. Perhaps because it didn't install?" Yes, that's why. Sorry, I meant for you to check one of the controllers that did install. But matching ID isn't important to know at this point
Re: Inf name not on your Details pull down"All of them, including the one with the yellow triangle, have an entry described as Install Inf and it refers to oem26." Very strange. I can't explain why yours shows Install Inf vs Inf name. I looked at Device Manager Details on both Win10 v1511 and v1607 releases. Both show Inf name for me. But, again, not important as Install Inf shows what we wanted to verify
Re: "I assumed that windows 10 installed its generic drivers during the clean install"Yes, the MS generic drivers are installed on a clean install.

• But your current situation shows the Intel USB driver installed. It was downloaded sometime after you completed the re-install. (Either by you or Windows update i would think)
  
• Makes me wonder when it worked before, might it have worked when it was the Windows 10 generic driver installed?
  
• After the re-install, do you know how/when the Intel USB driver was downloaded? After re-install, do you know if your problem also occurred with MS generics, before Intel USB downloaded and installed

 

Hmm. Interesting. As I recall, the clean install went fine but then I had to manually install a couple of devices. The Line 6 was one and it failed. Can't think of any others. Of course I reinstalled a bunch of software but the wouldn't be the cause would it?

Is there a way to uninstall the Intel USB driver, delete it and allow Win 10 to install the generics? Would that be worth a try?

 

Yes! That's where i was headed with my line of questions...

1. Best to first backup drivers. IMHO Simplest approach in this case (and for driver newbies) use DoubleDriver (tutorial). It backups up your drivers in hierarchical folder order in the same hierarchy and using folders names same as the category and device names as you see in Device Manager.

Should you want to dive deeper also see Backup drivers before reinstalling Windows 10 using DISM. The DriverStore Explorer tool mentioned is a front end GUI for the pnputil command we used back in post #9. I have one correction to the guide: Though i've never tested it, all the MS documentation i've read indicates neither the pnputil command nor its GUI "DriverStore Explorer" uninstalls drivers. They only remove driver packages from the DriverStore.

2. Create a System Restore point. (always good to be safe)
> Look in Programs and Features. If there's an Intel uninstaller there, use it to uninstall the chipset drivers
> Otherwise, try right click the USB controllers->Uninstall. Click delete drivers, if asked.
> Reboot.

3. Right click a USB controller->Properties->Driver tab. The Provider should be Microsoft meaning the generics are installed. Test. How do things look? If the Provider is still Intel we have to remove the driver package. From an elevated command prompt Code: pnputil.exe -f -d oem26.inf[/quote] .
> Uninstall Intel from the USB controllers again
> Reboot

 

I found a source that might be helpful: check out Win-Raid's outstanding collection of USB drivers: USB 3.0/3.1 Drivers (original and modded). I've been messing around with them on my machines and they seem to be much more on-target and up to date than ANYTHING ELSE out there.
HTH,
--Ed--

 

Those .inf files will usually have a header showing the original name of the .inf and may provide guidance as to what it is. Just open it in notepad. Some .infs can be installed by just right clicking and selecting that option.

If it is a USB driver, it may need a chipset driver to install the basic configuration.

 

.
> Uninstall Intel from the USB controllers again
> Reboot[/quote] Well that was interesting. Look at the attachment. Those Intel drivers are tenacious. However, things do look better for the moment. There wasn't an Intel uninstaller in my list, so I tried to manually uninstall from the Device Manager. That just got into a loop at first, so I rebooted and ran the pnputil as described. Uninstalled again and this time it appeared to work.

However when I rebooted and looked in the Device Manager, there is now a bunch of these Intel drivers, but everything does seem to be working. I might try to reinstall my Line 6 hardware and see if it works now.

 

Looks pretty reasonable now, I'd say. Hopefully, you've got it sorted. If not, the site where I recommended the USB drivers (Win-Raid) also has a great chipset collection of individually installable drivers. Find it at: Other Drivers (= INF files). He already did what I was trying to figure out how to do on your behalf. Great stuff!
HTH,
--Ed--