TI 2018 disables fast startup in Windows 10 even though "run at startup" is unchecked
Hi!
I have a problem with TI 2018 (latest update) disabling Windows 10 fast startup all the time when a scheduled backup is starting or when I change settings for a backup task.
I know that there are several circumstances when TI disables fast startup on purpose, e.g. when a missed backup is scheduled to run at system startup after XX minutes. Such settings were set for my backup tasks during the last months because I wasn't using fast startup and disabled it by myself.
Now I want to use fast startup, so I enabled it again and unchecked all "run at system startup" settings in all my backup tasks. And none of my backup tasks is scheduled to run at shutdown or startup. The only schedules I use are "daily" and "monthly" at fixed times. But True Image is still disabling fast startup immediately whenever a backup task starts.
Could that be a bug because I used the "run at system startup" setting before? It wouldn't be too convenient if I have to reinstall TI or delete and recreate all my backups tasks just to convince it that there is nothing scheduled at startup and it can let fast startup enabled.
As a temporary workaround, I forced fast startup by applying a group policy (Computer Configuration\Policies\Administrative Templates\System\Shutdown\Require use of fast startup). The setting is now "managed by administrator" and greyed out. TI still unticks the fast startup checkbox on each run, but Windows is ignoring this setting because of the group policy.
But this is not my preferred solution. Any suggestions or did I miss something?


- Log in to post comments

Martin & Steve,
I believe that the data for Fast Startup to work is stored in hiberfil.sys. Steve...please verify this.
Here's my theory:
If Fast Startup is enabled, then at shutdown, Windows stores the computer state in hiberfil.sys, and hiberfil.sys is not updated during normal computer ops, only at shutdown.
Therefore, if hiberfil.sys is not excluded and is included in the .tib file, then ATI turns Fast Start off for the backup. If the .tib has a hiberfil.sys file and Fast Startup is enabled, then the first boot up after a restore would be based on an old (not updated) hiberfil.sys which could possibly result in lost data.
If hiberfil.sys is excluded and Fast Startup is enabled, then after a restore, at boot up, Windows looks for hiberfil.sys, does not find it, then goes through a full boot up sequence. So, if hiberfil.sys is excluded, ATI does not need to turn Fast Startup off.
Based on previous threads, I know that Steve usually excludes hiberfil.sys.
This could explain why Martin gets the problem and Steve does not.
Question for Martin...is hiberfil.sys excluded in your backups?
Once again, this is theory.
- Log in to post comments

Randy, interesting theory - I have never included any of the Windows system files that ATI excludes by default (pagefile.sys, hiberfil.sys & swapfile.sys) but you raise an interesting scenario in your theory! I cannot really think of any good reason to include any of these files - their contents is volatile to say the least and Windows creates new versions of the files if any are missing, plus of course they can be of significant size.
- Log in to post comments

Steve, Like you, I don't include any of Windows system files that ATI excludes. I also don't use Fast Startup as both of my computers have SSDs.
If Martin does not exclude them, then I will turn on Fast Startup and do a test.
If Martin does exclude them, then my theory is shot.
- Log in to post comments

Actually, that's an interesting theory and worth to check.
While I have excluded these files from my daily incremental backups (to prevent it from backing up GBs of rubbish data each day), I do a second monthly backup of everything to an external USB drive. Because this is only done monthly as a secondary backup (in case of my primary backup is lost for any reason), I just disabled exclusions completely.
And you're right, restoring an old hiberfil.sys with fast boot enabled and Windows trying to resume from this won't work and can be desastrous. I haven't really thought about that when I included these files...
Ok, I will try what happens if I add these three files (pagefile.sys, hiberfil.sys & swapfile.sys) to exclusion list.
- Log in to post comments

Hello Martin,
does the issue still reproduce on your system? even with enabled exclusions? If yes, it's something worth investigation with the help of our support team.
- Log in to post comments