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

After a recent clean re-install of Windows 10, there's a USB Controller device that is reporting itself unable to configure. The Events list reports:
Device not configured (oem42.inf)
Device install requested
Device not configured (oem42.inf)
Device installed (ich78usb.inf)

It keeps doing this every day. The Event information for the first entry is:

Device PCI\VEN_8086&DEV_27C9&SUBSYS_50041458&REV_01\3&13c0b0c5&0&E9 failed configurationDriver Name: oem42.infClass Guid: {36FC9E60-C465-11CF-8056-444553540000}Driver Date: 07/31/2013Driver Version: 9.1.9.1006Driver Provider: IntelDriver Section: Intel_OHCI.Dev.NT.ServicesDriver Rank: 0xFF2001Matching Device Id: PCI\VEN_8086&DEV_27C9Outranked Drivers: usbport.infCI\VEN_8086&DEV_27C9:00FF2001 usbport.infCI\CC_0C0300:00FF2005Device Updated: falseStatus: 0xC0000494Parent Device: ACPI\PNP0A03\1

Can anyone tell me what this means, and what I can do about it?

:)

 

The windows 10 fall upgrade 1709 fails after about 45% mark.. Then gives an error message and returns system to 1703

Any clues in those?

 

The windows 10 fall upgrade 1709 fails after about 45% mark.. Then gives an error message and returns system to 1703

Any clues in those?

Nothing really..

two were Microsoft drivers (\pd\f and xml writer)

other was audio driver.. I deleted all audio drivers and let them recreate by themselves..

I deleted all traces of oem43,42 and 6.. but they keep returning??

 

It means that you need to install the manufacturer specific driver for that piece of hardware. You say you did a recent clean re-install of Windows 10. Did you save a backup image of the old installation, or at least export the manufacturer's drivers before doing the clean re-install? Have you tried going to the manufacturer's website and see what drivers they have for download?

 

From the vendor ID and a quick Google search looks like you're talking about Intel(R) N10/ICH7 Family USB Universal Host Controller.
According to what I find online various Intel chipset drivers for your motherboard should include this item. The resource I found mentioned chipset driver version 9.1.1.1016, but you can probably find something newer that works. Try this page at Station-Drivers for the most recent series 9x chipset drivers.
HTH,
--Ed--

 

Not that smart. I did backup all the user files (which has proved useful). I'm guessing the way forward would be to uninstall the rogue entry. Then unplug all my USB connections and add them back one at a time and look in Device Mgr to see which one produces the bad install. Would that work?

 

The driver appears to be a motherboard driver, not a discrete device driver. Your approach my work, but if it fails, it's because the problem is on the PC side of the USB connection, not the device side. If your troubleshooting fails, I urge you to seek out a 9x series Intel chipset driver from Driver-Station, to unpack the contents of that file into a directory, and then to use Device Manager to manually update the device driver, pointing it at the directory where you put the contents of the 9.x.x.x.inf file.
HTH,
--Ed--

 

I would just go to Intel's website and see what they say:
Drivers & Software

The driver update utility even found new drivers for my WiFi/Blutetooth adapter

 

Dear NavyLCDR:
Thanks for chiming in. I pointed the OP at Station-Drivers because they have a larger and more current set of Intel drivers available than does Intel itself. IMO, stuff is easier to find there than on the Intel site. It sounds like he needs to go back to the old 9.x.x.x drivers, given the age of his mobo. Always glad to hear from you, though, and finally also glad to have a chance to say "Thanks for your many, frequent, and helpful posts here at TenForums!"
Best wishes,
--Ed--

PS: if you're going to use the Intel Driver Update Utility, please make sure to grab the most current version 2.6.2.3.

 

Think the water's a bit deep here. I ran the 2.6.2.3 version of Driver Update Utility from Intel. It tried to update my drivers from 9.xxx to 10.xxx. It failed, reporting an "unknown error". But I assume that's consistent with Ed's advice. I also downloaded a 9.4.4.1006 driver set from Station Drivers but I'm not sure I am using it right. It unpacks into a folder that contains only the one executable file, viz., infinst_autol.exe which is the Intel Driver Installer. It runs the Intel Package Manager which unpacks a stack of files (but I don't know where to). After a long delay (like about 3 minutes) the Intel Chipset Device Software Manager window opens. I run it and it finishes, but nothing seems changed. What am I missing?

 

To get any further,

• You need tell us your system specs. The specific make/model of your computer or m/b.
• Open a command prompt window. Type: pnputil -e > "%userprofile%\Desktop\pnp.txt". Then upload pnp.txt file from Desktop on your C drive.
• Point us to the driver file you're trying to install
• Also please generate and attach aDirect X report

• Click Start button in lower left corner, enter dxdiag in the search box
• When DxDiag opens, look along the buttons at the bottom of the DxDiag window===> If you’re running 64 bit Windows, you’ll see a 64-bit DxDiag button. Click it to run the 64-bit version of dxdiag
• Notice progress in lower left window corner
• When done, click Save Information button and save as a text file to your Desktop
• Upload the file to your next post

 

The Intel chipset utility doesn't really tell you much when it runs. When the extraction from the infinst...exe file occurs on my system it deposits files to C:\Users\etitt\AppData\Local\Temp\IPMx2\All\wptahci.inf. You should be able to find those files in your AppData hierarchy and try them out manually, or copy them elsewhere (the Intel installer deletes them when it finishes, so try to grab them before closing the program). Then you can work with those files directly yourself.
HTH,
--Ed--

 

In response to Computer Geek (thanks), here are the two files requested. I can't point you to the driver I'm trying to install because it's not listed (I guess because it won't install). The error message implies it's an Intel USB Controller driver but you will notice that there is a driver already installed for that. The USB ports seem to be working fine except I couldn't get the Line 6 drivers to recognise my device (it's a UX1 sound card for playing the guitar through the computer sound system). I talked with Line 6 but they say there is no incompatibility problem with Windows 10. This may be a red herring.

pnp.txt
DxDiag.txt

 

oemnn.inf is just a naming convention Windows uses when installing a 3rd party driver (more specifically, a 3rd party driver that wasn't included on the original Windows installation media). nn is just the next sequential number appended to oem when the driver is installed and the filename created

Yea, that error message also has me a bit confused as it seems to indicate oem42.inf was an attempt to re-install what pnputil shows as oem26.inf (Intel USB controller driver with same version number and date as oem42)

You say all your usb ports currently work. Look in Device Manager, are there any devices with yellow icons? Also, am curious, right click one of the USB controllers->Properties->Details tab. Use the pull down to select Matching Device Id. What does it show?

Also, your Gigabyte EP41-UD3L mobo is a bit old and doesn't appear certified for Win 10 which may be the root of your Line 6 problem.

Will look at it more sometime tomorrow

 

Thanks for the explanation. Always learning! It used to be complicated enough when I just had an Atari 400 and a cassette recorder!

Yes, there's a USB Controller with a yellow icon. That's the one I've been looking at and wondering about. The "Compatible IDs" (presume that's what you mean) are:
PCI\VEN_8086&DEV_27C9&REV_01PCI\VEN_8086&DEV_27C9PCI\VEN_8086&CC_0C0300PCI\VEN_8086&CC_0C03PCI\VEN_8 086PCI\CC_0C0300PCI\CC_0C03

Yeah, I've been thinking the problem might be mobo. Although it passed the upgrade check. Could I use my existing CPU on a newer mobo? Intel(R) Core(TM)2 Duo CPU E7400. I see the answer is NO.