Table of Contents
This tutorial provides instructions on how to Fix “DISM Error 50” issue on Windows 11/10 that occurs when the DISM command “Dism.exe /Online /Cleanup-Image /Restorehealth” is executed from the Windows Recovery Environment: “Error 50, DISM does not support servicing Windows PE with the /Online option” . Resolving this error on your computer can be accomplished in a number of different ways. Windows PE is one of the many things that can cause this error to appear on your personal computer.
We will walk you through the steps to take in order to continue troubleshooting your Windows 11 or Windows 10 system, as well as show you what to do when this error appears on your screen. The aforementioned error has occurred due to the fact that the operating system is not running in WinRE, which means that the /Online switch is effectively useless in this scenario. We mentioned below are the simple ways how to Fix “DISM Error 50” issue on Windows 11/10.
Causes of the “DISM Error 50” issue on Windows 11/10
- Corrupted system files: If system files essential for DISM (Deployment Image Servicing and Management) operation are corrupted, it can lead to Error 50.
- Disk errors: Errors on the disk where Windows is installed may prevent DISM from functioning correctly.
- Third-party antivirus: Sometimes, third-party antivirus programs can interfere with DISM operations, causing Error 50.
- Insufficient permissions: If the user account running DISM doesn’t have sufficient permissions, it may result in Error 50.
- Software conflicts: Conflicts with other software installed on the system can also trigger this error.
- Outdated Windows version: Using an outdated version of Windows 11/10 may lead to compatibility issues with DISM, resulting in Error 50.
How to Fix “DISM Error 50” issue on Windows 11/10
Run DISM with Administrative Privileges
- Press Windows Key + X and select Command Prompt (Admin) or Windows PowerShell (Admin) from the menu.
- In the command prompt, type:
DISM /Online /Cleanup-Image /RestoreHealth
and press Enter. - Allow the process to complete, which might take some time depending on your system’s condition.
Perform System File Checker (SFC) Scan
- Open Command Prompt (Admin) or Windows PowerShell (Admin) as in the previous step.
- Type:
sfc /scannow
and press Enter. - Let the scan finish, and follow any instructions prompted upon completion.
Check Windows Update Service
- Press Windows Key + R to open the Run dialog.
- Type:
services.msc
and press Enter. - Locate Windows Update service from the list.
- Right-click on it and select Start if it’s not already running.
Perform a Clean Boot
- Press Windows Key + R to open the Run dialog.
- Type:
msconfig
and press Enter. - In the System Configuration window, navigate to the Services tab.
- Check Hide all Microsoft services, then click Disable all.
- Go to the Startup tab and click Open Task Manager.
- Disable all startup items one by one.
- Restart your computer and attempt to run DISM again.
Use DISM with Install.wim
- Insert your Windows installation media (USB/DVD).
- Open Command Prompt (Admin) or Windows PowerShell (Admin).
- Type:
DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:X:\Sources\Install.wim:1 /LimitAccess
(Replace X with your drive letter) and press Enter. - Allow the process to complete without interruptions.
Perform a System Restore
- Press Windows Key + S, type System Restore, and select Create a restore point from the results.
- In the System Properties window, click System Restore.
- Follow the on-screen instructions to choose a restore point and initiate the process.
Conclusion
When you attempt to execute DISM (Deployment Image Servicing and Management) commands on your personal computer, you are informed of a “Error: 50” message. You don’t need to worry for us. In addition to explaining why it happens in the first place, we will also walk you through the steps necessary to fix it on Windows 11 and Windows 10.
Questions and Answers
The occurrence of a generic error during the process of Windows attempting to write data to the disc results in the logging of an event ID 50 message. The occurrence of this error takes place when Windows is attempting to commit data from the Cache Manager of the file system to the physical disc, rather than the hardware level cache. The management of memory in Windows includes this behaviour as a required component.
If this error occurs, what causes it? It would appear that the DISM utility is operating under the assumption that you are executing the commands during Windows PE or Windows RE. However, in reality, you are operating the tool on an operating system that is already running. The root cause of this issue is a registry key that was misplaced.
By utilising the /ResetBase parameter in conjunction with the /StartComponentCleanup parameter of DISM.exe on a computer running Windows 10 or a later version, it is possible to eliminate all obsolete versions of each and every component that is stored in the component store.