Windows 7 installation help for Intel Skylake and Kaby Lake laptops

How much free space do you have on D:

 

Sometime MSMG Toolkit is uncooperative, for reasons not understood, but doing the WIM mods on a different drive has always caused it to work right for me when that happens. Maybe that is what is going on here?

 

Everything is on D. I have 2.5 tb free

 

Try moving the whole process and the files to the C:\ drive and see if it completes properly. I have had this happen multiple times with MSMG Toolkit. I normally do everything on D:\ as well. Not sure why it matters, but it seems to. Just weird that it is random. @Phoenix has experienced the same thing.

 

I will give that a try.

Edit: Still the same result, only it takes about a third of the time
Maybe its not a clean install.wim. I know I had an untouched 64x Win 7 sp1 iso somewhere, but may have lost it. Maybe MDL has some mirrors of clean ISO images, as Microshaft doesnt supply them anymore, even with a legit key.

 

@Atak_Snajpera Is there a way to add modified .dll files using this program? lIKE Imageres.dll, and shell32.dll. I would like to create a custom install of how I set everything up.

 

Still getting errors with moving to C drive, and a freshly downloaded untouched ISO from MDL.

[2018-01-30 09:49:16]
[2018-01-30 09:49:16] Deployment Image Servicing and Management tool
[2018-01-30 09:49:16] Version: 6.1.7600.16385
[2018-01-30 09:49:16]
[2018-01-30 09:49:17] Image File : C:\Users\CPHome\Desktop\Windows_7_Image_Updater\Image\sources\boot.wim
[2018-01-30 09:49:17] Image Index : 2
[2018-01-30 09:49:18] Saving image
[2018-01-30 09:49:23] Unmounting image
[2018-01-30 09:49:28] The operation completed successfully.

----------------[ install.wim -> Windows 7 ULTIMATE ]----------------
[2018-01-30 09:49:28]
[2018-01-30 09:49:28] Deployment Image Servicing and Management tool
[2018-01-30 09:49:28] Version: 6.1.7600.16385
[2018-01-30 09:49:28]
[2018-01-30 09:49:34] Mounting image
[2018-01-30 09:50:02] The operation completed successfully.

[2018-01-30 09:50:02]
[2018-01-30 09:50:02] Deployment Image Servicing and Management tool
[2018-01-30 09:50:02] Version: 6.1.7600.16385
[2018-01-30 09:50:02]
[2018-01-30 09:50:05] Image Version: 6.1.7600.16385
[2018-01-30 09:50:05]
[2018-01-30 09:50:06] Searching for driver packages to install...
[2018-01-30 09:50:11] Found 163 driver package(s) to install.
[2018-01-30 09:50:11] Installing 1 of 163 - C:\Users\CPHome\Desktop\Windows_7_Image_Updater\Windows7\Drivers\x64\Alcor Micro Smart Card Reader\SZCCID.INF: Error - An error occurred. The driver package could not be installed.
[2018-01-30 09:50:11] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 09:50:11] Installing 2 of 163 - C:\Users\CPHome\Desktop\Windows_7_Image_Updater\Windows7\Drivers\x64\Alcor Micro USB Card Reader\AmUStor.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 09:50:11] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 09:50:11] Installing 3 of 163 - C:\Users\CPHome\Desktop\Windows_7_Image_Updater\Windows7\Drivers\x64\Alpine Ridge USB\USBController\ausb3xhc.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 09:50:11] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 09:50:11] Installing 4 of 163 - C:\Users\CPHome\Desktop\Windows_7_Image_Updater\Windows7\Drivers\x64\Alpine Ridge USB\USBHub\ausb3hub.inf: Error - An error occurred. The driver package could not be installed.

 

This may sound silly but you could try updating on virtual machine with win10
I have no idea why it does not work on your pc.

 

I have just updated Windows 7 Image Updater

v2018.02 - Change Log

Code:

Added: Support for splitted images (install.swm)
Added: Support for compressed images which use LZMS-solid algorithm
Added: Automatic splitting of install.wim if file size is bigger than 4095 MiB (FAT32 Compatibility)
Added: Automatic recompression using the strongest algorithm supported by selected installer (2009 [Win7] installer supports only LZX while latest [Win10] much more efficient LZMS-solid)
Added: Automatic import of any files to selected edition(s) via Import folder (Folder structure after importing is maintained!)
Updated: Tools (7z v18.01 , DISM 10.0.16299.15 , oscdimg v2.56, rufus v2.18.12.13 , wimlib 1.12.0)

LINK is the same
https://forum.videohelp.com/threads...SkyLake-KabyLake-CoffeLake-Ryzen-Threadripper

 

Can you add drivers for the Killer E2200/2400/2500 Ethernet adapters in a future update? Your pack already contains some for their Wi-Fi counterparts.

 

Please provide HARDWARE ID for missing device

 

You should be able to pull them from the driver package available here.

 

OK. Thanks.

 

Maybe I can get this new version to work for me. I love this tool too. I have a SSD that will be here Saturday to install Windows 10 on for benchmarking. I will try and use it while in Windows 10.
Thanks @Atak_Snajpera for your work on this! You should create a dedicated thread for this, and I think it should be stickied

 

I just installed Windows 7 on my new Dell 7577's SATA SSD using @Atak_Snajpera's tool. Was running into an unspecified error at initial disk partitioning stage while in Legacy, Secure Boot OFF, RAID. Switched my disk mode to AHCI in BIOS and it allowed me to install it to my SATA SSD without a hitch. Now I may see if I can get it to install to my NVMe drive. Will report back if/when I need more help. Big thanks to @Atak_Snajpera since I was having no luck manually integrating drivers and updates via NTlite and Simplix pack. Still hoping to master that method though TBH.

 

Done. I've just reuploaded whole package with Rivet Networks LAN drivers. I've also updated Atheros Wireless drivers and AMD GPU drivers.

 

I finally got around to testing this tool. First two attempts to use it failed. I was trying to output the new modded ISO to the desktop. I chose the same folder as the tool (which I unzipped on the desktop) and that worked. So, anyone having issues with it erring out, if you're trying to save the new ISO to the desktop, choose another location.

My new ISO is actually an AIO (64-bit only) ISO rather than single version. (I thought the ISO I downloaded was Ultimate only and named it accordingly.) This process took a couple of hours to run, probably because it was injecting Home Basic, Home Premium, Pro and Ultimate. Nice job, Brother @Atak_Snajpera. @Phoenix tried it yet?

 

What was exact error message? I'm asking because I always save ISO on desktop and no issues so far.

Uncheck "Apply to all editions" next time.

 

There was one error and both times it was "unable to find specified file" (or something similar to that). Both times is was about 30 minutes into the process. As soon as I made the destination for the new ISO another location it completed without error.

I did not mind waiting. I wish the ISO had not been an AIO version simply because I don't like an AIO ISO. I only use the Pro/Ultimate versions of Windows, so the Home Basic and Home Premium being included are pointless. I would prefer to have only Pro and Ultimate standalone ISO. I cannot find an Ultimate-only ISO available for download except from sketchy web sites. I do have a Pro-only ISO.

 

Official ISOs from M$ always had multiple editions. Download and see en_windows_7_ultimate_with_sp1_x64_dvd_u_677332.iso

 

That is the one I already have.

 

I didn't but about taking a long time, it's because it has to do the same process for every image, mount, update, unmount, cleanup. Exactly how it is with the Windows 7 USB Creator from Intel, it'd takes ages if you hadn't removed the other editions that you don't want. You can remove other editions via the MSMG Toolkit from the remove menu, you have to remove then one by one until only the edition that you want exists, then go to option 6 and do a cleanup then create the ISO again

 

Those who have got a license key for Win 7 pro N can use this link to grab de-bloated W7 http://www.nomaher.com/forum/index.php?topic=3350.210

 

Actually a very important one, for a lot of Intel HWA accelerated applications like Vegas, Video Pro X, and Corel Video Studio 2018, all of which can render in less than half the time with an IntelGPU present. And there are others. More and more non-gaming applications are moving to that built in Intel GPU. In fact some vendors have now officially DROPPED support for Nvidia and AMD in favour of IntelGPU as it has the performance needed at a better price-point.

 

Raiderman, can you tell me which version of the Intel driver you got working? I have spent hours trying to get Windows 7 to use the iGPU on my 8700K. There is a well-documented work-around for Kaby Lake modifying the igdlh64.inf file but that doesn't work on Coffee Lake. I have everything else working fine except for that, which I need to accelerate my Video Editing application, that now only uses iGPU (Magix Video Pro X). WikiChip claims that the graphics is identical on KL and CL but the drivers are not. I figured wIntel had crippled the drivers to stop this workaround but when I saw your post I got all excited again...

 

Have you tried adding manually your hardware_id (UHD 630) in igdlh64.inf ?

Code:

;=====================================================================
;    Windows 7 Install - DT Only
;=====================================================================
[IntelGfx.NTamd64.6.1]
; SKL HW
%iSKLULTGT1%    = iSKLD_w7, PCI\VEN_8086&DEV_1906
%iSKLULTGT2%    = iSKLD_w7, PCI\VEN_8086&DEV_1916
%iSKLULXGT2%    = iSKLD_w7, PCI\VEN_8086&DEV_191E
%iSKLDTGT2%      = iSKLD_w7, PCI\VEN_8086&DEV_1912
%iSKLULTGT2f%    = iSKLD_w7, PCI\VEN_8086&DEV_1921
%iSKLULTGT3e%    = iSKLD_w7, PCI\VEN_8086&DEV_1926
%iSKLULTGT3%    = iSKLD_w7, PCI\VEN_8086&DEV_1923
%iSKLULTGT328W% = iSKLD_w7, PCI\VEN_8086&DEV_1927
%iSKLDTGT1%      = iSKLD_w7, PCI\VEN_8086&DEV_1902
%iSKLHaloGT1%   = iSKLD_w7, PCI\VEN_8086&DEV_190B
%iSKLHaloGT4%   = iSKLD_w7, PCI\VEN_8086&DEV_193B
%iSKLHaloGT3fe% = iSKLD_w7, PCI\VEN_8086&DEV_192B
%iSKLHaloGT2%   = iSKLD_w7, PCI\VEN_8086&DEV_191B
%iSKLSRVGT3e%   = iSKLD_w7, PCI\VEN_8086&DEV_192D
%iSKLSRVGT4%   = iSKLD_w7, PCI\VEN_8086&DEV_193A
%iSKLWSGT2%   = iSKLD_w7, PCI\VEN_8086&DEV_191D
%iSKLWSGT4%   = iSKLD_w7, PCI\VEN_8086&DEV_193D
;KBL HW
%iKBLULTGT1%        = iSKLD_w7, PCI\VEN_8086&DEV_5906
%iKBLULTGT2%        = iSKLD_w7, PCI\VEN_8086&DEV_5916
%iKBLULTGT2F%       = iSKLD_w7, PCI\VEN_8086&DEV_5921
%iKBLULTGT3E15%     = iSKLD_w7, PCI\VEN_8086&DEV_5926
%iKBLULTGT3E28%       = iSKLD_w7, PCI\VEN_8086&DEV_5927
%iKBLULXGT2%        = iSKLD_w7, PCI\VEN_8086&DEV_591E
%iKBLDTGT1%         = iSKLD_w7, PCI\VEN_8086&DEV_5902
%iKBLDTGT2%         = iSKLD_w7, PCI\VEN_8086&DEV_5912
%iKBLHALOGT1%       = iSKLD_w7, PCI\VEN_8086&DEV_590B
%iKBLHALOGT2%       = iSKLD_w7, PCI\VEN_8086&DEV_591B
%iKBLWGT2%          = iSKLD_w7, PCI\VEN_8086&DEV_591D

 

Yup - that does not work on Coffee Lake. Works fine on KL though. I have put the working igdlh64.inf for CL side by side with the last one that works for KL and copy-pasted all the missing sections, even analysing the DLL file-versions. I am missing something small because it installs just fine, no errors, but then after a restart it goes yellow exclamation mark in DevMngr.

I have windows 7 running on Z270 with i7-7700K and iGPU (v21.20.16.4860 Nov-2017) which is the last version I can get to work. Anything after that will not work with 7th gen...
Then I move the OS drive over to Z370 with i7-8700K and the iGPU fails to load, when in theory it should actually run just fine - the differences are cosmetic from what I read.

 

You would have to ask @Mr. Fox as my screenshot was of my Ryzen build. He also has an 8700k on Windows 7.

Sent from my SM-G935T using Tapatalk

 

My apologies - you are correct - I got confused with the quoting - it is indeed Mr Fox who said he got iGPU working on Coffee Lake.... so my question goes out to him now
Mr Fox, can you tell me which version of the Intel driver you got working? You said you have it stashed in case you ever need it again....

 

I'm glad that AMD is back in business with laptops with Ryzen + Vega GPU on board.
The sad thing is that Intel + Vega GPU in laptop won't work on win7 because Intel igpu driver is required to support external GPU.

Summary. You want win7? Buy AMD laptops!

 

If memory serves me correctly, it was from the ASUS driver support web page for my Maximus X Hero WI-FI AC motherboard for Windows 10 but it allowed me to install it on Windows 7. If that does not work, let me know. I will re-enable the iGPU temporarily and see which of the drivers I downloaded will install.

 

Hi Mr. Fox, the version on ASUS driver page is 23.20.16.4849 (Dec 2017) and only has the windows 10 sections in it. I tried adding the Windows 7 sections and it does install but fails on reboot. I have tried to modify the following versions without success:
21.20.16.4508
21.20.16.4541
21.20.16.4551
21.20.16.4590
21.20.16.4678
21.20.16.4821
21.20.16.4860
The Above all work with Windows 7 on Kaby Lake by modifying the igdlh64.inf file. None work with Coffee Lake
The below do not work on Kaby Lake or Coffee Lake by modifying the igdlh64.inf file. They are all missing the Windows 7 sections completely:
22.20.16.4729
22.20.16.4738
22.20.16.4758 (Provided on ASUS Prime Z370-A DVD-ROM)
22.20.16.4771
22.20.16.4815
23.20.16.4849 (ASUS Z370 Support Website)
23.20.16.4901 (Latest on Intel Drivers Website)

It is probably more than co-incidence that all the versions that DO work on KabyLake actually have the Windows 7 section, just without the KL Hardware ID's. This is where one simply adds the relevant Hardware ID for your KL CPU.

I have attempted to insert the missing Windows 7 sections (Driver ID's and device Driver Section are both absent) into post 21.20.16.4860 without success on either KL or CL. When i do that the driver installs without complaint, but fails to start on reboot. I believe wIntel have changed something to recognize Win7 on KL or CL that cripples it. The answer is to pour through every driver and replace the one that does it....above my pay-grade. The fact is that it SHOULD work because it works on KL and there is no difference in the GPU of KL and CL.

If anyone has a version between 21.20.16.4860 and 22.20.16.4729 (I am looking for the earliest version of the 22.20.16.x series) I can analyze, I would be most grateful, as I believe that is where they started tinkering to create the cripple.

 

Thanks for putting so much effort in it! Yes, somehow it should work, because we talk about the same architecture. Unfortunately I do not have yet Coffe Lake laptop to test and try different moddings and maybe i am not so good in it. But i think you are on the good track. Or would not be possible to change the CL hardware ID to KL hardware ID? Than the driver installation could happen correctly?

 

Ok follow my logic. The Intel installer looks to the Hardware DEV_X number and then looks in the igdlh64.inf file to match that up.

So for my 7700K CPU I add:
%iKBLDTGT2% = iSKLD_w7, PCI\VEN_8086&DEV_5912
We are equating the Kaby Lake driver to the Sky Lake value and it works

The value iKBLDTGT2 is "Intel(R) HD Graphics 630"

For my 8700K CPU I add:
%iCFLDTGT2% = iSKLD_w7, PCI\VEN_8086&DEV_3E92
We are equating the Coffe Lake driver to the Sky Lake value and it does NOT work.

The value iCFLDTGT2 is "Intel Coffee Lake UHD Graphics"

As an aside, how did we all figure the KL workaround out? Well Kaby Lake WAS supported in one early version: 21.20.16.4508 (08/27/2016) - after that it was stripped out. I imagine there were hasty meetings over at Mintel and a bottom-feeder-tech's head rolled into the proverbial French bucket. In that version we find the secret to Windows 7 on Kaby Lake - it was included:

;=====================================================================
; Windows 7 Install - DT Only
;=====================================================================
[IntelGfx.NTamd64.6.1]
; SKL HW
%iSKLULTGT1% = iSKLD_w7, PCI\VEN_8086&DEV_1906
%iSKLULTGT2% = iSKLD_w7, PCI\VEN_8086&DEV_1916
%iSKLULXGT2% = iSKLD_w7, PCI\VEN_8086&DEV_191E
%iSKLDTGT2% = iSKLD_w7, PCI\VEN_8086&DEV_1912
%iSKLULTGT2f% = iSKLD_w7, PCI\VEN_8086&DEV_1921
%iSKLULTGT3e% = iSKLD_w7, PCI\VEN_8086&DEV_1926
%iSKLULTGT3% = iSKLD_w7, PCI\VEN_8086&DEV_1923
%iSKLULTGT328W% = iSKLD_w7, PCI\VEN_8086&DEV_1927
%iSKLDTGT1% = iSKLD_w7, PCI\VEN_8086&DEV_1902
%iSKLHaloGT1% = iSKLD_w7, PCI\VEN_8086&DEV_190B
%iSKLHaloGT4% = iSKLD_w7, PCI\VEN_8086&DEV_193B
%iSKLHaloGT3fe% = iSKLD_w7, PCI\VEN_8086&DEV_192B
%iSKLHaloGT2% = iSKLD_w7, PCI\VEN_8086&DEV_191B
%iSKLSRVGT3e% = iSKLD_w7, PCI\VEN_8086&DEV_192D
%iSKLSRVGT4% = iSKLD_w7, PCI\VEN_8086&DEV_193A
%iSKLWSGT2% = iSKLD_w7, PCI\VEN_8086&DEV_191D
%iSKLWSGT4% = iSKLD_w7, PCI\VEN_8086&DEV_193D

%iBXTGTP% = iBXTD_w7, PCI\VEN_8086&DEV_5A84
%iBXTGTP12% = iBXTD_w7, PCI\VEN_8086&DEV_5A85
;KBL HW
%iKBLULTGT1% = iKBLD_w7, PCI\VEN_8086&DEV_5906
%iKBLULTGT2% = iKBLD_w7, PCI\VEN_8086&DEV_5916
%iKBLULTGT2F% = iKBLD_w7, PCI\VEN_8086&DEV_5921
%iKBLULTGT3% = iKBLD_w7, PCI\VEN_8086&DEV_5923
%iKBLULTGT3E15% = iKBLD_w7, PCI\VEN_8086&DEV_5926
%iKBLULTGT3E28% = iKBLD_w7, PCI\VEN_8086&DEV_5927
%iKBLULXGT2% = iKBLD_w7, PCI\VEN_8086&DEV_591E
%iKBLDTGT1% = iKBLD_w7, PCI\VEN_8086&DEV_5902
%iKBLDTGT2% = iKBLD_w7, PCI\VEN_8086&DEV_5912
%iKBLHALOGT1% = iKBLD_w7, PCI\VEN_8086&DEV_590B
%iKBLHALOGT2% = iKBLD_w7, PCI\VEN_8086&DEV_591B
%iKBLSRVGT2% = iKBLD_w7, PCI\VEN_8086&DEV_591A
%iKBLWGT2% = iKBLD_w7, PCI\VEN_8086&DEV_591D

And there is a corresponding Kaby Lake Device section in the file, which is IDENTICAL to the Sky Lake section except for two lines you will find in the SkyLake Device section:
AddReg = SKL_PANEL_DRIVER_AddSwSettings
DelReg = SKL_PANEL_DRIVER_DelSwSettings

Somewhere in all this is the very simple answer to getting it to work.....

 

There are two ways to approach this: Either take an early "WIN10 on CL" driver and attempt to add the Win7 sections...OR take the last working Win7 driver and fool the installer that you are on Kaby Lake and not Coffee Lake.

 

Here is the current list of drivers I have, along with their "native" Windows and CPU support (offered in the igdlh64.inf file without modifications). It suggests that Intel went back and forth on what they intended to support - maybe according to how many rounds of golf the two CEO's played together:

Windows 7,8 and 10 on SkyLake and Kaby Lake (the version released the day after the Microsoft CEO beat the Intel CEO on the golf course):
21.20.16.4508 (08/27/2016)
21.20.16.4526 (09/23/2016)

Windows 7,8 and 10 on SkyLake only (WTF?):
21.20.16.4821 (10/02/2017)

Windows 7, 8 on SkyLake and Windows 10 on Kaby Lake:
21.20.16.4528 (09/23/2016)
21.20.16.4534 (10/07/2016)
21.20.16.4541 (10/20/2016)
21.20.16.4542 (10/24/2016)
21.20.16.4550 (11/11/2016)
21.20.16.4551 (11/18/2016)
21.20.16.4565 (12/10/2016)
21.20.16.4664 (04/21/2017)
21.20.16.4678 (05/17/2017)
21.20.16.4860 (11/15/2017)

Windows 10 on SkyLake and Kaby Lake:
22.20.16.4691 (06/02/2017)
22.20.16.4729 (07/05/2017)
22.20.16.4771 (08/13/2017)

Windows 10 on Skylake, Kaby Lake and Coffee Lake
22.20.16.4738 (07/13/2017)
22.20.16.4785 (08/29/2017)
22.20.16.4815 (09/26/2017)
22.20.16.4849 (10/27/2017)
23.20.16.4944 (02/04/2018)

Windows 10 on Skylake, Kaby Lake, Coffee Lake and "GLK" (huh?)
23.20.16.4901 (12/18/2017)

Now the thing is when you sort this list by date you can see that they bounce around with their "native" supported platforms:
21.20.16.4508 08/27/2016 Windows 7,8 and 10 on SkyLake and Kaby Lake
21.20.16.4526 09/23/2016 Windows 7,8 and 10 on SkyLake and Kaby Lake
21.20.16.4528 09/23/2016 Windows 7, 8 on SkyLake and Windows 10 on Kaby Lake
21.20.16.4534 10/07/2016 Windows 7, 8 on SkyLake and Windows 10 on Kaby Lake
21.20.16.4541 10/20/2016 Windows 7, 8 on SkyLake and Windows 10 on Kaby Lake
21.20.16.4542 10/24/2016 Windows 7, 8 on SkyLake and Windows 10 on Kaby Lake
21.20.16.4550 11/11/2016 Windows 7, 8 on SkyLake and Windows 10 on Kaby Lake
21.20.16.4551 11/18/2016 Windows 7, 8 on SkyLake and Windows 10 on Kaby Lake
21.20.16.4565 12/10/2016 Windows 7, 8 on SkyLake and Windows 10 on Kaby Lake
21.20.16.4664 04/21/2017 Windows 7, 8 on SkyLake and Windows 10 on Kaby Lake
21.20.16.4678 05/17/2017 Windows 7, 8 on SkyLake and Windows 10 on Kaby Lake
22.20.16.4691 06/02/2017 Windows 10 on SkyLake and Kaby Lake
22.20.16.4729 07/05/2017 Windows 10 on SkyLake and Kaby Lake
22.20.16.4738 07/13/2017 Windows 10 on Skylake, Kaby Lake and Coffee Lake
22.20.16.4771 08/13/2017 Windows 10 on SkyLake and Kaby Lake
22.20.16.4785 08/29/2017 Windows 10 on Skylake, Kaby Lake and Coffee Lake
22.20.16.4815 09/26/2017 Windows 10 on Skylake, Kaby Lake and Coffee Lake
21.20.16.4821 10/02/2017 Windows 7,8 and 10 on SkyLake only
22.20.16.4849 10/27/2017 Windows 10 on Skylake, Kaby Lake and Coffee Lake
21.20.16.4860 11/15/2017 Windows 7, 8 on SkyLake and Windows 10 on Kaby Lake
23.20.16.4944 02/04/2018 Windows 10 on Skylake, Kaby Lake and Coffee Lake
23.20.16.4901 12/18/2017 Windows 10 on Skylake, Kaby Lake, Coffee Lake and "GLK"

I have 21.20.16.4860 working on Kaby Lake. They released this driver 4 months after Coffee Lake support started but gave it the "21.20" code.

EDIT: I have added a number of versions by editing this post.
An interesting version that I just found on an oem website is: 22.20.16.4691 06/02/2017 which is the earliest version I can find of the newer 22.20.16.x series that universally excludes Windows 7 and 8. What is interesting is that the igdlh64.inf file in that driver-pack still has the remnants of the Windows 7 and 8 sections - just with the Hardware ID's stripped out. It even has the Windows 7 Device section still there...although it is an older version than the 21.20.16.4860 that I have working, it IS from the newer 22 series....which is the first series that supports Coffee Lake...

Another interesting fact: Look at the drivers they released on the 23rd of Sept 2016...identical, one with Kaby Lake support for Windows 7 and the second without.

 

Yes, we should work on this two way you wrote above. I think also for a third way, but maybe more difficult or less chance; we should figure out how to install a recent (22.20 or 23.20) driver on Windows 7 for Kaby Lake. Once that figured out, it is easy to mod further for Coffe Lake.

 

Shame, shame on Intel for getting into bed with Microshaft. IMO, this is just another black eye for Intel whom continues to shoot themselves in the foot. Hmmm, two corporations that seem to be falling from grace lately. One produces a virus called Windows 10, and the other has a hole in its architecture to allow for viruses.

 

Is this 22.20.16.4691 driver supports Coffe Lake already? So maybe you just needs to fill out the missing Hardware ID's... Or it is just giving an idea to where to put the Windows 7 sections in the 22 series drivers?

 

If Intel would support with drivers the Windows 7, it would stay the most popular OS. But why Intel goes against that? Microsoft can pay off Intel?

 

No it does not natively support Coffee Lake. What I mean is that it is from the "22.x.x.x" series, that became Coffee Lake shortly after (less than, or at least, 40 days later in fact). I am almost finished pulling down many additinal oem versions from manufacturers websites. Once I have them all sorted I can start to look closer and try them one-by-one.

They both get to make more money...by combining and forcing upgrades to both the OS and hardware needed to run the latest bloated version.

Of further interest for folk out there doing Windows 7 on Kaby Lake. So I discovered that the iGPU driver v21.20.16.4508 works without any modification required. It fully supports Kaby Lake but is referred to as a "Beta" version wherever it appears (on various oem websites). I have now found the final release of that strain: v21.20.16.4526 buried in Gigabytes "Brix" section.
This supports Windows 7 on Kaby Lake natively and is the last version (maybe v21.20.16.4527 has it - but I cannot find that) before they quietly deleted the Windows 7 sections for KBL support.
Of course you can get much later versions to work but it does prove the point - Intel "developed" a supported driver for Windows 7 on Kaby Lake. And then suddenly they "unDeveloped" it on the same day - the 23rd of Sept 2016 by re-releasing the identical driver and deleting the Windows 7 sections. BUSTED INTEL!!!!!

OK if anyone can help me out with the Intel drivers between 21.20.16.4678 and 22.20.16.4738 (After the 17th of May 2017 and before the 13th of July 2017) - here lies the way to get this working. I already have 4691 and 4729. I just need the file called igdlh64.inf in the \graphics directory. Alternatively if anyone knows where I can find such versions - is there an ftp site somewhere?

 

Little help,

22.20.16.4678
22.20.16.4686 exist, but do not know yet where to download
22.20.16.4687 exist, but do not know yet where to download
22.20.16.4691
22.20.16.4695 may exist
22.20.16.4704 may exist
22.20.16.4708
21.20.16.4718
22.20.16.4718
21.20.16.4720 exist, but do not know yet where to download
21.20.16.4727
22.20.16.4727 may exist or not
22.20.16.4729 you have already
22.20.16.4734 exist, but do not know yet where to download
21.20.16.4735 exist, but do not know yet where to download
22.20.16.4735
22.20.16.4736 exist, but do not know yet where to download
22.20.16.4738

So these the drivers I could found between the area you mentioned. Looks exactly as you sad, the transition happened in these packages.

 

Micro$oft, Intel, Amd or Nvidia, doesn't matter. They all are in bed with each other. Micro$haft's last payback

 

Atom Ant, very helpful thank you - I have narrowed it down to 22.20.16.4736
This is the revision where they switched to Coffee Lake...searching....

 

Is there a working link, all the links are either dead or require membership, a torrent or magnet will do.

Thanks.

John.

 

Here it is. http://www.nomaher.com/forum/index.php?topic=3350.msg28607#msg28607
Old link expires after 4 weeks.

 

Premium Access Only, You have to pay to download

John.

 

Then try this https://uploadfiles.io/sr2et

 

I re-enabled the Intel HD Graphics on my desktop and re-tested the driver that worked before would not work now for some reason. It installed successfully, but the Intel iGPU reports code 43. So, I do not have a working Windows 7 driver to share with you for Intel Coffeelake graphics.

 

It was always suspicious, nobody sent exact proof that Coffe Lake IGP working with Windows 7. Just mentioning it is working or maybe I received a sceenshoot Win 7 installed on Coffe Lake, but nothing indicated the IGP is installed correctly.
Fortunately we got DesertSweeper working hard on it and we should support his work! He would deserve some reputation, even if he fails to figure out the trick... There is a trick certainly, since it is the same architecture than Kaby Lake, question is just how well Intel hidden the key.