DISM Sloowwwww

So, I've boot.wim
mount: ~ 2 minutes (not too bad)
unmount ~ 20 minutes
install.wim
mount ~ 5 minutes
unmount ~ 40 minutes I've noticed that file. Also, C:\Documents and \Dism.exe" Deployment Image Version: 6.1.7600.16385
Image File : D:\rmfisher\2008 Image Index : 1
Then, once it eventually These are the commands "C:\Program "C:\Program Any ideas would EDIT:
Here is some more 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info 2011-04-24 10:19:41, Info had to upgrade my Windows WIAK to start using it with server 2008 R2, and it seems that imageX is not there anymore, so I've been using DISM, and it is SO SLOW to mount and unmount images. I see the following times with:
(AND STILL WAITING!)
if I kill the process and reboot the server and try again it will unmount faster. Looking at resource manager, the server is basically sitting idle and not doing anything, so it's not like it's grinding the disks through the image
this install.wim image that I'm trying to unmount now, it seems to hang at the following:
Settings\rmfadmin>"C:\Program Files\Windows AIK\Tools\Servicing
/unmount-wim /Mountdir:D:\mount /commit
Servicing and Management tool
R2\install.wim
starts showing a progress bar, it runs at an acceptable pace. So, something is causing it to hang when it's first starting this process. This happens with any .wim file I try to mount/unmount. ImageX worked so well!
I'm using to mount and unmount:
Files\Windows AIK\Tools\Servicing\Dism.exe" /mount-wim /wimfile:"D:\rmfisher\2008 R2\install.wim" /index:1 /mountdir:d:\mount
Files\Windows AIK\Tools\Servicing\Dism.exe" /unmount-wim /Mountdir:D:\mount /commit
be great! Thanks!
infor from the log file I have it generating during unmounting. I have it set at level 4. This is where the log sits when the process shows that it's just sitting at Image Index 1
DISM PID=4360 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
DISM PID=4360 Scratch directory set to 'C:\DOCUME~1\rmfadmin\LOCALS~1\Temp\1\'. - CDISMManager::put_ScratchDir
DISM PID=4360 Local image session has not been created, creating now. - CDISMManager::CreateLocalImageSession
DISM PID=4360 Attempting to load the Dism stack from "C:\Program Files\Windows AIK\Tools\Servicing" - CDISMManager::LoadImageSession
DISM PID=4360 Successfully loaded the ImageSession at "C:\Program Files\Windows AIK\Tools\Servicing" - CDISMManager::LoadImageSession
DISM DISM Provider Store: PID=4360 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
DISM DISM Provider Store: PID=4360 The requested provider was not found in the Provider Store. - CDISMProviderStore::Internal_GetProvider(hr:0x80004005)
DISM DISM Provider Store: PID=4360 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
DISM DISM Provider Store: PID=4360 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
DISM DISM Provider Store: PID=4360 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
DISM DISM Provider Store: PID=4360 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
DISM DISM Image Session: PID=4360 Obtained the local logger instance. Configured the local session to use it. - CDISMImageSession::get_ProviderStore
DISM DISM Provider Store: PID=4360 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
DISM DISM Provider Store: PID=4360 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
DISM DISM Manager: PID=4360 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
DISM DISM Provider Store: PID=4360 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
DISM DISM Provider Store: PID=4360 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
DISM DISM.EXE:
DISM DISM.EXE: <----- Starting Dism.exe session ----->
DISM DISM.EXE:
DISM DISM.EXE: Host machine information: OS Version=5.2.3790, Running architecture=x86, Number of processors=1
DISM DISM.EXE: Executing command line: "C:\Program Files\Windows AIK\Tools\Servicing\Dism.exe" /unmount-wim /Mountdir:D:\mount /commit /LogPath:"D:\rmfisher\2008 R2\dismunmountlog.txt" /LogLevel:4
DISM DISM Provider Store: PID=4360 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! - CDISMProviderStore::GetProviderCollection
DISM DISM Provider Store: PID=4360 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
DISM DISM Provider Store: PID=4360 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! - CDISMProviderStore::GetProviderCollection
DISM DISM Provider Store: PID=4360 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
DISM DISM Provider Store: PID=4360 Loading Provider from location C:\Program Files\Windows AIK\Tools\Servicing\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
DISM DISM Provider Store: PID=4360 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\Servicing\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
DISM DISM Provider Store: PID=4360 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
DISM DISM Provider Store: PID=4360 Loading Provider from location C:\Program Files\Windows AIK\Tools\Servicing\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
DISM DISM Provider Store: PID=4360 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\Servicing\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
DISM DISM Provider Store: PID=4360 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
DISM DISM Provider Store: PID=4360 Loading Provider from location C:\Program Files\Windows AIK\Tools\Servicing\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
DISM DISM Provider Store: PID=4360 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\Servicing\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
DISM DISM.EXE: Attempting to add the commands from provider: WimManager
DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.
DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
DISM DISM.EXE: FolderManager does not support command lines.
DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
DISM DISM.EXE: DISM Log Provider does not support command lines.
DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
DISM DISM Provider Store: PID=4360 Getting Provider WimManager - CDISMProviderStore::GetProvider
DISM DISM Provider Store: PID=4360 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

Hi,
Have you tested it on another Windows Server 2008 R2 computer?
Tim Quan

Similar Messages

Dism - The directory could not be completely unmounted - process explorer can't find open processes and unmounting fails

Hi all,
Installed WAIK on server 2008 R2 64 bit. I'm setting up some boot images, and am having a real hard time getting drivers to integrate into the driver store in the boot images.
What I'm finding is that when adding drivers to the boot image the gui hangs part way through over 50% of the time using Dell 760 or HP NX9420 drivers extracted to pull out the inf files. It's really flakey and will work after a couple of attempts and when the wind is right.
The main problem is that when the process fails the image is left open, so using dism to list mounted images and then umount the open images is the only way to try again.
However, some images won't unmount and the unmount process displays the following:
C:\Windows\system32>dism /get-mountedwiminfo
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Mounted images:
Mount Dir : C:\Users\davros\AppData\Local\Temp\~$WDSMGMT.000
Image File : \\DAVROS.stafflib.flinders.edu.au\REMINST\Boot\x86\Images\boot-(2).
wim
Image Index : 2
Mounted Read/Write : Yes
Status : Invalid
The operation completed successfully.
C:\Windows\system32>dism /unmount-wim /mountdir:C:\Users\davros\AppData\Local\Te
mp\~$WDSMGMT.000 /discard
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image File : \\DAVROS.stafflib.flinders.edu.au\REMINST\Boot\x86\Images\boot-(2).
wim
Image Index : 2
Unmounting image
[==========================100.0%==========================]
Error: 0xc1420117
The directory could not be completely unmounted. This is usually due to applica
tions that still have files opened within the mount directory. Close these file
s and unmount again to complete the unmount process.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Using process explorer shows no running processes that have the files open and the dism.log file shows:
2009-12-16 11:49:35, Error                 DISM   DISM WIM Provider: PID=5580 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimimage.cpp:75 - CWimImage::Unmount(hr:0xc1420117)
2009-12-16 11:49:35, Error                 DISM   DISM WIM Provider: PID=5580 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:1068 - CWimManager::InternalOpUnmount(hr:0xc1420117)
2009-12-16 11:49:35, Error                 DISM   DISM WIM Provider: PID=5580 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2318 - CWimManager::InternalCmdUnmount(hr:0xc1420117)
2009-12-16 11:49:35, Error                 DISM   DISM WIM Provider: PID=5580 Error executing command - CWimManager::InternalExecuteCmd(hr:0xc1420117)
2009-12-16 11:49:35, Error                 DISM   DISM WIM Provider: PID=5580 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:516 - CWimManager::ExecuteCmdLine(hr:0xc1420117)
2009-12-16 11:49:35, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2009-12-16 11:49:35, Info                  DISM   DISM.EXE:
2009-12-16 11:49:35, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2009-12-16 11:49:35, Info                  DISM   DISM.EXE:
2009-12-16 11:49:35, Info                  DISM   DISM Image Session: PID=5580 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2009-12-16 11:49:35, Info                  DISM   DISM Provider Store: PID=5580 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2009-12-16 11:49:35, Info                  DISM   DISM Provider Store: PID=5580 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2009-12-16 11:49:35, Info                  DISM   DISM Provider Store: PID=5580 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2009-12-16 11:49:35, Info                  DISM   DISM Provider Store: PID=5580 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2009-12-16 11:49:35, Info                  DISM   DISM Provider Store: PID=5580 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
Rebooting the server clears the lock, but it's really becoming a joke, as I can create a boot image with the drivers, but then going back into add another driver causes the gui to not respond.
Any suggestions gratefully accepted. - Matt.

Hi all,
had same problem unmounting the wim file using Windows 7 Pro 32bit.
My solution was: Checking for "wrong" Dism.exe
Preparing a WinPE I followed the steps in the help of AIK. I ran the
copype.cmd batch. When it was finished, it said that it added something
to the path environment variable. It was clear that it did so in order
to find the tools needed for the further steps. As long as everything
worked, I didn't give it a second thought. Then I could not unmount the
WIM.
I looked at the PATH variable: NO entry pointed to the directory where
dism.exe was in. (In my case that would have been
     c:\program files\windows aik\tools\x86\servicing
Magically, dism.exe started from everywhere though.
Doing a      dir c:\dism.exe /s /a     showed I had a Dism.exe in
c:\windows\system32, as well. This one has a file size different from
the correct one. Obviously I had started this one (because PATH points
there).
Starting the correct dism.exe let me unmount the WIM without problems.
Regards,
Robert

Win 8.1 Pro dism /Online /Cleanup-Image /RestoreHealth returns Error: 14098

I am running Windows 8.1 Pro and have recently been experiencing some odd behavior. This has lead me to discover that my component store is corrupt.
I have attempted to use sfc with no luck and have posted that on a separate thread.
When I attempt to use dism /online /cleanup-image /retorehealth, dism quickly comes back with Error: 14098.
Event the dism log looks corrupt. Below is just the beginning of the file. the not English character portion continues and is quite large:
[2580] Caller did not request sparse mount
[2580] Mounting new image.
Wim: [\\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim]
Image Index: [1]
Mount Path: [C:\WINDOWS\TEMP\c18ce950-f10f-4afc-a811-28b1ffe5b733]
[2580] Wimserv process started for guid b3e8550e-9dd9-4246-855b-f0ac5d1c531f. Id is 956
[956] ImageUnmarshallHandle: Reconstituting wim at
\\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.
[956] Mounted image at C:\WINDOWS\TEMP\c18ce950-f10f-4afc-a811-28b1ffe5b733.
[2580] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[2580] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[2580] [0xc142011c] WIMGetMountedImageHandle:(2568)
[2580] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[2580] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[2580] [0xc142011c] WIMGetMountedImageHandle:(2568)
[2580] ImageUnmarshallHandle: Reconstituting wim at
\\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.
[2580] ImageUnmarshallHandle: Reconstituting wim at
\\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.
〲㌱ㄭⴰ㠱ㄠ㨵㘲〺ⰷ䔠牲牯††††††††䐠卉⁍†䥄䵓䐠楲敶⁲慍慮敧㩲倠䑉㤽㈵吠䑉㈽㠷‸慆汩摥琠⁯湩瑳污⁬桴⁥牤癩牥瀠捡慫敧✠㩃坜湩潤獷卜獹整㍭尲牄癩牥瑓牯履
Is partition1 the "System Reserved" partition? Could it be corrupted and if so, can it be repaired or rebuilt?
Any ideas or help would be greatly appreciated.
Thanks,
Glen

Honestly this is something MS should check into. There should be an easier way for users to implement this command rather then a complete dictionary to fix broken windows files. This is a Microsoft windows problem. I know for myself I had to use this command
quite often because I installed something windows did not like. Because of that window files became unusable. It would make practical sense for Microsoft to incorporate a feature that runs these commands in administration tools.
Run
Dism /Online /Cleanup-image/ScanHealth
if that runs an error then run
Dism /Online /Cleanup-Image /StartComponentCleanup
then run
dism /online /cleanup-image /retorehealth
http://technet.microsoft.com/en-us/library/dn251565.aspx
Edit: Microsoft has to make a serious decision. During setup, Metro, or desktop. Installing items in desktop mode is creating errors in Metro or windows store items. In future upgrades consider the flavors of OS, implement a users
choice. Desktop, Metro, or classic. Face the facts if you follow Linux method of desktop, and the install process. There is no confusion between desktops and we have a choice. This makes common sense. I like the feature of gnome or Ubunto it gives
the user a choice and a better picture for Microsoft. Lets face it, Bill Gates choose to hand over his business to people. This gave Bill Gates time to help other people that need help. How about Microsoft do the same and give people the choice between
desktops during install. Follow Bill Gates important roll in his life now. Bring some fairness and happiness to people that like Microsoft and what to help users get what they want and the best support they need. Doing this allows Microsoft the glory
to help people feel good about themselves. Sure MS can live in a dictatorship roll and continue to bully users to use the product, there is a consequence to this. Good young developers are working on a better OS and this is going to happen. It is better
to help people then to fight people.

Unable to capture C drive using Dism and imageX commands

I am trying to capture C drive using dism command but it did not work, but the same command is capturing E drive. i am using following command.
dism /Capture-Image /ImageFile:E:\image.wim /CaptureDir:C:\ /name:"Image File"
I am getting following error.
Deployment Image Servicing and Management tool
Version: 6.3.9431.0
Error: 32
The process cannot access the file because it is being used by another process.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
An in the log file the error is: DISM DISM.EXE: WimManager processed the command line but failed. HRESULT=80070020

Hi,
As far as I know, Dism command doesn't support hot image backup, that to say, you do need to complete the image backup job at Windows PE enviroment.
The contents of the link below also list the Dism command capture image requirement：
http://technet.microsoft.com/en-us/library/hh825072.aspx
Roger Lu
TechNet Community Support

Access Denied Error:5 Adding Package to .WIM with DISM

I am trying to add .CAB packages to a custom .wim file. I am able to mount the image, but upon trying to add .cab packages to the image, it gives me an error like:
An error occurred - Package_for_KB2588516 Error: 0x80070005
Error: 5
Access is denied.
Here is a segment of the DISM.log. I can post the full Logfile if needed. I am running the command prompt with elevated privileges.
2012-02-10 11:58:45, Info                  CBS    Failed to delete registry value: LastProgressState [HRESULT = 0x80070005 - E_ACCESSDENIED]
2012-02-10 11:58:45, Info                  CBS    Failed to delete store object value named: LastProgressState [HRESULT = 0x80070005 - E_ACCESSDENIED]
2012-02-10 11:58:45, Info                  CBS    Failed to delete registry value: LastError [HRESULT = 0x80070005 - E_ACCESSDENIED]
2012-02-10 11:58:45, Info                  CBS    Failed to delete store object value named: LastError [HRESULT = 0x80070005 - E_ACCESSDENIED]
2012-02-10 11:58:45, Info                  CBS    Failed to delete registry value: ExtendedError [HRESULT = 0x80070005 - E_ACCESSDENIED]
2012-02-10 11:58:45, Info                  CBS    Failed to delete store object value named: ExtendedError [HRESULT = 0x80070005 - E_ACCESSDENIED]
2012-02-10 11:58:45, Info                  CBS    Failed to persist status for package: Package_for_KB2588516~31bf3856ad364e35~x86~~6.1.1.1 [HRESULT = 0x80070005
- E_ACCESSDENIED]
2012-02-10 11:58:45, Info                  CBS    Failed to delete registry value: ExtendedError [HRESULT = 0x80070005 - E_ACCESSDENIED]
2012-02-10 11:58:45, Info                  CBS    Failed to delete store object value named: ExtendedError [HRESULT = 0x80070005 - E_ACCESSDENIED]
2012-02-10 11:58:45, Info                  CBS    Failed to query sources for package: Package_for_KB2588516~31bf3856ad364e35~x86~~6.1.1.1 [HRESULT = 0x80070005
- E_ACCESSDENIED]
2012-02-10 11:58:45, Info                  CBS    Failed to persist package: Package_for_KB2588516~31bf3856ad364e35~x86~~6.1.1.1. [HRESULT = 0x80070005 -
E_ACCESSDENIED]
2012-02-10 11:58:45, Info                  CBS    Failed to delete registry value: LastProgressState [HRESULT = 0x80070005 - E_ACCESSDENIED]
2012-02-10 11:58:45, Info                  CBS    Failed to delete store object value named: LastProgressState [HRESULT = 0x80070005 - E_ACCESSDENIED]

Hi,
If you plan on using DISM to install a .cab file, it is recommended that you use the WUSA.exe tool to extract the files to a directory first.
Make sure that the permission setting of the temp folder that save the mounted image allows the user to modify.
Make sure that you run the command lines in a prompt window with Administrator privilege.
If the issue persists, you’d better consider to change with another image.
The following operating-system-package servicing options are available for a mounted offline image:
DISM.exe /image:<path_to_mounted_image_directory> [/Get-Packages | /Get-PackageInfo | /Add-Package | /Remove-Package ] [/Get-Features | /Get- FeatureInfo | /Enable-Feature | /Disable-Feature ]
The following operating system package servicing options are available for a running operating system:
DISM.exe /online [/Get-Packages | /Get-PackageInfo | /Add-Package | /Remove-Package ] [/Get-Features | /Get-FeatureInfo | /Enable-Feature | /Disable- Feature ]
Pay attention to the following please.
1. You cannot use a network share location as a scratch directory to expand a package (.cab or .msu file) for installation. The directory used for extracting files for temporary usage during servicing must be a local directory.
2. If subsequent actions are requested, they cannot be processed until the previous pending online action is completed.
3. If a package is in the “installed requested” state and then you stage the package, the package state is set to “uninstall requested”. This is because it must be uninstalled before it can be staged.
4. Some packages require other packages to be installed first. Because of this dependency requirement, you should use an answer file if you are installing multiple packages.
Hope that helps.

How to install MSFT application security updates in cab file format using DISM

Hi,
I tried to install security updates for MS Office which are cab files like any other windows security updates cab file. It is giving an error called "file not found". But other windows security updates cab files are installing fine without any error.
I tried to install these updates manually using DISM on commandline. It is not installing. I even tried using pkgmgr.exe, but that is not working either. I looked at DISM logs which is saying it failed opening the cab file. I tried different other commandline
options of DISM to install this, but nothing else is suitable for a cab file install.
Does anyone know how to install a cab file for application security updates via DISM.exe or other MSFT commandline tools?
Thanks,
ANSA
DISM log:
=======
2015-02-25 14:42:59, Info                  DISM   PID=4916 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2015-02-25 14:42:59, Info                  DISM   PID=4916 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadImageSession
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Failed to get and initialize the PE Provider. Continuing by assuming that
it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Manager: PID=4916 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM.EXE:
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2015-02-25 14:42:59, Info                  DISM   DISM.EXE:
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=4
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Executing command line: "C:\Windows\System32\Dism.exe" /online /add-package /packagepath:"C:\ProgramData\Application
Data\Autonomic\ANSA Patch Manager\_Installs\mscomctlocx-x-none_8699d53bec82460b948612f4f35d2f6a0ad018f4.cab" /ignorecheck /norestart
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=4916 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Manager: PID=4916 Successfully loaded the ImageSession at "C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B"
- CDISMManager::LoadImageSession
2015-02-25 14:42:59, Info                  DISM   DISM Image Session: PID=11836 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\OSProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\OSProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM OS Provider: PID=11836 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2015-02-25 14:42:59, Info                  DISM   DISM OS Provider: PID=11836 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\LogProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\LogProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Getting Provider OSServices - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\PEProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Warning               DISM   DISM Provider Store: PID=11836 Failed to Load the provider: C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\PEProvider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Failed to get and initialize the PE Provider. Continuing by assuming that
it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Manager: PID=4916 Image session successfully loaded from the temporary location: C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B
- CDISMManager::CreateImageSession
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Getting Provider OSServices - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_OBJECT_PATH_NOT_FOUND
2015-02-25 14:42:59, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_SUCCESS
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Target image information: OS Version=6.1.7601.17592, Image architecture=amd64
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\CbsProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\CbsProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_OBJECT_PATH_NOT_FOUND
2015-02-25 14:42:59, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_SUCCESS
2015-02-25 14:42:59, Info                  DISM   DISM Package Manager: PID=11836 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2015-02-25 14:42:59, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_OBJECT_PATH_NOT_FOUND
2015-02-25 14:42:59, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_SUCCESS
2015-02-25 14:42:59, Info                  DISM   DISM Package Manager: PID=11836 CBS is being initialized for online use. More information about CBS actions can
be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2015-02-25 14:42:59, Info                  DISM   DISM Package Manager: PID=11836 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\MsiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\MsiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\IntlProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\IntlProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\DmiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\DmiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_OBJECT_PATH_NOT_FOUND
2015-02-25 14:42:59, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_SUCCESS
2015-02-25 14:42:59, Info                  DISM   DISM OS Provider: PID=11836 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2015-02-25 14:42:59, Info                  DISM   DISM Driver Manager: PID=11836 Further logs for driver related operations can be found in the target operating
system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\UnattendProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                 DISM   DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\UnattendProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\SmiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\SmiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\TransmogProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\TransmogProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2015-02-25 14:42:59, Info                  DISM   DISM Transmog Provider: PID=11836 Current image session is [ONLINE] - CTransmogManager::GetMode
2015-02-25 14:42:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info                  DISM   DISM Package Manager: PID=11836 Processing the top level command token(add-package). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2015-02-25 14:42:59, Info                  DISM   DISM Package Manager: PID=11836 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2015-02-25 14:42:59, Info                  DISM   DISM Package Manager: PID=11836 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2015-02-25 14:42:59, Info                  DISM   DISM Package Manager: PID=11836 Encountered the option "packagepath" with value "C:\ProgramData\Application
Data\Autonomic\ANSA Patch Manager\_Installs\mscomctlocx-x-none_8699d53bec82460b948612f4f35d2f6a0ad018f4.cab" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
2015-02-25 14:42:59, Error                 DISM   DISM Package Manager: PID=11836 Failed opening package. - CDISMPackageManager::Internal_CreatePackageByPath(hr:0x80070002)
2015-02-25 14:42:59, Error                 DISM   DISM Package Manager: PID=11836 Failed to get the underlying CBS package. - CDISMPackageManager::OpenPackageByPath(hr:0x80070002)
2015-02-25 14:42:59, Error                 DISM   DISM Package Manager: PID=11836 Failed to open the package at location: "C:\ProgramData\Application Data\Autonomic\ANSA
Patch Manager\_Installs\mscomctlocx-x-none_8699d53bec82460b948612f4f35d2f6a0ad018f4.cab" - CPackageManagerCLIHandler::ProcessPackagePath(hr:0x80070002)
2015-02-25 14:42:59, Error                 DISM   DISM Package Manager: PID=11836 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070002)
2015-02-25 14:42:59, Info                  DISM   DISM Package Manager: PID=11836 Further logs for online package and feature related operations can be found at
%WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2015-02-25 14:42:59, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070002
2015-02-25 14:42:59, Info                  DISM   DISM Image Session: PID=11836 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Package Manager: PID=11836 Finalizing CBS core. - CDISMPackageManager::Finalize
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Found the OSServices. Waiting to finalize it until all other providers are
unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Found the PE Provider. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Found the OSServices. Waiting to finalize it until all other providers are
unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info                  DISM   DISM Provider Store: PID=11836 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:43:00, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2015-02-25 14:43:00, Info                  DISM   DISM.EXE:
2015-02-25 14:43:00, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2015-02-25 14:43:00, Info                  DISM   DISM.EXE:
2015-02-25 14:43:00, Info                  DISM   DISM Image Session: PID=4916 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2015-02-25 14:43:00, Info                  DISM   DISM Provider Store: PID=4916 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:43:00, Info                  DISM   DISM Provider Store: PID=4916 Found the OSServices. Waiting to finalize it until all other providers are
unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-02-25 14:43:00, Info                  DISM   DISM Provider Store: PID=4916 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

You need to extract and install it - Refer this link
http://blogs.technet.com/b/askcore/archive/2011/02/15/how-to-use-dism-to-install-a-hotfix-from-within-windows.aspx
Regards Chen V [MCTS SharePoint 2010]

How to change the name and description of a wim using DISM

With Imagex we could update the name and description of the wim with on easy command:
imagex /info img_file [img_number or
img_name] [new_name] [new_desc]
e.g.
imagex /info Win7Combined.WIM 1 "Win7(x86)" "Windows 7 x86"
Since the ImageX tool is deprecated in Windows 8 and has been replaced with DISM, can someone explain how to update the name and description with one easy command using DISM like we could with Imagex?

It looks like this person had the same issue. Have you seen this
link
It talks about exporting an Index into a new WIM. Which, in a way, would be renaming it. It's really recreating it and you have to give it a name. But it seems to work.
Dustin Estes - MCP | www.dustinestes.com

Error when running DISM /Online /Cleanup-Image /RestoreHealth - error 0x800f0906

Hello.
I wonder if you can help me.
I keep getting error 0x800f0906 when running DISM /Online /Cleanup-Image /RestoreHealth.
DISM /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.2.9200.16384
Image Version: 6.2.9200.16384
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required to restore the feature.
For more information, review the log file.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
relevant bits from it seem to be:
Checking System Update Readiness.
(p)   CSI Payload Corrupt           amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.8.9200.16927_none_28265fa316d944b7\wuaext.dll
Repair failed: Missing replacement payload.
(p)   CSI Payload Corrupt           amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.8.9200.16927_none_28265fa316d944b7\wushareduxresources.dll
Repair failed: Missing replacement payload.
Summary:
Operation: Detect and Repair
Operation result: 0x800f0906
Last Successful Step: Entire operation completes.
Total Detected Corruption:   2
   CBS Manifest Corruption:   0
   CBS Metadata Corruption:   0
   CSI Manifest Corruption:   0
   CSI Metadata Corruption:   0
   CSI Payload Corruption:   2
Total Repaired Corruption:   0
   CBS Manifest Repaired:   0
   CSI Manifest Repaired:   0
   CSI Payload Repaired:   0
   CSI Store Metadata refreshed:   True
In adition, my windows 8 will not carry out a scheduled maintenance session.
Is this something I can repair. Any help would be appreciated. The setup event logs mentions 2 errors, so presumably this is the issue.

Use the "source" option to specify the location of the files that are required to restore the feature."
If we read the documentation, we might infer we can use any existing WinSxS as source?
http://technet.microsoft.com/en-us/library/hh825265.aspx
<quote>
You can restore and enable a feature that has previously been removed from the image. Use the
/Source argument to specify the location of the files that are required to restore the feature. The source of the files can by the Windows folder in a mounted image, for example c:\test\mount\Windows. You can also use a Windows side-by-side
folder as the source of the files, for example z:\sources\SxS.
If you specify multiple /Source arguments, the files are gathered from the first location where they are found and the rest of the locations are ignored. If you do not specify a
/Source for a feature that has been removed, the default location in the registry is used or, for online images, Windows Update (WU) is used.
Use /LimitAccess to prevent DISM from contacting WU for online images.
</quote>
That quote was actually from under the /Enable-Feature operand but the /Source: operand has wider scope.
Compare the briefer description of the same operand given later under the /Cleanup-Image operand
<quote>
Use /Source with /RestoreHealth to specify the location of known good versions of files that can be used for the repair, such as a path to the Windows directory of a mounted image.
If you specify multiple /Source arguments, the files are gathered from the first location where they are found and the rest of the locations are ignored. If you do not specify a
/Source for a feature that has been removed, the default location in the registry is used or Windows Update (WU) is used for online images.
Use /LimitAccess to prevent DISM from contacting WU for repair of online images.
</quote>
Does this mean the functionality is limited or that they were just trying to avoid being redundant?   ; }
Good luck
Robert Aldwinckle

2012 R2 Essentials Windows Update error 80072EE2 and Dism errors 0x800f0906 and 0x800f081f

Since 11/2014 our R2 Essentials server on ESXI has been unable to run Windows Update, returning error 80072EE2. I ran the Windows Update troubleshooter which claimed it fixed something, but Windows Update returned the exact same error again. There are no
proxies or Internet access problems. I have ensured no firewall is blocking Windows Update URLs. So I tried the
sfc /scannow command which reports a file that cannot be repaired:
2015-01-12 20:56:41, Info CSI 00000801 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
For this error others suggested running dism /Online /Cleanup-Image /ScanHealth which on my server tells me "The component store is repairable." So next I run
Dism /Online /Cleanup-Image /CheckHealth which instantly returns the same result that it is repairable. Next I run
DISM.exe /Online /Cleanup-image /Restorehealth thinking this will fix it, but it returns this error: "Error 0x800f0906 source files could not be downloaded".
Articles suggest I use a different source, so I mount the R2 Essentials DVD used to install this server to drive letter Z: and use this command:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:Z:\sources\sxs /LimitAccess
This results in the error "Error 0x800f081f source files could not be found" and so I copy the sources\sxs folder locally to C: and re-run the last command pointing to this new location. I get the same error.
I have run chkdsk and I have tried rebooting between each of the above commands, which did not work. I have run all these commands as Administrator.
Does anyone know what I do next? I see references to these errors with several users attempting to install .NET framework but those solutions do not apply to my situation.
As a next step I considered uninstalling the last successfully installed Windows update (KB3011780) on this machine in case it broke something. Thoughts?

Hi,
Please refer to following KB and reset Windows Update components, then check if can help you to solve this issue.
How do I reset Windows Update components?
In addition, did you check relevant log files (such as: DISM.log, CBS.log or others) whether find more clues?
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How to change screen refresh rate in windows 7sp1 and windows 8.1 iso image using dism

sir when i install windows 7sp1 and windows 8.1 then after the completion of setup when first time windows boots up then task bar is not shown and display is not clear and when i check under monitor settings the screen refresh rate is 60 Hertz and when i
set the screen refresh rate from 60 Hertz to 75 Hertz, then everything is OK, plz tell me why this happens?
why windows 7 sp1 and windows 8.1 automatically sets the screen refresh rate to 60Hertz instead of 75Hertz.
how can i set screen refresh rate 75 Hertz permanently in iso image using DISM ?

That is not a function of DISM. Resolution and refresh rate capabilities can be determined by multiple causes. Drivers are one, another is that most modern displays will report their capabilities to Windows.
You can specify display settings with an answer file however:
<Display>
<HorizontalResolution>640</HorizontalResolution>
<VerticalResolution>480</VerticalResolution>
<ColorDepth>16</ColorDepth>
<RefreshRate>60</RefreshRate>
</Display>
http://technet.microsoft.com/en-us/library/ff716344.aspx

PE dism error - failed to get and initialize the PE provider

This all started with: Win 8.1 could not be installed. error code 0X8007003. I ran DISM successfully with the /RestoreHealth flag, but it made no difference to installing Win 8.1. I ran DISM again (successfully) and looked at the log for "fails".
The repeated fail was:
2011-06-10 10:12:47, Warning DISM DISM Provider Store: PID=2552 Failed to Load the provider: C:\Users\ROSMAR~1\AppData\Local\Temp\0709052E-4C8D-43AD-B837-FB57E1CF832A\PEProvider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2011-06-10 10:12:47, Info DISM DISM Provider Store: PID=2552 Failed to get and initialize the PE Provider. Continuing by assuming that it
is not a WinPE image. - CDISMProviderStore::Final_OnConnect
How can I fix this? Is this the reason I can't install Win 8.1? Should I be looking at something else to fix whatever is generating error code 0X8007003?
Thanks.

WIM format changed in Win 8.1. You need to use the DISM from the ADK from Windows 8.1. Older versions of DISM cannot service drivers or packages for example.

DISM reports corruption, repair-windowsimage states HEALTHY

I have been working a several Windows 8.1 systems regarding issues. Some state out of memory (which it does not have), just black screen when sitting for a while. I have run dism /online /cleanup-image /restorehealth which consistently states it fixed "component
store corruption was repaired" but never does. The powershell cousin to the command (repair-windowsimage) states "Image Health State" is HEALTHY. I know the commands have very minimal differences and believe they execute the same exe but runs
just a bit different.
HELP!

Hi willrow,
Basically the Repair-WindowsImage command is under DISM Cmdlets so there is no difference.
I think you might have little misunderstand about dism /online /cleanup-image /restorehealth
This is a command which perform a whole system components repair but not a health checking.
The health checking command is dism /online /cleanup-image /checkhealth
and I think it will give same result with PowerShell.
Regards

DISM gives Error 11

I have been running MS systems since you needed to 5-1/4' floppies to boot them. I know the difference between 32-bit and 64-bit systems. This one has me a bit frazzled.
When I run Dism.exe, I consistently get the following error:
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Error: 11
You cannot service a running 64-bit operating system with a 32-bit version of DISM.
Please use the version of DISM that corresponds to your computer's architecture.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
It's obvious that the command that's loading is the 32-bit version. I scanned the hard drive and found several versions of DISM.exe. Each time I get the same error, regardless of which DISM.exe I execute. Each time I was in an "elevated" cmd environment.
I even tried going into Powershell and running it. Same problem. I have checked the path, just to be sure. sysWOW64 appears before system32 in the path variable. I have tried running dism.exe from each individual location on the drive, just to make sure
the "local" command is/was being executed. Same error.
The reason for this is that sfc /scannow found some corrupted files it could not repair. I wanted to run the DISM command, then rerun the sfc command.
Where can I find the 64-bit version of dism.exe? It should be on the hard drive somewhere or at least you would think so.
I also tried running Powershell and the Repair-WindowsImage -Online -RestoreHealth. It failed with a similar error.
Outside of these commands, I will likely have to restore Windows 8.1 and start over.
What prompted all this was the laptop started doing some flaky things. For example, when you try to open a cmd environment, the system would just stall and restart explorer.exe after a few minutes. This happened repeatedly. I was finally able to get a cmd
environment to open from the directory where the command is located. After that, it worked flawlessly. Similar things were happening trying to run other commands/features. This all started after installation of one of the MS security patches.
At this point, wiping the system and starting with a clean slate may be the best option.
Oh - system running Windows 8.1, latest patches. HP Laptop 750GB HD, 6GB RAM, i3 processor.
Bob
Bob C., OCP

Okay... don't take this wrong, but "I didn't fall off the truck yesterday"! I will admit that I had not tried the solution you suggested, but I do know how to open a command environment, etc. I tried your suggestion and that's when I got
the message below - "Access denied".
I think I have found the root cause of this problem:
I started perusing the system in general. I checked everything from A to Z. Then, it hit me when I got an error message "Access Denied..." message.
I checked my access to the system and found that my account (not the System Administrator account) had been changed from an Administrator to a Standard User. That's easy enough to fix. WRONG! I logged in as the Administrator and found that I could no longer
change an account from a Standard to an Administrator role. How this happened, I do not know. I have not gotten any viruses or malware - I check every week with Norton, then Malwarebytes. I know some things can get by one product, but there is a slim chance
that it would get by two products. But, I digress...
I checked the Administrator access to the suspect folders. The Administrator account has NO access to the Windows folder. I have full access to the "C" drive, but ZERO access almost all the subsequent folders. Yes, I can list folder contents, etc.
But, I cannot change anything. For example, the c:\windows folder is set to Read Only. Just for grins, I tried to change it... wouldn't allow it.
I did find that the only account that has FULL access to everything is the TrustedInstaller account. Sounds suspicious...
Okay, while still logged in as Administrator, I went to Control Panel>User Accounts>Manage Another Account and tried to change my "usual" account from a Standard User to an Administrator User. It won't let me, as the Administrator Role/User
is greyed out. Mind you, this is from the Administrator account to another user.
I found several instances of this on the internet. I have tried the "fixes" I found, but thus far it has been a "no go." I am beginning to think the only way out of this is a system refresh, i.e., backup all my files and re-install the
OS.
I am going to give this one final shot from a "clean boot" with network access. If that doesn't work, I am looking at a backup and reload.
Any ideas/suggestions will apprecisted.
Bob
Bob C., OCP

DISM restorehealth error 14098

We have a windows server 2012 box that is hosted remotely. I've been trying to install a security patch and the windows update component appears to be corrupted. The error code i'm getting is 80073712. It will download the updates but fails to install them.
Installing manually with msu file doesn't work either. So far the steps i've taken are
run the microsoft fix it tools. It says that it fixed the problems, but then it just fails again.
Rename/delete the SoftwareDistribution folder in the windows folder
Use the Dism command to try and repair it- dism /online /cleanup-image /restorehealth This cause an error 14098. The component store has been corrupted
Used the equivalent command in powershell
I downloaded a server 2012 iso directly from microsoft and mounted it to try and use the /source switch to repair using the iso. Now I haven't really seen a lot of good examples of what the syntax should be for this. This is the command i was trying to
use:
DISM /online /cleanup-image /restorehealth /source:wim:D:\sources\install.wim:2
2 is the index number for server standard, which is what we are running. I get the same result, error 14098
Now i also tried this in powershell with this command:
Repair-WindowsImage -Online -RestoreHealth -Source:Wim:D\Sources\install.com:2. I get an error stating the component store is corrupted.
So i'm not sure where to go from this point. I don't even know if i have the syntax right for it to use the install disk as the source file. Any help is appreciated. If there is some other method i haven't thought about maybe

Hi BradSwink1,
Could you try to use elevated command prompt to run sfc /scannow and dism /online /cleanup-image /restorehealth, most times the corrupt files may cause the
14098 error.
The similar thread:
DISM /restoreHealth fails with 0x800f081f AFTER 8.1 update successfully installed
http://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/dism-restorehealth-fails-with-0x800f081f-after-81/a83650a9-c515-4bb8-aa7d-298be85e7bc3
Windows KB2802618 update error, then DISM error 14098
http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_update/windows-kb2802618-update-error-then-dism-error/cb5d53e6-82dd-4064-b762-517268bcf158
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How to run: system32 dism/online /cleanup-image /restorehealth

I can run this on my Window's 8.1 pc but not on my Windows 7 pc.

Hi,
correct me if I am wrong, but I think that /restorehealth applies only to:
Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2
Please take a look at this link: http://technet.microsoft.com/en-us/library/hh824869.aspx
I tried DISM on my PC and this is what I am getting when I run: DISM /online /cleanup-image /?
PS C:\windows\system32> dism /online /cleanup-image /?
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7600.16385
/Cleanup-Image /RevertPendingActions
WARNING! This operation will revert pending actions from previous servicing
operations. It should be used for recovery operations only. This command
is not supported against an online image.
Example:
DISM.exe /Image:C:\test\offline /Cleanup-Image /RevertPendingActions
/Cleanup-Image /spsuperseded [/hidesp]
WARNING! The service pack can't be uninstalled after this operation is
completed. This operation will remove backup files created during service
pack installation. Use /hidesp switch to hide the service pack from Installed
Updates.
Example:
DISM.exe /Image:C:\test\offline /Cleanup-Image /spsuperseded /hidesp

DISM Sloowwwww

Similar Messages

Maybe you are looking for