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
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.
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] CleanupDeleteUnmountedStubs
[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
Last edited by FastTurtle; 25 May 2019 at 13:12.
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.
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.
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
@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
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
Had to go back to the instructions on where to set the NVME Update - Might work now as it wasn't being integrated
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.
Quote