DISM Error 3017 “System reboot is required”

When you run DISM ScanHealth or RestoreHealth to repair the component store, error 3017 may occur. The entire error message verbatim is given below:

Deployment Image Servicing and Management tool 
Version: 10.0.22621.2792 

Image Version: 10.0.22631.3527 

[==                         4.9%                           ] 

Error: 3017 

The requested operation failed. A system reboot is required to roll back changes made. 

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log"

The DISM log may show the following entries:

Info DISM DISM Package Manager: PID=21568 TID=1556 Error in operation: (null) (CBS HRESULT=0x80070bc9) - CCbsConUIHandler::Error
Error DISM DISM Package Manager: PID=21568 TID=19684 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070bc9)
Error DISM DISM Package Manager: PID=21568 TID=19684 Failed processing package changes with session options - CDISMPackageManager::Internal_ProcessChangesWithOptions(hr:0x80070bc9)
Error DISM DISM Package Manager: PID=21568 TID=19684 Failed processing package changes with session option CbsSessionOptionDetectStoreCorruption - CDISMPackageManager::ScanHealth(hr:0x80070bc9)
Error DISM DISM Package Manager: PID=21568 TID=19684 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80070bc9)
Error DISM DISM Package Manager: PID=21568 TID=19684 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070bc9)

Cause

The error code 3017 (hex: 0x80070bc9) or ERROR_FAIL_REBOOT_REQUIRED denotes that a restart of the client computer is pending.

Resolution

First, restart the system to complete the pending update install or rollback operation. If restarting Windows does not fix the DISM error 3017, please do the following:

Step 1: Revert Pending Actions via WinRE

  1. Launch the Windows Recovery Environment. For more info, see How to access Windows Recovery Environment.
  2. In WinRE, click TroubleshootAdvanced OptionsCommand Prompt.win re system image backup recovery
  3. In the Command Prompt window, run the following command to find the drive letter of your OS partition.
    bcdedit

    bcdedit - find windows drive letter osdevice

  4. Look for the osdevice value and path entry containing the data winload.efi.In the above example, the OS partition is drive E:\. It varies from system to system.
  5. Type the following commands, where E: is the OS partition:
    dism /Image:E:\ /Cleanup-Image /RevertPendingActions
    del E:\Windows\WinSxS\pending.xml /a
  6. Restart the system and enter Windows normally.

Step 2: Fix the registry settings

  1. From an admin Command Prompt, run these commands:
    reg load HKLM\COMPONENTS C:\Windows\System32\Config\COMPONENTS
    regedit.exe
  2. In the Registry Editor, go to the following key:
    HKEY_LOCAL_MACHINE\COMPONENTS
  3. In the right pane, delete the following values:
    • PendingXMLIdentifier
    • ExecutionState

    pendingxmlidentifier

  4. Exit the Registry Editor.

Step 3: Set TrustedInstaller to Manual start

Open services.msc and double-click Windows Modules Installer.



Set its Startup type to “Manual.”

Attempt to start the service manually. Make a note of error messages, if any.

That’s it. The above should resolve the DISM error 3017.


One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
  • Pin it!
  • Share it to your favorite blog + Facebook, Reddit
  • Tweet it!
So thank you so much for your support. It won't take more than 10 seconds of your time. The share buttons are right below. :)

Ramesh Srinivasan is passionate about Microsoft technologies and he has been a consecutive ten-time recipient of the Microsoft Most Valuable Professional award in the Windows Shell/Desktop Experience category, from 2003 to 2012. He loves to troubleshoot and write about Windows. Ramesh founded Winhelponline.com in 2005.

Leave a Comment