Re: Disable Fastboot
Posted: Fri Sep 30, 2016 1:15 pm
I have read the forum notice - that's what prompted my question. The notice says "It appears that Windows does not clear its cache and remount file systems after resuming from hibernation."
Previously, Terabyte Support said "the fastboot issue has to do with windows in general." Bob Coleman added "if multiple OSs with fastboot enabled have access to the same drive/partition..."
To clarify the specific case I'm asking about, consider the following:
1) IFW is installed on a Windows 10 machine - Windows is the only OS present.
2) IFW is run as a scheduled task, and regularly creates images with VSS or PHYLOCK, saving them to a server.
3) At some point, the drive fails.
4) A new drive is installed. The system is booted to IFL, and IFL is used to restore the image created by IFW from the server.
In that case, the image was not created from a disk that was "hibernated". It was created from a running Windows environment with IFW. So my question is, does having Fastboot enabled change the structure and organization of the disk _on_a_running_system_ in a way that prevents IFW with VSS or PHYLOCK from creating a valid image that can be successfully restored to a new drive?
Previously, Terabyte Support said "the fastboot issue has to do with windows in general." Bob Coleman added "if multiple OSs with fastboot enabled have access to the same drive/partition..."
To clarify the specific case I'm asking about, consider the following:
1) IFW is installed on a Windows 10 machine - Windows is the only OS present.
2) IFW is run as a scheduled task, and regularly creates images with VSS or PHYLOCK, saving them to a server.
3) At some point, the drive fails.
4) A new drive is installed. The system is booted to IFL, and IFL is used to restore the image created by IFW from the server.
In that case, the image was not created from a disk that was "hibernated". It was created from a running Windows environment with IFW. So my question is, does having Fastboot enabled change the structure and organization of the disk _on_a_running_system_ in a way that prevents IFW with VSS or PHYLOCK from creating a valid image that can be successfully restored to a new drive?