The coolest new DISM command (to me at least)
Since I spoke about DISM in the last post, I wanted to highlight my personal favorite new DISM command.
DISM.exe /Image:C:\test\offline /Cleanup-Image /RevertPendingActions
Where this is handy is in situations where you have installed an update on an installation and the machine gets stuck applying "Stage 3 of 3". You can boot into WinRE in Windows 7, run this command against the installation from the command prompt and it should allow you to rollback the changes that the update was attempting to apply. When you enable this command and reboot, you should see a blue splash screen that shows the updates being reverted.
So, something cool for everyone running RC to play with while we finish up Windows 7. More DISM stuff to come soon.
Comments
Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Yes Drew, checking ofr the existence of a pending.xml would be your best bet. I like the idea of the command though. I'll bring it up in meetings.Anonymous
December 16, 2009
do you have any solutions to make dism.exe faster? driver injection is horribly slow for me when utilizing via sccm driver injection.Anonymous
February 16, 2011
A very useful command. Someone said: "4. Windows Vista and Server 2008 updates are numbered the same way (Windows6.0___). I understand the 2 OSes are serviced simultaneously and share the same kernel etc but updates' numbering should be differentiated so users can figure out what to install on what." Perhaps it would be better if WindowsVersion identifiers were used. msdn.microsoft.com/.../ff547089(v=vs.85).aspx Example: Server2008_X64-KB954768.msuAnonymous
February 27, 2011
Apart from when a system gets stuck applying "Stage X of Y", what would be the simplest method of determining if pending actions exist? Is it to look for the pending.xml file? How useful might a command like this be?: DISM.exe /Image:C:testoffline /Get-PendingActionsAnonymous
February 27, 2011
That would be much appreciated. Thanks Joseph.