What is DISM exe?

DISM stands for the Deployment Image Servicing and Management (DISM.exe) tool in Windows. DISM is a Windows command-line tool used to service, prepare and repair Windows images, including those used for Windows Recovery Environment (Windows RE), Windows PE,  and Windows Setup.

What is DISM.exe?

DISM.exe is the file executable that helps deploy important and necessary images from the DISM utility. It is a safe, secure tool and does not cause any trouble or threat to your PC.

dism.exe command

Generally, the DISM tool can be used to fix common Windows PC issues. For example, it can be used to service or repair a Windows image (.wim) or even a virtual hard disk (.vhd or .vhdx).

Where is DISM.exe?

DISM.exe is a Windows image repair tool. It comes built into the Windows Operating System. It is generally available through the command line (Command Prompt) or from Windows PowerShell.

If you need to use the DISM.exe tool, you will just launch the Command Prompt or Windows PowerShell and type the command line you want to execute. The DISM will be executed based on the command you specify.

For example, DISM comes built-in with Windows 10 in the c:\windows\system32 folder. However, you can run the DISM command in the Command Prompt from any Windows location. But you must be running the Command Prompt as administrator to use DISM in Windows 10 effectively.

Which File Formats can DISM Service?

By utilizing the DISM.exe tool, you can mount and service any Windows image from the following Windows OS file formats.

.wim files
.vhd files
.vhdx files
.ffu files

You can also use DISM.exe to update a running operating system.

How do I Use DISM.exe?

You can use the DISM command tool in three ways:

  • CheckHealth: DISM /Online /Cleanup-Image /CheckHealth – this command will check for corruption or damages in the system files and local but will not repair them.
  • ScanHealth: DISM /Online /Cleanup-Image /ScanHealth – this command will determine if the Windows 10 image has any problems but won’t repair it.
  • RestoreHealth: DISM /Online /Cleanup-Image /RestoreHealth – this command will repair local and Windows image problems and restore its health.

Note: If you need a step-by-step guide on how to use the DISM.exe tool, see this post. There are a few guidelines to using the DISM command lines as follows:

  • You need to launch the Command Prompt as an administrator.
  • You need to run these three command components in that hierarchy order to allow DISM to function effectively.

When do I Use DISM?

When your Windows device is facing issues with performance, start-up, system file errors, or ‘unexpected’ errors your first tool is always the System File Checker (sfc /scannow). The SFC scan will detect and replace missing or corrupted system files on the computer’s local image.

However, sometimes the issue may be residing deeper within the Windows image that the SFC may be unable to solve or repair. In this case, your next best option is to use the DISM tool to repair and solve the underlying issue.
Microsoft outlines that you can use the DISM tool under the following scenarios for image servicing and image management solutions:

  • Managing the information or data included in the Windows image: for example, enumerating (or recording the inventory of) the drivers, updates, applications, or components contained in an image. In addition, you can also use DISM to capture or split an image, mount an image or append or delete images within a .wim file.
  • Servicing the image itself: which includes adding or removing drivers and driver packages, modifying PC language settings, disabling or enabling Windows features, and upgrading Windows to higher editions.

So, basically, DISM is used for information gathering, Windows upgrade, and Windows image repair.

Which Windows Images Support DISM?

You can use the DISM.exe tool with older Windows image files (.wim files). But you cannot use it with Windows images, which are more recent than the Operating System’s installed DISM version.
In addition, you can use DISM to service Windows images beginning with the following Windows versions:

  • Windows 7.
  • Windows Server 2008 R2.
  • WinPE.
  • WinRE.
  • Windows 8.
  • Windows 8.1.
  • Windows 10.

Typically, the options and commands available for Windows image servicing depend on which Windows Operating System or Windows version you are servicing. It also largely depends on whether the image is offline or if it is a running Operating System.

What’s New for DISM in Windows 10?

Microsoft has updated DISM in Windows 10, which supports new features including:

  • Full Flash Update (.FFU): DISM now supports the .FFU file format in Window 10, which captures and applies an entire drive and includes partition information. It makes deployment easier and faster.
  • Capabilities: the new Windows package type now allows you to request services like .NET or languages without specifying the version. You can now use DISM to search multiple sources such as your corporate services or Windows Update to find and install the latest version.
  • Compress Operating system and provisioning packages to save space on a Windows image. This new feature replaces the WIMBoot features in Windows 8.1.

DISM in the Windows ADK

The Windows Assessment and Deployment Kit can help you run DISM on an older Windows version or if you need a different DISM version on your PC.

If you download the Windows ADK, DISM will appear in the Windows ADK in the following path:
C:\Program Files (x86)\Windows Kits\\Assessment and Deployment Kit\Deployment Tools\\DISM


  • <version> can be 8.0, 8.1, or 10.
  • <arch> can be x86 or amd64.

Runtime Broker Using Too Much CPU

When you check the Task Manager, you may notice Runtime broker using too much CPU resources. This has been a concern to many Windows users. Those who do not know the runtime broker process even wonder if it is a virus.

About Runtime Broker

Microsoft first introduced the runtime broker process in Windows 8 and has kept using it up to Windows 10. The process is run using the RuntimeBroker.exe executable. It is a legitimate process designed and distributed by Microsoft Corporation.

The Runtime Broker process is linked to the Universal Windows Apps (UWA). These applications came with the operating system, or those installed from Windows Store, and sideloaded apps.

The Runtime Broker process’s main task is to check if these apps and programs have declared all the safety and required permissions to function on your Windows system. If not, the runtime broker will block the applications and inform you about the applications trying to access your system without your permission.

Simply put, the runtime broker acts as a security middleman on your device between the UWA app and your hardware and data.

aSince Runtime Broker is majorly linked to Universal Windows Apps, it normally becomes active whenever you start one of the UWAs on your device. The runtime broker process is not active all the time.

Why Is Runtime Broker Using Too Much CPU?

Runtime Broker has a bad reputation for sporadically increasing CPU load and memory usage on the PC system. This is a big concern to users because increased CPU usage reduces the performance of the PC.

Normally, the Runtime Broker should not use much of your system’s resources. It should use just a small percentage of the CPU and a few megabytes of memory.

Sometimes your antivirus program can cause problems with Runtime Broker, leading to high CPU usage. Besides, a faulty UWA application or one that is incorrectly installed or working incorrectly can cause runtime broker to use high CPU and high memory in the PC – even up to 30% CPU and gigabytes of memory.

Background Task Infrastructure Service, OneDrive, TeamViewer, fresh paint, Windows tips, and notifications, etc., are the usual UWA culprits when you notice high system resource usage by the runtime broker. For example, a faulty YourPhone.exe process can cause the Runtime Broker to spike CPU usage.

How Can I Fix Runtime Broker Using Too Much CPU?

Usually, Runtime Broker is not a virus. However, if the runtime broker is using too much CPU, it may affect your system’s performance. You need to scan your system with a quality antivirus to see if any virus or application files stand behind it. Running the SFC and DISM scans can help repair corrupted system files or fix missing files and solve runtime broker using too much CPU.

Microsoft also suggests killing the Runtime Broker Process if it starts using more than 15% of memory. Restarting the system can also help install any pending Windows Updates that can be causing runtime broker to use much CPU.

You can get a more detailed guide, with guided steps, to fix runtime broker using too much CPU here.

Other solutions that can help fix the issue of runtime broker using too much CPU include:

  • Disable or turn off the get tips, tricks, and Windows suggestions
  • Edit the Windows registry entries
  • Disable Windows background apps or limit the number of background apps
  • Change the lock screen background
  • Check if runtime broker is a virus

Is Runtime Broker a Virus

No, runtime broker is not a virus. It is a genuine and legitimate process that comes preinstalled with your Windows system. Microsoft introduced the runtime process to help users verify the safety and security of UWA applications.

However, since Runtimebroker.exe is an executable, it is vulnerable to virus or malware infection. Some malware can copy the Runtimebroker.exe name and camouflage as the Runtime broker process to avoid detection.

Using a quality antivirus can help you ensure the system errors are not caused by malware. It is relevant for Windows update errors like 0x80070002 or when Avast Blocked Host Process for Windows Services.

Sometimes, you may notice multiple Runtimebroker.exe processes running in the background. This is simply an indication that you’re running more than one UWA app. The runtime broker is checking all of them. But this could also be the doing of a virus, and you need to scan your system to verify if it is not.

Final Word

Since runtime broker is used to managing apps and programs from Windows Store, it is necessary to protect your privacy and security when running those apps. It would help if you did not disable this process in Task Manager to fix the increased CPU usage error.

Using Windows 10 operating system may result in several system issues. In Outbyte blog you can find detailed instructions on how to fix the most popular errors.