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

Page 2 of 3 FirstFirst 123 LastLast
  1.    13 Dec 2016 #11

    Computer info


    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
      My ComputerSystem Spec

  2.    14 Dec 2016 #12

    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

    The error message implies it's an Intel USB Controller driver but you will notice that there is a driver already installed for that.
    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
      My ComputerSystem Spec

  3.    14 Dec 2016 #13

    ComputerGeek said: View Post
    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.
    Last edited by Pjh; 14 Dec 2016 at 01:23.
      My ComputerSystem Spec

  4.    14 Dec 2016 #14

    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--
      My ComputerSystem Spec

  5.    14 Dec 2016 #15

    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 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.

    Click image for larger version. 

Name:	2016-12-14_160838.jpg 
Views:	13 
Size:	66.7 KB 
ID:	113584
      My ComputerSystem Spec

  6.    14 Dec 2016 #16

    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 .?
      My ComputerSystem Spec

  7.    14 Dec 2016 #17

    ComputerGeek said: View Post
    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?

    Yes. The earlier install was the upgrade from 8.1. Worked fine.


    • Have you tried just right click the controller in Device Manager, select Update Driver?

    Yes, did that first.


    • 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?

    I assumed that windows 10 installed its generic drivers during the clean install.


    As to your processor question, can't answer. I'm more of a software guy 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.

    Click image for larger version. 

Name:	2016-12-14_160838.jpg 
Views:	13 
Size:	66.7 KB 
ID:	113584
    Not on mine. Perhaps because it didn't install?
    Click image for larger version. 

Name:	Untitled-1.jpg 
Views:	10 
Size:	55.5 KB 
ID:	113596
      My ComputerSystem Spec

  8.    14 Dec 2016 #18

    ComputerGeek said: View Post
    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 .?
    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.
      My ComputerSystem Spec

  9.    14 Dec 2016 #19

    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

      My ComputerSystem Spec

  10.    15 Dec 2016 #20

    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?
      My ComputerSystem Spec


 
Page 2 of 3 FirstFirst 123 LastLast

Related Threads
Yeah, this stupid os is still trying to install SHitty crush saga by itself (200mb) stalling all the critical updates on qeue and saturating all the bandwidth (1mbit) available. WTF, who the hell is developing this, how is possible everybody...
I'm not sure how this happened, but I created a dual boot of Windows 7 and 10. When I installed 10 on a second partition (MBR, not EFI) Windows 10 does not remap it's OS partition to C: but stays on E: This is causing a lot of problems because I...
Hi I have looked through solutions for this issue, but the suggestions don't seem to fix my issue... I am running Windows 7 SP1 Pro 64-bit on a Dell Optiplex 760, and try to do a clean install of Windows 10, using the ISO file which I downloaded...
1. Sfc /scannow does not work...........Windows Resource protection could not start the repair service. 2. Dism /online /cleanup-image /restorehealth works. 3. Safe mode does not work. Once got to safe mode, the screen kept...
Solved Windows 10 install doesn't in Installation and Upgrade
I am trying to install Windows 10 on a computer that is running 8.1. All checks and prerequ's passed and I finally selected "Install Now". Windows 10 downloaded (pretty slow btw.) and then the box rebooted. It then slowly counted up to 100%...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 11:36.
Find Us