105437

We have deployed 3 or 4 additional devices and have not run into this again. The one that did have the issue had a hybrid hard drive if that could make any difference.

The c drive was renamed to d on the target PC when deploying an image. Imaged PC would not boot as a result. Is this a known bug that happens sometimes?