Skip to main content

Boot time much longer?

Thread needs solution

Before installing ATIH 2016 my boot up was 45-60 sec. to desktop, Now  3m:45 sec

I have a SSD, Intel I7-5820K, 16gb ram. What is causing ATIH 2016 to add 3 min to the boot time?

No other OS Win 10 settings were changed. Not happy, may have to uninstall and request a refund.

0 Users found this helpful

Sam, this is another gripe that has been aired in the forum previously. ATIH changes the Windows 'Fast Boot' settings which you can find via the Power options.

See post https://forum.acronis.com/forum/114438 where this was mentioned recently.

I've uninstalled ATIH and requested a refund. Boot time 21 sec vs 3m 45 sec, which I can't endure. No fastboot  hiberfile (hiberfil.sys) is created, so must be just a quick booting system. I don't think my issue was related to Windows 'Fast Boot' settings because my ssd software diables hibernate with it's optimization software and a fastboot option power setting is non-existent. Thanks for the reply!

Sam,

You might want to run a SMART disk health scan on your drives in your PC as Acronis scans disks on startup for errors and if found can delay boot time.  Something to look at just to make sure this was not related to an underlying issue.

Good point, ssd all good, HDD WDC ok, Seagate HDD has ECC ERROR RATE FAIL? Ran CHKDSK and Windows reported: Windows has scanned the file system and found no problems. No further action is required. ?? Thanks for the tip!

Sam,

Just to be doubley sure , you don't have any post command shutdowns or restarts in your backup tasks do you?  If you do, this behavior is by design since fastboot would not allow for the shutdown commands to actually perform as expected if fastboot remained enabled.

The links that Steve sent show that Acronis found this to be a bug in some instances where fastboot is disabled even if shutdown tasks are not in the post backup script commands, and it was mentioned that it's scheduled to be resovled in the next update. We don't have an exact date yet, but sounds like it should be this month, as Gaidar, General Manager, has posted in other forum threads that he anticipates the release to be in April.  Perhaps, you can reach out to Acronis to have them "hold/extend" your refund timeline until you can test with the new update and see how it goes?  Worth a shot anyway.

I have never been able to reproduce this issue on any of my systems.  I wonder if instead of upgrading to 2016 (as it looks like you upgraded from a previous version), you could try a clean uninstall and reinstall using the ATIH 2015/2016 clenaup tool and see if the issue still exists after a "fresh" install?  If that works - awesome.  If not, hopefully the next update does resolve this, but if not, then at least we all tried.  

I currently have an unfinished version of the new ATIH 2016 update for beta testing and will test creating a shutdown task to force disabling fastboot and make sure that works.  I will then remove the shutdown task and enable fastboot on the test system and see if it maintains the setting or not and provide feedback to Acronis if something is amiss.  Unfortunately, I cannot got into specifics about the next update before it is released, but I can say that there does seem to be a lot of stability improvements (in my testing) and updated driver support in the default bootable recovery media.  Really looking forward to the finished version release and am hoping it won't be too much longer now, but I'm not privy to that type of information, nor could I discuss it beforehand (even if I was).  

CHKDSK would not work to detect or fix the ECC Fail error.  Best to use the Seagate Seatools application to attempt repair of the drive.  If that fails I would pursue an RMA of the drive from Seagate.

Additionally you should backup your drive by some means as you could be facing emminate drive failure.

Update, I DL Seagate's See Tools for Windows. Ran the tests on the Seagate drive, all good 100%.  I understand there is no standard SMART test, each manufacturer has a unique method of what is reported. The ECC Fail error was reported by Samsung Magician software that came with my SSD. CrystalDiskInfo reports health status good. OK, It seems to be a tail chase. I'll wait for the updated ATIH 2016 that was mentioned to be in beta testing and try again. My system is working as before this Acronis adventure, boot up in 21 seconds. I've had Macrium free installed and boot time not affected.

Hello, Sam.

Did this start happening immediately after installing True Image? Or after having used the program for some time?

Did you use any of the additional tools, such as Try&Decide or Startup Recovery Manager?

Hi Dmitry,
Yes, immediately after installing True Image.
Did not use any of the additional tools, such as Try&Decide or Startup Recovery Manager.
Just configured & scheduled a full system backup.
I then removed the scheduled backup and still long boot time. All back to normal after ATIH uninstalled.

Thanks,
Sam

 

__________________

Hello Sam,

If you do not need Nonstop backup feature, you can disable it and see if this speeds up the process. There was an issue in one of previous versions of the program when Nonstop backup service was affecting particular system bootup time. Open Windows Start menu, type services.msc and hit Enter. Double-click on Acronis Nonstop Backup Service and choose Disabled from Startup type drop-down menu. Click OK to save changes and reboot.

Regards,

Slava

Sam DuPont, if you're still following this thread as well, v6559 was released on Monday and comes with some improvements and bug fixes.  Personally, I would suggest not using the in-app update (that's just me though) . I would shutdwon Acronis, download the update from the account and right-click "run as administrator" while Acronis is shutdown.  Be advised, it will kill Windows Explorer briefly for the update as well - this is normal and only lasts a short time, but if you have any file transfers in progress, hold off on updating until they're done.