Error code 0x80091007 during Task Sequence

After running a task sequence in the SCCM client, error 0x80091007 may occur:

Task Sequence Error
Running: Install <software title / os title>
Task sequence: Install <software title / os title> has failed with the error code (0x80091007). For more information, please contact your system administrator or helpdesk operator

This error code stands for the message that “the hash value is not correct”.

To resolve this issue, one of the following things should be done:

  • update the distribution point with the latest version of the package. Right-click on the package and choose Update Distribution Points. Please note that this could take a while, depending on the total size of your packages. 20 minutes is not exceptional.
  • modify the advertisement to not download the files locally but access the files directly from the DP. To do this, double click the advertisement, go to the tab Distribution Point and choose “Access content directly from a distribution point when needed by the running task sequence”


0 0 votes
Article Rating
Notify of
Newest Most Voted
Inline Feedbacks
View all comments

OMG I tried all sorts all day today to get my Task Sequence to work. Kept getting a hash error. Updated the DP with a new version a few times, even deleted package from DP and re-added/refreshed etc… No luck. Then I deleted the task sequence and advertisement, recreated them and that twice to no avail. I came across this thread and indeed as soon as I changed the source on how to retrieve the content it just worked straight up. The only different with this package and my other ones for other task sequences is that this is an… Read more »


I get this error because my packages had french specific caracters…

So no é, è, à, ù, … in files name or SCCM can’t check hash.

It took me a lot of time to discover what was wrong, so if this tips can help someone else.


Had a single machine that gave this error, ended up being bad HD in workstation.


I had the same problem – tried all the suggestions from all the blogs and it ended up being a bad HDD in the laptop I was imaging.


Wow, like others have posted, got this error on one PC only. Tried the steps through SCCM to no avail.

Ran a Dell diagnostic, and turns out it had bad RAM!


Also, for SCCM 2012 you may want to try and Validate the image package again. Go to Software Library > Operating Systems > Operating System Images and then right click on the image giving you the error and go to properties. Now under the content locations tab highlight your distribution point (or distribution point group) and then click validate. You have to wait a few minutes (if your server isn’t under much stress) but you can verify that this “re-validation” has taken place by going to Monitoring > Distribution Status > Content Status and then double click on your image… Read more »


Thank you, this worked for me.

However within my task sequence I have applications to which I am deploying and the multiple laptops are becoming stuck on a specific application. I have removed this and now it is hanging on another application.

2 of my 15 laptops have built but the others are failing. Any suggestions?

Marcos Cruz

Hello , I had this same mistake today and the problem was on the hard drive . I made the change and could send the image by SCCM . I hope this helps .

Jodi Anderson

Thanks for posting that your problem was the HD, every other solution involved the Windows Image. I suspected it was my HD and turns out it was. Once I tried the image on a known-good it worked.


Fixed hi everyone. I got this error when trying to reimage a system with SCCM and I couldn`t figure out what the problem is. Since I`m working on an facility where we use multiple computers with identical configurations, I have tried to swap the HDD to check if that`s the problem. It wasn`t. After I have replaced the RAM memory I could reimage the system without receiving any error messages. I`ve followed somebody`s advice on a forum and replaced it to test the reimaging and everything works fine now. just to be 100% that the RAM was the fault, I`ve… Read more »


Brilliant. I have tried about 6 times with different wim files and failed every time with error 0x80091007 and 0x80070057. Then took out one of the RAM strips and windows 7 has been installed. Thanks for the tip.


Yeah.. I also gave problem when to reimage I tried change the HDD but also same problem, then I replace the RAM then it success. TQ guys..


Changing RAM solved my incident


Ram worked here!



Mine too! 6/5/2023


In case any stumbles upon this thread for the same reason I did… I had this issue with a 2012 R2 Hyper-V Failover Cluster gen 2 VM (UEFI), so I know it isn’t a faulty drive or bad RAM because it’s all virtual. However, the RAM comments gave me a clue. I turned off dynamic memory on the VM and gave it a static 4GB. I also turned off secure boot at the same time, so I can’t say for certain which one fixed it (I know, bad troubleshooting technique). However, it was definitely one, the other, or the combination.… Read more »


Me funciono perfectamente cambiando la memoria… Muchas Gracias Chris por tu ayuda…

Would love your thoughts, please comment.x