[INSTALL ERROR] 0xc0000005 While decompressing Windows Files

G

Giovany86

New Member
Messages
6
Reaction score
2
Hello there !

I'm looking for help for a little issue on my side.
I've made a really big installation of around 200GB, which i captured using dism /Capture-Image without compression specified for a maximum compatibility, then i converted the WIM to ESD and then created the installation ISO using NTLite (latest version 2025.1010631).

I've tried installing it but i have the error 0xc0000005 when the install goes around 75% of decompressing the files. I know it isn't a capture issue as when the ISO is created with the WIM instead of the ESD file, it works correctly.

I'm using the latest Windows 10 22H2 x64 ISO files to be extra sure.
The ISO using WIM is taking a massive 118GB while the ISO using the ESD file is only around 89GB and i plan on using the ISO with Ventoy and a 128GB USB Flash drive

Anyone have encountered this issue before and succesfully fixed it ?
Have a nice day :)
 
garlin said:
Several users have complained about this exact problem, but there is no known solution. For certain images, the conversion from WIM to ESD results in an image which fails extraction at some point. The same source image in WIM format has no issues.

What creates the problem is unknown. NTLite uses the open-source wimlib library to perform this work.

Installation of ISO with install.esd images constantly crashes 0xC0000005: ACCESS_VIOLATION in \sources\ImageLib.dll
Click to expand...
is there any newer information about this?
 
Nope. You have a recurring problem with wimlib, but nobody bothers to preserve a failing ESD file that can be tested and possibly submitted to wimlib's author for debugging.

Instead you can skip having NTLite convert its WIM to ESD, and manually use "DISM /Export-Image /Compress:Recovery" to make a solid ESD. If DISM does create a target ESD file that Setup cannot read, it's probably a Setup-related bug.

MS does weird things. For example, the current MCT (Media Creation Tool) will create a "split WIM" on your USB device to get around the FAT32 file limits. Except it's not a traditional WIM file split into multiple parts. it's more like a solid ESD split into multiple parts. Neither wimlib or 7-Zip will read the MCT-made "SWM" files.

Obviously they don't intend for anyone to play with it. DISM can convert this "SWM" back into a WIM for processing. But it's a hassle.
 
You must log in or register to reply here.
Back
Top