Sfc scannow windows resource protection could not start the repair

Означает ли это, что всё так плохо, что даже SFC не работает? Не всегда, просто во время проверки в системе происходит сбой или инструмент не может получить доступ к каталогу WinSxS, в коем расположены важные файлы. Вероятны и другие причины — повреждение файловой системы, наличие физически нечитаемых секторов на диске, отсутствие у пользователя соответствующих прав доступа. Что делать и с чего начинать поиск причин неполадки?

Причиной ошибки сканирования может быть ограничение доступа SFC к каталогу WinSxS. Попробуйте снять их, выполнив в консоли CMD команду

и перезагрузив компьютер.

sfc /scannow /offbootdir=D: /offwindir=C:Windows

• Примечание: определить буквы томов в загрузочной среде проще всего с помощью Блокнота, запустив его командой notepad и выбрав Файл → Сохранить как.

Если приведенные выше способы не дали результатов, высока вероятность, что отказ защиты ресурсов Windows вызван повреждением самого хранилища системных компонентов, то есть содержимого папки WinSxS. Проверить его состояние можно командой

если она выдает сообщение о необходимости восстановление хранилища, выполняем в консоли такую команду:

Компьютер при этом должен быть подключен к интернету, поскольку Windows может потребоваться подключиться к серверу Microsoft и скачать недостающие файлы. По завершении процедуры перезагружаемся. Теперь, когда хранилище восстановлено, sfc/scannow должна заработать как надо.

Are you trying to run the System File Checker (sfc /scannow) but run into the “Windows Resource Protection could not start the repair service” error message? You’ll learn how to fix it here.

The System File Checker is an incredibly useful tool millions of users rely on to fix system-wide issues by restoring missing or corrupted files. It’s able to automatically detect and fix system files causing issues on your computer. But what are you supposed to do when the feature fixing your issues needs fixing as well?

Users have been reporting that when trying to execute the “sfc /scannow” command, they get yet another error message in return: Windows Resource Protection could not start the repair service. There are a few things you can do in order to fix this and successfully run the System File Checker.

Why Is the SFC Scan Not Working?

The reason why your System File Checker isn’t able to function is the TrustedInstaller (Windows Modules Installer) service. It’s a necessary service that helps your system install, modify and remove various applications. It also “owns” your system files in order to prevent other sources from modifying or deleting them.

Despite this, you still may run into issues with corrupted system files and so, you need to use the SFC scan. TrustedInstaller has full access to Windows Resource Protection (WRP) files and registry keys, which are necessary for the SFC scan to work.

This service starts on-demand whenever you execute the “sfc /scannow” command. If the service has been completely disabled, the scan won’t be able to restore any missing or corrupted WRP files.

This issue appears most commonly in Windows 7, but may appear on Windows 8 as well as the latest Windows 10.

How Do I Fix the “sfc /scannow” Not Working? Fix Windows Resource Protection Could Not Start the Repair Service Error

There are a few different solutions to help you if you’re struggling to run the System File Checker and scan your device for corrupt files or missing resources.

Method 1. Start the Windows Modules Installer (TrustedInstaller)

The most straightforward solution is manually starting the required service. It’s important to configure the Windows Modules Installer in a way that allows it to start whenever you try to run the SFC scan. The steps below will guide you through this setup.

1. Press the Windows + R keys on your keyboard. This is going to bring up the Run utility.
2. Type in services.msc and click on the OK button. This is going to launch the Services window, which might take a few seconds to fully load.
   
   
3. Right-click on the Windows Modules Installer service and choose Properties.
   
   
4. Set the Startup type to Manual. If the service isn’t running, click on the Start button. Click Apply, then OK. You should be back at the list of services.
   
   
5. Close the Services window and try running the “sfc /scannow” command again. If the scan still doesn’t work, move on to the next solution.

Method 2. Use the Command Prompt

This method is essentially the same one as the first but done in the Command Prompt. It’s possible that this solution may work, as you need administrative permissions to make the modification.

1. Open the search bar in your taskbar by clicking on the magnifying glass icon. You can also bring it up with the Windows + S keyboard shortcut.
2. Type cmd or Command Prompt in the search bar. When you see it in the results, right-click on it and choose Run as Administrator.
   
   
3. When prompted by the User Account Control (UAC), click Yes to allow the app to launch with administrative permissions.
4. Once the Command Prompt window is open, type in the following command and press Enter to execute it: sc config trustedinstaller start= auto. If the command worked, you should see the SUCCESS message.
   
   
5. Afterwards, execute the following command: net start trustedinstaller. There should be a message about the Windows Modules Installer service starting successfully.
   
   
6. Now, you can try to run the System File Checker by executing the sfc /scannow command. If you still don’t have any luck running it, try a different method below.

Method 3. Try To Run the System File Checker in Safe Mode

There’s a possibility that a background application or service is interfering with the System File Checker, causing it to not work. In this case, you can try simply executing the scan command in Safe mode. Safe mode boots your system with only the necessary Windows components enabled.

1. Press the Windows + R keys on your keyboard. This is going to bring up the Run utility.
2. Type in “msconfig” without the quotation marks and press the Enter key on your keyboard. This will launch the System Configuration application.
   
   
3. Switch to the Boot tab. Under Boot options, check Safe boot and keep it on the Minimal setting, then click the OK button.
   
   
4. Restart your computer. It should boot in Safe mode without any third-party applications, only starting the necessary services. Open the Command Prompt and execute the sfc /scannow command to see if the SFC scan is working.

Method 4. Run the DISM Command

Some users have reported that running the DISM command fixed the System File Checker. The Deployment Image Servicing and Management (DISM) tool re-deploys your system image in order to fix issues directly related to it. The step-by-step instructions to run this scan can be found below.

1. Open the search bar in your taskbar by clicking on the magnifying glass icon. You can also bring it up with the Windows + S keyboard shortcut.
2. Type cmd or Command Prompt in the search bar. When you see it in the results, right-click on it and choose Run as Administrator.
   
   
3. When prompted by the User Account Control (UAC), click Yes to allow the app to launch with administrative permissions.
4. Once the Command Prompt window is open, type in the following command and press Enter to execute it: DISM /Online /Cleanup-Image /RestoreHealth
   
   
5. Wait for the scan to complete, and then restart your computer. When going back to the Command Prompt, try running the SFC scan and see if it works now.

Final Thoughts

Our Help Center offers hundreds of guides to assist you if you’re in need of further help. Return to us for more informative articles, or get in touch with our experts for immediate assistance.

One More Thing

Would you like to receive promotions, deals, and discounts to get our products for the best price? Don’t forget to subscribe to our newsletter by entering your email address below! Be the first to receive the latest news in your inbox.

You May Also Like

» How to Fix Inaccessible Boot Device Error in Windows 10
» How To Fix ‘Remote Desktop Can’t Connect to the Remote Computer’
» How to Fix the “Default Gateway Is Not Available” Error in Windows 10

The System File Checker is a user-friendly tool to check whether there is a corruption for system files. However, if it is not working, you may receive an error message Windows resource protection could not perform the requested operation. But this post will show how to solve the problem SFC scannow not working issue.

The Issue SFC Scannow Not Working

SFC is a very useful tool to check whether there is a corruption for system files. However, some uses complain that sometimes the System File Checker may fail to work. And they usually receive the following two error messages when SFC Scannow is not working.

• Windows resource protection could not perform the requested operation.
• Windows resource protection could not start the repair service.

Thus, do you know how to solve the issue SFC scannow? Just go on your reading, this post will show you how to solve the SFC error respectively.

Windows Resource Protection Could Not Perform the Requested Operation

One of the SFC error is the Windows resource protection could not perform the requested operation. You can see the error message in the following picture.

Thus, how can you solve the issue Windows resource protection could not perform the requested operations? You can read the following four methods.

Quick Video Guide:

Solution 1. Run SFC Scannow Command in Safe Mode

If you have encountered the issue Windows resource protection could not perform the requested operation, you can try to run SFC scannow command in safe mode to solve the problem. Here, we will show you how to solve the problem step by step.

Step 1: Press Windows key and R key together to launch Run box.

Step 2: Type msconfig in the box and hit Enter to continue.

Step 3: Then go to Boot tab, tick on Safe boot and click OK to continue.

Step 4: Then restart your computer to apply this change. Click Restart to continue.

Then your computer will boot in safe mode and you can input SFC scannow command again to check whether the issue Windows resource protection could not perform the requested operation is solved.

Solution 2. Run Check Disk

If there are some errors on your hard disk, the SFC scannow not working issue can also occur. So in this situation, you can try to check the disk and try to solve the problem Windows resource protection could not perform the requested operation. And we will introduce how to check disk step by step.

Step 1: Type cmd in the search box of Windows 10 and right-click the Command Prompt to choose Run as administrator.

Step 2: Type chkdsk /r command in the popup command window and hit Enter to continue.

Step 3: Then you will receive a message that shows ‘Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts?’. Thus, you need to type Y to continue.

Step 4: After that, close the command window and restart your computer. Then it will start to check the disk and fix the detected error automatically.

When the process of checking disk is finished, you can run SFC scannow again to check whether the issue Windows resource protection could not perform the requested operation is solved.

Solution3. Change Security Descriptors

A security descriptor contains the security information associated with a securable object. If SFC scan fails to access winsxs folder, the issue SFC scannow not working issue may also occur.

So in order to solve the issue SFC Windows resource protection could not perform the requested operation, you can try to change the security descriptors to solve SFC error. Here, we will show how to change security descriptors in detail.

Step 1: Type cmd in the search box of Windows 10 and right-click Command Prompt to choose Run as administrator.

Step 2: In the command window, type the ICACLS C:Windowswinsxs command and hit Enter to continue.

After that, you need to close the command window and restart your computer to check whether the issue SFC Windows resource protection could not perform the requested operations is solved.

Solution 4. Run Automatic Repair

If the above solutions are not working, you can try to go on this method to solve the issue Windows resource protection could not perform the requested operation. You can run Automatic Repair to solve SFC scannow not working problem. And we will show you how to run Automatic Repair step by step.

Step 1: Insert the Windows 10 bootable installation to your computer and boot your computer from it. If you don’t have the Windows 10 installation disc, you can click here to download the Microsoft Media Creation Tool and launch it to create an installation disc.

Step 2: Then you will enter the welcome interface and click Next to continue.

Step 3: Then click Repair your computer in the bottom-left corner to continue.

Step 3: You need to choose Troubleshoot in the popup window to continue.

Step 4: Click Advanced options to go to the next page.

Step 5: Choose the Startup Repair in the Advanced options screen and wait for the process to be completed.

Now, when the process is finished, you can restart your computer to check whether the Windows resource protection could not perform the requested operation is solved.

I have successfully solved the issue Windows resource protection could not perform the requested operation. Have a try now!Click to Tweet

Windows Resource Protection Could Not Start the Repair Service

As we have mentioned in the above part, this post focuses on two cases of SFC scannow not working issue. And the issue Windows resource protection could not perform the requested operation has been talked in the above paragraphs.

Now, we will talk about another issue Windows Resource Protection could not start the repair service.

When you are running SFC scannow command, you may receive the following error message which shows that Windows resource protection could not start the repair service.

This SFC error may occur when Windows Modules Installer services are disabled. Windows Modules Installer services have full access to Windows Resource Protection files and registry keys. If you want to use SFC scannow command to restore missing or corrupted WRP resources, Windows Modules Installer services need to be running.

Thus, if you receive the SFC error message Windows resource protection could not start the service, we can enable Windows Modules Installer to fix the problem. Now, we will show how to enable Windows Modules Installer step by step.

Step 1: Press Windows and R keys together to launch Run dialog, and input services.msc in the box, then click OK to continue.

Step 2: In the popup window, select the Windows Modules Installer and double-click it.

Step 3: You will see Windows Modules Installer Properties window, set Startup type as Manual, then click Apply and OK to confirm this change.

Step 4: Close the services window. Then type cmd in the search box of Windows 10 and right-click Command Prompt to choose Run as administrator.

Step 5: Type the following commands in the command window and hit Enter to continue after each command.

sc config trustedinstaller start= demand
net start trustedinstaller

When you have finished the above process, you can restart your computer and input the SFC scannow command to check whether the issue Windows resource protection could not start the repair services is solved.

Top Recommendation

Although SFC scannow command can scan for corruptions in Windows system files and restore corrupted files, things will become worse when SFC scannow is not working, in particular when the computer is corrupted and SFC scannow not working.

Therefore, we strongly suggest that you create a Windows image when your computer can work normally since not only you can use the backup image to perform some recovery actions especially when some accidents occur, but also can protect your data.

For instance, when your Windows 10 is corrupted or you don’t like the current Windows version, you can use the backup image to restore to an earlier date.

Thus, to create a backup image, many computer users choose the professional Window 10 backup software – MiniTool ShadowMaker. This free software can handle lots of backup matters with its various powerful features, such as system backup, files and folders backup, disk backup and so on.

The automatic backup software – MiniTool ShadowMaker can protect your computer well and can provide disaster recovery solutions when some accidents happen.

Therefore, in order to create a system image, you can get the MiniTool ShadowMaker from the following button which can be freely used within 30 days.

Free Download

After installing the free backup software, we will show you how to create a system image step by step with pictures.

Step 1: Launch the software and click Keep Trial to continue. Then click Connect in This Computer to enter its main interface.

Step 2: Then, MiniTool ShadowMaker will remind you to back up if you haven’t performed any backup action with this backup tool. You just need to click SET UP BACKUP to continue. MiniTool ShadowMaker is set to back up the operating system by default.

Of course, you can also go to the Backup tab to select the Source tab and Destination tab to choose what you want to back up and where you want to save the backup image. In addition, it is recommended to choose an external hard drive as the destination path.

Step 3: Now, you can click Back up Now to perform backup action immediately. Of course, you can also click Back up Later to delay the backup process.

Step 4: After successfully creating the backup image, you had better go to the Tools tab to create a bootable media which can be used to help you to restore to an earlier date or do some other recovery actions with the backup image at any time you want.

MiniTool ShadowMaker is a fantastic tool that can easily create a backup image within a few steps. With this backup software, you can protect your PC and important data and files well.Click to Tweet

Bottom Line

In conclusion, this article focuses on two cases of SFC scannow not working issue, which respectively are Windows resource protection could not perform the requested operation and Windows resource protection could not start the repair service.

Aiming at those two different situations, we also list different solutions to solve the SFC error. Now, it is your turn to have a try.

In addition, if you have any better solution to the SFC scannow not working issue, you can share it on the comment zone. Or if you have any problem with MiniTool ShadowMaker, you can feel free to contact us via the email [email protected].

Windows Resource Protection Could Not Perform the Requested Operation FAQ

When you run the System File Checker (Sfc.exe) using the /scannow parameter to restore missing or corrupt system files, the following error may occur.

Windows Resource Protection could not start the repair service.

Additionally, you may experience problems running Windows Installer Setup files and installing fixes from Windows Update.

Cause

The above error occurs due to one or more of the following reasons:

1. The TrustedInstaller (Windows Modules Installer) service is disabled. The TrustedInstaller service has full access to Windows Resource Protection (WRP) files and registry keys. This service needs to be running to restore missing or corrupted WRP resources. The TrustedInstaller service starts on-demand when running the System File Checker.
2. The supporting DLL files required to run Sfc.exe may be missing. Some of the modules needed are wrpint.dll and wrpintapi.dll. The missing module names will be reported in the CBS.log located in the C:WindowsSystem32CBS folder.
3. There is file system corruption on the system drive. This will be evident if DISM reports the error 1392 (“File or directory is corrupted”).

Solution

1) Start the Trusted Installer Service

To resolve the “Windows Resource Protection could not start the repair service” error, set the startup type of the Windows Modules Installer (“TrustedInstaller”) service to manual.

1. Right-click Start, and click Run to launch the Run dialog.
2. Type services.msc, and click OK.
3. Double-click Windows Modules Installer.
4. Set its Startup type to Manual
5. Click OK.
   

Using Command-line

To accomplish the same using command-line, open Command Prompt as administrator. Run the following commands.

sc config trustedinstaller start= demand
net start trustedinstaller

That should fix the problem. Another option would be to run Sfc /scannow in offline mode (Windows Recovery Environment).

2) Restore Missing DLL files

Open the C:WindowsLogsCBSCBS.log file and see if you find entries like the ones below:

Info CBS TiWorker: Client requests SFP repair object.
Info CBS Failed to load sfp DLL from path: C:WINDOWSwinsxsamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22000.975_none_0493932d4c9bedcc\wrpint.dll [HRESULT = 0x8007007e - ERROR_MOD_NOT_FOUND]
Info CBS Failed to initialize WRP integrity check and repair. [HRESULT = 0x8007007e - ERROR_MOD_NOT_FOUND]
Info CBS TiWorker: Client requests SFP repair object.
Info CBS Failed to load sfp DLL from path: C:WINDOWSwinsxsamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22000.975_none_0493932d4c9bedcc\wrpint.dll [HRESULT = 0x8007007e - ERROR_MOD_NOT_FOUND]
Info CBS Failed to initialize WRP integrity check and repair. [HRESULT = 0x8007007e - ERROR_MOD_NOT_FOUND]
Info CBS Failed to get class factory for service: 1 [HRESULT = 0x8007007e]
Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

[Scroll horizontally to see the missing file name(s) and the version]

If you find those errors in the log file, download the exact version (which, in this case, is 10.0.22000.975) of the file wrpint.dll from Microsoft via WinBIndex.

Also, check if the file C:WindowsServicingwrpintapi.dll exists. If it’s missing, you need to download the appropriate version of the file via WinBIndex.

Instructions for copying those files

1. Copy the downloaded DLLs to “C:DLLs”
2. Start Command Prompt as TrustedInstaller by downloading AdvancedRun (More Information).
3. Close AdvancedRun.
4. Run these commands from the Command Prompt (TrustedInstaller) window:
   (Note: The winsxs subfolder name below corresponds to the above CBS.log entries. Please change the path accordingly in your case.)

   cd /d C:DLLs
   copy wrpint.dll "C:WINDOWSwinsxsamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22000.975_none_0493932d4c9bedcc"
   copy wrpintapi.dll C:WindowsServicing
   exit
   

5. Open admin Command Prompt, and try running SFC /SCANNOW now. It should run fine.

3) Repair disk errors using Chkdsk

Open an admin Command Prompt and run the following command:

chkdsk c: /r

Press Y when you’re prompted to schedule the volume fixed by Chkdsk upon the next restart.

Let Chkdsk complete the repairs on the next startup.

After loading Windows, try running “Sfc /scannow” again.

Please see the article DISM Error 1392 – File or directory is corrupted for detailed information.

(Information in this article applies to all versions of Windows, including Windows 11.)

How to Fix the «Windows Resource Protection could not start the repair service» Error on Windows 10

System File Checker (SFC) is a utility in Windows that allows users to scan for corrupt Windows system files and restore them. Unfortunately, you may get the «Windows Resource Protection could not start the repair service» error when running the «SFC /Scannow» command. This article will show you how to fix this problem.

Windows Resource Protection (WRP) prevents the replacement of essential system files, folders, and registry keys part of the operating system. Permission for full access to modify WRP-protected resources is restricted to TrustedInstaller.

WRP-protected resources can only be changed using the Supported Resource Replacement Mechanisms with the Windows Modules Installer service.

TrustedInstaller is a process belonging to the Windows Modules Installer service in Windows 10, 8, 7, and Vista. Its primary function is to enable installing, removing, and modifying Windows Updates and optional system components.

Sometimes TrustedInstaller.exe may become corrupted, and you may get an error message. In such a case running the System File Checker may help.

However, sometimes, even the Windows Resource Protection service, which runs the System File Checker (SFC), is affected. In such a case, if you try to run the «sfc /scannow» command, you may get the error message saying: «Windows Resource Protection could not start the repair service».

Read the guide below to fix the «Windows Resource Protection could not start the repair service» error while trying to run the System File Checker.

Video Showing How to Fix the «Windows Resource Protection could not start the repair service» Error:

Table of Contents:

• Introduction
• Enable Windows Modules Installer Service
• Run System File Checker in Safe Mode
• Run DISM Scan
• Video Showing How to Fix the»Windows Resource Protection could not start the repair service» Error

Enable Windows Modules Installer Service

Windows Services (also known as services.msc), are used to modify how Windows services run on your system. You can modify a service’s settings for security, troubleshooting, and performance-related reasons.

You will need to access the Windows Installer service, which enables installation, modification, and removal of Windows updates and optional components. If this service is disabled, install or uninstall of Windows updates might fail for your computer.

To access the Windows Modules Installer service type «run» in Search and click the «Run» result.

In the Run dialog box, type «services.msc» and click «OK» to open Windows Services.

Now scroll down through the services list to find the «Windows Modules Installer» service. Right-click it and select «Properties» in the dropdown menu. Or simply double-click the Windows Modules Installer service.

Make sure that «Startup type» is set to «Manual». If it is not set to Manual, then set it this way and click «Apply» to save the changes made.

You can also try to enable the TrustedInstaller using Command Prompt and its commands. Some commands available in Windows require that you run them from an elevated Command Prompt. This means you have to be running it with administrator-level privileges.

To open Command Prompt, type «command prompt» in Search and then right-click on the «Command Prompt», select «Run as administrator» from the dropdown menu to run Command Prompt with administrator privileges.

Now you will need to execute a couple of commands. Type «sc config trustedinstaller start=demand» and press Enter on your keyboard.

Then type «net start trustedinstaller», and press Enter on your keyboard again.

Now try to run the System File Checker and see if you are still getting the «Windows Resource Protection could not start the repair service» error.

[Back to Table of Contents]

Run System File Checker In Safe Mode

Another thing you might want to try is to run the System File Checker in Safe Mode. Safe Mode is a diagnostic start-up mode in Windows operating systems used to obtain limited access to Windows when the operating system does not start or function normally.

If you are not sure how to start your Windows in Safe Mode, read this article.

[Back to Table of Contents]

Run DISM Scan

DISM stands for Deployment Image Servicing and Management, and it can be used to repair and prepare Windows images, including the Windows Recovery Environment, Windows Setup, and Windows PE.

To run DISM scan, you need to open Command Prompt as administrator again and type in this command: «DISM /Online /Cleanup-Image /RestoreHealth». Press Enter on your keyboard to execute it.

See if this fixes the «Windows Resource Protection could not start the repair service» error while trying to run the System File Checker.

We hope this article was helpful in trying to fix the «Windows Resource Protection could not start the repair service» error, and now you can run the System File Checker without any problems. Do not hesitate to write a comment in the comment section below if you found another workaround for this error!

[Back to Top]

I cannot run SFC. How do I fix it?

C:>sfc /scannow

Windows Resource Protection could not start the repair service.

C:>net start trustedinstaller
The requested service has already been started.

C:>Dism /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Error: 11

You cannot service a running 64-bit operating system with a 32-bit version of DISM.
Please use the version of DISM that corresponds to your computer's architecture.

The DISM log file can be found at C:windowsLogsDISMdism.log

C:>findstr /c:"[SR]" %windir%logscbscbs.log

C:>

dism.log

2017-11-03 16:06:12, Info                  DISM   PID=6268 TID=3252 Scratch directory set to 'C:UsersChloeAppDataLocalTemp'. - CDISMManager::put_ScratchDir
2017-11-03 16:06:12, Info                  DISM   PID=6268 TID=3252 DismCore.dll version: 6.3.9600.17031 - CDISMManager::FinalConstruct
2017-11-03 16:06:12, Info                  DISM   PID=6268 TID=3252 Successfully loaded the ImageSession at "C:windowsSystem32Dism" - CDISMManager::LoadLocalImageSession
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Manager: PID=6268 TID=3252 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: 
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: 
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.3.9600, Running architecture=x86, Number of processors=8
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: Dism.exe version: 6.3.9600.17031
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: Executing command line: Dism  /Online /Cleanup-Image /ScanHealth
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Loading Provider from location C:windowsSystem32DismFolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Connecting to the provider located at C:windowsSystem32DismFolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: 
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2017-11-03 16:06:12, Info                  DISM   DISM.EXE: 
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2017-11-03 16:06:12, Info                  DISM   DISM Provider Store: PID=6268 TID=3252 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

I have not tried running it in Safe Mode yet.