Install Errors and "It's Not Possible" Debunked? - Need Suggestions!

New2This

New Member
Windows 7 Ultimate SP1 On 7G HP Pavilion Laptop - Need Suggestions/Thoughts/etc!

Using NTLITE, my goal is to install Windows 7 Ultimate SP1 onto an HP Pavilion Laptop! Laptop Specs are;

Product Name: HP Pavilion Laptop 15-cs3147tx
Processor Name: Intel (R) Core (TM) i7-1065G7 [email protected]
If the need be, I can provide other specs!
-------------------------------------------------------------------------------

I have been spending almost 10 days trying to put a clean Windows 7 Ultimate SP1 image onto a USB, and plugging it in to the HP, and then getting the usual errors:
"Things not recognized"
"Bootsect.exe errros"
"Black Screen"
"Windows Startup Screen Freezing"

I already have updated the BIOS through HP's website.

I have the BIOS set to "Secure Boot disabled", Legacy enabled" and the UEFI and Legacy/CFM Boot order for USB/CD/DVD priority!

Everything I tried met with failure, and I have gone through over a hundred hours worth of watching YT videos and reading forums and articles on this Great Mystery!

Then, on a lark, yesterday I used Rufus, the Gigabyte USB Installation Tool (GUIT) to mount a clean Windows 10 Home ISO onto a random USB, using a USB 2.0 port, and plugged the installer USB into the HP laptop, and within 12 seconds of turning it on, I was looking at the beautiful installation screen... to install Windows 10 onto Windows 10!!!

So, my present thought is; there is only one problem here, and it isn't any of the following: that my USB sticks are faulty or the wrong brand or capacity, or my USB ports, or the tools I'd been using, or anything else I had been following, including talk of different motherboards, GPT/MBR Partitions, Ryzen, AMD, Intel, Kaby Lake, Sky Lake, makes and models, 7th, 8th or 9th generation processors!

So... WHAT... on that Windows 10 Home ISO image... makes the HP Laptop accept the USB Install within 12 seconds?

All I used was Rufus, the Gigabyte USB Installation Tool (GUIT) and the Windows 10 ISO, a USB 2.0 port and a beat up old NTFS-formatted USB I had laying around!

If anyone experiencing this can put any clean Win10 image on a USB and try this on their installed-Win10 OS, and go right into the Install Screen without a problem, then it must be the image, and not anything else, right?

And my question is, "What items on the Windows 10 ISO do I need to extract and incorporate into the Windows 7 ISO to get the same results?"

NTLite can do it. NTLite is the Tool, and I am the Mechanic, and the Win10 and Win7 images are the two vehicles, but I need suggestions on what I need to remove from Win10 and place into Win7 to get it accepted by the Indy500 (the new gen processors)!

I suspect that I have to deal with the Windows 7 boot.wim and install.wim/esd files, and that logic dictates I cannibalize stuff from the Windows 10 boot.wim and install.wim/esd files and place them into their related Windows 7 files... but which files need to be brought over!

Also, logic dictates I need to transfer a lot of drivers into the Windows 7 image to have basic functionality to do post installs of other drivers.

I will figure this out, but the main intention of my post is that if everything I had been doing is successful on a Win10 ISO image, then all of my failures were because I was focusing on the wrong troubleshooting areas, and not the ISO images themselves!

If the technique works with a Win10 image, on any Windows OS, and any i7/8/9 Processor, then I am concluding that any Win7 image just needs to be slip streamed with the things from the Win10 image, and the install should provide excellent results!

I am new to this, so I welcome any suggestions and starting points to focus on!

My next step is to do a full comparison of the contents of the boot.wim and install.wim files for both images, and use NTLite to slipstream and test my operations on the HP laptop!

I welcome any feed back and I apologize if my post is lengthy, or out of the terms of use for this forum! It's simply that I have no hair remaining on my head, and this recent discovery really has me excited! ;)

Some people like classic Chevy and Classic Win7. They should not be forced to run modern cars and modern Win10, full of bloat and nosy "telemetry", when the classics run better and cleaner! Just my view, is all!

Anyway, thanks for this!
 
Last edited:
You're going to have a difficult time:

1) Tenth generation Intel cpu drivers do not support Windows 7.
2) Windows 7 doesn't natively support USB 3.1 (your computer's spec sheet says your laptop only has usb 3.1 ports)
3) You need to include two hotfix updates to support your NVME drive -- updates that Microsoft no longer publicly offers.

You may be able to find modified drivers to address all of those issues, but I'm not sure.
 
I have read months ago that starting from 8th gen Intel core, Win 7 wouldn't be supported by Intel but I think Clanger knows more about that.

You can have a boot.wim 10 to install from a .ESD Win 7 image. But don't know about installing 7 on lates Intel CPU.

Understood! Thank you for the link! I will read it today!

And so, what I would conjecture is that were someone to take a clean image of a Win10 on a USB, and insert the usb into an 8th or 9th gen intel core device, and were able to boot right into the install screen, then doesn't it stand that it is the image contents which make it possible, and not anything else?

What I am suspecting is that once I discover which components in the Win10 image are needed to slip-stream into the Win7 image, then it shouldn't matter, right?

Respectfully, I suspect that we are so busy trying to install Win7 on Win10 systems and motherboards, that we first do not check to see if we can install a Win10 into a Win10 system and at least boot right into the installation screen! Then... at least we know that the Win10 image holds the "Keys" that we need to put into the Win7 image. Does that make sense?

I suspect the solution involves items in the boot.wim / install.wim, and certain drivers from the Win10 image!

Good post! Any more thoughts?
 
You are presuming that what works on Windows 10 will also work on Windows 7. Especially with drivers, that is not often the case.

Like Kasual mentioned, you can usually use a Windows 10 boot.wim to support installation of a Windows 7 install.wim, but you still need that install.wim to have all of the correct supporting drivers.
 
You're going to have a difficult time:

1) Tenth generation Intel cpu drivers do not support Windows 7.
2) Windows 7 doesn't natively support USB 3.1 (your computer's spec sheet says your laptop only has usb 3.1 ports)
3) You need to include two hotfix updates to support your NVME drive -- updates that Microsoft no longer publicly offers.

You may be able to find modified drivers to address all of those issues, but I'm not sure.

tharri, thank you! I did not know that!

I did a quick search and found good 'intel' (here, here and here) where I can obtain those items and set them aside in the event they are required. + I will research more on this!

Also... I believe I heard that even if excessive drivers and updates/patches are slip-streamed into an image, and are not required, that the "install" process just 'ignores' them... so it must be possible to create a universal USB installer in anticipation of the newer processors, or at least have several ISO image "versions" set aside in the event of, yes?

I sense that my limited knowledge of the lexicon and acronyms will lead me astray in my thoughts and expressions, so I really appreciate any guidance and "nudging" as I learn how to overcome "their" efforts to put my beloved Windows 7 out to pasture with their newer tech! It's almost as if they are wasting more time to obstruct old, reliable things whilst cranking out newer things which make the user vulnerable to them, and not instead to be able to be private and innocuous!

Everyone who posts to me is providing information I need to study, so... this is good!

Thank you!
 
You are presuming that what works on Windows 10 will also work on Windows 7. Especially with drivers, that is not often the case.

Like Kasual mentioned, you can usually use a Windows 10 boot.wim to support installation of a Windows 7 install.wim, but you still need that install.wim to have all of the correct supporting drivers.

And so, what if I have drivers for both in those files?

Doesn't the respective system automatically search for what it needs, and overlooks what it does not need, when being triggered by the process?
 
There's no harm in trying, but do you think that if you just add a *lot* of drivers that your system will automatically choose the correct ones without any problems? Because you will almost certainly have problems with driver conflicts.
 
There's no harm in trying, but do you think that if you just add a *lot* of drivers that your system will automatically choose the correct ones without any problems? Because you will almost certainly have problems with driver conflicts.

An excellent question! And not a lot of drivers or any driver, but only OS specific drivers!

So... what I intend to do is take my targeted system (in this case the HP Laptop) and get a full list from the its OS' 'System Information', as well as a list from Speccy. Installing NTLite on that system and firing it up will also give me an accurate inventory of its innards, which I will copy down!

As the HP Laptop will be my target, only that which is incorporated into it will dictate what I need to research and obtain in order to inject the components into the Win7 image... including any KB patches, etc. which you kindly pointed out prior.

Do I sound sensible, or does my conjecture make sense?

Thank you for querying me! Questions contain information, which I did not know about!
 
Last edited:
I have read months ago that starting from 8th gen Intel core, Win 7 wouldn't be supported by Intel but I think Clanger knows more about that.

You can have a boot.wim 10 to install from a .ESD Win 7 image. But don't know about installing 7 on lates Intel CPU.
It's not boot.wim from 10, only setup engine, boot.wim will remain original from Windows 7, only setup folder inside is used from 10.

For installing Windows 7 in 2021 I'm working for more than year on project, that can help build AIO with 36v1 in any language, this means all 36 languages are supported to build single language ESD DVD / USB with all latest updates (10 - 2020 for now) and also with DriverPacks integrated from https://drp.su/en/info/driverpack-offline. Masstorage, USB, Chipset, LAN / Wlan, Monitor drivers will be integrated by default. And 6 ISOs will be gerated during building process. So universal Windows 7 image is possible, also with drivers folder on DVD / USB that will beapplied into installed image before first reboot to easy mantain GPU / Sound and other specific drivers

This project will be posted soon. A lots of testing still remaining :)
 
I have read months ago that starting from 8th gen Intel core, Win 7 wouldn't be supported by Intel but I think Clanger knows more about that.

Here. OEMs are locking out certain os's, that could be OPs problem. if you are locked down to 10 then you are FoL installing 7.
 
Last edited:
George King if you need anything driver related from me then be patient because i will have to refresh my memory, pm me with your requirements. i have installed 7 x64 on B365 and H310C(R2.0) - w7 offficially supported. there are a few usb3 drivers about. 1 from win-raid gives problems if you slipstream it but you can update to it from Device Manager later and its stable.

i dont build all hardware images, i only add drivers as and where needed.
 
Last edited:
its an MS driver then, from 8 or 8.1? ive put it on my download page as a place holder so i dont lose it. Thank you George :)
 
It's not boot.wim from 10, only setup engine, boot.wim will remain original from Windows 7, only setup folder inside is used from 10.

For installing Windows 7 in 2021 I'm working for more than year on project, that can help build AIO with 36v1 in any language, this means all 36 languages are supported to build single language ESD DVD / USB with all latest updates (10 - 2020 for now) and also with DriverPacks integrated from https://drp.su/en/info/driverpack-offline. Masstorage, USB, Chipset, LAN / Wlan, Monitor drivers will be integrated by default. And 6 ISOs will be gerated during building process. So universal Windows 7 image is possible, also with drivers folder on DVD / USB that will beapplied into installed image before first reboot to easy mantain GPU / Sound and other specific drivers

This project will be posted soon. A lots of testing still remaining :)

Forgive me, but I am remiss if I do not laud you for your good intentions and endeavors! Well said, and well done! Yours is that which inspires the weary and downtrodden! Kudos, mate! ;)
 
I love the banter!

Isn't it curious that we have joined together as a collective, to thwart "their" efforts to coerce us into "their" corrals?

The ingenuity and stamina of my brothers simply amazes me... that no matter how much "they" endeavor to "nudge" us into "their" "society"... that we resist and scratch and bite and struggle until the brutal, bitter end!

It was just a thought, but I thought to myself... why not simply purchase now... all the mother boards and items one needs to have an OS (ancient style) for the next 25 years... because the average item has a lifetime of about 5 years!

No!... "they" are going full out to eradicate what we once had, and to make it so we are literally married to "their" versions of what they think we need, instead of granting "us" that greatest of freedoms... "Choice"!

Hang in there, all! We are a dying breed!
 
Back
Top