need driver for intel uhd620

[johnhoh]

My new laptop has an 8th-gen CPU

Can you tell us what is your motherboard chipset and what method you used to get USB3 working on win7?

 

[PrinceOfAbyss]

According to biostar you did not need to add the line:

%iKBLULTGT2R% = iSKLD_w7, PCI\VEN_8086&DEV_3EA0[/CODE]

in the W7 section in the .inf file

I wonder if it would have worked had you not added the line? The reason I ask is we are trying to validate whether the biostar tool will work for those not too technically inclined

EDIT: I see now that the biostar tool DOES include Coffee Lake Hardware IDs but does NOT include Whiskey Lake (PCI\VEN_8086&DEV_3EA0 is whiskey lake) so the tool should not work for you unless you add the line to the .inf like you did)

I suppose it would have worked if I had done a "Choose my hardware from the list", and then "Have disk" option; in other words, if I had forced the driver installation. But anyway, TBH I have no idea what this Biostar tool you're referring to is.

Can you tell us what is your motherboard chipset and what method you used to get USB3 working on win7?

This is the laptop: https://topics-cdn.dell.com/pdf/inspiron-15-3580-laptop_setup-guide_en-us.pdf It has a i5-8265U CPU but I'm not sure about the chipset.


For the USB installation, I downloaded this file: Forum - [Solution] Win7 drivers for USB 3.0/3.1 Controllers of new Intel chipset systems


It's funny that without the driver, the laptop wouldn't recognize even a USB stick and I had to burn the above mentioned driver in a CD! It was years before that I burnt a CD!


By the way guys, though it's offtopic, do you have a recommendation for the appropriate driver for the discrete (secondary) video card in my laptop? I tried to install an "Adrenaline" catalyst I found that was meant to be appropriate for my discrete VGA, but the device remained unrecognized in Device Manager. Though I tried that before I installed the UHD 620 driver, so I wonder if that plays a role.


The discrete VGA is PCI\VEN_1002&DEV_6665&SUBSYS_08C91028&REV_C3 that is a Radeon 520 Graphics with 2G GDDR5. TIA for any help with this too!

 

[johnhoh]

The discrete VGA is PCI\VEN_1002&DEV_6665&SUBSYS_08C91028&REV_C3 that is a Radeon 520 Graphics with 2G GDDR5. TIA for any help with this too!

According to the AMD website the Radeon 520 only has win10 drivers. Hopefully someone has figured out a way around that. Meantime, have you tried amd auto-detect?

https://www.amd.com/en/support/kb/faq/gpu-131
https://drivers.amd.com/drivers/ins...nalin-2019-19.7.1-minimalsetup-190706_web.exe

 

[SIW2]

canonkong usb mods look very good.

 

[johnhoh]

I suppose it would have worked if I had done a "Choose my hardware from the list", and then "Have disk" option; in other words, if I had forced the driver installation. But anyway, TBH I have no idea what this Biostar tool you're referring to is.

The biostar tool is supposed to provide windows 7 support on 310-chipset motherboards. I want to see someone try it on a 370 chipset machine.
Biostar Adds Windows 7 Support to Dozens of Current Gen Motherboards

For the USB installation, I downloaded this file: Forum - [Solution] Win7 drivers for USB 3.0/3.1 Controllers of new Intel chipset systems
It's funny that without the driver, the laptop wouldn't recognize even a USB stick and I had to burn the above mentioned driver in a CD! It was years before that I burnt a CD!

Although whiskey lake has an integrated chipset, the biostar tool is supposed to make you able to install win7 from a usb on a 310 chipset, so I wonder if it would have worked for you.

 

[Vineet Garg]

Hi All,
Great contributions!
There is a clean driver directly available from Driver Pack Solution : PCI\VEN_1002&DEV_6665&SUBSYS_08C91028&REV_C3 download driver for Windows 7 x64
Go for Download.zip :
Download.zip ( direct download link ) : http://dl.drp.su/driverpacks/repack...Catalyst-7x64-26.20.11015.5009_19.5.2-drp.zip

 

[SIW2]

I am rebuilding my pe3.1. I had to mod the usb3/3.1 drivers a little, but surprisingly, they now appear to work when running pe on a B75 motherboard. The official usb3 drivers for that are intel 1.0.10.255.

These modded 5.0.5.55 seem to be ok. I haven't speed tested them in pe. The ports work ok and no major problems as far as I can tell.

View attachment 5.05.55-modded-for-B75.zip

Added the bolded lines to the iusb3xhc.inf

[Intel.NTAMD64]	 
%IUsb3XhcDeviceDesc02% = IUsb3XhcModel, PCI\VEN_8086&DEV_A36D 
%IUsb3XhcDeviceDesc02% = IUsb3XhcModel, PCI\VEN_8086&DEV_A36D&CC_0C03
%IUsb3XhcDeviceDesc02% = IUsb3XhcModel, PCI\VEN_8086&DEV_A36D&CC_0C0330
%IUsb3XhcDeviceDesc02% = IUsb3XhcModel, PCI\VEN_8086&DEV_9DED 
%IUsb3XhcDeviceDesc02% = IUsb3XhcModel, PCI\VEN_8086&DEV_31A8

[B]%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_1E31&REV_00 
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_1E31&REV_01 
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_1E31&REV_02 
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_1E31&REV_03 
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_1E31&REV_04 [/B]

 

[PrinceOfAbyss]

Guys you are super helpful and I really thank you for this!

An update about my current situation: I installed the proposed discrete VGA drivers you proposed, but when the computer was turned on and once Win7 was loaded, the screen was flashing a couple of times, as if the display driver was re-installed, and I was getting a message that the hardware had changed and proposed a system restart... So I found another file (https://www2.ati.com/drivers/beta/Win7-64Bit-Radeon-Software-Adrenalin-Edition-18.1.1-Jan18.exe) which although it didn't identify initially my VGA correctly (it identified it as "AMD Radeon R5 M435", but I was able to correct that by altering the device name in the inf file) it fixed the problem with the flashing screen prompting for a restart... So I suppose both VGA cards (primary and discrete) are installed correctly.

Now, as you are so helpful, I'm gonna take advantage of it, risking to get really off-topic, and will tell you about two more (the last ones) problems I have:

So, I have an unrecognized device (ACPI\INT34BB) which in Google it's supposed to be some Intel(R) Serial IO GPIO Host Controller but I can't find a driver appropriate for it. What's more funny is that I can't locate the correct driver file even in the Dell site for it, which would be for Win 10 anyway, but I'd like to give it a try to install it... The Dell's drivers page for my laptop is this: https://www.dell.com/support/home/gr/el/grdhs1/product-support/servicetag/9x9mbv2/drivers

The last unrecognized device is PCI\VEN_8086&DEV_9DE0&SUBSYS_08C91028&REV_30 which is the Intel Management Engine driver (it's recognized as a PCI Simple Communications Controller in Device Manager). The funny thing is that every driver for Windows 7 has a different DEV_ID than 9DE0, and ONLY the Windows 10 drivers are for this DEV_ID. Any help would be very much appreciated.

Thank you in advance!

 

[johnhoh]

So I found another file (https://www2.ati.com/drivers/beta/Win7-64Bit-Radeon-Software-Adrenalin-Edition-18.1.1-Jan18.exe) which although it didn't identify initially my VGA correctly (it identified it as "AMD Radeon R5 M435", but I was able to correct that by altering the device name in the inf file) it fixed the problem with the flashing screen prompting for a restart...

That's the second link from my post #23. (though I see now AMD misdirects that link for some reason. anyway..)

I have an unrecognized device (ACPI\INT34BB) which in Google it's supposed to be some Intel(R) Serial IO GPIO Host Controller but I can't find a driver appropriate for it.

Try this one.
Download Intel(R) Processor I/O Controller Driver for Windows 7* for Intel(R) NUC

Also try the intel driver assistant.
Download Intel(R) Driver & Support Assistant

Also trying getting up to date with windows update. You may need to run the wufuc zeffy utility, or just run WUMT
https://softfamous.com/windows-update-minitool/

The last unrecognized device is PCI\VEN_8086&DEV_9DE0&SUBSYS_08C91028&REV_30 which is the Intel Management Engine driver (it's recognized as a PCI Simple Communications Controller in Device Manager). The funny thing is that every driver for Windows 7 has a different DEV_ID than 9DE0, and ONLY the Windows 10 drivers are for this DEV_ID. Any help would be very much appreciated.

What are you referring to in the bold type above? Sounds like you have your hands on an inf file for Intel Mgt Engine Driver?

 

[PrinceOfAbyss]

What are you referring to in the bold type above? Sounds like you have your hands on an inf file for Intel Mgt Engine Driver?

Yup, I tried many MEI packages, for Win7, Win8, Win8.1, Win10, and those appropriate for W7 don't have my DEV_9DE0, and those appropriate for any other OS indeed mention 9DE0 in their .INF's

Take for example an extract from the inf of MEI DriverVer = 04/04/2019,1914.12.0.1256 which is appropriate for Win7:

[Intel.NTx86.6.1]
; DisplayName               Section           DeviceId
%TEE_DeviceDesc%=TEE_DDI, PCI\VEN_8086&DEV_9CBA   ;ME10.x - BDW/WPT-LP
%TEE_DeviceDesc%=TEE_DDI, PCI\VEN_8086&DEV_9D3A   ;ME11.x - SKL/SPT-LP, KBL/SPT-LP
%TEE_DeviceDesc%=TEE_DDI, PCI\VEN_8086&DEV_A13A   ;ME11.0 - SKL/SPT-H
%TEE_DeviceDesc%=TEE_DDI, PCI\VEN_8086&DEV_A2BA   ;ME11.6 - KBL/KBP-S


[Intel.ntamd64.6.1]
; DisplayName               Section           DeviceId
%TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_9CBA   ;ME10.x - BDW/WPT-LP
%TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_9D3A   ;ME11.x - SKL/SPT-LP, KBL/SPT-LP
%TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_A13A   ;ME11.0 - SKL/SPT-H
%TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_A2BA   ;ME11.6 - KBL/KBP-S
%TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_A1BA   ;ME11.x - Purley WS SKL/LBG - Production
%TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_A23A   ;ME11.x - Purley WS SKL/LBG - PreProduction

Nowhere is mentioned anything for DEV_9DE0

Now take a look an extract from MEI DriverVer = 04/04/2019,1914.12.0.1256 which is for Win8+

[Intel.NTx86.6.2]
; DisplayName               Section           DeviceId
%TEE_DeviceDesc%=TEE_DDI_W8, PCI\VEN_8086&DEV_9DE0   ;ME12.0 - CNL/CNP-LP

[Intel.ntamd64.6.2]
; DisplayName               Section           DeviceId
%TEE_DeviceDesc%=TEE_DDI_W8_x64, PCI\VEN_8086&DEV_9DE0   ;ME12.0 - CNL/CNP-LP

;
; ============== Win10 Support ==================
;
[Intel.NTx86.10.0]
; DisplayName               Section           DeviceId
%TEE_DeviceDesc%=TEE_DDI_W10_RS4_AND_BEFORE, PCI\VEN_8086&DEV_9DE0   ;ME12.0 - CNL/CNP-LP

;

[Intel.ntamd64.10.0]
; DisplayName               Section           DeviceId
%TEE_DeviceDesc%=TEE_DDI_W10_RS4_AND_BEFORE_x64, PCI\VEN_8086&DEV_9DE0   ;ME12.0 - CNL/CNP-LP

[Intel.NTx86.10.0...17763]
; DisplayName               Section           DeviceId
%TEE_DeviceDesc%=TEE_DDI_W10, PCI\VEN_8086&DEV_9DE0   ;ME12.0 - CNL/CNP-LP

;

[Intel.NTamd64.10.0...17763]
; DisplayName               Section           DeviceId
%TEE_DeviceDesc%=TEE_DDI_W10_x64, PCI\VEN_8086&DEV_9DE0   ;ME12.0 - CNL/CNP-LP

Here you can see that DEV_9DE0 is used, but the OS is inappropriate...


Trying to alter either the first case by adding the DEV_9DE0, or the second case by adding Intel.ntamd64.6.1 (Win7) ends up in a recognized device, which however cannot start after installation...

 

[johnhoh]

This guy Canon Kong at win-raid.com has written or modded a lot of drivers over the years and he may have an Intel Mgt Engine Interface driver that works for your machine on win7. I am not sure how to search for his driver repository though. But here is a thread about IMEI fwiw

Forum - Intel Management Engine: Drivers, Firmware & System Tools

 

[PrinceOfAbyss]

This guy Canon Kong at win-raid.com has written or modded a lot of drivers over the years and he may have an Intel Mgt Engine Interface driver that works for your machine on win7. I am not sure how to search for his driver repository though. But here is a thread about IMEI fwiw

Forum - Intel Management Engine: Drivers, Firmware & System Tools

Trying to alter either the first case by adding the DEV_9DE0, or the second case by adding Intel.ntamd64.6.1 (Win7) ends up in a recognized device, which however cannot start after installation...

This part of my last post made me wonder if I really tried to manually remedy the first case, that is to add the 9DE0 device id in the Win7 driver... And to my surprise, I didn't!!!!!


So I just added it to the Win7 x64 section of the driver, and it worked!!!!

[Intel.ntamd64.6.1]
; DisplayName               Section           DeviceId
%TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_9CBA   ;ME10.x - BDW/WPT-LP
%TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_9D3A   ;ME11.x - SKL/SPT-LP, KBL/SPT-LP
%TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_A13A   ;ME11.0 - SKL/SPT-H
%TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_A2BA   ;ME11.6 - KBL/KBP-S
%TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_A1BA   ;ME11.x - Purley WS SKL/LBG - Production
%TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_A23A   ;ME11.x - Purley WS SKL/LBG - PreProduction
%TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_9DE0   ;ME12.0 - CNL/CNP-LP <--- ALL IT NEEDED WAS THIS LINE

That's what you get for trying a hundred different things... At the end of the day you can't remember what you tried and what you didn't... I'm so embarrassed and at the same time so relieved that it finally worked!


Now what's left to make it work is the ACPI\INT34BB... Not that it's something important... Will give it some time just so that it disappears from the Other devices in DevMgr... If anyone has any suggestions, let me know! Ah that driver for the Intel NUC that someone proposed didn't work!

 

[johnhoh]

Now what's left to make it work is the ACPI\INT34BB... Not that it's something important... Will give it some time just so that it disappears from the Other devices in DevMgr... If anyone has any suggestions, let me know! Ah that driver for the Intel NUC that someone proposed didn't work!

just a note, a quick way to see the DeviceIDs with issues is to do
start > run > msinfo32 > enter > components > problem devices

All your issues will be on the right hand pane

For ACPI\INT34BB you could try downloading one or more of these:

Microsoft Update Catalog

then extract the cab file using 7-zip, then inserting your deviceid in the inf file like you have been doing

But it appears intel never even had a gpio host controller on win7, so this device might be dead in the water

 

[PrinceOfAbyss]

I managed to find the appropriate software from Dell's website https://downloads.dell.com/FOLDER05345907M/1/Intel-Serial-IO-Driver_M31NN_WIN_30.100.1841.2_A02.EXE

However, the appropriate inf (iaLPSS2_GPIO2_CNL.inf) only mentions Win10.

So I changed

[Manufacturer]
%INTEL%=Intel,NTamd64.10.0

[Intel.NTamd64.10.0]
%iaLPSS2_GPIO2.DeviceDesc_0%=iaLPSS2_GPIO2_Device, ACPI\INT34BB
%iaLPSS2_GPIO2.DeviceDesc_1%=iaLPSS2_GPIO2_Device, ACPI\INT3450

to

[Manufacturer]
%INTEL%=Intel,NTamd64.6.1

[Intel.NTamd64.6.1]
%iaLPSS2_GPIO2.DeviceDesc_0%=iaLPSS2_GPIO2_Device, ACPI\INT34BB
%iaLPSS2_GPIO2.DeviceDesc_1%=iaLPSS2_GPIO2_Device, ACPI\INT3450

to allow the driver to get recognized as a valid driver for Win7. Indeed the installation ran smoothly, but once finished, Windows complained that the driver needed a valid digital signature (which obviously isn't recognized, as while it exists, it's meant for Win10). So now, while the device moved from Other devices to System devices list, it has a yellow exclamation mark on it, and can't be started.

Is there any way to overcome that digital signature obstacle? I suppose that the same issue was faced by the person whose USB3.1 driver I'm using. So there must be a solution, like a custom signature?

 

[Vineet Garg]

Hi,
I would suggest to install Chipset driver with '-overall' command line switch & have a look on Device Manager :
1) Make a system restore point.
2) download 'Intel Chipset Device Software Driver' listed under 'Win 10' from 'Inspiron 3580' support page.
(Direct Download Link : https://downloads.dell.com/FOLDER05...e-Driver_KK6C2_WIN_10.1.17903.8106_A07_01.EXE )
3) Extract the driver executable with 7zip & run SetupChipset.exe -overall
4) It can be useful in the near future if you make note about offered drivers from 'SetupChipset.exe -overall' execution.

 

[johnhoh]

once finished, Windows complained that the driver needed a valid digital signature (which obviously isn't recognized, as while it exists, it's meant for Win10). So now, while the device moved from Other devices to System devices list, it has a yellow exclamation mark on it, and can't be started. Is there any way to overcome that digital signature obstacle? I suppose that the same issue was faced by the person whose USB3.1 driver I'm using. So there must be a solution, like a custom signature?

To disable signature enforcement
How to Enable/Disable Driver Signature Enforcement in Windows 7 | Incredigeek

Or you can load drivers modded by someone else who also provides a Certificate you can tell your computer to trust. I am not sure how to find the driver you need but its probably on win-raid.com somewhere, written by either Fernanado or canonkong who have modded dozens of drivers.

Forum - [Tips+Discussion] Usage of "mod+signed" Drivers

 

[PrinceOfAbyss]

Yup, I contacted canonkong and he offered to sign the driver for me. Seems such a kind person... So hopefully with his help my last device will be installed correctly! I'll keep you guys posted! You are also such a great and helpful team! Thank you for everything and sorry for the off-topic posts!

 

[SIW2]

If he kindly does that for you, then you could upload it somewhere so others in need can use it.

 

[PrinceOfAbyss]

Sure I will. Sharing is caring!

 

[PrinceOfAbyss]

After some days of investigating the driver and the accompanying app from Intel for its Serial I/O device, one thing got pretty clear: The device is not usable under W7, nor is the driver or the app instalable by any means... So canonkong from the other forum created a "fake driver" (an empty cell) so as to just get rid of the yellow triangle at least... Actually, the driver contains the H/W IDs of other Serial I/O devices from Intel as well, so it will suit more than my INT34BB device.


Here is the link to download it: https://mega.nz/#!G25VyQrD!is7NaaOH0WITC1_MlIbxxVmkwibV9UWFTd07fsTf-3s


So thanks a lot for all the help you've given me guys during my quest to make my new laptop 100% functional under W7.