Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form

Error 0xc1420117: The directory could not be completely unmounted

Posted on 24/10/202031/08/2026 Christian By Christian No Comments on Error 0xc1420117: The directory could not be completely unmounted
  1. Home
  2. Windows Server
  3. Error 0xc1420117: The directory could not be completely unmounted
Unmounting errors

Deployment Image Servicing and Management (DISM) is a tool that allows you to service your images offline. In this article, you will learn how to fix Error 0xc1420117: The directory could not be completely unmounted, this is usually due to applications that still have files open within the mount directory. Here are some DISM-related errors, Failure 5627: How to fix error 0x800f0805, run DISM executable. Also, see Error 0xc1420127: The specified image in the specified wim is already mounted for read and write access.

Before I proceed with the steps to resolve this issue, I would like to explain some key differences between mounting and unmounting a wim file. Suppose you need to change a WIM file by adding or removing packages.

In that case, you must mount it properly on Windows using DISM, a command line that enumerates, installs, uninstalls, configures, and updates features and packages in Windows images.

After you modify a mounted image, you must unmount it. If you mounted your image with the default read/write permissions, you can commit your changes. This makes your modifications a permanent part of the image.

See the following guides for more details on ADK, MDT, Microsoft Endpoint Configuration Manager (SCCM), Intune, Autopilot, and WSUS. Also, see how to configure and deploy Windows using Microsoft Deployment Toolkit, and Windows Deployment Services for Windows 10 (ADK, MDT, and WDS).

0xc1420117 Error Incomplete Unmounting Due to Open Files

You may encounter this issue when mounting an image (install.wim) file. The “0xc1420117 Error Incomplete Unmounting Due to Open Files” occurred when I tried to mount a new Windows image, due to leftover residue in the previous mount point.

0xc1420117 error

See the following hyperlink for more details on ADK, MDT, Microsoft Endpoint Configuration Manager (SCCM), Intune, Autopilot, and WSUS. Also, see how to configure and deploy Windows using Microsoft Deployment Toolkit, and Windows Deployment Services for Windows 10 (ADK, MDT, and WDS).

Step 1: Only perform this step if you have some residue folder left in the mounted directory (folder).

To resolve the 0xc1420117 error, delete these folders before mounting the wim file again. See this guide on going about this issue “The action cannot be completed because the folder or file is open in another program: How to determine where a file is open in windows“.

Step 2: Now that you’ve removed the folders. Execute the command to unmount the Windows Image (install.wim file), optimizing it for your environment.

Dism /Unmount-image /MountDir:<target_mount_directory> {/Commit | /Discard}

After unmounting the win file. You should be able to address the 0xc1420117 Error Incomplete Unmounting Due to Open Files and then proceed to mount your Windows image again.

Continue with the modification by using the command below. Please modify this command to reflect your information. For more information, see the following guide on how to mount and unmount a Windows image file.

DISM /Mount-Wim /WimFile:"filename.wim" /index:3 /MountDir:"c:\temp"

I hope you found this blog post on how to fix Error 0xc1420117: The directory could not be completely unmounted, this is usually due to applications that still have files open within the mount directory helpful. Please let me know in the comment session if you have any questions.

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
Windows Server Tags:DISM, WDS, Windows 10

Post navigation

Previous Post: Error 0x800f0830: Discard the modified Image and start again, no operation was performed
Next Post: Log Off: How to sign out of Windows Server 2012

Related Posts

  • dism failed errors windows thumbnail 1
    Error 0x800f0830: Discard the modified Image and start again, no operation was performed Windows Server
  • Keep personal files and apps
    Fix Keep personal files and apps option greyed out during Upgrade Windows Server
  • Secure Boot 2023 Compliance for wds e1781352448233
    Secure Boot 2023 Compliance Across WinPE, MDT, WDS, and ADK: Boot Chain Alignment and PXE Validation [Final Part] Windows
  • MBAM
    Fix MBAM Client Deployment is only supported on MBAM 2.5 SP1 Windows
  • windows update 03
    How to target WSUS clients with the registry keys Windows Server
  • images 8
    Microsoft Direct Access: Now Always On VPN Windows Server

More Related Articles

dism failed errors windows thumbnail 1 Error 0x800f0830: Discard the modified Image and start again, no operation was performed Windows Server
Keep personal files and apps Fix Keep personal files and apps option greyed out during Upgrade Windows Server
Secure Boot 2023 Compliance for wds e1781352448233 Secure Boot 2023 Compliance Across WinPE, MDT, WDS, and ADK: Boot Chain Alignment and PXE Validation [Final Part] Windows
MBAM Fix MBAM Client Deployment is only supported on MBAM 2.5 SP1 Windows
windows update 03 How to target WSUS clients with the registry keys Windows Server
images 8 Microsoft Direct Access: Now Always On VPN Windows Server

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

vexpert-badge-stars-5

Virtual Background

VEEAMLEGEND

Categories

veeaam100

Veeam Vanguard

  • windows 1 1
    Generation 2 VM: Set up a HyperV VM through PXE boot Virtualization
  • dfgh
    How to install Pleasant Password Server Password Manager
  • Featured image
    Exploring the Reasons to use or not use Screensavers in Windows Windows
  • Featured image Periodic scanning
    How to enable or disable Windows Defender Antivirus Scanning periodically on Windows via Windows Settings Security | Vulnerability Scans and Assessment
  • Slide1 1
    How to manage Microsoft Defender Antivirus using Group Policy and Command Line Utility Anti-Virus Solution
  • veeam
    Error 1064: An exception occurred in the service when handling the control request Backup
  • How to Fix Microsoft Edge Not Responding on Windows 11
    How to Fix Microsoft Edge Not Responding on Windows 11 Network | Monitoring
  • Norton Antivirus Free Download For Mac 1st
    How to fix repeated app-blocking connection alerts from Norton on Mac Mac

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,757 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Contact
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon
  • Bsky

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2026 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.