Update your Win 7 installation media

[Vineet Garg]

That is the purpose of the Import folder.

If you like, you can put NetFramework installer in the Import folder like this:

Import\Windows\Setup\Scripts\NET_Framework\NDP472-KB4054530-x86-x64-AllOS-ENU.exe

and also include

Import\Windows\Setup\Scripts\SetupComplete.cmd

Setupcomplete.cmd

%windir%\Setup\Scripts\NET_Framework\NDP472-KB4054530-x86-x64-AllOS-ENU.exe /q /norestart

I might include setupcomplete.cmd and cpufix in the next version.

The drivers need to be inf cat and sys files. Dism cannot integrate drivers in exe format.

Many Thanks Sir, Sorry to get late in response, Your utility is really amazing & its getting better & better!

Thanks & Regards. ...

 

[Gipreps]

SIW2 Many thanks SIW2, I succeeded in integration, opened new frontiers, I used dism ++ to mount the image, I modified the cmd for new paths, and everything went well, even with the windows 7 drivers. Now I will work with an aio vista sp2 , so that it will be complete. God bless you.

 

[caricasvix]

UEFI Boot

Hello SIW2,

After the process complete i burnt the iso to USB using Rufus but it doesnt boot in UEFI mode, gives me an error that bottx64.efi was not found.
I noticed that the file in efi\boot dir was called bootx64 so i renamed it to bootx64.efi and it gave me a bcd boot error :

File: EFI\BOOT\BCD
Status: 0xc000000d
Info: An error occurred while attempting to read the boot configuration data


Thanks.

 

[SIW2]

Thanks.

New version 19 feb 2019 on first post.

Hello SIW2,

After the process complete i burnt the iso to USB using Rufus but it doesnt boot in UEFI mode, gives me an error that bottx64.efi was not found.
I noticed that the file in efi\boot dir was called bootx64 so i renamed it to bootx64.efi and it gave me a bcd boot error :

File: EFI\BOOT\BCD
Status: 0xc000000d
Info: An error occurred while attempting to read the boot configuration data


Thanks.

 

[benedictum]

hello guys, i don't want you to think i am lazy, but if there are already modified iso files made by you, why you don't uploaded them?????? i know that is nice to get it done by yourself, but when you don't want to spend an entire day doing things that others already made I think it is better to have a download link.



just saying ...

 

[caricasvix]

Hi,

Now i get this error :

The WimDir or INSWimpath has an extra char added (') and i can not find where, lol.

 

[SIW2]

I don't see it either.

Lines 263-267

IF %DOIE11% EQU YES (
%PACKNAM% /ie11 /WimFile=%wimdir%\sources\install.wim /Index=%INDNO%& >nul %DISM% /cleanup-wim
 ) ELSE (
 %PACKNAM% /WimFile=%wimdir%\sources\install.wim /Index=%INDNO%& >nul %DISM% /cleanup-wim
  )

Lines 321-325

IF %DOIE11% EQU YES (
%PACKNAM% /ie11 /WimFile=%wimdir%\sources\install.wim /Index=%INDNO%& >nul %DISM% /cleanup-wim
 ) ELSE (
 %PACKNAM% /WimFile=%wimdir%\sources\install.wim /Index=%INDNO%& >nul %DISM% /cleanup-wim
  )

There is a patch for the updatepack - put UpdatePatch-19.3.3.exe next to your already downloaded UpdatePack7R2-19.2.15.exe and run it. It will create UpdatePack7R2-19.3.3.exe.

Then you need to move/delete UpdatePack7R2-19.2.15.exe from that directory or the cmd file will get confused.

View attachment UpdatePatch-19.3.3.zip

 

[caricasvix]

Thanks for the reply,
still get the same error. Previous version does not give me this error.

 

[SIW2]

New version march 2019 on first post.

 

[Paul Black]

New version march 2019 on first post.

Thank you!

 

[drib]

From post 1, when I follow these instructions:
1. Copy and paste your installation media to your hard drive (OK, seems easy enough to understand)
2. Right click and Run as administrator on the the 7update.cmd (OK, did that)
...The blue cmd window that opens just freaks out, flashes wildly, scrolls in high speed, and seems to be trying to flash messages about (hard to read as it's all flashing)
1. "please select the path of the windows installation file"
2. "BIN\setwimdirpath.cmd is not a recognized internal or external command"
But it's impossible to enter any text or interact with the cmd window at all now that it's freaking out. All I can do is close it again.

...is that what happens to everyone else when they try it? lol

I'm trying to get my new NVME drive to be recognized when I try to install Windows 7 x64 on it. Of course, with every new supposed fix I discover on the internet and try, I'm the only one getting the dead end results I keep seeing.
I see some have mentioned retrieving a driver from the drive's manufacturer which can be loaded via USB during the W7x64 install process. But there is no such driver referenced on the manufacturer's website. (it's a Sabrent Rocket 250GD NVME drive "SB-ROCKET-256")

 

[SIW2]

Works fine for me:

best if you don't have spaces in the path

 

[drib]

The thread topic fix didn't work for me, so I used free MSI Win7 Smart Tool, which was specifically made to effortlessly integrate NVME drivers into W7 installation media. It worked!
...It also supposedly can (I didn't try this) integrate USB drivers for the new AMD CPU's that normally force you to install Windows 7 with no USB support.

 

[SIW2]

Yes, I am aware of it. This tool can do much more. It is really intended to create updated installation media.

 

[drib]

Yes, I am aware of it. This tool can do much more. It is really intended to create updated installation media.

OK, NOW I'm confused.
I know this whole thread is specifically about updating installation media, because it's in the title. I also know that the MSI Win7 Smart Tool I mentioned was specifically created to update installation media. So when you say "this tool" and "is really intended to create updated installation media" I can't know for sure which tool you're talking about. I assume you're talking about the thread topic tool, but who knows.



In the end, my fix didn't really work either. The NVME drive was finally recognized with my updated installation media (created by MSI Win7 Smart Tool) during my Windows 7x64 install attempt. Problem was, it stopped right there and gave a fun new warning message about: "this drive might not be able to boot" so it would once again not allow me proceed with OS installation to my NVME drive. The warning said to make sure it's set to "AHCI" in the bios ("RAID" was my only other choice) which is definitely already is... Still, I got their tool to do stuff instead of just freaking out, so that was nice.

 

[SIW2]

Most people use 7Updater to integrate the 200 or so windows updates into their installation media. 7updater was originally intended to use Simplix update pack.

However, the user can also answer N to the Download Updates question and therefore not use Simplix. 7updater will then continue and only integrate updates and drivers that the user has placed in the relevant folders. See first and second post of this thread.

Other advantages are that it updates boot.wim and winre.wim as well as install.wim. It can also update either an individual image or all images.

 

[drib]

I still can't make it past step 2.
When right click and run 7UPDATEv21.cmd as administrator, all heck breaks loose.
"3. Browse to the folder containing your win 7 installation media" is impossible, and a mere pipe dream.

I could do a Rubik's cube in under a minute when I was 13. Taught myself to play multiple instruments.

I seem to be able to read
'BIN\setWindirpath.cmd' is not recognized as an internal or external command, operable program, or batch file
flashing/scrolling at hyper-speed, filling the entire cmd window.
When I just right-click on "7UPDATEv21.cmd" and open as administrator [i.e. step 2 of the instructions] it sets off a funhouse of unstoppable action in the cmd window. All I can do is close the window when I've had my fill of watching it scroll wildly.

 

[SIW2]

Not sure what you are doing wrong.

1) First, it is always a good idea to use short paths without spaces.
Extract the zip file directly to the root of the drive, so you should have C:\7UPDATEv21 folder
Also make sure the ISO contents have been extracted to a short path without spaces. E.G. C:\EXTRACTED-ISO

2) Check the contents of the C:\7UPDATEv21\BIN folder.
It should contain the following: ( the two arrowed files are used for that browse function)

 

[SIW2]

 

[drib]

I finally got past the wackiness with your added instructions, thanks!

Now the resulting installation files are too massive to put on a fat32 USB stick or a DVD. So I'll now assume the installations created with this method cannot be UEFI-install capable. I tried some methods to split it, and tried a fix (Rufus) that claimed NTFS file system could work instead of FAT32 USB. Nothing worked for me. Thanks for all your help getting your extremely clever tool working for me, it clearly did run as intended in the end. It was like a fantastic Rube Goldberg machine the way it took off and did things on its own.