K2000 3.5 WIM Imaging - taking forever to rebuild image
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 - balcinovic21 6 years ago
Answers (1)
Please log in to answer
Posted by:
andrew_lubchansky
11 years ago
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.
Comments:
-
Not big - just a basic Windows 7x64 sysprepped image. - sfigg 11 years ago
-
How long has it been since the image finished within the KBE? - andrew_lubchansky 11 years ago
-
About 2 hours right now. - sfigg 11 years ago
-
(and stuck at 3.57GB, which the image I'm guessing should be bigger) - sfigg 11 years ago
-
Yeah that is definitely not the correct behavior. Also, WIMs are compressed so a base install of Win7 around that size is not abnormal. - andrew_lubchansky 11 years ago
-
Not to point out the obvious but did you refresh the page? - Timi 11 years ago
