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:
- SCCM Task Sequence Failed with error code 0x000001B6
- SCCM Task Sequence Failed with Error Code 0x800702C2
- Fix SCCM Task Sequence Failed with Error Code 0x80070002
- Failed to Resolve Task Sequence Dependencies 0X80040102
- Fix Task sequence has failed with the error code 0x800700A1
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.
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.
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.
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.