I deployed an existing WIM image to a machine about an hour ago, then re-captured as a new WIM. I got rid of any non-relevant tasks as requested per the instructions, and after capturing this still shows. Why does it take so long? Is this normal? I don't want to wait hours for it to rebuild with built in WIM imaging, when the old KNIT way was instant.


A rebuild process is currently in progress. This configuration is locked for edit until the process completes. Refresh this page to check for status changes.

1 Comment   [ + ] Show Comment


  • So is there an answer to this? Why does the rebuild process take so long? I captured a new WIM only took 20 minutes, but it's still working on rebuild
Please log in to comment



How big of an image did you capture?  This could take a little bit of time once the image has finished capturing, but should not be taking a long time. 

Answered 03/25/2013 by: andrew_lubchansky
Black Belt

  • Not big - just a basic Windows 7x64 sysprepped image.
  • How long has it been since the image finished within the KBE?
  • About 2 hours right now.
  • (and stuck at 3.57GB, which the image I'm guessing should be bigger)
  • Yeah that is definitely not the correct behavior. Also, WIMs are compressed so a base install of Win7 around that size is not abnormal.
  • Not to point out the obvious but did you refresh the page?
Please log in to comment
Answer this question or Comment on this question for clarity