need driver for intel uhd620  

PrinceOfAbyss said:

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?

johnhoh said:

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.

johnhoh said:

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/insp...uide_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!

PrinceOfAbyss said:

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/inst...190706_web.exe

PrinceOfAbyss said:

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

PrinceOfAbyss said:

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.

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/Wi....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...x9mbv2/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!

PrinceOfAbyss said:

So I found another file (https://www2.ati.com/drivers/beta/Wi....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..)

PrinceOfAbyss said:

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/

PrinceOfAbyss said:

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?

johnhoh said:

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:

Code:

[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+

Code:

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