siw2,
so, I need to format in NTFS and then use the media creation tool to download win 10 setup files and then insert the .wim file, correct?
That did not work, because MS is converting my usb drive back to fat32
I will need to covert my .wim back to .esd.
Will try that later
Last edited by Sven1458; 14 Feb 2021 at 23:31.
@Sven1458
As already written, Fat32 is limited to files with a maximum of 4GB.
To work around the problem, you can use the following tutorials from @Kari:
DISM - Split install.wim file
or
You are being redirected...
By the way, Rufus also uses the same trick from the Winguru website. But Rufus uses a different boot loader for Uefi which makes it necessary to deactivate Secure Boot.
Friendly greetings
Sorry for any mistakes. English is not my native language.
Tekkie,
Dein Englisch ist wunderbar. keine probleme.
I did managed to convert the .wim file back to .esd and then was able to reinsert it to my usb drive. i then installed windows and all is working fine. thanks to Kari. it is a great tutorial
Sven
I usually do direct servicing to offline Windows (add drivers for each different PC) which have been sysprep in the VM using Windows PE (customize PE Bakery), then capture it to the ffu image.
I feel quite comfortable with the flexibility of this method. But is it as safe as servicing to mounted offline image?
I didn't see an answer to my question, so hoping I didn't miss it...
I am a tech for a small school department, and I often use DISM to create images of our computers in the District, we create an image so we can always have the opportunity to reimage when needed.
So we just got a shipment of inexpensive HP laptops with SSD drives, and right off the bat the Windows 10 install (from USB) couldn't find the drivers for the SSD. I found the drivers and was able to install. So now that the OS and all needed programs are installed, I am trying to boot from a USB to run DISM to create an image, which is what I've done a million times.
The problem I'm having is that when I do DISKPART, then LIST VOLUME, I don't see the SSD drive. I've tried the steps in this post to inject the drivers into the install.wim (and even boot.wim), but I still can't see the SSD. I usually run DISM and /Capture-Image to create the WIM file, but if I can't see the drive with the data on it, I can't create the image.
Did I miss something?? Is there anything else I can try?
Sometimes in winpe mode a drive is not assigned a drive letter.
Try this - install Macrium Reflect Free, and create a boot entry.
Boot from boot entry and you will probably see the ssd.
If not, click on c drive icon and run diskpart to see if drive is visible but no letter assigned. If so, assign letter.
You can run capture image from this command prompt.
If it is not listed by diskpart lis vol, then probably the irst drivers havent been succesfully integrated into boot.wim image 2.now that the OS and all needed programs are installed, I am trying to boot from a USB to run DISM to create an image
I am trying to boot from a USB to run DISM to create an image, which is what I've done a million times.
The problem I'm having is that when I do DISKPART, then LIST VOLUME, I don't see the SSD drive. I've tried the steps in this post to inject the drivers into the install.wim (and even boot.wim), but I still can't see the SSD.
Is there a way to remove built in drivers (the ones that microsoft includes with the installation media) from the install.wim? I can't even get a list of them with get-drivers.
Quote
