USMT Restore Task Sequence failing with error code 0xC0000135

Posted on 2016-07-14
Medium Priority
Last Modified: 2016-07-18
Hello Experts-Exchange,

I've been tasked with testing USMT at the company I work at and I have created two seemingly simple task sequences to capture a user state to a state migration point and then restore it to a different computer. The two task sequences are really straightforward, as you can see:
I created a computer association between two lab machines and then proceeded with testing the task sequences. The capture went through without error and I can see the folder with the USMT.mig file that was created on the state migration point. However, when I run the restore task sequence, it fails every time during the Restore User State step. Here is what shows up in the smsts.log file:

PreLonghorn USMT returned error (0xc0000135). Look USMT log file loadstate.log for detail error message.      OSDUSMT      7/14/2016 9:35:55 AM      4484 (0x1184)
Invoking ReleaseSource on USMTPackagePath C:\_SMSTaskSequence\Packages\CDP00001      OSDUSMT      7/14/2016 9:35:55 AM      4484 (0x1184)
ReleaseSource() for C:\_SMSTaskSequence\Packages\CDP00001.      OSDUSMT      7/14/2016 9:35:55 AM      4484 (0x1184)
reference count 1 for the source C:\_SMSTaskSequence\Packages\CDP00001 before releasing      OSDUSMT      7/14/2016 9:35:55 AM      4484 (0x1184)
Released the resolved source C:\_SMSTaskSequence\Packages\CDP00001      OSDUSMT      7/14/2016 9:35:55 AM      4484 (0x1184)
OSDMigrateUserState finished: 0xc0000135      OSDUSMT      7/14/2016 9:35:55 AM      4484 (0x1184)
Process completed with exit code 3221225781      TSManager      7/14/2016 9:35:55 AM      132 (0x0084)
!--------------------------------------------------------------------------------------------!      TSManager      7/14/2016 9:35:55 AM      132 (0x0084)
Failed to run the action: Restore User State.
Unknown error (Error: C0000135; Source: Unknown)      TSManager      7/14/2016 9:35:55 AM      132 (0x0084)
Set authenticator in transport      TSManager      7/14/2016 9:35:55 AM      132 (0x0084)
Set a global environment variable _SMSTSLastActionRetCode=-1073741515      TSManager      7/14/2016 9:35:55 AM      132 (0x0084)
Set a global environment variable _SMSTSLastActionSucceeded=false      TSManager      7/14/2016 9:35:55 AM      132 (0x0084)
Clear local default environment      TSManager      7/14/2016 9:35:55 AM      132 (0x0084)
Failed to run the action: Restore User State. Execution has been aborted      TSManager      7/14/2016 9:35:55 AM      132 (0x0084)
Set authenticator in transport      TSManager      7/14/2016 9:35:55 AM      132 (0x0084)
Failed to run the last action: Restore User State. Execution of task sequence failed.
Unknown error (Error: C0000135; Source: Unknown)      TSManager      7/14/2016 9:35:55 AM      132 (0x0084)
Set authenticator in transport      TSManager      7/14/2016 9:35:55 AM      132 (0x0084)
Task Sequence Engine failed! Code: enExecutionFail      TSManager      7/14/2016 9:35:57 AM      132 (0x0084)
****************************************************************************      TSManager      7/14/2016 9:35:57 AM      132 (0x0084)
Task sequence execution failed with error code 80004005      TSManager      7/14/2016 9:35:57 AM      132 (0x0084)

I've looked for the LoadState.log file but it does not exist. The only relevant information I found on this problem was from (Technet but the answer provided there did not help me.

Thanks in advance!
Question by:IC-ADMIN
1 Comment

Accepted Solution

IC-ADMIN earned 0 total points
ID: 41717754
I ended up figuring it out on my own. It turns out that the Loadstate.exe command line was failing when ran manually with the following message (which I was not seeing in the logs or otherwise):

"The program can’t start because DismApi.DLL is missing from your computer. Try reinstalling the program to fix this problem."

Turns out this is a documented issue at Microsoft:


I followed this resolution to update my USMT package in SCCM and the issue was resolved.

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Understanding the various editions available is vital when you decide to purchase Windows Server 2012. You need to have a basic understanding of the features and limitations in each edition in order to make a well-informed decision that best suits …
Are you looking to start a business? Do you own and operate a small company? If so, here are some courses you need to take before you hire a full-time IT staff.
This Micro Tutorial will teach you the basics of configuring your computer to improve its speed. It will also teach you how to disable programs that are running in the background simultaneously. This will be demonstrated using Windows 7 operating…
This Micro Tutorial will go in depth within Systems and Security in Windows 7 and will go into detail regarding Action Center, Windows Firewall, System, etc. This will be demonstrated using Windows 7 operating system.

621 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question