locked
WinPE 5 error access denied when applying .wim RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello TechNet,

    I have been struggling with deploying surface pro 3s using DISM.  I keep receiving an access denied error when I try to apply a windows image to a brand new surface pro 3 using the latest version of DISM.  Any insight would be greatly appreciated.

    Regards,

    Thursday, November 20, 2014 8:14 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I will probably end up making a script to format the drive.  Maybe in the future I will move to MDT if I start doing bulk rollouts but since I'm only doing a few at a time its faster applying the image from an external drive.

    Thank you for your replies.


    • Edited by Isak Aronov Monday, December 8, 2014 2:17 PM
    • Marked as answer by Daniel JiSun Tuesday, December 9, 2014 1:13 AM
    Monday, December 8, 2014 2:17 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Are you using DISM to custom your install image?

    Please check permission of mounted folder, in addition check anti-virus software.

    Similar thread:

    Access Denied error when trying to add a driver to a x64 wim with DISM

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

    • Proposed as answer by Daniel JiSun Friday, November 28, 2014 5:43 AM
    Friday, November 21, 2014 6:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for the reply. 

    This is what I have done I; I have installed all software on my surface pro 3 and all drivers.  I used DISM rto capture that image.  Now I am trying to apply that image to another surface pro 3 that's new out of box and I get access denied error.  I looked at the DISM log and its getting an error when accessing the windowsapp folder.  I mounted the image and gave full access to system, administrators and truested installer to the "windows app" folder but I am still getting access denied error.  If I delete everything in that folder then the image works and I don't get any errors but that breaks all the windows apps.  I also tried uninstalling all the preloaded windows apps but that gave me an access is denied error also.  If I format the C:\ drive I can apply the image with out any issue but I want to be able to drop an image without having to format the drive.

    Monday, December 1, 2014 3:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You do not want to create a hardware specific image, you always build your image on a VM and load the drivers into the console to be deployed as driver packages.

    Microsoft recently released an OSD guide that goes over some basics. http://technet.microsoft.com/en-us/library/dn818437.aspx

    There are also lots of other guides out there for proper image creation and deployment.

    https://www.google.com/?gws_rd=ssl#safe=active&tbs=qdr:y&q=sccm+osd+image+build

    Daniel Ratliff | http://www.PotentEngineer.com

    Monday, December 1, 2014 4:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am only using surface pro 3s and I would like to skip the system setup part that's why I created a hardware specific image. Do you have any idea why I am getting the access denied error when applying the image to a brand new out of box surface pro3?
    Monday, December 1, 2014 4:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I looked at the DISM log and its getting an error when accessing the windowsapp folder.

    Are these app installed via windows store? Try to uninstall them before capturing the image if in that case.

    Tuesday, December 2, 2014 2:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    these are the default apps that come with a new surface pro 3.  I did uninstall them and gave full access permissions to system, trusted installer, and administrator group and I still got the same access denied error.  Does DISM use another account that I need to give access to? 

    Tuesday, December 2, 2014 5:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Since you have captured the image successfully, I doubt if the folder is causing problem. If you install this image with SCCM OSD please check smsts.log, and if you apply the image with DISM manually or use WDS you need check setupact.log.

    Wednesday, December 3, 2014 7:49 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Did you sysprep the image before you captured it?
    Wednesday, December 3, 2014 2:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    -Daniel

    Thanks for the reply Where can I find the setupact.log?

    I didn't sysprep it because I don't want it to go through the driver installation process because its the same hardware.

    Wednesday, December 3, 2014 2:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The logfile can be found in %windir%\Panther.

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, December 3, 2014 3:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I looked at the log file after running DISM but it didn't log anything current.  All the information is months old.
    Wednesday, December 3, 2014 4:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Ah, it may be that DISM isn't actually running. You may need to run a /cleanup command first. Give that a google.

    I remember having a similar issue a couple years ago. hopefully that helps.

    NN

    Wednesday, December 3, 2014 4:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I ran all the cleanup commands and created a new image. I then tried to apply the image and I got the same access denied error message.  I looked at the DISM log and it said:

    2014-12-03 12:54:26, Info                  DISM   DISM Provider Store: PID=912 TID=916 Getting Provider WimManager - CDISMProviderStore::GetProvider

    2014-12-03 12:54:26, Info                  DISM   DISM Provider Store: PID=912 TID=916 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

    [912] [0x80070005] RestoreDirMetadata:(3768): Access is denied.
    [912] [0x8144012d]

    2014-12-03 12:54:28, Warning               DISM   DISM WIM Provider: PID=912 [RestoreDirMetadata:(3774) -> Error restoring directory metadata] c:\Program Files\WindowsApps\Flipboard.Flipboard_2014.902.1532.705_neutral_~_3f5azkryzdbc4 (HRESULT=0x80070005) - CWimManager::WimProviderMsgLogCallback
    [912] [0x80070005] RestoreDirMetadata:(3904): Access is denied.
    [912] [0x80070005] WimCreateDirectory:(4384): Access is denied.
    [912] [0xc144012e]

    2014-12-03 12:54:28, Error                 DISM   DISM WIM Provider: PID=912 c:\Program Files\WindowsApps\Flipboard.Flipboard_2014.902.1532.705_neutral_~_3f5azkryzdbc4 (HRESULT=0x80070005) - CWimManager::WimProviderMsgLogCallback
    [912] [0x80070005] RestoreDirTree:(4665): Access is denied.
    [912] [0x80070005] WIMApplyImageInternal:(1069): Access is denied.

    2014-12-03 12:54:28, Error                 DISM   DISM WIM Provider: PID=912 TID=916 base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:1095 - CWimManager::Apply(hr:0x80070005)

    2014-12-03 12:54:28, Error                 DISM   DISM WIM Provider: PID=912 TID=916 base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:4205 - CWimManager::InternalCmdApply(hr:0x80070005)

    2014-12-03 12:54:28, Error                 DISM   DISM WIM Provider: PID=912 TID=916 Error executing command - CWimManager::InternalExecuteCmd(hr:0x80070005)

    2014-12-03 12:54:28, Error                 DISM   DISM WIM Provider: PID=912 TID=916 base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:1936 - CWimManager::ExecuteCmdLine(hr:0x80070005)

    2014-12-03 12:54:28, Error                 DISM   DISM.EXE: WimManager processed the command line but failed. HRESULT=80070005

    2014-12-03 12:54:28, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.

    2014-12-03 12:54:28, Info                  DISM   DISM.EXE:
    2014-12-03 12:54:28, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->

    I searched Google for those error messages but I couldn't find anything similar to what I am experiencing.

    Wednesday, December 3, 2014 7:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    If I format the C:\ drive I can apply the image with out any issue but I want to be able to drop an image without having to format the drive.

    Why not do this if it works? You could call a script at the beginning if you want this more automated.

    Ideally I would recommend you use MDT 2013 as it is a free tool. It would have taken the same time as this.

    My other guess would be that the WindowsApps is User specific in its metadata and no user but the original would have access. Maybe to prevent copying apps that need purchasing? Honestly, I don't know. But the above would be my advice.

    See this link for a how to: http://www.windows-noob.com/forums/index.php?/topic/11479-how-can-i-deploy-windows-81-x64-to-the-microsoft-surface-pro-3-using-mdt-2013/

    • Proposed as answer by Daniel JiSun Monday, December 8, 2014 1:15 AM
    Thursday, December 4, 2014 10:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I will probably end up making a script to format the drive.  Maybe in the future I will move to MDT if I start doing bulk rollouts but since I'm only doing a few at a time its faster applying the image from an external drive.

    Thank you for your replies.


    • Edited by Isak Aronov Monday, December 8, 2014 2:17 PM
    • Marked as answer by Daniel JiSun Tuesday, December 9, 2014 1:13 AM
    Monday, December 8, 2014 2:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This is some brutal and buggy implementation.

    I'm a developer, so I'll never use MDT since I just make some custom images occasionally. Whoever I give the image to will probably be using MDT but I won't.

    This bug should be fixed. The Imagex.exe tool in Windows 7 never had this problem, so what's up with DISM??

    Thursday, March 15, 2018 6:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    this is from 2014; stop it.
    Thursday, March 15, 2018 6:33 PM