Completing installation is not "endless loop", but SetupComplete.cmd phase. It takes a while, because .NET Framework 4.8 and updates are installed during this phase.
Thank you for the information - I am learning a lot here. I used the tem "endless loop" because at the first attempt to reboot (W7 reboots several time during the installation) the installation stops with a "Windows could not prepare the computer to boot into the next phase of installation. To install Windows restart the installation". I can't restart the installation since another message states: "The installation was cancelled any changes made to your computer won't be saved" and I end up having to restart the whole process. I don't have access to my laptop so I cannot tell whether if I left everything alone W7 would eventually install or not. I will have to wait for a couple of months until I finish being abroad to find out...
Today I used Integrate7 5.23, en_windows_7_ultimate_with_sp1_x64_dvd_u_677332.iso I set all options to 0 except AddDrivers=1 and CreateISO=1 Setup ran till reboot normally and after reboot I got the message "File .../msnvme.sys status 0xc0000428 Info: Windows cannot verify the digital signature for this file" I think the option I used is legitimate. In my opinion the option I used is the main option for making Windows 7 run on modern hardware. Please I need help. Thank you.
Hello, today I made a bootable Windows 7 install usb using integrate7 and rufus I enabled CSM in bios and I successfully booted into the installer However I was unable to install windows due to the no cd/dvd driver issue The NVMe and USB3 driver should be loaded properly as all my ssd and usb devices were recognized and usable I have tried unpluging and repluging the install usb, using a different port and using a usb 2.0 drive as the installer, still no luck Any idea on how to solve the issue? I am trying to install windows 7 on my 5900x x570 pc
I found a bug in your beautiful script and would like to help. I found a bug in a script option I am interested in and wish I could use it. I can make the ISO as I need it, attach a screenshot of the error and attach the Integrate7.cmd file as I used it. Unfortunately, I haven't found an option to create a log. A quality log would have helped to easily figure out the source of the error. Please reply me due to my interest in the success of the bug fixing.
Hi, I want to update all image indexes but the script does not let me when I press "A" for All Any ideas? It only lets me choose an image index.
For me - had it crash with (only) some nVME SSD - not even sure why, since works with others.. Due the fact that some still not detected - i tend to use Win10 iso + diskpart + extract..
Nothing is reverted. In the previous version Win8 NVMe was used inside boot.wim (installer) and Win7 NVMe (KB2990941) inside install.wim (the main system). In version 5.24, you have choice which driver you want inside install.wim (the main system) - Win8/backported - or - Win7/KB2990941. Inside boot.wim, there is no choice because Win7/KB2990941 simply doesn't work here, no way. So Win8/backported is the only option.
It's just a variable in script - policy key is not affected, since registry entry is: HKLM\Software\Policies\Microsoft\Windows NT\DNSClient\EnableMulticast=0
I'm guessing you used win 7 .wim that is is localized (Japanese)? Is it untouched (no prior updates integrated)? Did the updates download properly - you had some errors about loading xml from cab... Also make sure sure to use short path with no special symbols ( x:\Int7\ ) i haven't tried on localized - but works fine with original: en_windows_7_enterprise_with_sp1_x86_dvd_u_677710.iso en_windows_7_enterprise_with_sp1_x64_dvd_u_677651.iso At the very least - delete and redownload these 4 .msu: KB4474419 KB3125574 KB5022338 KB5029296 You also have some weird errors unloading registry hives - which can lead to corruption, Make sure you don't have smoething using registry at those TK_* keys - or AV is not keeping the keys locked.. !!! Use x64 Host OS to service x64 .wim
Most errors are due to crappy antiviruses (or other crappy "security" software) that lock everything. I have tested it dozens of times on clean host OSes (Win7 and Win10) without a single error anywhere. And what is more important, once installed, these modded OSes work in my company for years without single issue anywhere. So if you have tons of so called "security" software inside your host OS that block normal tools (like DISM, Reg, NSudo, etc.) from normal functioning, it is you fault. And I don't care about it at all. Sorry.