DISM Error 80

I'm trying to capture a windows 8 image from PE. I'm using dism to capture the C drive only. When I run dism, it finishes but I get an error 80. 

---------------------------------
 Error: 80
 The file exists.
 The DISM log file can be found at X:\windows\Logs\DISM\dism.log
 Failed to create image
 ---------------------------------

I've checked my save location and there is no such file.

Upon examining the logs I find that dism thinks there is not enough space, followed by the file already exists. The drive that dism is saving to has over half a terabyte of free space.

[828] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[828] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[828] [0x80070070] WriteDataCallback:(1140): There is not enough space on the disk.
[828] [0x80070070] ResExtract:(5208): There is not enough space on the disk.
[828] [0x80070050] WimImageEnqueueOperation:(777): The file exists.
[828] [0x80070050] CompressCaptureNode:(3570): The file exists.
[828] [0x80070050] WimImageEnqueueOperation:(777): The file exists.
[828] [0x80070050] ResAddFromFileAndHandle:(4415): The file exists.
[828] [0x80070050] AddFileNodeToImage:(2041): The file exists.
[828] [0x80070050] EnumImageFiles:(1903): The file exists.
[828] [0x80070050] EnumImageFiles:(1921): The file exists.
[828] [0x80070050] EnumImageFiles:(1921): The file exists.
[828] [0x80070050] WriteFileImage:(1867): The file exists.

Any help would be appreciate!

July 29th, 2013 5:28pm

Is the OS volume actually the C: drive in WinPE? Usually the C: ends up being the System Reserved partition (or a card reader) unless you had done an unattended install to only create one partition.

What are you trying to capture the image to?

Free Windows Admin Tool Kit Click here and download it now
July 29th, 2013 5:42pm

Is the OS volume actually the C: drive in WinPE? Usually the C: ends up being the System Reserved partition (or a card reader) unless you had done an unattended install to only create one partition.

What are you trying to capture the image to?

July 29th, 2013 5:42pm

Unfortunately, Microsoft has chosen to completely ignore this bug in Windows 8.1 DISM.  Whatever genius engineer(s) decided to modify the DISM utility from Windows 8 obviously didn't bother testing out every single function of DISM for 8.1.

While the fix to errror 80 is simple (simply add /ScratchDir:[drive]:\ to command line), unless it is added when running WinPE, the /capture-image command will fail every time without question due to running out of space in the default WinPE scratch directory (which only has a size of 32MB).  

While this issue is a massive inconvenience in and of itself, I'm beyond irritated at Microsoft's refusal to address this in any type of literature on their website, which has lead to 4 days of failed imaging attempts of my system partition.  (Why not just add an italicized warning under the /capture-image flag on the DISM command page, Microsoft?)  The ONLY place I could find this simple fix was here within post #61... after 4 days of searching Google.

Perhaps Microsoft could put a bit of effort into making this common knowledge while running the /Capture-Image command within WinPE.




  • Edited by JW0914 Saturday, March 29, 2014 11:05 AM
  • Proposed as answer by ischilling Monday, May 12, 2014 10:57 AM
Free Windows Admin Tool Kit Click here and download it now
March 29th, 2014 11:03am

Unfortunately, Microsoft has chosen to completely ignore this bug in Windows 8.1 DISM.  Whatever genius engineer(s) decided to modify the DISM utility from Windows 8 obviously didn't bother testing out every single function of DISM for 8.1.

While the fix to errror 80 is simple (simply add /ScratchDir:[drive]:\ to command line), unless it is added when running WinPE, the /capture-image command will fail every time without question due to running out of space in the default WinPE scratch directory (which only has a size of 32MB).  

While this issue is a massive inconvenience in and of itself, I'm beyond irritated at Microsoft's refusal to address this in any type of literature on their website, which has lead to 4 days of failed imaging attempts of my system partition.  (Why not just add an italicized warning under the /capture-image flag on the DISM command page, Microsoft?)  The ONLY place I could find this simple fix was here within post #61... after 4 days of searching Google.

Perhaps Microsoft could put a bit of effort into making this common knowledge while running the /Capture-Image command within WinPE.




  • Edited by JW0914 Saturday, March 29, 2014 11:05 AM
  • Proposed as answer by ischilling Monday, May 12, 2014 10:57 AM
March 29th, 2014 11:03am

I haven't encountered this error doing a capture before. What is the size of the image you are creating? I think I've seen others needing to increase scratch space when trying to create large images.
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2014 3:58pm

Image size of the system partition with max compression is around 325GB.  Size shouldn't matter... the whole point of .wim and .swm files are to image partitions and/or entire disks regardless of size. Microsoft retired ImageX with their release of Windows 8, making ImageX completely incompatible with the Windows 8/8.1 architecture (this was never an issue with ImageX). 

While DISM is a comprehensive utility covering many facets (as well as being highly useful), it doesn't take a genius to say "hey, we updated this utility within Windows 8.1, so how about we test if it's possible to create .wim and .swm files under all circumstances, seeming as it's the only utility within windows 8.1 that can do so". There is no other utility (at least that I know of) included within Windows 8/8.1 that allows for the capture of drives and creation of .wim or .swm files.

Like so many other issues with broken software included in Windows 8.1 (SkyDrive/OneDrive for instance), Microsoft's choice is to simply ignore it with the belief they shouldn't have to inform consumers [or businesses] of programs they broke within Windows 8.1 and how to fix them with a workaround. 


And why would there be such a small default scratch dir within windows 8/8.1 when not used on a tablet (which doesn't even run the same architecture/version that PCs and laptops use)?  All modern computers, whether desktop or laptop, generally come with a minimum 500GB HDD.  WinPE, and it's variations, are not run from the internal HDDs (unless you purposefully create a WinPE partition containing a PE/RE combined image [since PE doesn't contain recovery programs like bcdedit or bootrec] before the system partition, as I have done), so why would they not make the default scratch dir the non-system partition instead of the x: drive running from the memory... at the very least put it on the DISM TechNet page that /scratchdir:[drive]:/ needs to be added.





  • Edited by JW0914 Friday, April 11, 2014 2:21 AM
April 11th, 2014 2:07am

Image size of the system partition with max compression is around 325GB.  Size shouldn't matter... the whole point of .wim and .swm files are to image partitions and/or entire disks regardless of size. Microsoft retired ImageX with their release of Windows 8, making ImageX completely incompatible with the Windows 8/8.1 architecture (this was never an issue with ImageX). 

While DISM is a comprehensive utility covering many facets (as well as being highly useful), it doesn't take a genius to say "hey, we updated this utility within Windows 8.1, so how about we test if it's possible to create .wim and .swm files under all circumstances, seeming as it's the only utility within windows 8.1 that can do so". There is no other utility (at least that I know of) included within Windows 8/8.1 that allows for the capture of drives and creation of .wim or .swm files.

Like so many other issues with broken software included in Windows 8.1 (SkyDrive/OneDrive for instance), Microsoft's choice is to simply ignore it with the belief they shouldn't have to inform consumers [or businesses] of programs they broke within Windows 8.1 and how to fix them with a workaround. 


And why would there be such a small default scratch dir within windows 8/8.1 when not used on a tablet (which doesn't even run the same architecture/version that PCs and laptops use)?  All modern computers, whether desktop or laptop, generally come with a minimum 500GB HDD.  WinPE, and it's variations, are not run from the internal HDDs (unless you purposefully create a WinPE partition containing a PE/RE combined image [since PE doesn't contain recovery programs like bcdedit or bootrec] before the system partition, as I have done), so why would they not make the default scratch dir the non-system partition instead of the x: drive running from the memory... at the very least put it on the DISM TechNet page that /scratchdir:[drive]:/ needs to be added.





  • Edited by JW0914 Friday, April 11, 2014 2:21 AM
Free Windows Admin Tool Kit Click here and download it now
April 11th, 2014 2:07am

Unfortunately, Microsoft has chosen to completely ignore this bug in Windows 8.1 DISM.  Whatever genius engineer(s) decided to modify the DISM utility from Windows 8 obviously didn't bother testing out every single function of DISM for 8.1.

While the fix to errror 80 is simple (simply add /ScratchDir:[drive]:\ to command line), unless it is added when running WinPE, the /capture-image command will fail every time without question due to running out of space in the default WinPE scratch directory (which only has a size of 32MB).  

While this issue is a massive inconvenience in and of itself, I'm beyond irritated at Microsoft's refusal to address this in any type of literature on their website, which has lead to 4 days of failed imaging attempts of my system partition.  (Why not just add an italicized warning under the /capture-image flag on the DISM command page, Microsoft?)  The ONLY place I could find this simple fix was here within post #61... after 4 days of searching Google.

Perhaps Microsoft could put a bit of effort into making this common knowledge while running the /Capture-Image command within WinPE.




Worked for me ! :D thanks a lot
March 26th, 2015 2:04pm

Create a new partition (min 10 GB) either by shrinking existing volume or adding new disk or use any other volume. Create a folder TEMP (not necessary or point to drive) on new volume, e.g., D:\TEMP. Then change the TEMP and TMP environment variables to D:\TEMP.

SET TEMP=D:\TEMP

SET TMP=D:\TEMP

Now you can capture image without any hindrance.

Free Windows Admin Tool Kit Click here and download it now
June 18th, 2015 7:48am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics