Update your Win 7 installation media

[SIW2]

June 2019 version on first post.

 

[Paul Black]

June 2019 version on first post.

 

[Leo625]

If I may add something.

I finally was able to successfully integrate SP1 into my original Windows 7 image (Manually Slipstream SP1 Into Windows 7 Installer DVD) and one of the problems I ran into while doing this was that DISM had trouble mounting and unmounting images so searching for an answer brought this:

"DISM errors………….
None of that permissions things ever help here

try

DISM.exe /Cleanup-Wim

then delete this registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images

then delete your mount folder

If not reboot and delete it
Edited January 30, 2010 by maxXPsoft"

Once I started deleting the "Mounted Images" folder in the registry every time I used DISM I experienced no more problems. Apologies for no link to the article.

So then I used SIW2's 7Updater to add NVME and USB3 and 3.1 and during this task I also had trouble with DISM mounting and unmounting images so again I followed the above instructions and was successful integrating NVME and USB3 and 3.1 drivers into my image.

For integrating SP1 I used Win8.1 ADK and for 7Updater I chose to let 7Updater use it's version of DISM and I wasn't using a "mount" folder for this task so you can skip that just do the /Cleanup-Wim and delete the registry key. In fact, I delete the whole "Mounted Images" folder.

I hope this helps anyone having trouble using DISM. Not sure why the problem. I haven't run into this until recently.

Also, I start the 7Updater cmd file then close the folder that holds the project so that Windows has no open "handles ?" to it and close any other tasks, even browser. Plus after I delete the registry key I always reboot then proceed with using 7Updater which works great by the way!.

Thanks SIW2!

 

[Leo625]

SIW2 I do have a question.


Do you know where your DISM looks for the Windows 7 version?


Reason I ask is after integrating SP1 into my image the DISM that comes with your tool still shows the Windows 7 without SP1. When I burn the image to DVD ImgBurn recognizes the image as Windows 7 w/SP1.


I noticed that in my image's Boot Wim, the XML file still shows "Build 7600" and "Service Pack Build 16385".
The DISM you include in your tool shows "Build 7600" and "Service Pack Build 16385".


Any ideas? And could you point me to instructions as to changing the XML file in my updated image so it reflects SP1 or can I just modify the file and put it back into the boot wim?

 

[SIW2]

Do you know where your DISM looks for the Windows 7 version?

Depends whether you downloaded newer version dism when prompted.

Mostly the wim info is queried using wimlib.

after integrating SP1 into my image

How did you do that?

in my image's Boot Wim, the XML file still shows "Build 7600" and "Service Pack Build 16385".

did you integrate any updates into boot.wim?

When I burn the image to DVD ImgBurn recognizes the image as Windows 7 w/SP1

.
What is the name of the iso file?

 

[Leo625]

Hi SIW2:
I used instructions from here and it worked really well after I figured out how to follow instructions.


I just named my ISO a generic WIN7SP1 and ImgBurn liked that. Booted the DVD and on an AORUS Gaming 7 WiFi the DVD works perfectly as far as being able to use the mouse and keyboard.


I used your tool to integrate drivers you link to and also the NVME hotfixes into the image.


However, it seems no matter what I do with integration the XML file in the boot wim still says 16385 instead of indicating SP1. I think next I will try modifying the XML and see if that fixes the issue. Will report back later.



Leo625

 

[SIW2]

Hi SIW2:
I used instructions from here and it worked really well after I figured out how to follow instructions.
Leo625

The intructions you posted don't affect boot.wim. It stays as it was.

 

[Leo625]

Alright then I will have to venture out on my own here . Thanks again for 7Updater tool.

 

[Fox Modem]

Hello, SIW2!


I've found these here USB drivers that are supposed to work with Z390 motherboards.
I intend to use your updater to include those drivers in my install media, but English isn't my first language and I am a little confused.


If I put those files in the DRIVERS/Bootx64 folder, they will be automatically installed with W7?
Or should I put them in UPDATES/Bootx64?
As I also need the NVME drivers, can I put each set of files within their own folders, like DRIVERS/Bootx64/NVME and DRIVERS/Bootx64/USB?


Thanks for your amazing tool and all the help!

 

[SIW2]

Yes, I am aware of those. Currently testing them. They look very promising so far.


I suggest you put them in DRIVERS/Bootx64

As I also need the NVME drivers, can I put each set of files within their own folders, like DRIVERS/Bootx64/NVME and DRIVERS/Bootx64/USB?

Yes.

 

[Fox Modem]

Thanks again for the clarification. Amazing work!

 

[Fox Modem]

I've encountered a problem.


When running 7UPDATERv27.cmd as administrator, I get a blue prompt saying:


PLEASE SELECT THE PATH OF THE WINDOWS INSTALLATION FILES
e.g. C:\GRMCULXFRER_EN_DVD


and a message blinking quickly in a loop:


'BIN\setWimdirpath.cmd' is not recognized as an internal command


I checked the BIN directory and there's no setWimdirpath.cmd file in there.


Could you please advise?

 

[SIW2]

Do you get the browse window?



Possibly something missing from the bin folder. Maybe turn off your a/v and extract the 7updater zip folder again

I checked the BIN directory and there's no setWimdirpath.cmd file in there.

setWimdirpath.cmd is created by browsing to the installation media. It is not there beforehand.

Pecmd.exe and getwimdir.ini should be in the bin folder.

 

[Fox Modem]

Nope, I only get the blue prompt.

It asks whether I want to download the latest version of DISM, which I accepted. The download happened without problems, but after that it will just blink with that message and won't take any input.

 

[SIW2]

Possibly something missing from the bin folder. Maybe turn off your a/v and extract the 7updater zip folder again

 

[Fox Modem]

I don't use antivirus software. The machine is clean.


I downloaded and extracted v27 again, but the same issue presents itself.
I only get a blue prompt with a blinking message:


'BIN\setWimdirpath.cmd' is not recognized as a internal command


I've checked the zip package against the extracted directory, no files are missing.

 

[Fox Modem]

[SOLVED]


I was running the updater from within a couple of folders in the E:\ drive.
I moved it to the C:\ drive and now it seems to be working fine - currently downloading Simplix updates.


Thanks for the help!

 

[SIW2]

Simplix automatically includes a usb3 installer - which runs during windows installation and inserts the matching usb3 drivers. If you already included your usb drivers in install.wim, then afaik the simplix usb installer won't do anything.

 

[Fox Modem]

The cryptic hacker stuff is top notch, I'm completely mesmerized by your wisdom and thoroughly confused by the hints you're so parcimoniously dropping piecemeal.

I'm sure the breadcrumbs are showing the way, but I just can't see it yet.
I'm not lazy, I'm just a little bit out of my depth.

I don't want to waste your time or bother you in any way, but the thing is, I only have the one machine.
Once it's disassembled for the upgrade, I won't have a working computer to go online and seek help if something goes wrong and the new machine refuses to boot or don't have working USB ports. Therefore, it's important to be sure I haven't done anything stupid with my install media.

So, if you can find it in your heart to lend me a hand in more clear terms, I'd be very grateful.

Here's my situation:

Mobo is a Gigabyte Z390 Aorus Pro Wifi, which according to the manual doesn't have a PS/2 port.
CPU is the i7 9700k.

I'll advance in baby steps; once (and if) I get Win7 installed and working, I'll get the Simplix pack.

But in order to have Win7 installed and working, I'll need USB drivers to guide the Win7 setup.
I will also need working USB drivers for the Z390 chipset, which need to be installed along with Windows, so the USB ports will work AFTER Win7 is installed - Those would be the drivers provided by Canon Kong.

As you said earlier, I should put CK's drivers in the DRIVERS/Bootx64 to have them installed with Windows; yet, the instructions on the first post say:

Any drivers in bootx64 folder will be included in boot.wim. Any drivers in installx64 folder will be included in install.wim.

[...]

Nvme updates for 64 bit go in the UPDATES\Bootx64 and UPDATES\Installx64 folders.
Nvme updates for 32 bit go in the UPDATES\Bootx86 and UPDATES\Installx86 folders.

I am not sure what goes where anymore, since we have 2 bootx64 and installx64 folders:

DRIVERS\bootx64
UPDATES\bootx64
DRIVERS\installx64
UPDATES\installx64

Here are my questions. Please feel free to dispense any additional advice you might consider important.

1.Does your updater make it possible to have Canon Kong's USB drivers installed DURING Win7 setup?
2. If so, in which folder should I put the files?
3. What files do I need (and in which folder) to ensure I'll have working USB ports during the Win7 setup?
4. What files do I need (and in which folder) in order to enable NVME support, as Win7 will be installed in a M2 SSD?

Sorry for hogging your time. I'm trying my best.

Thank you, yet again!

 

[SIW2]

What files do I need (and in which folder) in order to enable NVME support, as Win7 will be installed in a M2 SSD?

1.Microsoft NVME Updates are .msu files

They need to go in both the UPDATES\Bootx64 and the UPDATES\Installx64 folders.

What files do I need (and in which folder) to ensure I'll have working USB ports during the Win7 setup?

2. Drivers are .sys, .cat and .inf files

They need to go in both the DRIVERS\Bootx64 and the DRIVERS\Installx64 folders.



I would put the ms nvme update files in both updates folders.

Put canonkings usb3/3.1drivers in both the drivers folders.

Also put the oem nvme drivers in both the drivers folders

It is possible MS nvme updates will be enough, but we can't be sure, so put the oem nvme drivers in as well. View attachment OEM_NVME_DRIVERS_x64.zip