Fix SCCM Task Sequence Error Code 0X80091007

In this article, I will show you how to resolve SCCM task sequence error code 0X80091007. The error 0X80091007 occurs during operating system deployment when a task sequence step fails to execute correctly.

One of the SCCM engineers working at a remote site reported that the task sequence had failed. The task sequence failed with error code 0X80091007, and this happened while imaging a new laptop. The task sequence wasn’t modified by anyone, and all the TS steps were working fine.

The site engineer reported that error code 0X80091007 was observed during the application installation step of the task sequence. One of the applications that was a part of the task sequence failed to install and this resulted in task sequence error 0X80091007. In another instance, the task sequence failed during apply operating system step.

Before you read further, here are some troubleshooting guides for task sequence failures:

Review SMSTS.log file for Error 0X80091007

Whenever the task sequence fails during OSD, make a note of the error code, and review the SCCM log files. The smsts.log file is an important log file that records the OSD process. The location of smsts.log file changes as the OSD progresses. Take a look at location of smsts.log file during SCCM OSD.

After reviewing the Configuration Manager OSD log files, I found that task sequence failed during installation of Microsoft Office 2013. However, I was confident that the Office 2013 package was not corrupt, and the same package got deployed on the computers without any issues.

The below log snippet reveals that task sequence fails with error 0x80091007 and the reason being the hash value is not correct. At this point, you may want to consider recreating the package only if you determine the package is corrupt. Otherwise, please try the solutions that I have mentioned in the next section to resolve the error 0X80091007.

Failed to run the action: Error in the task sequence.
Task Sequence Error Running: Install Microsoft Office 2013 Professional.
Install Microsoft Office 2013 Professional has failed with the error code (0x80091007).
The hash value is not correct. (Error: 80091007; Source: Windows)
For more information, please contact your system administrator or help-desk operator.

Fix SCCM Task Sequence Error Code 0X80091007

Let’s understand more about the error 0X80091007 responsible for task sequence failure. The error code 0X80091007 translates to “The hash value is not correct“. The error 0X80091007 occurs when an application, package associated with task sequence is corrupt, system memory is faulty or the content is distributed to distribution points correctly.

The below screenshot shows an example of task sequence error 0X80091007, and we see the following details:

Task Sequence: Windows 10 Enterprise x64 has failed with the error code (0x80091007). For more information, contact your system administrator or helpdesk operator.

SCCM Task Sequence Error Code 0X80091007
SCCM Task Sequence Error Code 0X80091007

When you encounter task sequence failures, you can translate SCCM error codes to error messages using multiple ConfigMgr error lookup tools. Using an SCCM error lookup tool, if you translate error 0X80091007, you get “The has value is not correct” message.

SCCM Task Sequence Error Code 0X80091007
SCCM Task Sequence Error Code 0X80091007

Solutions to Fix Task Sequence Error Code 0X80091007

We will now look at multiple unique solutions to resolve the task sequence error 0X80091007.

Solution 1: Redistribute the package to distribution point

If the task sequence is failing with error 0X80091007 on a specific application install step, it means the content is either corrupt or not fully distributed to the DP. You can recreate the package in SCCM and associate it with task sequence or redistribute the content to the distribution points.

Take a look at this guide to redistribute the packages in SCCM. You can also update the content to the distribution points, with this action, you send the entire content to the distribution points.

Another solution that you can try is remove the content from the DP and distribute back the same content. This will send a fresh copy of the content (application, package) to the distribution point.

Solution 2: Check if the RAM (System Memory) is bad or corrupt

This is interesting !! If your system memory (RAM module) is corrupt or bad, you may encounter task sequence error code 0X80091007. Swapping the corrupt RAM/memory has helped many admins to resolve the error 0X80091007. You can read the post comments to find out how this trick has helped so many users.

Solution 3: Turn off binary differential replication

Configuration Manager uses binary differential replication (BDR) to update content that you previously distributed to other sites or to remote distribution points. When you enable BDR, it resends only the new or changed content instead of sending the entire set of content source files each time you change those files.

To resolve the error 0X80091007, ensure you turn off the binary differential replication on the package that is failing in the task sequence. It is observed that some users got the hash mismatch error resolved by turning off binary differential replication and redistributing the package to DP.


  1. Getting this issue and believe it’s a gpo that’s causing it. Looking at Windows defender or similar built in win 10 security

    I see an update go into ccmcache and then disappear on downloading. Looks like it’s getting quarantined but nothing in any logs.

    Now have to look at hundreds of gpos and of settings, because when I move it into staging ou it’s fine

  2. Hello all, I can add some informations of my case.

    First of all, I manage two differents SCCM infrastructure for two differents network and both are current branch full update, clean. One from 2011 and one from 2018.
    Both are on VMWare and have good perf, good space, cpu etc etc no problem.
    The first infrastructure never showed this error 0x80091007. I discover it with the second, with only one package on the DP !

    For example I started a deployment Tuesday at 5 pm :
    * around 1000 computers installed the package between 5 and 6 pm
    * then I had between 800 – 1000 computers with 0x80091007 and no one able to download and install it anymore…

    That’s not the first time, everytime I make an update of this program (which is a Innosetup package signed by editor) it works similarly for a bunch of computers then hash mismatch until refresh content… then computers install it, then hash mismatch, then refresh distribute content, then install, then hash mismatch until full deployment is ok…
    Within this package on the DP is “hash mismatch” all other are fully functionnal and the DP keep on doing his stuff of course.

    Of course I tried to recreate package, to overwrite it, to encapsulate it in ps1, bat, to make it an msi, to log in local, to not log, to log on the network… I’m out of solution, and of ways to investigate.
    I’m wondering on how to solve this case… it started in end of 2018 and come regularly at every update for this app… I’m goind crazy 🙂

    If you have anything, please… Thanks 🙂

    1. I had this issue following a requirement to rollback our SCCM server (not recommended at all!). I was able to image machines via PXE F12 but not when attempting to run the same Task Sequence from within Software Center.

      I resolved this by right-clicking on my boot image and selecting ‘Update distribution points’

      Version 1802

  3. i am facing the issue in software deployment getting the below error.

    Checking Account subkeys returned status 0x80070002, returning false.
    OnContentAvailable program Install NOT available, 0x80091007
    Fatal error 0x80008602 enountered for program Install. This program will not retry.

    deployed to 10K machines in that 400+ machines getting this issue.

  4. Avatar photo Mohammed Labeeb says:

    Thanks Prajwal !!!
    Replacing the RAM is fixed the issue.

  5. Avatar photo Imran Shaikh says:

    Hi Prajwal,

    In-place Upgrade Task Sequence failing on encrypted Laptops. so how is it possible to Encrypted Laptop upgrade OS through Task Sequence.

    I have using below command line given by McAfee Team, but not resolved issue.
    Setup.exe /ReflectDrivers “%programfiles%\McAfee\Endpoint Encryption\OSUpgrade”

    1. that command should work fine. What error do you see when you run the task sequence ?.

      1. Avatar photo Imran Shaikh says:

        some systems are not facing error but systems is going on reboot stage I have reboot the system after rollback the build.

        some system given error task sequence exception failed during upgradation. Error-: 0xc0000098

  6. Avatar photo Imran Shaikh says:

    Hi Prajwal,

    I have tried to upgrade build version required system getting below error please suggest how to resolved below issue.

    The hash value is not correct. 0X800910073012973,,
    Feature update to Windows 10 (business editions), version 20H2, en-us x64,Install the latest update for Windows 10: Windows 10, version 20H2.,Required,Failed to download update,29-01-2021 15:44

    1. Can you explain more about the issue. Like how are you upgrading it and I see failed to download the update, is the update distributed to all DP’s ?.

      1. Avatar photo Imran Shaikh says:

        I want to The hash value is not correct. 0X800910073012973 error when come during build upgradation

  7. Avatar photo Imran Shaikh says:

    Hi Prajwal,

    I want solution SCCM inactive client, I have multiple time troubleshoot but same. after finally I have uninstalled SCCM client reboot system once installed again SCCM client then Client is active,

    But I want to resolution without SCCM client removal.

    1. Without reviewing the log files, I cannot tell you why the issue is occurring.

      1. Avatar photo Imran Shaikh says:

        can you suggest me which logs file refer and share you errors

  8. Avatar photo Simon Burbery says:

    Hi there, just to add to the list of possible causes – we had this issue at one site when Multicast was enabled on the Distribution Point. The MDT toolkit and settings packages are Multicast enabled by default, so the TS was giving this error at the first ‘Use Toolkit Package’ step, showing the hash mismatch error 0X80091007 in the log. This wasn’t a problem at any other site with a DP so must have been something to do with the networking at the problem site. Multicast was no longer required as the OS is applied directly from the DP (not copied locally first), so we were able to disable Multicast and the problems were solved.


  9. Avatar photo Rasmus Thue als says:

    Swappet RAM. Worked like a charm

  10. Hi Prajwal,
    Can you help to understand is the RAM faulty or what cause this?

  11. Avatar photo Biju Mani says:

    I was getting the same error message for OS Deployment. Solved this by adding a New OS image and TASK sequence. I had to do this because I had re-installed the DP Role.

    Thanks Prajwal

  12. Avatar photo Jamie Randall says:

    I would not have believed it if I had not seen it myself! it was the RAM, Prajwal you are a genius, thank you not only for this but for all of your expert content on here

  13. Avatar photo Iassine Schoeman says:

    Hi Mr Prajwal, i get this error when i install cad software on my end. first time ever. i can forward you a picture.

  14. Antivirus scan can delay large application deployments hash checks, causing the same error message. Having ccmcache excluded in antivirus resolved issue.

  15. Trocar a RAM funcionou para mim. Obrigado.

  16. Avatar photo Chris Flagg says:

    I’m getting this error after upgrading sccm to the most recent version. Windows 7 will not image on machines it used to image on.

  17. Avatar photo Manish Sharma says:

    Swapping the RAM worked fine. Excellent and thank you.

  18. Avatar photo Cris Acevedo says:

    Swapping the RAM worked for me also. Thank you very much!

  19. Thank you for the post.

  20. Swapping the RAM worked for me. Thank you.

      1. Avatar photo Santosh Chauhan says:

        Thank you.

  21. Have seen hash errors also with TrendMicro Office Scan. Disabling it during OS deployment fixed it for me.

      1. Avatar photo Euclides Parra says:

        Swapping the RAM worked for me. Thank you.

Comments are closed.