Share via

DISM, Export WIM>ESD (recovery) > Crashes (0x80070008)

Anonymous
2018-10-10T01:52:17+00:00

Well, got interesting error with latest Windows 10 ADK, crashes while exporting image from WIM to ESD using /compress:recovery switch, same happens also with wimlib and solution seems the same (Figured perhaps this helps someone who might have same error).

HW information:

4-16 logical cores (no difference)

2-16GB of RAM (no difference)

1TB HDD with around 900GB of space.

4,3GB Regular RW-DVD

System #A:

Windows 8.1 Pro - 64-bit - 6.3.9600 - Windows ADK 10.0.17763.1 - HDD

Error:

Not enough storage is available to process this command.

System #B:

Windows 10 PE - 64-bit - 10.0.17763.1 - DVD

Error:

Not enough free space.

System Exported:

Windows 10 Home - 32-bit - Version: 10.0.10240.16384.

Error log (Windows 8.1 Pro):

2018-10-10 02:10:57, Info                  DISM   DISM.EXE:

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->

2018-10-10 02:10:57, Info                  DISM   DISM.EXE:

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.3.9600, Running architecture=amd64, Number of processors=4

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.17763.1

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Executing command line: dism  /Export-Image /SourceImageFile:INSTALL.WIM /SourceIndex:1 /DestinationImageFile:INSTALL.ESD /Compress:recovery /CheckIntegrity

2018-10-10 02:10:57, Info                  DISM   DISM Provider Store: PID=3700 TID=184 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection

2018-10-10 02:10:57, Info                  DISM   DISM Provider Store: PID=3700 TID=184 Connecting to the provider located at C:\MICROSOFT\ADK\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2018-10-10 02:10:57, Info                  DISM   DISM Provider Store: PID=3700 TID=184 Connecting to the provider located at C:\MICROSOFT\ADK\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2018-10-10 02:10:57, Info                  DISM   DISM Provider Store: PID=3700 TID=184 Connecting to the provider located at C:\MICROSOFT\ADK\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2018-10-10 02:10:57, Info                  DISM   DISM Provider Store: PID=3700 TID=184 Connecting to the provider located at C:\MICROSOFT\ADK\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2018-10-10 02:10:57, Info                  DISM   DISM Provider Store: PID=3700 TID=184 Connecting to the provider located at C:\MICROSOFT\ADK\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2018-10-10 02:10:57, Info                  DISM   DISM Provider Store: PID=3700 TID=184 Connecting to the provider located at C:\MICROSOFT\ADK\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2018-10-10 02:10:57, Info                  DISM   DISM Provider Store: PID=3700 TID=184 Connecting to the provider located at C:\MICROSOFT\ADK\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2018-10-10 02:10:57, Warning               DISM   DISM Provider Store: PID=3700 TID=184 Failed to load the provider: C:\MICROSOFT\ADK\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SiloedPackageManager

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: SiloedPackageManager.

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: FfuManager.

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager

2018-10-10 02:10:57, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.

[3700] [0x80070008] InitLZMSCompression:(2442): Not enough storage is available to process this command.

[3700] [0x80070008] CompressChunk:(789): Not enough storage is available to process this command.

[3700] [0x80070008] ProcessWimQueueNode:(98): Not enough storage is available to process this command.

[3700] [0x80070008] DequeueWimData:(304): Not enough storage is available to process this command.

[3700] [0x80070008] ImageWorkerThread:(250): Not enough storage is available to process this command.

[3700] [0x80070008] GetImageErrorCode:(2837): Not enough storage is available to process this command.

[3700] [0x80070008] ResAddFromFileAndHandle:(497): Not enough storage is available to process this command.

[3700] [0x80070008] ExportCopyStream:(207): Not enough storage is available to process this command.

[3700] [0x80070008] ExportHash:(129): Not enough storage is available to process this command.

[3700] [0x80070008] ExportFileNode:(147): Not enough storage is available to process this command.

[3700] [0x80070008] ExportForCrossFileTarget:(484): Not enough storage is available to process this command.

Solution for Windows 8.1 Pro using Windows 10 ADK 10.0.17763.1:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

DWORD: IRPStackSize

VALUE(decimal): 50

Stuck with Windows 10 PE still, well the PE only has ~500MB space at system drive X: while booted from DVD and can't figure out why the "Not enough free space.", while the drive having the WIM and exporting the ESD has over 900GB of space. Perhaps I am missing something like explaining dism.exe where the "temp" or "tmp" is located. I did try "set TMP=C:\TEMP" and "set TEMP=C::\TEMP" where C: is the 1TB HDD, but seems still ending up same

Anyway, if someone else has this error at installed system there's sort of solution, if someone got idea how to solve the Windows PE side error would be nice.

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-10-10T02:06:24+00:00

    Boot with your install media or Windows PE. Get a Command Prompt (SHIFT-F10 from first screen of install media setup).

    Before you run your export from WIM to ESD, create the folders \Recycler\Scratch on the partition that has 900GB empty. When you run the export command, add /ScratchDir=C:\Recycler\Scratch or use whatever drive letter has the 900GB space. You need a drive with minimum 1024MB for a Scratch directory.  Windows PE does not have 1024 room in its RAM disk (Drive X:).

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-10-10T04:36:09+00:00

    That worked miracles, thanks for the solution for WinPE.

    Makes me wonder, if the ScratchDir could be located in ramdrive like extending the PE WIM or using 3rd party solutions to have that ~1024MB. Assuming ScratchDir being written same time at same drive where WIM is read and ESD is written causes quite some IO loss. RAM/Memory would be way faster solution.

    -edit-

    Hmm, didn't know there was a command for this already. Here's first example:

    https://community.ivanti.com/docs/DOC-7807

    Stupid me for not reading a bit about subject first.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments