DISM Scan Stuck at 62.3%. Fails With Message “The Source Files Could Not Be Found.” In Windows FIX

DISM Scan Stuck at 62.3%: How to Fix the "The Source Files Could Not Be Found" Error in Windows

If you are a Windows user and have ever encountered issues with system integrity, you may have used the Deployment Image Servicing and Management (DISM) tool. It’s a powerful utility for repairing Windows images and managing system files. However, running a DISM scan can sometimes lead to frustrating errors, such as the scan getting stuck at 62.3% with the message “The source files could not be found.” In this article, we will delve into the reasons for this issue and provide step-by-step instructions to fix it.

Understanding DISM and Its Purpose

The DISM tool is designed to help administrators and advanced users maintain and repair Windows operating systems. It can perform various tasks, such as:

  • Deploying Windows images: Use DISM to work with Windows Installation files.
  • Servicing and managing Windows images: Apply updates and make changes to Windows images offline.
  • Repairing system files: Fix corruption issues in the Windows component store.

When you encounter the “The source files could not be found” error during a DISM scan, it indicates that the tool is unable to access the files it needs to fix the system corruption or damage. Often, this issue occurs when the system files that DISM requires are not available or accessible, possibly due to file corruption, missing files, or incorrect configurations.

Why Does DISM Get Stuck at 62.3%?

The stalling at 62.3% is a well-documented problem experienced by many Windows users. This percentage corresponds to the process where the DISM tool attempts to connect to the Windows Update servers to download the files necessary to complete the scanning and repair process. If this part of the process encounters issues, it can lead to the scan freezing.

Several reasons can contribute to this situation:

  1. Corrupted System Files: Existing corruption in the Windows Operating System may hinder DISM from completing its operations.

  2. Insufficient Permissions: Sometimes, administrative permissions are needed to execute DISM commands. Lack of necessary permissions can lead to failures in execution.

  3. Windows Update Issues: If your machine has problems connecting to Windows Update, DISM may not find the files it needs online.

  4. Network Problems: Poor or unstable network connections can interrupt the communication between DISM and the update servers, causing a timeout.

  5. Incorrect Source Path: If you have specified a source path for the repair files that is incorrect or doesn’t exist, DISM will not be able to proceed.

  6. Third-party Software Conflicts: Some antivirus or system optimization tools can interfere with DISM’s operations.

Preliminary Steps Before Fixing

Before diving into the fixes for the DISM issue, there are some preliminary steps you should take:

  1. Check for Windows Updates: Ensure your Windows Operating System is fully updated. Sometimes, upcoming patches can resolve issues with built-in tools like DISM.

    • Go to Settings > Update & Security > Windows Update.
    • Click Check for updates and install any available updates.
  2. Run SFC Scan First: Before using DISM, running a System File Checker (SFC) scan could help fix corrupted system files.

    • Open the Command Prompt as an administrator.
    • Type sfc /scannow and press Enter.
    • Wait for the scan to complete. If it finds corrupted files, it will attempt to repair them.
  3. Ensure Stable Internet Connection: To perform an online repair, DISM requires a stable internet connection. Make sure that your connection is consistent before proceeding.

Fix #1: Use a Windows Installation Media

If the DISM tool fails to find source files, you can provide the required files manually using Windows installation media. Here’s how to do this:

Steps:

  1. Create a Windows Installation Media: Use another computer to download the Media Creation Tool from the official Microsoft website and create bootable USB or DVD.

  2. Locate the Install.wim file:

    • Insert the installation media.
    • Open File Explorer and navigate to the drive where the installation media is located, usually the E: or F: drive.
    • Locate the sources folder. Inside, you’ll find the install.wim or install.esd file. Note the path to this file.
  3. Open Command Prompt as Administrator:

    • Click on the Start menu.
    • Type cmd, right-click on Command Prompt, and select Run as Administrator.
  4. Run the DISM command with Source Path:

    DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:E:sourcesinstall.wim:1 /LimitAccess

    Replace E: with the letter of your installation media drive.

  5. Wait for the Process to Complete: This may take some time, so be patient.

Using the installation media can bypass the issues related to downloading the necessary files online, thus providing a more reliable source.

Fix #2: Use Local Source Files from Another Windows PC

If you have access to another Windows PC with the same version and build, you can copy the install.wim from that system:

Steps:

  1. Get install.wim from Another PC:

    • On the source PC, navigate to C:WindowsSystem32sources and copy the install.wim file to a removable drive.
  2. Insert the Removable Drive: Plug the removable drive into the affected PC.

  3. Follow the steps in Fix #1: Use the copied install.wim file on the affected PC as you would with the installation media.

This method ensures you are using the correct and compatible system files.

Fix #3: Reset Windows Update Components

Corrupted Windows Update components can often cause network-related issues for DISM. Resetting these components can potentially resolve the issue:

Steps:

  1. Open Command Prompt as Administrator:

    • Type cmd in the Start menu, right-click, and select Run as Administrator.
  2. Run the Following Commands:

    net stop wuauserv
    net stop cryptSvc
    net stop bits
    net stop msiserver
    net stop appidsvc
    
    net start wuauserv
    net start cryptSvc
    net start bits
    net start msiserver
    net start appidsvc
  3. After Running the Commands, Restart Your Computer: Upon reboot, try running the DISM command again.

Fix #4: Check Disk for Errors

Sometimes, disk errors can prevent DISM from running smoothly. Using the Check Disk (CHKDSK) utility can help:

Steps:

  1. Open Command Prompt as Administrator.

  2. Run the CHKDSK Command:

    chkdsk C: /f /r
  3. Restart the Computer: If it prompts you to schedule the scan for the next restart, you can agree.

  4. Once the Scan Completes: Try running the DISM command again.

Fix #5: Disable Antivirus Temporarily

Third-party antivirus software can sometimes cause interference with system utilities like DISM. Temporarily disabling your antivirus might allow DISM to complete its process without hindrance:

Steps:

  1. Locate the Antivirus Icon: Find the antivirus icon in the system tray.

  2. Right-click on the Icon: Choose the option to either disable protection for a specific duration or exit.

  3. Run DISM Again.

  4. Re-enable Your Antivirus After Completion: It’s crucial to turn your antivirus back on after the process is complete to ensure your system remains protected.

Fix #6: Perform a Repair Install

If none of the previous fixes work, performing a repair installation of Windows may be the best course of action. This process reinstalls Windows files without affecting your personal files.

Steps:

  1. Download Windows 10 Installation Media: Use the Media Creation Tool from Microsoft’s website.

  2. Run the Setup: Open the downloaded file and follow the prompts.

  3. Choose the Repair Option: When prompted, choose to "Keep personal files and applications" to ensure no data loss occurs.

  4. Follow Through with the Installation: Completing this will reset system files and resolve many issues, including the DISM error.

Conclusion

Experiencing a DISM scan stuck at 62.3% with the message “The source files could not be found” can be frustrating, especially if you are trying to maintain system integrity. However, by understanding the potential causes and implementing the solutions provided above, you can effectively resolve this issue. Always ensure to back up your data before performing any major repairs, and consider creating restore points to safeguard against unexpected errors.

If, after following all these steps, you are still encountering errors, it may be worthwhile to seek professional support or consider a system reset or clean installation, depending on your specific needs. Remember, keeping your system files intact is crucial for a healthy computing experience.

Leave a Comment