DISM Can Mount Image but Can't Apply Itdism unmount with commit on offline image and changes are still in pending status when remountedWindows Deployment Server and Re-Re-Imaging via PXE BootDISM inject drivers into WIM gives error 2Windows deployment services introductionHow to stop DISM resetting activation?Why does DISM say the Package is not applicable to this Image?Is it possible to capture an Image with WDS without local saveInjecting Updates via Dism gives error 50 all the timeHow to re-enable test mode when deploying Windows 10 wim image with Dism?Apply Customized Image after PXE boot
Was this a power play by Daenerys?
Anatomically Correct Carnivorous Tree
Why not just directly invest in the holdings of an ETF?
Meaning of「〜てみたいと思います」
Why do Thanos's punches not kill Captain America or at least cause some mortal injuries?
Smallest Guaranteed hash collision cycle length
Proof that the inverse image of a single element is a discrete space
Early arrival in Australia, early hotel check in not available
Light Switch Terminals
SSD - Disk is OK, one bad sector
tikz: not so precise graphic
What does a comma mean inside an 'if' statement?
Why was the Ancient One so hesitant to teach Dr. Strange the art of sorcery?
How to compact two the parabol commands in the following example?
What is the best way for a skeleton to impersonate human without using magic?
Can 'sudo apt-get remove [write]' destroy my Ubuntu?
Make all the squares explode
Is taking modulus on both sides of an equation valid?
How to minimise the cost of guessing a number in a high/low guess game?
How can I answer high-school writing prompts without sounding weird and fake?
Why doesn't Rocket Lab use a solid stage?
Word for being out at night during curfew
Does Lawful Interception of 4G / the proposed 5G provide a back door for hackers as well?
On what legal basis did the UK remove the 'European Union' from its passport?
DISM Can Mount Image but Can't Apply It
dism unmount with commit on offline image and changes are still in pending status when remountedWindows Deployment Server and Re-Re-Imaging via PXE BootDISM inject drivers into WIM gives error 2Windows deployment services introductionHow to stop DISM resetting activation?Why does DISM say the Package is not applicable to this Image?Is it possible to capture an Image with WDS without local saveInjecting Updates via Dism gives error 50 all the timeHow to re-enable test mode when deploying Windows 10 wim image with Dism?Apply Customized Image after PXE boot
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I am using DISM to capture a Windows image. I have successfully captured an image from the reference computer after running sysprep and booting from Windows PE. This was done manually using the DISM /Capture-Image command with the verify argument.
It created an image which I want to deploy through WDS.
Before we even get there, I try to deploy the image manually to test that it works using the DISM /Deploy-Image command. If I do this then it fails with error 13.
The thing is that if I copy this image file to my laptop locally, I am able to mount it successfully to an empty directory and browse the files.
Can anyone help?
imaging dism
asked May 2 at 8:35
RLBChrisBriantRLBChrisBriant
111
add a comment |
I am using DISM to capture a Windows image. I have successfully captured an image from the reference computer after running sysprep and booting from Windows PE. This was done manually using the DISM /Capture-Image command with the verify argument.
It created an image which I want to deploy through WDS.
Before we even get there, I try to deploy the image manually to test that it works using the DISM /Deploy-Image command. If I do this then it fails with error 13.
The thing is that if I copy this image file to my laptop locally, I am able to mount it successfully to an empty directory and browse the files.
Can anyone help?
imaging dism
asked May 2 at 8:35
RLBChrisBriantRLBChrisBriant
111
Looks like this can happen when dism runs out of scratch space. Have you tried using the /ScratchDir option to explicitly select which disk the scratch directory is on? It needs to be sufficiently large, IIRC then typically the best choice is the same disk you are deploying the image to.
– Harry Johnston
May 2 at 19:10
Same error unfortunately. I have created a scratch directory on the volume where the image file exists. I have ran the command as "dism /apply-image /scratchdir:D:scratch /imagefile:D:<imagefilename>.wim /index:1 /applydir:W:
– RLBChrisBriant
May 3 at 8:18
I have also since tried installing all the updates available onto the image and re-imaging.
– RLBChrisBriant
May 3 at 8:19
This is Windows 10 1809, are there any known issues as I was able to successfully image from a wim created of a Windows 10 1803 image. Both have been created in the same fashion. The 1809 image was created as a fresh install of this version of Windows, not an inplace upgrade.
– RLBChrisBriant
May 3 at 8:21
add a comment |
I am using DISM to capture a Windows image. I have successfully captured an image from the reference computer after running sysprep and booting from Windows PE. This was done manually using the DISM /Capture-Image command with the verify argument.
It created an image which I want to deploy through WDS.
Before we even get there, I try to deploy the image manually to test that it works using the DISM /Deploy-Image command. If I do this then it fails with error 13.
The thing is that if I copy this image file to my laptop locally, I am able to mount it successfully to an empty directory and browse the files.
Can anyone help?
imaging dism
asked May 2 at 8:35
RLBChrisBriantRLBChrisBriant
111
I am using DISM to capture a Windows image. I have successfully captured an image from the reference computer after running sysprep and booting from Windows PE. This was done manually using the DISM /Capture-Image command with the verify argument.
It created an image which I want to deploy through WDS.
Before we even get there, I try to deploy the image manually to test that it works using the DISM /Deploy-Image command. If I do this then it fails with error 13.
The thing is that if I copy this image file to my laptop locally, I am able to mount it successfully to an empty directory and browse the files.
Can anyone help?
imaging dism
imaging dism
asked May 2 at 8:35
RLBChrisBriantRLBChrisBriant
111
asked May 2 at 8:35
RLBChrisBriantRLBChrisBriant
111
asked May 2 at 8:35
RLBChrisBriantRLBChrisBriant
111
asked May 2 at 8:35
RLBChrisBriantRLBChrisBriant
111
asked May 2 at 8:35
RLBChrisBriantRLBChrisBriant
111
111
Looks like this can happen when dism runs out of scratch space. Have you tried using the /ScratchDir option to explicitly select which disk the scratch directory is on? It needs to be sufficiently large, IIRC then typically the best choice is the same disk you are deploying the image to.
– Harry Johnston
May 2 at 19:10
Same error unfortunately. I have created a scratch directory on the volume where the image file exists. I have ran the command as "dism /apply-image /scratchdir:D:scratch /imagefile:D:<imagefilename>.wim /index:1 /applydir:W:
– RLBChrisBriant
May 3 at 8:18
I have also since tried installing all the updates available onto the image and re-imaging.
– RLBChrisBriant
May 3 at 8:19
This is Windows 10 1809, are there any known issues as I was able to successfully image from a wim created of a Windows 10 1803 image. Both have been created in the same fashion. The 1809 image was created as a fresh install of this version of Windows, not an inplace upgrade.
– RLBChrisBriant
May 3 at 8:21
add a comment |
Looks like this can happen when dism runs out of scratch space. Have you tried using the /ScratchDir option to explicitly select which disk the scratch directory is on? It needs to be sufficiently large, IIRC then typically the best choice is the same disk you are deploying the image to.
– Harry Johnston
May 2 at 19:10
Same error unfortunately. I have created a scratch directory on the volume where the image file exists. I have ran the command as "dism /apply-image /scratchdir:D:scratch /imagefile:D:<imagefilename>.wim /index:1 /applydir:W:
– RLBChrisBriant
May 3 at 8:18
I have also since tried installing all the updates available onto the image and re-imaging.
– RLBChrisBriant
May 3 at 8:19
This is Windows 10 1809, are there any known issues as I was able to successfully image from a wim created of a Windows 10 1803 image. Both have been created in the same fashion. The 1809 image was created as a fresh install of this version of Windows, not an inplace upgrade.
– RLBChrisBriant
May 3 at 8:21
Looks like this can happen when dism runs out of scratch space. Have you tried using the /ScratchDir option to explicitly select which disk the scratch directory is on? It needs to be sufficiently large, IIRC then typically the best choice is the same disk you are deploying the image to.
– Harry Johnston
May 2 at 19:10
Looks like this can happen when dism runs out of scratch space. Have you tried using the /ScratchDir option to explicitly select which disk the scratch directory is on? It needs to be sufficiently large, IIRC then typically the best choice is the same disk you are deploying the image to.
– Harry Johnston
May 2 at 19:10
Same error unfortunately. I have created a scratch directory on the volume where the image file exists. I have ran the command as "dism /apply-image /scratchdir:D:scratch /imagefile:D:<imagefilename>.wim /index:1 /applydir:W:
– RLBChrisBriant
May 3 at 8:18
Same error unfortunately. I have created a scratch directory on the volume where the image file exists. I have ran the command as "dism /apply-image /scratchdir:D:scratch /imagefile:D:<imagefilename>.wim /index:1 /applydir:W:
– RLBChrisBriant
May 3 at 8:18
I have also since tried installing all the updates available onto the image and re-imaging.
– RLBChrisBriant
May 3 at 8:19
I have also since tried installing all the updates available onto the image and re-imaging.
– RLBChrisBriant
May 3 at 8:19
This is Windows 10 1809, are there any known issues as I was able to successfully image from a wim created of a Windows 10 1803 image. Both have been created in the same fashion. The 1809 image was created as a fresh install of this version of Windows, not an inplace upgrade.
– RLBChrisBriant
May 3 at 8:21
This is Windows 10 1809, are there any known issues as I was able to successfully image from a wim created of a Windows 10 1803 image. Both have been created in the same fashion. The 1809 image was created as a fresh install of this version of Windows, not an inplace upgrade.
– RLBChrisBriant
May 3 at 8:21
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
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%2fserverfault.com%2fquestions%2f965529%2fdism-can-mount-image-but-cant-apply-it%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f965529%2fdism-can-mount-image-but-cant-apply-it%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
Looks like this can happen when dism runs out of scratch space. Have you tried using the /ScratchDir option to explicitly select which disk the scratch directory is on? It needs to be sufficiently large, IIRC then typically the best choice is the same disk you are deploying the image to.
– Harry Johnston
May 2 at 19:10
Same error unfortunately. I have created a scratch directory on the volume where the image file exists. I have ran the command as "dism /apply-image /scratchdir:D:scratch /imagefile:D:<imagefilename>.wim /index:1 /applydir:W:
– RLBChrisBriant
May 3 at 8:18
I have also since tried installing all the updates available onto the image and re-imaging.
– RLBChrisBriant
May 3 at 8:19
This is Windows 10 1809, are there any known issues as I was able to successfully image from a wim created of a Windows 10 1803 image. Both have been created in the same fashion. The 1809 image was created as a fresh install of this version of Windows, not an inplace upgrade.
– RLBChrisBriant
May 3 at 8:21