-deleted-
Re: BitLocker fun and a SQ about mounting an image as a HD
-deleted-
Last edited by Scott on Tue Apr 28, 2020 3:41 pm, edited 1 time in total.
Re: BitLocker fun and a SQ about mounting an image as a HD
-deleted-
Last edited by Scott on Tue Apr 28, 2020 3:42 pm, edited 1 time in total.
-
TeraByte Support
- Posts: 3624
- Joined: Thu May 05, 2011 10:37 pm
Re: BitLocker fun and a SQ about mounting an image as a HD
The only thing that happens is if you don't change the signature and
it's an image of the hard drive, the mounted drive will be offline since
you can't have two with the same signature. Bringing it online would
make the mounted one have a new sig which if you then backed up wouldn't
work. If you change sign on mount, all that is handled. If it's from
another system, then don't have to change signatures on mount.
On 4/24/2020 5:11 PM, Scott wrote:
> Soon after receiving a new Windows 10 system, I used TBIHD to mount an image on it from my previous Windows 10 installation. When I was done, Windows wouldn't let me dismount the image, which concerned me--what was Windows doing with that mounted Windows volume? (And it was literally Windows itself that had open file handles preventing the dismount; I believe it was the "System" process, but I can't remember for sure.)
>
> After the required reboot, I could swear that something about the partitions on my new system's drive looked different in Disk Management. I believe the "System" and "Recovery" labels no longer appeared, as they had before.
>
> So, maybe this is a stupid question, but would mounting and accessing a Windows 10 image as a hard disk with TBIHD cause a running Windows 10 system to automatically make changes in the background--and potentially, changes that wouldn't affect boot until BitLocker was enabled?
>
> Today, I tried using BitLocker to encrypt my Windows volume, but it rendered my system unbootable during the pre-encryption system check: My BIOS didn't even recognize my Windows 10 drive as bootable.
>
> Any idea if these two events are related, and/or what Windows/BitLocker would have changed to cause this issue?
>
>
it's an image of the hard drive, the mounted drive will be offline since
you can't have two with the same signature. Bringing it online would
make the mounted one have a new sig which if you then backed up wouldn't
work. If you change sign on mount, all that is handled. If it's from
another system, then don't have to change signatures on mount.
On 4/24/2020 5:11 PM, Scott wrote:
> Soon after receiving a new Windows 10 system, I used TBIHD to mount an image on it from my previous Windows 10 installation. When I was done, Windows wouldn't let me dismount the image, which concerned me--what was Windows doing with that mounted Windows volume? (And it was literally Windows itself that had open file handles preventing the dismount; I believe it was the "System" process, but I can't remember for sure.)
>
> After the required reboot, I could swear that something about the partitions on my new system's drive looked different in Disk Management. I believe the "System" and "Recovery" labels no longer appeared, as they had before.
>
> So, maybe this is a stupid question, but would mounting and accessing a Windows 10 image as a hard disk with TBIHD cause a running Windows 10 system to automatically make changes in the background--and potentially, changes that wouldn't affect boot until BitLocker was enabled?
>
> Today, I tried using BitLocker to encrypt my Windows volume, but it rendered my system unbootable during the pre-encryption system check: My BIOS didn't even recognize my Windows 10 drive as bootable.
>
> Any idea if these two events are related, and/or what Windows/BitLocker would have changed to cause this issue?
>
>