Hi Dave,
good news from your side. Would you bother to describe your steps more? Have you used Microsoft's explanation here to add your drivers to boot.wim and install.wim? Or have you tried out the sysprep configuration passes as well? And with what result?
Looking forward to your answer.
Frank
I have managed to add drivers by using NTLite, which is less complex, takes some time, but is well documented: https://www.win-raid.com/t750f25-Gui...Win-image.html
I needed to integrate a hotfix for NVME harddisk support and drivers for USB 3 to a Windows 7 SP1 ISO. Otherwise it was impossible to boot on a deployed machine. The USB 3 drivers were also a must on a Japanese Windows 10 Enterprise ISO. Otherwise there was an unreadable error at the beginning.
In NTlite it is quite easy to add those drivers (the ISO itself (install.wim) and to Windows Setup (boot.wim)) and the hotfix.
Frank
I've been using a new method (to me) of creating my wim for use in my SCCM Task Sequence tenforums cutomize win 10 audit capture
Basically going into audit mode and customizing everything I can before sysprep and capture. I've been adding a couple of features and then capturing, and it was going fine until I tried setting the start menu and taskbar with this solution.experts exchange win10 taskbar and startmenu
Now I's getting weird results - took the newest wim and stuck it in my TS - and the machine only booted to admin account w/out joining the domain. SMSTS.log here
tried a different approach and am getting errors that aren't repeating. Going to go backwards in my VM checkpoints and start diff approach. Hate wasting time so asking for two things.
If you see anything in the SMSTS log to fix, that'd be great (I am but an egg in reading them.)
Tell me if you do updates in audit mode or not? I have but might have to try another path.
Thanks in advance
Hi Kari,
first of all I would like to say thank you for the great guides you provide on this Forum and YouTube. Unfortunately I got stuck on my Image creation due to some differences to your guide.
So I am hoping you or someone else can help, since Google and search here did not :/
Background:
wanting to create "General" Image
using Hpyer-V on a strong Workstation to build Image
used media creation tool to get an ISO of my 64-bit Windows 10 Pro (which the Image is supposed to be on)
followed your steps up to the Point where the adk Setup install.wim copy steps happen, that is where I ran into the following issues:
1. I do not have an install.wim file, I am running W10 Pro 1803, but the file is not where it is in your tutorial. Has something changed over the years?
2. I cannot install the latest adk (based on Version 1803), I always get an error and roll-back at 66%: "Could not acquire privileges; GLE=0x514"
Would be super thankful for any help.
All the best!
Media Creation tool will give you a install.esd file not a install.wim file. You need to use Powershell or Command Prompt to extract the specific index you want from the install.esd file then convert it to a .wim using DISM. Here are the steps:
1. Open cmd as admin
2. Path to the location of your install.esd file. I find it easiest to extract the ISO (if you downloaded that) OR plug in your bootable drive. Either will work. Note: If you mount the ISO in Win10 I'm not sure if it allows DISM to extract.
3. The install.esd file will have multiple indexes. You need to locate the edition of Windows 10 you need. The command is:
dism /get-wiminfo /wimfile:install.esd
4. Locate the index number for version of Win10 you want.
5. Next run this command and it will create your .wim file you need. Under SourceIndex:# input the index number you need. If it's index 6 it would look like /SourceIndex:6
dism /export-image /SourceImageFile:install.esd /SourceIndex:# /DestinationImageFile:install.wim
Hope that helps.
hello and thank you very much for this tutorial.
could someone please confirm if edge does or does not work in audit mode?
i clicked cancel on the system prep box and i can use edge. am i still in audit mode?
Quote