Skip to main content

Issues deploying a .tib taken from a 500GB drive to a 256GB drive

Thread solved

I've been using Snap Deploy 6 (WinPE based) on a USB stick to capture images with Master Image Creator and then deploy them using the Standalone Utility and it's worked well for my Windows 10 machines, including the two machines I'm working with now (so no issues with the drives or their drivers in these two computers)

I captured a Windows 11 image from a PC with a 500GB SSD. The actual .tib file is 38GB. When I try to use the Standalone Utility to deploy to the other machine (with a 256GB SSD), it fails with the message: "Failed to deploy the image to target disk 1. Possibly, the disk size is less than the source image or the image may be corrupted."

If I instead change the disk space utilization setting from "occupy entire disk" to "as in the master image", WinPE appears to crash/fail and the computer shuts down!

I've tried re-capturing the image 3 times to rule out a corrupt file, but get the same results each time.

A quirk that seems notable, maybe:

On the "select the volume that you want to deploy" screen, the C drive in the captured image says-- capacity, 446GB, free space, blank, FS: Unknown Partition 0x0. Makes me think something about the donor's C drive is hinky. Does it need a label or something similar? I've run chkdsk on both the captured drive and the drive i want to deploy to with no issues found.

What can I change about either the donor or the recipient machine to make this deploy work?

0 Users found this helpful

Found it- the new Windows 11 install had BitLocker in a state I would describe as "semi-on" ("waiting to enable" or something similar in the interface, "BitLocker Encrypted" in Disk Management.) Decrypting from the command line with manage-bde -off c: did the trick, just in case this catches someone else off guard. After capturing a new image from the decrypted drive I had all the options and behaviors I would normally expect.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Allison Cavis wrote:

Found it- the new Windows 11 install had BitLocker in a state I would describe as "semi-on" ("waiting to enable" or something similar in the interface, "BitLocker Encrypted" in Disk Management.) Decrypting from the command line with manage-bde -off c: did the trick, just in case this catches someone else off guard. After capturing a new image from the decrypted drive I had all the options and behaviors I would normally expect.

Hello Allison!

Welcome to the forum.

Thanks for participating and for sharing what helped to solve the issue.

Thanks in advance!