Windows 7 installation help for Intel Skylake and Kaby Lake laptops

UEFI if I'm not mistaken requires GPT partition. If you install in Legacy mode then windows installer creates MBR partitions. I doubt that simple swaping HDD from old to new laptop will work.

 

What about partition manager programs that can convert MBR to GPT though?

Or possibly trying to attempt a "boot repair" on the new machine it is being swapped into since the system would already be setup and contain the additional necessary drivers?

 

The question is why do you want to go this route?
Windows7 x64 supports UEFI. (32bit does not)

Besides windows installer creates more partitions in UEFI/GPT mode

Legacy mode


UEFI mode

 

Deleted the proposed folders and now it stops at disk.sys.

I've just tried installing it on nvme disk but all I get after the installation is a boot error message.

Any ideas?

 

There is something odd with your laptop because another guy from my original thread ( http://forum.pclab.pl/topic/1189112...hreadripper/page__view__findpost__p__14921445 ) succesfuly installed win7 on Asus s15 s510UN with i5 8250u on board.
He didn't have to delete anything from driver folder neither.

I'm starting to think that there something in BIOS/UEFI what prevents storage drivers to load on your machine.

This looks similar to your issue
https://answers.microsoft.com/en-us...e/63b99de9-5e93-4c99-a411-35bcf6a855bd?auth=1

 

Sorry for the late reply...

Multiple partitions don't bother me. I usually create 3+ partitions myself anyways to organize my stuff better. Idk the specifics so well of BIOS vs UEFI when dealing with Win 7. It just seems like BIOS mode has always been more solid and trustworthy for me than UEFI in the little bit of experience I've had with UEFI compared to BIOS.

 

UEFI is required if you plan to install OS on NVMe SSD.

 

Good to know. I am new to the SSD game. My old machine with hybrid BIOS/UEFI never got the privilege of an SSD drive. My new machine has an NVMe and SATA SSD, but was also factory spec'd with the NVMe so they at least intended for such scenarios to be encountered straight out of the box.

 

It does not required and i don't reccommend (at least on Dell) by my experience. I have Win 7 on Samsung 960 NVMe SSD and it was installed in legacy, still in legacy.

I cannot read that topic, can you provide any info if for i5-8250U was possible to install modded IGP driver?

Dantei:
Too much trouble with that laptop. Buy Dell, it is better brand anyway than Acer...

 

NVMe SSD in PCI adapter won't boot in non-UEFI mode. However you can use this trick to boot from NVMe ssd on old PC ( Pentium 4 !!! )
http://forum.pclab.pl/topic/1214961...ws-7-x64-SP1/page__p__14760867&#entry14760867

Yes! Modded IGPU driver is working fine. However by default IGPU in Device Manager has weird name but this can be easily fixed using this method
https://www.eightforums.com/customization/15321-tutorial-how-change-device-names-device-manager.html
Regarding IGPU driver biostar has modded and signed drivers
http://download.biostar.com.tw/upload/Driver/Chipset/Intel/VGA/KBLake/WIN7Beta/win64_154514.4590.zip

One thing we couldn't figure out was driver for touchpad

 

Nice informations from you Atak_Snajpera. I was asking, because i worry if i am going to have IGP driver for Coffe Lake IGP or not... But that is good sign!
Try touchpad driver from the one older model of that Asus laptop. Like I'm using the Inspiron 7559 touchpad driver for my Inspiron 5577.

 

BTW i5-8250U is still Kaby Lake
http://www.cpu-world.com/CPUs/Core_i5/Intel-Core i5 i5-8250U.html

Nevertheless IGPU in Coffe Lake is basically the same as in Kaby Lake so after adding new entry in .inf file moded driver should also work on newer PCs.

 

Damn, I thought that is Coffe Lake. Why did they do that? Good i didn't purchase for testings.
I read that too, but if the hardware ID entirely missing from the inf file that we used to mod? Intel for these new CPUs now making drivers which only installs for Win10.

 

I had a multiboot system on my old laptop that used GRUB2 boot manager to launch all the OS's (Windows 7 x64 + Windows 7 x86 + multiple Linux distros). It looks like that could be an option with GPT/UEFI and maybe a chainload if necessary? I think my old system was still on MBR/Legacy though, so my experience was much simpler at the time.

I am getting ready to attempt my Windows 7 install on my Dell 7577 hopefully tomorrow. I gathered all the necessary files tonight while reading through your guide so I am (hopefully) thoroughly prepared for any mishaps.

If I get Win7 up and running I hope installing Ubuntu won't wreck my setup. I hope to use GRUB2 as my bootloader because I enjoyed it so much with my last multiboot setup.

USEFUL LINKS:

https://askubuntu.com/questions/808156/triple-boot-windows-10-ubuntu-16-04-os-x-10-11

 

If I left out the /ie11 flag in the integration step for the Simplix pack do I need to repeat the entire process over again? Or is there a way I can add just the necessary ie11 stuff on top of my already-integrated install.wim file? Do we even need the ie11 trash? I NEVER use internet explorer and always go straight to chrome.

 

I've updated my tool (Windows 7 image updater) with some additional drivers
Full list of drivers in package

Code:

Alcor Micro Smart Card Reader
Alcor Micro USB Card Reader
Alpine Ridge USB
AMD Chipset
AMD GPU
Asmedia USB
Atheros Bluetooth
Atheros Wireless
Broadcom Wireless
Genesys Card Reader
Intel AHCI
Intel Camera
Intel Chipset
Intel DPTF
Intel GPU
Intel IO
Intel LAN
Intel MEI
Intel NVMe
Intel USB
Intel Wireless
OCZ Toshiba NVMe
Plextor NVMe
Realtek Audio
Realtek Bluetooth
Realtek Camera
Realtek Card Reader
Realtek LAN
Realtek Wireless
Samsung NVMe

 

Hello, I was on Holiday in the last two weeks. Did you managed the Win 7 installation? When you do the Simplix pack integration, there is a different command to skip the ie11, but on older ie is anyway there, so i think it is good to update to the newest.

 

So I understand the entire process pretty well now and managed to package what was supposed to be a modified Win7Ultimate-onlyx64_ISO. I included all the drivers and then some. However I've been trading off between having the missing drivers preventing install altogether at the very beginning and the drivers being in place but running into a different error part way through the installation process. Forgot what it said exactly.

The entire image modifying and building process is very time consuming on my old laptop especially. I may just try making the changes using DISM commands directly since using some of the tools in sequence seems to screw up things. I also had Rufus fail to create a bootable disk on what should have been the fully patched final ISO ready to go.

I've been using the /ie11 and /Optimize flags and setting a custom temp directory when applying Simplix's pack. Using NTLite and/or Gigabytes WIU Tool to add USB drivers (which I thought Simplix's pack did). Had luck with Gigabytes newest version. I'm currently browsing my Windows 10 drivers so I can try to extract a few in particular to try adding to the image build.

Still have more workflows to try, but herb is recreational now and school hasn't started again yet so...

 

This won't work because .inf files may not have sections for NT6.1. Windows 7 will basically ignore those drivers.

 

So what actually all these means? Like I won't even need to insatll IGP or chipset driver on my freshly installed windows 7?
Have you seen anyone yet running Windows 7 on Coffe Lake?

 

Why do you use rufus? Try Windows 7 USB DVD Download Tool...

 

Yes, I have

 

I do. It works better for Sky Lake, Kaby Lake or Coffee Lake than Windows 10 does. It is a blatant lie and a scam that Micro$loth states that Windows 10 is required for support and full functionality of these processors. They are bald-faced liars and will say or do anything to try to force people into adopting that piece of trash OS.

Better yet, use the ASUS EZ Installer tool and it automatically adds USB 3, USB 3.1 and NVMe support. You can use it to create a USB installer from DVD, ISO, or update an existing USB installer with support for modern tech. Just a few clicks and it is done. It is not specific to ASUS and adds no ASUS branding. You can use it to install Windows 7 on anything, any brand, regardless what the lying sacks of feces from Redmond want us to believe.

 

Even AMD was spreading lies to promote windows 10!

https://www.pcworld.com/article/316...-no-official-ryzen-drivers-for-windows-7.html

And now take a look here!

http://support.amd.com/en-us/download/chipset?os=Windows 7 - 64

Ps. What is hardware id for CoffeLake igpu? (UHD 630)

 

I guess Micro$hit ask manufacturers to not support Windows 7 with drivers. However AMD is a smaller company and for them matters that plus sales, what Windows 7 support can generate.
For next I will not be suprised if Nvidia also drop support for Volta.

Mr. Fox:
Good to see a screenshot finally from someone, who running Windows 7 on Coffe Lake. Did you managed to install IGP driver or you have dedicated GPU and you use that all time?

 

Here ya go

 

is there anyone encounter bluescreen? the bios is not acpi compliant when installing windows 7? on kaby lake?

i use HP Omen 15

 

Is there a reliable source for a Windows 7 ISO that contains the most current updates? The places I've come across in a cursory search look really sketchy.

 

It is in the guide how to slipstream the simplix pack, so you get the most recent iso. Very simple.

 

Alternatively you can use my app
https://forum.videohelp.com/threads...SkyLake-KabyLake-CoffeLake-Ryzen-Threadripper

 

That's an awesome little utility. I had a W7 Ultimate ISO on my NAS drive and was able to use that with your program, along with the Windows 7 USB media creation tool to get a fully functional boot disk. The entire process, including USB creation, took about an hour applying your updates only to the Ultimate version and using a Crucial MX 300 SSD. For S&G I tried it on my Kaby Lake laptop, and it worked flawlessly. The only drivers needed, aside from peripherals, were for the Killer Ethernet controller, Intel MEI, and GPU. It even activated fine with an old key I had.

I haven't used W7 in ages, and getting back in tune with it, after having used Windows 8 and 10 since their respective launches, made me realize what a phenomenal operating system it was. Yes, at its most fundamental level, the cores of Windows 8 and 10 have advantages, but from a style and usability standpoint, I don't think we will ever see something like W7 from Microsoft ever again.

 

If you really want to make it seamless, you could inject the .INF driver files - https://www.killernetworking.com/driver-downloads/item/killer-drivers-inf - into the installation media's driver store, and then it should have Internet during install.

-- Anthony with Killer Networking
*-*-*Check out this review on the Killer Wireless 1535!*-*-*

 

It's strange because the Killer 1535 Wi-Fi works out of the box with that program. It's the Ethernet that wasn't detected. I would be installing the control center package anyway, so not having the Ethernet driver immediately available isn't a big deal.

 

I havent been able to use this tool, as it errors for some reason during the last phase of driver installs. I would love to be able to use it to create a completely updated ISO. I am using an original, clean ISO of Windows 7 Sp 1 also. Maybe someone could shed some light for me.

 

Yes, I got the iGPU driver installed fine. Not because I wanted to, but because I bricked the 1080 Ti playing with a non-standard vBIOS and needed to use it for a bit while I corrected that issue. As soon as that was fixed, I disabled the iGPU again. If memory serves me correctly, I got the W7 driver from ASUS on my mobo support page, but I'm not certain. It was that or one that I found on Stations Drivers web site. I saved them both in case I ever need to use it again.

 

What purpose would an IGP serve on a desktop? none.

 

Flashing a bricked discrete GPU. Or, being able to use the desktop temporarily while you are replacing or modding the discrete GPU. Other than that, pretty much nada. Intel iGFX es mierda. My personal preference would be that all of the K and X CPUs not even include an integrated graphics chip. The HEDT processors do not have it. Just a waste of silicon when you can use the space for something better.

 

Or use another card I figured thats why you disabled it anyway/

 

Did you buy another 1080 GTX card?

 

I have a couple cards to use if I bricked my 1080. But yes, I have a 1080ti coming.

 

You should provide some information for people at MyDigitalLife.info as they specialize in all version of Windows. Your help would be a great asset.

 

Very nice. Thank you for sharing. Hope you do well with promoting it.

This is a really good idea. MDL is a great resource. Without some of the resources available there, things would be a whole lot worse than they are in the technology realm.

 

I agree Mr.Fox, without MDL I would be on Linux by now

 

I'm already on Linux. Hahaa.
I'm using Couple of Dark side Win 10 from MDL forums, which are now on Light side thanks to MSFT.
These days Linux is comparable to Windows 10 and I dare say its faster than FCU. Only issue is some very good apps like HWINFO,TS, banking apps, money mgmt apps etc aren't available or better than Windows counterparts.
On Older laptops with HDD, I use Linux 80% of the time and Windows 10 20% to fix NTFS/FAT32 disk errors, Word,excel and powerpoint.
With Wine 2.x, windows binaries are loaded faster than 1.6.x versions and I feel Wine can replace Windows 10.

 

I think there is a Linux version of AIDA64, but otherwise all of my overclocking tools, 3DMark, 3DMark 11, 3DMark Vantage, 3DMark 06, 3DMark 05, Cinebench, wPrime, most of the other benchmarks and the vast majority of the 250+ games in my Steam, Origin, Uplay and Origin libraries do no function at all, or function poorly, under Linux. The support for Linux benchmarks on HWBOT.org is dismal. Heck, even NVIDIA Control Panel has limited functionality in Linux. SLI support is marginal. Hardware configuration and monitoring options are limited and/or cumbersome, and what few there are have been mostly antiquated and unaesthetic, like something I might have used back in the days of Windows 95 or DOS. I think the underlying problem is the majority of the key players involved with Linux development have little or nothing in common with guys like me.

The way my wife and our parents use a computer (web browsing and email 99.9% of the time) is the perfect scenario for replacing Windows with Linux. I do not believe it will ever be capable of replacing Windows for me unless I reduce my use of a computer to the same point. As things continue to get dumbed down on the hardware side of computing, reducing my use of a computer to match their limitations is certainly within the realm of possibility. Linux runs really great on anemic, inexpensive hardware and the OS UI looks very nice as well.

 

Perfectly agree with you. I really need MSO, VS, gaming etc.. on Windows which Linux doesn't even have an alternative. So, I use both of them.

 

1) make sure that you have enough free space on system partition for temp files
2) update you host OS first . Outdated DISM may fail with some newer drivers!

 

I have 400gb of free space on my system partition, and Windows is updated to January of 2018 via Simplix pack. I will try again, and show you what happens. Its the first phase of installing drivers on the Install.wim. On this ISO en_windows_7_ultimate_with_sp1_x64_dvd_u_677332.iso


Here is where it starts to error out. I love this tool you made, but I dont know what is going on here.


----------------[ install.wim -> Windows 7 ULTIMATE ]----------------
[2018-01-30 06:10:53]
[2018-01-30 06:10:53] Deployment Image Servicing and Management tool
[2018-01-30 06:10:53] Version: 6.1.7600.16385
[2018-01-30 06:10:53]
[2018-01-30 06:10:58] Mounting image
[2018-01-30 06:11:27] The operation completed successfully.

[2018-01-30 06:11:27]
[2018-01-30 06:11:27] Deployment Image Servicing and Management tool
[2018-01-30 06:11:27] Version: 6.1.7600.16385
[2018-01-30 06:11:27]
[2018-01-30 06:11:39] Image Version: 6.1.7600.16385
[2018-01-30 06:11:39]
[2018-01-30 06:11:42] Searching for driver packages to install...
[2018-01-30 06:11:47] Found 163 driver package(s) to install.
[2018-01-30 06:11:47] Installing 1 of 163 - D:\Microsoft\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 06:11:47] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:47] Installing 2 of 163 - D:\Microsoft\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 06:11:47] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:47] Installing 3 of 163 - D:\Microsoft\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 06:11:47] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:47] Installing 4 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\Alpine Ridge USB\USBHub\ausb3hub.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:47] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:47] Installing 5 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\AMDPSP\W764A\amdpsp.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:47] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:47] Installing 6 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\Bolton\RAID_CFG\W764A\rccfg.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:47] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:47] Installing 7 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\Bolton\RAID_Driver\W764A\rcraid.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:47] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:47] Installing 8 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\Bolton\USB30\amdhub\W764A\amdhub30.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:47] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:47] Installing 9 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\Bolton\USB30\amdxhc\W764A\amdxhc.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:47] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:47] Installing 10 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\Errata\W764A\AMDeFix.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:47] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:47] Installing 11 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\Filter\IOV\W764A\AmdIOV.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:47] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:47] Installing 12 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\GPIO\W764A\amdgpio2.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:47] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:47] Installing 13 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\hseries\AHCI\W764A\amd_sata.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:47] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:48] Installing 14 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\hseries\CIR\W764A\AMDCIR.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:48] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:48] Installing 15 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\hseries\MINI_IDE\W764A\amdhdc.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:48] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:48] Installing 16 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\hseries\RAID\W764A\ahcix64s.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:48] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:48] Installing 17 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\hseries\USB30\amdhub\W764A\amdhub30.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:48] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:48] Installing 18 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\hseries\USB30\amdxhc\W764A\amdxhc.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:48] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:48] Installing 19 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\hseries\UsbFilter\W764A\USBFilter.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:48] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:48] Installing 20 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\I2C\W764A\amdi2c.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:48] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:48] Installing 21 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\PCI_INF\W764A\AMDPCIDev.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:48] For more information, check for log files in the <windir>\inf folder of the target image.
[2018-01-30 06:11:48] Installing 22 of 163 - D:\Microsoft\Windows_7_Image_Updater\Windows7\Drivers\x64\AMD Chipset\SBDrv\RAID_BR\RAID_bottom\W764A\rcbottom.inf: Error - An error occurred. The driver package could not be installed.
[2018-01-30 06:11:48] For more information, check for log files in the <windir>\inf folder of the target image.

 

Show me file dates in this folder

 

ok