You may see “Unable to access the image ” when reading or writing via DISM. In this guide, we shall discuss the fix to “Unable to access the image: Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder”. For a similar issue, see how to resolve “Error 740: Elevated permissions are required to run DISM“. Click here to learn more. Also see, You require permission from trustedinstaller: How to delete or rename files protected by Trusted Installer.

DISM is a utility for advanced users to clean, slim, backup, update, or recover their Windows operating system. Unable to access the image? Explore DISM.exe, a Windows image servicing and PE preparation command-line tool.

Also, see How to Monitor Windows Hosts via Nagios, and Trend Micro WorryFree Business Security Server Setup.

Reason for the error “Unable to access the image”

In my case, this error was that I thought I had already mounted the image “install.wim”, and then ran a script against the presumed mounted install image. Therefore the error “Unable to access the image.

Prompted by the issue, ensure the image path, Windows directory exist, and have Read permissions on the folder. Here is a similar error that might be of interest to you: Error 0xc1510111: You do not have permissions to mount and modify this image

Note: To confirm what I have just spoken about. The DISM log file can be found at this location C:\windows\Logs\DISM\dism.log. You may also want to check how this error was resolved: Error 0xc1420127: The specified image in the specified wim is already mounted for read and write access.

Below is the log output. As you can see from the error log, the “DISM.EXE: Failed to access the image folder or image’s windows folder”.

These are some related errors you can encounter when mounting images: Error 0x80070002: When trying to mount an image file. Also, see how to fix error 0xc1510114: The wim file needs to be remounted.

[10392.14636] [0x80070002] FIOReadFileIntoBuffer:(1456): The system cannot find the file specified.
[10392.14636] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)
[10392.14636] [0xc142011c] WIMGetMountedImageHandle:(2910)
2022-04-13 11:47:11, Info                  DISM   DISM WIM Provider: PID=10392 TID=14636 [X:\DISMMOUNT] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2022-04-13 11:47:11, Info                  DISM   DISM FFU Provider: PID=10392 TID=14636 [X:\DISMMOUNT] is not recognized by the DISM FFU provider. - CFfuImage::Initialize
2022-04-13 11:47:11, Info                  DISM   DISM VHD Provider: PID=10392 TID=14636 [X:\DISMMOUNT] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2022-04-13 11:47:11, Error                 DISM   DISM.EXE: Failed to access the image folder or image's windows folder.
2022-04-13 11:47:11, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2022-04-13 11:47:11, Info                  DISM   DISM.EXE: 
2022-04-13 11:47:11, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2022-04-13 11:47:11, Info                  DISM   DISM.EXE:

Here is how you can mount an image with DISM. You may also want to see this guide: How to remove Microsoft Defender update on Windows 10 and Windows Server image

Resolution

Ensure the install image is mounted before trying to run scripts against the “presumed” mounted image. Wish to unmount an image, please see this link. Also, wish to learn how to discard and commit changes to the mounted images, please visit this link.

dism /Mount-Wim /WimFile:G:\Path-to-the-install.wim-file\install.wim /Index:2 /MountDir:G:\Path-to-the-mount-file\MountZ

After the file has been mounted. You can now start running scripts against it such as removing the pre-provisioned apss from the image.

I hope you found this blog post on ‘Unable to access the image: Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder” very helpful. If you have any questions, please let me know in the comment session.