SCCM Task Sequence Error Code 0X80091007

In a remote site, while imaging a laptop, the SCCM task sequence failed with error code 0X80091007. This task sequence was working fine but this error occurred with no clue. I somehow got the access to the log files.

Checking the log files showed that task sequence failed during installation of Microsoft Office 2013. However I was very sure that the Office 2013 package was not corrupt. So this issue had some other resolution than recreating the package.

Upon some investigation, i found that it failed on two Dell latitude E7470 laptops. These laptops were brand new and had to be imaged before assigning it to employees. The log file revealed the below error.

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.

SCCM Task Sequence Error Code 0X80091007

I was not sure what the error code 0X80091007 meant. When i did some research, i found that error code 0X80091007 translates to Hash Mismatch (The hash value is not correct).

Most of all I realized that there is no single solution to this error. If you also come across SCCM Task Sequence Error Code 0X80091007, try the below solutions.

SCCM Task Sequence Error Code 0X80091007

  • If you see the error code 0X80091007, remove the package from distribution point and distribute the package. This is just to be sure that a valid package is available with distribution point.
  • Check if the RAM (memory) is bad or corrupt. This solution seems like the most silliest one. But believe me this swapping the RAM has resolved this issue for many people.
  • Some people got the hash mismatch error resolved by turning off binary differential replication and redistributing the package to DP.

34 thoughts on “SCCM Task Sequence Error Code 0X80091007”

  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 🙂

    • 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. 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”

      • 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

  5. 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

  6. 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.

  7. 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.


  8. 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

  9. 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

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

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

  12. 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.

Comments are closed.