Update your Win 7 installation media

[Megahertz07]

Welcome to the Forum FastTurtle.

One thing is partition size related to type and other is file size related to how it's formatted .
MBR disks has a partition size limit of 2T. Master boot record - Wikipedia
GPT disks has a partition size limit of 9.4 ZB GUID Partition Table - Wikipedia
Fat32 has a file size limit of 4G File Allocation Table - Wikipedia

 

[FastTurtle]

7Updater-v23 Failed

Have the usb 3 drivers for Win7 from Asrock (Asrock b450m pro board) and ran 7Updater. It threw several errors involving image already mounted/open (not sure why) when I ran it first time. Seemed to complete the update/patching yet no USB 3 support in the installer.

 

[FastTurtle]

If you don't succeed the first time, try it again. Seems that somehow I screwed the script up (not sure what I did) but the 2nd run went w/o errors


Errors that DISM throws
[4108] [0x80070003] FIOEnumerateReparsePoints615): The system cannot find the path specified.
[4108] [0x80070003] CleanupDeleteUnmountedStubs607): The system cannot find the path specified.
[4108] Badly formatted drive string: I:\. This drive will not be cleaned.
[4108] Badly formatted drive string: O:\. This drive will not be cleaned.


DISM DISM Provider Store: PID=4692 TID=1132 Failed to load the provider: C:\Windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)


I'm seeing several of these in the DISM Log - Could it be due to the errors on the first run?


Have to restore the bootable image as something went badly wrong - Used up all the space on the drive

 

[FastTurtle]

After rebuilding the ISO using the install disk (needed for the WIn7 USB/DVD tool), Ran the updater again along with adding in Simplex Updates (167 of them). The USB/DVD tool decided to not copy the boot.sec to either flash drive (not a major issue) as the EFI folder is there and it should boot.

 

[FastTurtle]

This was after getting an error message stating the image wasn't fully unmounted - not sure why it's stating the image wasn't fully unmounted unless there's a script issue and yes, I've already downloaded the latest version again in case it was borked



O'kay, I'm getting this as an error message


Error: 0xc1510115

The specified image is invalid.
Unmount the image or clean up the Wim and then try again.


The second Error


Image File : G:\sources\boot.wim
Image Index : 2

Error: 0xc142011d

The specified mounted image cannot be committed back into the WIM. This occurs when an image has been through a partial unmount or when an image is still being mounted. If this image was unmounted with commit earlier, then the commit probably succeeded. Please validate that this is the case and then unmount without commit.

 

[FastTurtle]

I'm not a dev and have no idea why the script is having trouble - the only thing I want is to add the USB 3 drivers and the NVME update to the boot and install images. I'm not adding any simplex or other updates at this time due to the error

 

[SIW2]

FastTurtle

Not sure how you managed to do that.

Best clean up any mounted images. At this point the simplest way might be to use dism++ to clean up those mount points.

https://www.chuyu.me/en/index.html

 

[FastTurtle]

It's taken some effort but I now have the USB working but no NVME support though that's beginning to look to be an Motherboard and AMD issue

 

[FastTurtle]

Had to go back to the instructions on where to set the NVME Update - Might work now as it wasn't being integrated

 

[FastTurtle]

Seems that the DISM script is causing some confusion as it's trying to integrate the Drivers and Windows Updates once again - Gives the Ivalid WIM file message.




CHECKING FOR UPDATES IN UPDATES\Installx64


Deployment Image Servicing and Management tool
Version: 10.0.17763.1


Error: 0xc1510115

The specified image is invalid.
Unmount the image or clean up the Wim and then try again.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log



CHECKING FOR DRIVERS IN "DRIVERS\Installx64"


Deployment Image Servicing and Management tool
Version: 10.0.17763.1


Error: 0xc1510115

The specified image is invalid.
Unmount the image or clean up the Wim and then try again.

 

[FastTurtle]

Well the installer now sees the NVME and handles the USB 3 (Kbd/ms) but now I have an issue with it wanting a missing CD/DVD driver ? and it wont allow me to continue the installation.

 

[SIW2]

Sounds like the sources\setup files haven't been updated. Something got messed up - possibly because you didn't have empty mount folders.

 

[FastTurtle]

So the only thing I should have in the folder is the Sources and WIM files?


What your instructions state is to copy the source installation files (screen shot shows all of them) to the drive. If that's not what's needed, then I can certainly clean them up

 

[FastTurtle]

Beginning to wonder if the DVD burner issue is related to Lite Scribe, which is a feature it has. The installer is picking it up and wanting a driver for it, which is blocking the install as it insists on a driver. I'll test by unplugging it later today to see if that solves that problem. Hopefully the NVME drive is now visible so I can install Win7.

 

[Basil]

Newbie alert!! Am I right or wrong in thinking the files within UPDATES-MS-Nvme-Win7x64.zip

should be added to the 7UPDATERv24/IMPORT directory at the start of things, along with any drivers to the DRIVER directories for (in my case) 64 bit? Or should the UPDATES-MS-Nvme-Win7x64.zip contents go into the UPDATES folder? Thanks. If I have ******** it up is the UpdatePack7R2 stored somewhere to use again, or do I need to re-download via my pitiful, out in the sticks, connection? Thanks!

 

[SIW2]

Basil,

UPDATES-MS-Nvme-Win7x64.zip contents go into the UPDATES folder?

NVME updates go in the UPDATES\Bootx64 folder AND in the UPDATES\Installx64 folder.

is the UpdatePack7R2 stored somewhere to use again

Yes it will still be there. It is downloaded right next to the .cmd files.

 

[SIW2]

So the only thing I should have in the folder is the Sources and WIM files?


What your instructions state is to copy the source installation files (screen shot shows all of them) to the drive. If that's not what's needed, then I can certainly clean them up

What should happen is that boot.wim ( image 2 ) has the nvme updates integrated.

Install.wim ( whatever image you selected) has the nvme updates integrated.

The sources folder from boot.wim ( image2 ) is then extracted to the installation media folder.

That means the updated files in boot.wim sources folder match the files in installation media sources folder.

If they don't match, then setup.exe that runs from boot.wim will not recognize the installation media.

 

[Basil]

Basil,



NVME updates go in the UPDATES\Bootx64 folder AND in the UPDATES\Installx64 folder.



Yes it will still be there. It is downloaded right next to the .cmd files.

Thanks, another seemingly successfully loaded bootable USB created, a very useful tool indeed.


If I wanted to add all the current Gigabyte drivers for my MB to a USB ISO, from the Gigabyte page for this MB, how do I know what files from the Gigabyte driver pages to extract? Some directories contain just an .exe file. Some directories have zips there that contain a myriad of directories, sub directories and files within. Thanks

 

[SIW2]

Drivers need to be .inf .cat and sys to be integrated.

You can probably extract them from .exe using 7-zip or uniextract

 

[FastTurtle]

WinDef on 10 told me that v23 has a trojan - maybe why I was having so many problems with it as v24 is clean. Well that didn't work again - using win10 always throws an error when dismounting the boot.wim after adding the NVME updates - all of the USB 3 drivers go in w/o issue so I'm not sure what the issue is other then Win10 - suspect WinDef as you can't disable it AFAIK



Will run it on a Win7 system