Mounting a wim using DISM error "A required privilege is not held by the client.

First off, I do not know what "client" they mean.
Second, I have tried this on 3 different machines, Win 7 DISM and Win 8.1 Dism, elevated cmd promt, i have local and net admin rights.  We are on a domain.  When trying to mount a wim file i get "A required privilege is not held by the client" message / error.  3 dif wim files, multiple mount locations attemped.
Part of my DISM log file:
[10672] Mounting new image.
Wim:         [k:\win7test.wim]
Image Index: [1]
Mount Path:  [e:\wims\mount]
[10672] [0xd0000061] WimApplyPrivileges:(3209)
[10672] [0xd0000061] RestoreAllData:(2424)
[10672] [0xd0000061] WIMApplyImageInternal:(1189)
[10672] [0x80070522] ImageStubMountDirectory:(296): A required privilege is not held by the client.
[10672] [0x80070522] WIMMountImageHandle:(1061): A required privilege is not held by the client.
2015-12-08 08:41:39, Error                 DISM   DISM WIM Provider: PID=10672 TID=1444 Failed to mount the image. - CWimImageInfo::Mount(hr:0x80070522)
2015-12-08 08:41:39, Error                 DISM   DISM Imaging Provider: PID=10672 TID=1444 base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:795 - CGenericImagingManager::InternalOpMount(hr:0x80070522)
2015-12-08 08:41:39, Error                 DISM   DISM Imaging Provider: PID=10672 TID=1444 base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:715 - CGenericImagingManager::InternalCmdMount(hr:0x80070522)
2015-12-08 08:41:39, Error                 DISM   DISM Imaging Provider: PID=10672 TID=1444 base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:51
No idea how to fix this.  Any help would be greatly appreciated.

5 Comments   [ + ] Show comments
  • so the drive your using, k:, that is available from the elevated CMD?? - Badger 5 years ago
  • Yes, I did net use to k: example test this morning:
    C:\windows\system32>net use k: \\\wims
    The command completed successfully.


    Volume in drive K is WIMs
    Volume Serial Number is 1F20-2FF5

    Directory of K:\

    10/14/2015 07:11 AM <DIR> .
    12/11/2015 02:09 PM <DIR> ..
    02/27/2015 10:58 AM 12,493,098,914 Win8ProBase.wim
    03/24/2015 04:02 PM 9,583,072,255 Win7ProBase.wim
    09/03/2015 04:07 PM 13,544,366,996 os-scanpro.wim
    10/14/2015 07:11 AM 8,591,746 wess-vm-win7.wim
    4 File(s) 35,629,129,911 bytes
    2 Dir(s) 6,819,901,325,312 bytes free


    C:\Windows\System32>dism /mount-image /imagefile:k:\win7probase.wim /index:1 /mo

    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031

    Error: 1314

    A required privilege is not held by the client.

    The DISM log file can be found at C:\windows\Logs\DISM\dism.log

    C:\Windows\System32> - wessdf 5 years ago
  • I am able to mount the image with my laptop that is not on the domain, but connected to the network and using my domain credentials to access the wims, (copy them to my laptop) - wessdf 5 years ago
  • so, you have it all sorted now?? - Badger 5 years ago
  • Not really, I'd like to be able to do this on my Technician PC that is on the domain, not my laptop which is not. I guess that is my "Workaround" lol - wessdf 5 years ago

Answers (1)

Posted by: BHC-Austin 5 years ago
4th Degree Black Belt

I had a similar issue. I traced it back to our anti-virus software. Specifically, we have McAfee VirusScan Enterprise, and the "Access Protection" feature. One of the default settings is to "Prevent Windows Process Spoofing", which was blocking DISM from creating the various Windows system files in the mount directory. We ended up creating a separate Access Protection Policy for our Desktop Engineers' PCs that added DISM.exe as an exception.

You may want to check your anti-virus to make sure it's not doing something similar, and if it is, add DISM.exe as an exception (but only on the PCs that would be doing this function).

  • Thanks, ill give our AV a look and let you know. - wessdf 5 years ago
  • No go. Made exception in Trend, turned Trend off on Tech PC, reboot etc. Still get same error message. - wessdf 5 years ago
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ