I am working with a task sequence specifically for a refresh scenario.  The TS uses USMT and hardlinks to capture user state data.  After a successful run of the task sequence, I am using usmtutils.exe to remove the state store with /rd /y.  That all seems to work well.
 
Now if I attempt to run the task sequence on the same machine again, the task sequence fails with the error:
 
The task sequence execution engine failed executing the action (Use Toolkit Package) in the group (Initialization) with the error code 2148077575
VerifyContentHash: Hash algorithm is 32780
DownloadContentAndVerifyHash() failed. 80091007.
Unable to delete directory C:\_SMSTaskSequence\Packages\ABC00010\Scripts (0x80070091).  Continuing.
Failed to open file c:\_smstasksequence\packages\ABC00010\scripts\autorun.inf with error [32].
ashFile - exclusive access check for the file failed.
Failed to hash file, Win32 error = 4103
Hash could not be matched for the downloded content. Original ContentHash = 70FD27B4FBDA91BFB804D6DE10E1AB9F287587FB22491F68F5C1752E87728201, Downloaded ContentHash =
Failed to resolve the source for SMS PKGID=ABC00010, hr=0x80091007
Install Software failed to run command line, hr=0x80091007. The operating system reported error 2148077575: The hash value is not correct.  
 
I can get the TS to run again if I remove the _SMSTaskSequence folder and then reboot.
 
Has anyone seen this before and have a solution?
 
Any insight is greatly appreciated!

The fact that it explicitly shows a hash mismatch related to autorun.inf leads me to believe its AV or On-Access Scanning of some kind.....

When the TS completes the first time, the _SMSTaskSequence folder "should" be deleted automagically at the end. I'd hypothesize that Antivirus, or some other on-access type security tool is interfering with the removal of the folder (or maybe just the autorun.inf file, antivirus tools HATE that specific file by default) so the folder sticks around, and next time you run the task sequence, you get a hash mismatch because some stuff exists/doesnt exist, and the Task Sequence either is confused, or is getting access denied trying to check the autorun.inf file's hash value (again, due to your on-access scan software blocking it for security reasons?

I know we were initially having similar (but not identical) issues until we altered our AV settings to exclude a lot of the common SCCM folders, including "_SMSTaskSequence"

Another thing to consider, do you really need an autorun.inf file in that package? or can it simply be removed, which may make everything much happier all around.

Hope this helps in some way,

Jason, thank you for the extra set of eyes.  I feel pretty dumb as I stared at that log all day and somehow missed the reference to autorun.inf.  It almost certainly is AV messing with the files.  I will double check in the morning and add exclusions for _SMSTaskSequence.

Thanks again,

Jeff