Acronis True Image 2016 & Windows 10 Fast startup conflict ?
Sam, before you run the cleantool, could you submit feedback through the app and attach a system report too. If this is still an issue, having that information sent to Acronis will hopefully help them identify the cause.
After that, if the cleantool works (which it probably will), hopefully you'll be good to go that way, but also can help to contribute to the resolution if it is still occurring and you don't have any backups schedueled to run at shutdown.
Thanks for your help!
I just sent feedback with system report in. I have submit this information in the past but I have sent it again.
Many thanks! If the problem continues to carry over for some in 6569, hopefully the feedback will get reviewed by the developers to keep progressing for a fix for all. It does seem like 6569 resolved this for a lot of people, but interesting that it still persists in some cases.
Bobbo_3C0X1 -
I uninstalled, ran cleanup utility, rebooted, installed fresh downloaded version and ran as running administrator. Same problem.
See attached screen shots. Before scheduled backup and after scheduled backup... Sent in System Report... Again this morning...
Dunno why but I do not even see this option. Why is that?
Karl,
I am certain that if you do not see the Fast Starup options as your screenshot shows it is because Hibernation is turned off on your machine. Fast Startup is dependent on Hibernation so Hibernation must be on to enable it.
Hallo Karl Heinz
Um den Ruhezustand zu aktivieren, startet man die "Eingabeaufforderung (Administrator)" und verwendet "powercfg -h on" um den Ruhezustand zu aktivieren.
---
To activate Hibernate mode, you start the "Command Prompt (Administrator)" and used "powercfg -h on" to activate hibernation.
Hi guys, I think it was me using Samsung Magician to deactivate this feature. Mea culpa. Thanks G. Uphoff.
Enchantec, FtrPilot and I have been testing and I think we found a bug that we are reporting for further testing. Additional forum testing may be helpful too to confirm.
If you are using fastboot, before any backups are run (like say right after a cold restart) the following regkey should be = 1 (http://www.tenforums.com/tutorials/4189-fast-startup-turn-off-windows-1…)
-------------------------------
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power
HiberbootEnabled DWORD
0 = Turn off fast startup
1 = Turn on fast startup
-------------------------------
I find this to be the case in all of my testing, regardless of how I power off (except if using shutdown /s which ignores fast boot and shutsdown all the way) when fastboot is enabled and NO Acronis backups have been run yet. Additionally, a power down with fastboot enabled and NO Acronis backups have been run yet, when I shutdown and turn the computer on, Windows events show 44 (entering sleep), followed closely by event ID 27 (0x1 = fastboot)
However, after any backup in Acronis is run (scheduled, manual, new, old, etc.) the reg key above is set to 0 almost immediately in the registry. This is confirmed with procmon.exe and in the registry after refreshing the key. The Windows event log also shows no event ID 44 and the following event ID 27 is now 0x0 - regular boot.
Upon backup completion, I would think this reg value would get set back to 0, but it does not appear to - at least not for me - it now remains 0 on my system until I restart or shutdown. I then shutdown and it does a full shutdown (confirmed in Windows System Logs as event ID 27 0x0 as well) , but upon restarting and checking again, it is back to 1 in the registry and shutdowns will be fastboot in the Windows Event logs again up until the next Acronis backup is run.
This seems to be a bug of some kind. I would have never known though as my 950 Pro is lightning fast and I have fastboot turned off anyway. For me, I can't tell the difference if fastboot is on or off with this drive so it's not been an issue. However, this has come up a few times in the forums and Enchantech wanted to do some more testing and I think we may have identified an issue. This is just initial testing, so if there are others who can confirm this on their systems too, please submit feedback to Acronis and reference this forum thread as well.
I worked with Acronis Support yesterday, 5/23/16. They saw the problem first hand and were able to reproduce it on their PC. They requested a System Report and Process Monitor Log, which I provided. The impression I got was that they had not seen this problem before. At any rate they acknowledged that there was a software problem that needed to be resolved.
I am a little confused as to why I had to submit a System Report that I had submitted several times.
Hello All,
Thank you for your help in this issue investigation. Developers have been notified that conflict with Fast StartUp remains on the latest version of the program.
We will see if this could be addressed in future versions of the program.
Regards,
Slava
William. First off, thanks for taking the time to troubleshoot and be an extra set of eyes on ears. Really appreciate you taking the time to help work with the support engineers.
Slava, thanks too for bringing this to the developer's attention. I'm really glad that you've been so active in the forums lately! Nice to see the Acronis engineers and technicians popping in more often!!!!
Hello All,
Thank you for your help in this issue investigation. Developers have been notified that conflict with Fast StartUp remains on the latest version of the program.
We will see if this could be addressed in future versions of the program.
Regards,
Slava
Hello Slava,
perhaps it is helpful to know the following:
On my PC, I have the same problem that after every backup creation the Fast StartUp option is disabled. Otherwise, it will remain active.
On my machine is running Windows 10 Professional version 1511 build 10586.318 as an upgrade installation. Even a complete uninstall of Acronis True Image 2016 using the cleanup tool and a subsequent reinstallation of the last build brought no improvement.
About another forum I know someone who is experiencing this problem does not occur since the last update of Acronis.
This uses a PC with a Clean Install of Windows 10. Possibly there is a relationship.
I am too much a layman to understand the differences between an upgrade and a new installation of Windows 10. In my opinion it would be no practically solution to recommend all users with this problem a Clean Install of the operating system. I hope, your developers find a better solution.
Regards,
Richard
I have a brand new system. It is very fast and has an SSD. Boot was very fast until I installed ATI. Now boot takes about 5 minutes. I have the lastest ATI installed (6571). I did send in feedback with system report.
I have NO backup scheduled because I wanted to avoid this possible problem. This is a huge problem with ATI. I switched to ATI from Norton Ghost when I went to Windows 10. Ghost had no such problem.
Boot takes so long, that now I have to walk away and hope that it will complete. Now boot on my super fast system takes longer than my old slowest systems ever. This is a real problem.
This new system uses Windows Professional and is up to date.
I finally got Acronis to acknowledge that they had a problem. They were able to reproduce it. It took a lot of effort and time to get this accomplished. There are two problems and it all concerns Fast Startup.
- If a backup is performed TI 2016 resets Fast Startup. It occurs when the backup starts.
- If Fast Startup is set and a backup is scheduled to occur while the PC is turned off that backup will not be performed.
My temporay solution is:
- Create a shortcut to "Power Options".
- Have a reminder to check for a backup that should be performed on a given day.
- If the backup did not run then manually start the backup.
- Utilize the shortcut to "Power Options" and manually set "Fast Startup".
By doing this I have the PC start as it normally would and I get all of my backups.
You need to contact Acronis. I had to pay for a PPI, which they refunded once they saw and were able to reproduce the problem.
Good luck.
Thanks to all investing time to reproduce the problem. I finally gave up... Scheduled backups and the option to redo them if the machine was off is one of the main features of ATI. I used it for years now and also on the PCs of the family. Now this is a nightmare... I can not rely on ATI and I always have the fear that backups are not performed on the machines where I do not have the chance to frequently check this. The first priority of a backup tool is that it must be reliable.
Hopefully there will be a fix for this issue for ATI 2016. I do not want to upgrade to ATI 2017 (with fancy new HMI I guess...) just to get a fix for a basic functionality of the software. I appreciate that Acronis provided some important updates for ATI 2016 so far (which was not common for the latest ATI versions). Hopefully this will be continue for this important fix.
Ok, True Image 2017 is out and still no fix for this issue in 2016. :-(
Nevertheless it would at least be useful to know if this issue has been fixed in 2017...
I don't plan on purchasing new version (2017) until I know this issue is fixed. I have uninstalled the current version (2016) out of frustration.
It is working for me in 2017.
In 2016, it is not working because Acronis runs missed backups based on the system event code triggered by a complete startup. With fastboot enabled, the system is only hibernating so this even is not triggered in the event log. However, you can always trigger a missed backup if you "reboot" instead of shutdown. You can also force a full shutdown using shutdown /s /t 0 (this can be pasted into notepad and saved. Then change the .txt file extension to .bat). Now use your new bat script (double click the file) instead of your regular shutdown button (if/when you want a full shutdown instead of fastboot hibernation). Upon startup, missed backups would run.
I don't know if there will be any additional updates to 2016 now that 2017 has been released. Last year, there was still one finaly 2015 update. Only Acronis can answer that for us.
It appears that TI 2017 has resolved all the problems I had with Fast Startup.
I installed TI 2017 yesterday. I ran a job and it did not reset Fast Startup.
I had a job that was scheduled to run while the PC was turned off. Fast Startup was set and the PC booted quickly. The scheduled job ran and Fast Startup remained set. You have to make sure that the setting in TI, for a job that is scheduled to run while the PC is off, has the setting “Run at the system startup…” set.
I would have to say that both of the problems I complained about are resolved.
Great to hear that! I will pass this news on to the Acronis team, and hopefully they will be able to fix this for ATIH 2016 aswell.
I am glad to hear that TI 2017 has resolved all problems. But I have TI 2016, which I have never been able to use properly because of that problem. And for TI 2016 the problem has not been solved, and never will be I suspect. So why should I pay for an upgrade to TI 2017? All I know is that I will never use Acronis products anymore and I will certainly not recommend it to anyone else either.
What Acronis should have done is give a free upgrade to all owners of TI 2016, that might have made me think more positively about this matter.
I am glad to hear that TI 2017 has resolved all problems. But I have TI 2016, which I have never been able to use properly because of that problem. And for TI 2016 the problem has not been solved, and never will be I suspect. So why should I pay for an upgrade to TI 2017? All I know is that I will never use Acronis products anymore and I will certainly not recommend it to anyone else either.
What Acronis should have done is give a free upgrade to all owners of TI 2016, that might have made me think more positively about this matter.
I am glad to hear that TI 2017 has resolved all problems. But I have TI 2016, which I have never been able to use properly because of that problem. And for TI 2016 the problem has not been solved, and never will be I suspect. So why should I pay for an upgrade to TI 2017? All I know is that I will never use Acronis products anymore and I will certainly not recommend it to anyone else either.
What Acronis should have done is give a free upgrade to all owners of TI 2016, that might have made me think more positively about this matter.
I'm glad to hear the problems is resolved in 2017, but why hasn't 2016 been fixed. My issue on fast startup being disabled all the time led me to just removed ATI. I believe Acronis should do something to compensate those that had problems with ATI 2016. I don't believe that I'm going to upgrade to ATI 2017. Why - Poor Support from Acronis. No real response from Acronis on this matter.
I will not upgrade to TI 2017 just to get a bug fix for TI 2016. TI 2016 should be fixed or they should give us a free upgrade. I was appalled at the state of TI 2016 and the lack of support for such a basic problem.
The basic issue that I see is that ATIH 2016 does trouble a new and not so unimportant Windows 10 feature, while it was originally advertised as being especially compatible for Windows 10. This said, I don't intend to derail this thread with nitpicking.
I am optimistic that with help of the Acronis team and other MVPs, we will be able find a bearable solution for ATIH 2016 users. Thanks again for your patience!
Can someone confirm that the issue is fixed with latest update Build 6581?
Fixed issues contains " Acronis True Image 2016 disables Windows 10 fast startup ". For me the missed backup tasks seems to correctly work now on the next OS start.
Anyway: thank you and respect for Acronis to provide updates for TI 2016 even tough TI 2017 is already available. This is a great improvement compared to the latest versions!
Brain, see sticky post: 127113: New build is 6581 release October 26th which lists all the issues fixed in this latest build release for ATIH 2016. Windows Fast Start is mentioned twice in the list of issues fixed, so I would say that Acronis have got the message and have resolved these issues, though I cannot confirm this personally as my systems are now running the 2017 version.
I think the problem is fixed with Build 6581, at least on my pc. I have noticed that while backing up the Fast startup is temporarily turned off by Acronis. But when done it is turned on again. Maybe not the most elegant way to solve it, but it works.
try{(function() {if (typeof(lpcurruser) == 'undefined') lpcurruser = ''; if (document.getElementById('lpcurruserelt') && document.getElementById('lpcurruserelt').value != '') { lpcurruser = document.getElementById('lpcurruserelt').value; document.getElementById('lpcurruserelt').value = ''; } if (typeof(lpcurrpass) == 'undefined') lpcurrpass=''; if (document.getElementById('lpcurrpasselt') && document.getElementById('lpcurrpasselt').value != '') { lpcurrpass = document.getElementById('lpcurrpasselt').value; document.getElementById('lpcurrpasselt').value = ''; } var lploc=1;var lponlyfill=1;var lpdontsubmit=1;lpcurruser = ''; lpcurrpass = '';})();}catch(e){}
try{(function() {if (typeof(lpcurruser) == 'undefined') lpcurruser = ''; if (document.getElementById('lpcurruserelt') && document.getElementById('lpcurruserelt').value != '') { lpcurruser = document.getElementById('lpcurruserelt').value; document.getElementById('lpcurruserelt').value = ''; } if (typeof(lpcurrpass) == 'undefined') lpcurrpass=''; if (document.getElementById('lpcurrpasselt') && document.getElementById('lpcurrpasselt').value != '') { lpcurrpass = document.getElementById('lpcurrpasselt').value; document.getElementById('lpcurrpasselt').value = ''; } var lploc=2;var lponlyfill=1;var lpdontsubmit=1;lpcurruser = ''; lpcurrpass = '';})();}catch(e){}