offline dism

Hi All,

Paul will know this one off the top of his head!

I have been reading articles that are confusing about how to run DISM in
PE mode (cmd from installation media). C: gets moved to D: in PE mode

I need to know the proper PE run string for

/Cleanup-Image /RestoreHealth

Many thanks,
-T

T wrote:
Hi All,

Paul will know this one off the top of his head!

I have been reading articles that are confusing about how to run DISM in
PE mode (cmd from installation media). C: gets moved to D: in PE mode

I need to know the proper PE run string for

/Cleanup-Image /RestoreHealth

Many thanks,
-T

It might be something like this, identifying the
drive letter at the time. The first is online, the second
offline.

dism /Online /cleanup-image /revertpendingactions

dism /image:c:\ /cleanup-image /revertpendingactions

You can try the usual for more details:

dism /?

When you boot WinPE, the X: drive is the boot media
itself, leaving the other letters for drives. Sometimes
the regular windows drive is C: . Sometimes it's D: .
You may on occasion have to do

dism /image:d:\ /cleanup-image /revertpendingactions

in cases where the target didn't happen to be C: . This
can happen on dual boot setups. (People who play old
16-bit games, might keep both a 32-bit and 64-bit
Windows install.)

And the example command above, is used for backing out
an update that refuses to allow the computer to boot.
You can stop an in-flight update.

Paul

On 12/17/18 3:40 AM, Paul wrote:
T wrote:
Hi All,

Paul will know this one off the top of his head!

I have been reading articles that are confusing about how to run DISM
in PE mode (cmd from installation media).Â* C: gets moved to D: in PE mode

I need to know the proper PE run string for

Â*Â*Â*Â*Â*Â*Â* /Cleanup-Image /RestoreHealth

Many thanks,
-T

It might be something like this, identifying the
drive letter at the time. The first is online, the second
offline.

Â*Â* dism /Online /cleanup-image /revertpendingactions

Â*Â* dism /image:c:\ /cleanup-image /revertpendingactions

You can try the usual for more details:

Â*Â* dism /?

When you boot WinPE, the X: drive is the boot media
itself, leaving the other letters for drives. Sometimes
the regular windows drive is C: . Sometimes it's D: .
You may on occasion have to do

Â*Â* dism /image:d:\ /cleanup-image /revertpendingactions

in cases where the target didn't happen to be C: . This
can happen on dual boot setups. (People who play old
16-bit games, might keep both a 32-bit and 64-bit
Windows install.)

And the example command above, is used for backing out
an update that refuses to allow the computer to boot.
You can stop an in-flight update.

Â*Â* Paul




So far what I have seen is

dism /image:c:\ /cleanup-image /restorehealth
/source:wim:X:\sources\install.wim:1

But I am confused at to what points where. \windows
is now d:\windows. X: is the PE disk's boot media.
C: is the PE Windows directory.

So in the above, how does it know to look to d:\windows?
Whose image in on /image:c:\?

I should play with this on my W10 VM as I don't care
what happens to it and I can just restore its disk
from backup.

On 12/17/18 3:26 PM, T wrote:
IÂ*shouldÂ*playÂ*withÂ*thisÂ*onÂ*myÂ*W10Â*VMÂ*asÂ* IÂ*don'tÂ*care
whatÂ*happensÂ*toÂ*itÂ*andÂ*IÂ*canÂ*justÂ*restore *itsÂ*disk
fromÂ*backup.


Crap. The ISO won't boot in qemu-kvm:

Bug 1655167 - qemu-kvm will not boot Windows 10-1809 x64 USB
https://bugzilla.redhat.com/show_bug.cgi?id=1655167

T wrote:
On 12/17/18 3:26 PM, T wrote:
I should play with this on my W10 VM as I don't care
what happens to it and I can just restore its disk
from backup.


Crap. The ISO won't boot in qemu-kvm:

Bug 1655167 - qemu-kvm will not boot Windows 10-1809 x64 USB
https://bugzilla.redhat.com/show_bug.cgi?id=1655167

There are other virtual machine environments.

Note that you can typically *install* more than one VM
host, but you cannot simultaneously *run* two of them.
Such is verboten. There are regular hypervisors and
inverted bypervisors, and for the more common case,
you can only run one host at a time.

*******

Do you absolutely need a source ?

dism /image:c:\ /cleanup-image /restorehealth /source:wim:X:\sources\install.wim:1

Maybe I'm remembering the regular OS version
consulting a Microsoft server or something as an "Online" repair.
This one didn't use a source and you ran this from
the running OS.

dism /Online /cleanup-image /restorehealth

I don't recollect having to point it to a WIM when /online.

I do remember in the past running SFC /scannow and needing
to have a disc loaded for it to use, and specifying a letter
for that.

The /image option should point to "the thing needing repair".

It's your job to "dir c:" "dir d:" and
make sure you've got your target lined up properly.

X: is what the installer disc or the emergency WinPE disc would
boot from. The X: was chosen specifically so it would not
conflict with C: (for a single boot default case). And while you
might assume that C: was always C: , that's not my experience.
I've had to do /image:d:\ for some stuff.

Since many environments don't support partition labels
the way they should, I've taken to dropping "IM_WINXP.txt"
on a WinXP OS partition. Then when I "dir" later,
I know I'm on the correct partition when fixing
something. On another partition, it would be "WIN10RLS.txt"
or "WIN10INS.txt".

Paul

On 12/17/18 4:30 PM, Paul wrote:
T wrote:
On 12/17/18 3:26 PM, T wrote:
I should play with this on my W10 VM as I don't care
what happens to it and I can just restore its disk
from backup.


Crap.Â* The ISO won't boot in qemu-kvm:

Bug 1655167 - qemu-kvm will not boot Windows 10-1809 x64 USB
https://bugzilla.redhat.com/show_bug.cgi?id=1655167

There are other virtual machine environments.

Note that you can typically *install* more than one VM
host, but you cannot simultaneously *run* two of them.
Such is verboten. There are regular hypervisors and
inverted bypervisors, and for the more common case,
you can only run one host at a time.

I will just stick with qemu-kvm and wait for RedHat
to fix the bug I posted. Usually they respond pretty
quick.



*******

Do you absolutely need a source ?

Â*Â* dism /image:c:\ /cleanup-image /restorehealth
/source:wim:X:\sources\install.wim:1

Maybe I'm remembering the regular OS version
consulting a Microsoft server or something as an "Online" repair.
This one didn't use a source and you ran this from
the running OS.

Â*Â* dism /Online /cleanup-imageÂ* /restorehealth

I don't recollect having to point it to a WIM when /online.

I do remember in the past running SFC /scannow and needing
to have a disc loaded for it to use, and specifying a letter
for that.

The /image option should point to "the thing needing repair".

It's your job to "dir c:" "dir d:" and
make sure you've got your target lined up properly.

X: is what the installer disc or the emergency WinPE disc would
boot from. The X: was chosen specifically so it would not
conflict with C: (for a single boot default case). And while you
might assume that C: was always C: , that's not my experience.
I've had to do /image:d:\ for some stuff.

Since many environments don't support partition labels
the way they should, I've taken to dropping "IM_WINXP.txt"
on a WinXP OS partition. Then when I "dir" later,
I know I'm on the correct partition when fixing
something. On another partition, it would be "WIN10RLS.txt"
or "WIN10INS.txt".

Â*Â* Paul

Hi Paul,

Next one I have to repair, I will try:

dism /image:d:\ /cleanup-image /restorehealth
/source:wim:X:\sources\install.wim:1

And next crashed upgrade:

dism /image:d:\ /cleanup-image /revertpendingactions

Thank you for all the help!

-T

On 12/17/18 4:14 PM, T wrote:
On 12/17/18 3:26 PM, T wrote:
IÂ*shouldÂ*playÂ*withÂ*thisÂ*onÂ*myÂ*W10Â*VMÂ*asÂ* IÂ*don'tÂ*care
whatÂ*happensÂ*toÂ*itÂ*andÂ*IÂ*canÂ*justÂ*restore *itsÂ*disk
fromÂ*backup.


Crap.Â* The ISO won't boot in qemu-kvm:

Bug 1655167 - qemu-kvm will not boot Windows 10-1809 x64 USB
https://bugzilla.redhat.com/show_bug.cgi?id=1655167



Red Hat fixed it in their Preview Repository (qemu 3.1.0)
https://fedoraproject.org/wiki/Virtu...iew_Repository

On 12/16/18 10:04 PM, T wrote:
Hi All,

Paul will know this one off the top of his head!

I have been reading articles that are confusing about how to run DISM in
PE mode (cmd from installation media).Â* C: gets moved to D: in PE mode

I need to know the proper PE run string for

Â*Â*Â*Â*Â*Â*Â* /Cleanup-Image /RestoreHealth

Many thanks,
-T

Followup:

Now that I have a VM that will boot the W10-1809 iso and
can tet, these worked:

Offline method from installation media in PE mode (C: moves to D:

sfc /scannow /offbootdir=D:\ /offwindir=D:\windows
dism /image:d:\ /cleanup-image /restorehealth
/source:wim:X:\sources\install.wim:1

Stop a pending upgrade/update (c: moves to d: in PE mode)
dism /image:d:\ /cleanup-image /revertpendingactions

Thanks to everyone especially Paul for their tips and help,
-T