Capturing an Image(wim) W7, W8.1, W10 1809.


Well-Known Member

abbodi, i need to pick your brains again. I am working on a untouched w8.1 pro u3 mounted registry. I am using the following information, is it correct?

HKEY_CLASSES_ROOT. Contains information about registered applications, including file associations and OLE object classes. (This hive displays the same settings as the HKEY_LOCAL_MACHINE\Software\Classes key.)
Is a subkey of HKEY_LOCAL_MACHINE\Software. The information that is stored here makes sure that the correct program opens when you open a file by using Windows Explorer. This key is sometimes abbreviated as "HKCR." Starting with Windows 2000, this information is stored under both the HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER keys. The HKEY_LOCAL_MACHINE\Software\Classes key contains default settings that can apply to all users on the local computer. The HKEY_CURRENT_USER\Software\Classes key contains settings that override the default settings and apply only to the interactive user. The HKEY_CLASSES_ROOT key provides a view of the registry that merges the information from these two sources. HKEY_CLASSES_ROOT also provides this merged view for programs that are designed for earlier versions of Windows. To change the settings for the interactive user, changes must be made under HKEY_CURRENT_USER\Software\Classes instead of under HKEY_CLASSES_ROOT. To change the default settings, changes must be made under HKEY_LOCAL_MACHINE\Software\Classes. If you write keys to a key under HKEY_CLASSES_ROOT, the system stores the information under HKEY_LOCAL_MACHINE\Software\Classes. If you write values to a key under HKEY_CLASSES_ROOT, and the key already exists under HKEY_CURRENT_USER\Software\Classes, the system will store the information there instead of under HKEY_LOCAL_MACHINE\Software\Classes.


Well-Known Member
Thanks Kas. I have managed to slip a few basic HKLM tweaks into ControlSet001 in a mounted registry and during setup and post install and they are working well, disabling search defender and a few others to create a new base image. I can add other tweaks post install with a batch file depending on its use.


Well-Known Member
Part 1. Capture Windows 8.1, Version 3 (2018-11-13). Working :)

Install Windows 8.1 from a clean untouched source, update and prepare for capture to create a custom install.wim with all chosen updates and .Nets fully integrated, not Pending.
abbodi86 for Install-Net-3.5.cmd- and his help and patience. :)
Kasual :)
Do everything in strict order.
Install Windows 8.1 from usb key drive using a clean untouched source.
01-Enable-User-Administrator.cmd - Logout and log in as Administrator.
Run HKLM tweaks.cmd from Power Run. - This disables Pagefile, Hibernation, Defender, Prefetch, Superfetch, Restore and Search/Indexing.
08-windows8.1-kb4054566-x64 - .NET Framework 4.7.2
09-windows8.1-kb4457045-x64 - .NET Framework 3.5 SP1 Security and Quality Rollup update
10-windows8.1-kb4457034-x64 - .NET Framework 4.6 - 4.7.2 Security and Quality Rollup update
Sysprep /OOBE /Generalize /Shutdown.

Capture the image with GImageX.
Load custom captured wim into NTLite for customisation.
Last edited:


New Member
how can i do that, Capture with GImageX i have never done bevore
and where can i find your HKLM tweaks.cmd , DISM-Online-Cleanup.cmd
thanks for helping me


Well-Known Member
I don thave time todo a guide for you but there should be plenty online, best is play around with it until you get the hang of it. Ive put both cmd files into a zip file, its Here,


Well-Known Member
Tried to install untouched iso, update and prepare for capture on Coffee Lake, failski. :mad:
I integrated the monthly rollups first then tried to add tons of smaller older updates, the error code online suggests that wu is blocking updating from a local source. I knew wu is blocking on CL but it works on amd steamroller. Will try again with CL with updates installed in strict update build date order because its the 2017 onwards updates that are the causing this. The amd captured cleaned and mild shrink image install on CL though and its working well, as i knew it would.

Captured wim with net3.5 and 472, abbodi86's Visual C++ pack(v17) enabled/installed, rinsed with ntlite, just cleaned up, is about the same as an untouched wim and is fully updated to satisfy WU. :)


New Member
made my own capture wim image guide in txt document that i use myself
for a few variations of windows 7 , 8.1 , 10
two winpe images with imagex included x86 and x64
windows updates help for windows 8 users aswell

hope this helps a few people out
lil-fella capture wim guide package
Last edited:


Well-Known Member
Windows 10 LTSC
Capture using GImageX v2.2, enable .net 3.5, update, no Liting, straight deployment of new custom wim
Deployment of custom wim gives oobekeyboard error during setup, you cant type anything at all into enter username. Knowledgable bods say dont use windows update before capture but thats what capturing an image is for for crying out loud. They suggest using an answer file. Try installing updates with dism and extracted cab files instead.

Appears to be a dism bug, 2 progress lines open when running component cleanup/reset base.


Well-Known Member
Windows 10 1809 LTSC(.107 iso, updated with setupcomplete.cmd, capture and deploy image), same specs as above.

Enabling the resetbase tweak and running resetbase cleanup is breaking captured image deployment giving an oobekeyboard error during setup.
I just used these 2 commands

Do not enable ResetBase tweak.

Dism /Online /Cleanup-Image /CheckHealth
Just to make sure everythings ok

Dism /Online /Cleanup-Image /StartComponentCleanup

I dont get the previous 2 progress bar problem using the full resetbase. I havnt checked which one is the bogey or if its a combination of the 2.
nuhi, can you disable the reset base tweak on 1809 (LTSC) :)
Last edited:


Well-Known Member
I used GimageX to capture, let me know if you want to know what settings i used, i will put a grab up later today/early evening.


Thanks. I use imagex for capture because I can set the edition flag (Professional, Enterprise, etc) and capture the image all in one command. Dism does not have /flags switch and the lack of flag in the image causes some problems.

I install Windows on VMware Workstation in audit mode, do sysprep, and map virtual disk with VMware on drive Z: and capture with imagex. I made a batch of it. I use a wimscript.ini.

abbodi86 updated his exclusions list I do not know if it is only for Windows 10.

Below is my batch. Just copy the imagex.exe and wimscript.ini to the folder where the batch is and run as administrator. The install.wim will be copied to the same folder. The imagex.exe can be copied from the Windows ADK or downloaded using GetWaikTools.

@echo off

:: Checking administrative rights
reg query "HKU\S-1-5-19" >nul 2>&1 || (
echo "Run as Administrator"
goto :End

cd /d "%~dp0"

set "Name=Windows 10 Enterprise LTSC"
set "Description=Windows 10 Enterprise LTSC"
set Edition=EnterpriseS

:: Main
imagex /compress maximum /config wimscript.ini /capture Z: install.wim /flags "%Edition%" "%Name%" "%Description%" /check /verify

echo Press any key to exit...
pause >nul
goto :eof


Well-Known Member
Thanks for the heads up about abbodi's updated wimscript, he did post one here and he did say about dism not setting flags. I just use GimageX from its folder and it always runs without a problem, i dont have to get imagex, it just runs. :)
Thanks for the cmd file, i'll look at that later ron :D


I always try to use Microsoft's official tools as much as possible, and I'm also not depending on other developers updating their tools, I can just get straight from the source :) although I do not think there are any very important updates to imagex. GimageX is just a GUI frontend for imagex. Anyway I posted the batch to other people also someone might be interested.

The advantage of batch is that I only set the name, description and edition once and just click. I do not need to adjust in the GUI every time :)


Well-Known Member
I was thinking to not do the dism cleanup on the system before capture but let NTLite do it in Updates - Clean Update - DISM Compatible,
Install, update/install net3.5 with setupcomplete.cmd(its only 4 updates and a dism run for net), sysprep, capture, make a copy then wash through with NTLite. The captured wim was quite large but NTLite coped very well with it. :)

I didnt use a wimscript to help see what was causing the aforementioned deployment bug, luckily is was the full resetbase, i was going potty wondering if i messed up somewhere.
Last edited:


I think the best solution is to use W10UI script from abbodi86 this integrates the updates in the correct order does the cleanup (you can determine whether with the resetbase or not) and only integrates net3.5 at the end because if you integrate before it generates a pending operation and cleanup is not possible. After integrating net3.5 the script integrates again the necessary updates to update the components of .net3.5. At the end you install Windows and capture only to perform the pending operations and have the updates fully installed. That's what I do.

At the end when you do the dism cleanup this will be fast because most of it has already been cleaned and the image size will be small so the capture will not be that long.