Software Question

Sysprep Creator pending reboot detected

02/15/2018 1821 views
Hello everybody,
i use the sysprep creator to manage my sysprep. But every time it says to me, that i have to reboot. I did this ten or more times and nothing changes. How can i solve this problem? It's very annoying...
My Windows version is 1709 x64.
with best regards
Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author

I found the solution at myself.

  1. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager.
  2. Right-click the PendingFileRenameOperations value and select Delete from the context menu. When prompted, click Yes to confirm the delete operation.

Also in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet01.

In my case there was a logitech registry entry.

Answered 02/20/2018 by: Xykar
White Belt

Community Chosen Answer


Did you run windows updates before the sysprep?

Maybe run all updates and a few more reboots and see.

I use it fine. in my case it would not turn of the tileDataModelServer

when i click fix issues. Had to turn it off manually.

If IT doesnt work, try a new install to image. Might be a fluke and

you could waste days troublshooting a one of problem.

Answered 02/16/2018 by: akmagnum
Red Belt

All Answers

Manually turn off anti-virus and stop the tileDataModelServer service as those have been my common red exes when using sysprep creator.
If that doesn't fix the problem, which items are being shown as errors? 
Answered 02/20/2018 by: ddelgadi
Senior White Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ