DISM fails with 'There is not enough space on the disk.' while capturing an image
I use DISM to capture images and store them on a network disk. I use a standard 32bit WinPE 4.0 environment to capture them.
My current path was set to i:images and I executed the following command:
dism /capture-image /imagefile:ae2212-w81-64bit-v1.wim /capture-dir:c: /name:system
It ran up to 100% and which point it failed with the error There is not enough space on the disk.. During capture I monitored the network drive and I could see the image growing. When the error message occurred the image was deleted.
What is odd is that the image would have been about 15GB and the network drive has over 500GB free.
What could be going wrong, should I use the /scratchdir option?
2014-02-19 01:04:37, Info DISM DISM WIM Provider: PID=1216 c:Windows.oldWindowsWinSxSx86_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.2.9200.16432_none_a2bd221c1cde6e62ServiceMonikerSupport.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[1216] [0xc144012f]
2014-02-19 01:04:37, Info DISM DISM WIM Provider: PID=1216 c:Windows.oldWindowsWinSxSx86_wcf-system.identitymodel_b03f5f7f11d50a3a_6.2.9200.16432_none_30a420f7f05ab330System.IdentityModel.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[1216] [0xc144012f]
2014-02-19 01:04:37, Info DISM DISM WIM Provider: PID=1216 c:Windows.oldWindowsWinSxSx86_wcf-system.runtime.serialization_b03f5f7f11d50a3a_6.2.9200.16432_none_123c6840d0913997System.Runtime.Serialization.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:1217 - CWimManager::Capture(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:4274 - CWimManager::InternalCmdCaptureBase(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 Error executing command - CWimManager::InternalExecuteCmd(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:1928 - CWimManager::ExecuteCmdLine(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM.EXE: WimManager processed the command line but failed. HRESULT=80070070
2014-02-19 01:56:22, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2014-02-19 01:56:22, Info DISM DISM.EXE:
2014-02-19 01:56:22, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2014-02-19 01:56:22, Info DISM DISM.EXE:
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
images clone disk-image wim dism
asked Feb 19 '14 at 9:12
WouterWouter
118128
add a comment |
I use DISM to capture images and store them on a network disk. I use a standard 32bit WinPE 4.0 environment to capture them.
My current path was set to i:images and I executed the following command:
dism /capture-image /imagefile:ae2212-w81-64bit-v1.wim /capture-dir:c: /name:system
It ran up to 100% and which point it failed with the error There is not enough space on the disk.. During capture I monitored the network drive and I could see the image growing. When the error message occurred the image was deleted.
What is odd is that the image would have been about 15GB and the network drive has over 500GB free.
What could be going wrong, should I use the /scratchdir option?
2014-02-19 01:04:37, Info DISM DISM WIM Provider: PID=1216 c:Windows.oldWindowsWinSxSx86_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.2.9200.16432_none_a2bd221c1cde6e62ServiceMonikerSupport.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[1216] [0xc144012f]
2014-02-19 01:04:37, Info DISM DISM WIM Provider: PID=1216 c:Windows.oldWindowsWinSxSx86_wcf-system.identitymodel_b03f5f7f11d50a3a_6.2.9200.16432_none_30a420f7f05ab330System.IdentityModel.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[1216] [0xc144012f]
2014-02-19 01:04:37, Info DISM DISM WIM Provider: PID=1216 c:Windows.oldWindowsWinSxSx86_wcf-system.runtime.serialization_b03f5f7f11d50a3a_6.2.9200.16432_none_123c6840d0913997System.Runtime.Serialization.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:1217 - CWimManager::Capture(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:4274 - CWimManager::InternalCmdCaptureBase(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 Error executing command - CWimManager::InternalExecuteCmd(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:1928 - CWimManager::ExecuteCmdLine(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM.EXE: WimManager processed the command line but failed. HRESULT=80070070
2014-02-19 01:56:22, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2014-02-19 01:56:22, Info DISM DISM.EXE:
2014-02-19 01:56:22, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2014-02-19 01:56:22, Info DISM DISM.EXE:
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
images clone disk-image wim dism
asked Feb 19 '14 at 9:12
WouterWouter
118128
add a comment |
I use DISM to capture images and store them on a network disk. I use a standard 32bit WinPE 4.0 environment to capture them.
My current path was set to i:images and I executed the following command:
dism /capture-image /imagefile:ae2212-w81-64bit-v1.wim /capture-dir:c: /name:system
It ran up to 100% and which point it failed with the error There is not enough space on the disk.. During capture I monitored the network drive and I could see the image growing. When the error message occurred the image was deleted.
What is odd is that the image would have been about 15GB and the network drive has over 500GB free.
What could be going wrong, should I use the /scratchdir option?
2014-02-19 01:04:37, Info DISM DISM WIM Provider: PID=1216 c:Windows.oldWindowsWinSxSx86_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.2.9200.16432_none_a2bd221c1cde6e62ServiceMonikerSupport.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[1216] [0xc144012f]
2014-02-19 01:04:37, Info DISM DISM WIM Provider: PID=1216 c:Windows.oldWindowsWinSxSx86_wcf-system.identitymodel_b03f5f7f11d50a3a_6.2.9200.16432_none_30a420f7f05ab330System.IdentityModel.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[1216] [0xc144012f]
2014-02-19 01:04:37, Info DISM DISM WIM Provider: PID=1216 c:Windows.oldWindowsWinSxSx86_wcf-system.runtime.serialization_b03f5f7f11d50a3a_6.2.9200.16432_none_123c6840d0913997System.Runtime.Serialization.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:1217 - CWimManager::Capture(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:4274 - CWimManager::InternalCmdCaptureBase(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 Error executing command - CWimManager::InternalExecuteCmd(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:1928 - CWimManager::ExecuteCmdLine(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM.EXE: WimManager processed the command line but failed. HRESULT=80070070
2014-02-19 01:56:22, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2014-02-19 01:56:22, Info DISM DISM.EXE:
2014-02-19 01:56:22, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2014-02-19 01:56:22, Info DISM DISM.EXE:
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
images clone disk-image wim dism
asked Feb 19 '14 at 9:12
WouterWouter
118128
I use DISM to capture images and store them on a network disk. I use a standard 32bit WinPE 4.0 environment to capture them.
My current path was set to i:images and I executed the following command:
dism /capture-image /imagefile:ae2212-w81-64bit-v1.wim /capture-dir:c: /name:system
It ran up to 100% and which point it failed with the error There is not enough space on the disk.. During capture I monitored the network drive and I could see the image growing. When the error message occurred the image was deleted.
What is odd is that the image would have been about 15GB and the network drive has over 500GB free.
What could be going wrong, should I use the /scratchdir option?
2014-02-19 01:04:37, Info DISM DISM WIM Provider: PID=1216 c:Windows.oldWindowsWinSxSx86_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.2.9200.16432_none_a2bd221c1cde6e62ServiceMonikerSupport.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[1216] [0xc144012f]
2014-02-19 01:04:37, Info DISM DISM WIM Provider: PID=1216 c:Windows.oldWindowsWinSxSx86_wcf-system.identitymodel_b03f5f7f11d50a3a_6.2.9200.16432_none_30a420f7f05ab330System.IdentityModel.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[1216] [0xc144012f]
2014-02-19 01:04:37, Info DISM DISM WIM Provider: PID=1216 c:Windows.oldWindowsWinSxSx86_wcf-system.runtime.serialization_b03f5f7f11d50a3a_6.2.9200.16432_none_123c6840d0913997System.Runtime.Serialization.dll (HRESULT=0x8007011A) - CWimManager::WimProviderMsgLogCallback
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
[1216] [0x80070070] ReadWriteDataInternal:(141): There is not enough space on the disk.
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:1217 - CWimManager::Capture(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:4274 - CWimManager::InternalCmdCaptureBase(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 Error executing command - CWimManager::InternalExecuteCmd(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM WIM Provider: PID=1216 TID=1220 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:1928 - CWimManager::ExecuteCmdLine(hr:0x80070070)
2014-02-19 01:56:22, Error DISM DISM.EXE: WimManager processed the command line but failed. HRESULT=80070070
2014-02-19 01:56:22, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2014-02-19 01:56:22, Info DISM DISM.EXE:
2014-02-19 01:56:22, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2014-02-19 01:56:22, Info DISM DISM.EXE:
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2014-02-19 01:56:22, Info DISM DISM Provider Store: PID=1216 TID=1220 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
images clone disk-image wim dism
images clone disk-image wim dism
asked Feb 19 '14 at 9:12
WouterWouter
118128
asked Feb 19 '14 at 9:12
WouterWouter
118128
asked Feb 19 '14 at 9:12
WouterWouter
118128
asked Feb 19 '14 at 9:12
WouterWouter
118128
asked Feb 19 '14 at 9:12
WouterWouter
118128
118128
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
Depending on the boot device (USB or CD/ROM) the capture process makes a decision of where to write its scratch files. Since a USB is writable, it tries to write massive scratch files to it. Try using the /scratchdir option and direct scratch files to media with plenty of room.
answered Apr 28 '14 at 19:44
James J. R. AielloJames J. R. Aiello
362
add a comment |
Rather than changing the "scratch directory" I increased the scratch space on WinPE (the default is 32MB). This worked for me:
DISM /Mount-Wim /WimFile:<imagepath> /index:indexnum
/MountDir:<mountdirlocation>
DISM /image:<mountdirlocation> /set-ScratchSpace:512
DISM /Unmount-Wim /MountDir:<mountdirlocation> /Commit
Set the scratch space as high as the systems you are trying to image will support. Valid values for the scratch-space are 32, 64, 128, 256 and 512 (MB).
More info: https://technet.microsoft.com/en-us/library/dd799261(WS.10).aspx
answered Jun 6 '16 at 21:17
Mi ReyMi Rey
214
add a comment |
I have a similar problem where the image fails around 60%. Like you, I have nearly a terrabyte free and there are no quota management features enabled on the servers. I'm using Windows PE4 32bit booted off a flash drive and the latest version of DISM.
The added complication is that I'm capturing to a DFS enabled share. Usually re-capturing the image succeeds so I'm not sure if my secondary fix of using a non-namespace share name the second capture works because I got lucky or if there is an issue with the namespace. I wish I had a better answer for you but you might have to capture it to flash drive and manually copy later.
answered Apr 16 '14 at 18:14
IconiuIconiu
392
add a comment |
I also had this problem on a VM that only had 1gb of memory assigned to it.
After assigning 4gb of memory it worked fine.
answered Jun 24 '15 at 4:01
JonJon
11
That actually helped me; due to Hyper-V dynamic memory my virtual machine failed to get enough RAM to be able to install through either the normal means or the manual dism apply-image one. Thanks. (the scratch directory option did not work)
– Paul Stelian
May 27 '17 at 20:15
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f718797%2fdism-fails-with-there-is-not-enough-space-on-the-disk-while-capturing-an-imag%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Depending on the boot device (USB or CD/ROM) the capture process makes a decision of where to write its scratch files. Since a USB is writable, it tries to write massive scratch files to it. Try using the /scratchdir option and direct scratch files to media with plenty of room.
answered Apr 28 '14 at 19:44
James J. R. AielloJames J. R. Aiello
362
add a comment |
Depending on the boot device (USB or CD/ROM) the capture process makes a decision of where to write its scratch files. Since a USB is writable, it tries to write massive scratch files to it. Try using the /scratchdir option and direct scratch files to media with plenty of room.
answered Apr 28 '14 at 19:44
James J. R. AielloJames J. R. Aiello
362
add a comment |
Depending on the boot device (USB or CD/ROM) the capture process makes a decision of where to write its scratch files. Since a USB is writable, it tries to write massive scratch files to it. Try using the /scratchdir option and direct scratch files to media with plenty of room.
answered Apr 28 '14 at 19:44
James J. R. AielloJames J. R. Aiello
362
Depending on the boot device (USB or CD/ROM) the capture process makes a decision of where to write its scratch files. Since a USB is writable, it tries to write massive scratch files to it. Try using the /scratchdir option and direct scratch files to media with plenty of room.
answered Apr 28 '14 at 19:44
James J. R. AielloJames J. R. Aiello
362
answered Apr 28 '14 at 19:44
James J. R. AielloJames J. R. Aiello
362
answered Apr 28 '14 at 19:44
James J. R. AielloJames J. R. Aiello
362
answered Apr 28 '14 at 19:44
James J. R. AielloJames J. R. Aiello
362
362
add a comment |
add a comment |
Rather than changing the "scratch directory" I increased the scratch space on WinPE (the default is 32MB). This worked for me:
DISM /Mount-Wim /WimFile:<imagepath> /index:indexnum
/MountDir:<mountdirlocation>
DISM /image:<mountdirlocation> /set-ScratchSpace:512
DISM /Unmount-Wim /MountDir:<mountdirlocation> /Commit
Set the scratch space as high as the systems you are trying to image will support. Valid values for the scratch-space are 32, 64, 128, 256 and 512 (MB).
More info: https://technet.microsoft.com/en-us/library/dd799261(WS.10).aspx
answered Jun 6 '16 at 21:17
Mi ReyMi Rey
214
add a comment |
Rather than changing the "scratch directory" I increased the scratch space on WinPE (the default is 32MB). This worked for me:
DISM /Mount-Wim /WimFile:<imagepath> /index:indexnum
/MountDir:<mountdirlocation>
DISM /image:<mountdirlocation> /set-ScratchSpace:512
DISM /Unmount-Wim /MountDir:<mountdirlocation> /Commit
Set the scratch space as high as the systems you are trying to image will support. Valid values for the scratch-space are 32, 64, 128, 256 and 512 (MB).
More info: https://technet.microsoft.com/en-us/library/dd799261(WS.10).aspx
answered Jun 6 '16 at 21:17
Mi ReyMi Rey
214
add a comment |
Rather than changing the "scratch directory" I increased the scratch space on WinPE (the default is 32MB). This worked for me:
DISM /Mount-Wim /WimFile:<imagepath> /index:indexnum
/MountDir:<mountdirlocation>
DISM /image:<mountdirlocation> /set-ScratchSpace:512
DISM /Unmount-Wim /MountDir:<mountdirlocation> /Commit
Set the scratch space as high as the systems you are trying to image will support. Valid values for the scratch-space are 32, 64, 128, 256 and 512 (MB).
More info: https://technet.microsoft.com/en-us/library/dd799261(WS.10).aspx
answered Jun 6 '16 at 21:17
Mi ReyMi Rey
214
Rather than changing the "scratch directory" I increased the scratch space on WinPE (the default is 32MB). This worked for me:
DISM /Mount-Wim /WimFile:<imagepath> /index:indexnum
/MountDir:<mountdirlocation>
DISM /image:<mountdirlocation> /set-ScratchSpace:512
DISM /Unmount-Wim /MountDir:<mountdirlocation> /Commit
Set the scratch space as high as the systems you are trying to image will support. Valid values for the scratch-space are 32, 64, 128, 256 and 512 (MB).
More info: https://technet.microsoft.com/en-us/library/dd799261(WS.10).aspx
answered Jun 6 '16 at 21:17
Mi ReyMi Rey
214
edited Jul 18 '16 at 17:16
answered Jun 6 '16 at 21:17
Mi ReyMi Rey
214
answered Jun 6 '16 at 21:17
Mi ReyMi Rey
214
answered Jun 6 '16 at 21:17
Mi ReyMi Rey
214
214
add a comment |
add a comment |
I have a similar problem where the image fails around 60%. Like you, I have nearly a terrabyte free and there are no quota management features enabled on the servers. I'm using Windows PE4 32bit booted off a flash drive and the latest version of DISM.
The added complication is that I'm capturing to a DFS enabled share. Usually re-capturing the image succeeds so I'm not sure if my secondary fix of using a non-namespace share name the second capture works because I got lucky or if there is an issue with the namespace. I wish I had a better answer for you but you might have to capture it to flash drive and manually copy later.
answered Apr 16 '14 at 18:14
IconiuIconiu
392
add a comment |
I have a similar problem where the image fails around 60%. Like you, I have nearly a terrabyte free and there are no quota management features enabled on the servers. I'm using Windows PE4 32bit booted off a flash drive and the latest version of DISM.
The added complication is that I'm capturing to a DFS enabled share. Usually re-capturing the image succeeds so I'm not sure if my secondary fix of using a non-namespace share name the second capture works because I got lucky or if there is an issue with the namespace. I wish I had a better answer for you but you might have to capture it to flash drive and manually copy later.
answered Apr 16 '14 at 18:14
IconiuIconiu
392
add a comment |
I have a similar problem where the image fails around 60%. Like you, I have nearly a terrabyte free and there are no quota management features enabled on the servers. I'm using Windows PE4 32bit booted off a flash drive and the latest version of DISM.
The added complication is that I'm capturing to a DFS enabled share. Usually re-capturing the image succeeds so I'm not sure if my secondary fix of using a non-namespace share name the second capture works because I got lucky or if there is an issue with the namespace. I wish I had a better answer for you but you might have to capture it to flash drive and manually copy later.
answered Apr 16 '14 at 18:14
IconiuIconiu
392
I have a similar problem where the image fails around 60%. Like you, I have nearly a terrabyte free and there are no quota management features enabled on the servers. I'm using Windows PE4 32bit booted off a flash drive and the latest version of DISM.
The added complication is that I'm capturing to a DFS enabled share. Usually re-capturing the image succeeds so I'm not sure if my secondary fix of using a non-namespace share name the second capture works because I got lucky or if there is an issue with the namespace. I wish I had a better answer for you but you might have to capture it to flash drive and manually copy later.
answered Apr 16 '14 at 18:14
IconiuIconiu
392
answered Apr 16 '14 at 18:14
IconiuIconiu
392
answered Apr 16 '14 at 18:14
IconiuIconiu
392
answered Apr 16 '14 at 18:14
IconiuIconiu
392
392
add a comment |
add a comment |
I also had this problem on a VM that only had 1gb of memory assigned to it.
After assigning 4gb of memory it worked fine.
answered Jun 24 '15 at 4:01
JonJon
11
That actually helped me; due to Hyper-V dynamic memory my virtual machine failed to get enough RAM to be able to install through either the normal means or the manual dism apply-image one. Thanks. (the scratch directory option did not work)
– Paul Stelian
May 27 '17 at 20:15
add a comment |
I also had this problem on a VM that only had 1gb of memory assigned to it.
After assigning 4gb of memory it worked fine.
answered Jun 24 '15 at 4:01
JonJon
11
That actually helped me; due to Hyper-V dynamic memory my virtual machine failed to get enough RAM to be able to install through either the normal means or the manual dism apply-image one. Thanks. (the scratch directory option did not work)
– Paul Stelian
May 27 '17 at 20:15
add a comment |
I also had this problem on a VM that only had 1gb of memory assigned to it.
After assigning 4gb of memory it worked fine.
answered Jun 24 '15 at 4:01
JonJon
11
I also had this problem on a VM that only had 1gb of memory assigned to it.
After assigning 4gb of memory it worked fine.
answered Jun 24 '15 at 4:01
JonJon
11
answered Jun 24 '15 at 4:01
JonJon
11
answered Jun 24 '15 at 4:01
JonJon
11
answered Jun 24 '15 at 4:01
JonJon
11
11
That actually helped me; due to Hyper-V dynamic memory my virtual machine failed to get enough RAM to be able to install through either the normal means or the manual dism apply-image one. Thanks. (the scratch directory option did not work)
– Paul Stelian
May 27 '17 at 20:15
add a comment |
That actually helped me; due to Hyper-V dynamic memory my virtual machine failed to get enough RAM to be able to install through either the normal means or the manual dism apply-image one. Thanks. (the scratch directory option did not work)
– Paul Stelian
May 27 '17 at 20:15
That actually helped me; due to Hyper-V dynamic memory my virtual machine failed to get enough RAM to be able to install through either the normal means or the manual dism apply-image one. Thanks. (the scratch directory option did not work)
– Paul Stelian
May 27 '17 at 20:15
That actually helped me; due to Hyper-V dynamic memory my virtual machine failed to get enough RAM to be able to install through either the normal means or the manual dism apply-image one. Thanks. (the scratch directory option did not work)
– Paul Stelian
May 27 '17 at 20:15
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f718797%2fdism-fails-with-there-is-not-enough-space-on-the-disk-while-capturing-an-imag%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
