Win10 Slow boot time. Help debug with Windows Performance Analyzer

My win10 has a long boot time -approx. 1 minute till boot main path ends.
I am trying to figure out what causes this long boot delay.
I also use Acronis boot manager. This is a pre boot sequence which happens before windows boot starts. The recording I refer to happened after the acronis boot.
This fits the actual time measurements I did which excluded the initial acronis loader.
I counted the time it takes for the initial ‘boot turning dots’ and it fits the Boot Main Path time which is ~52sec.
Part of this is due to autochk.exe (14 seconds) which keeps running every time.
But I don’t understand what happens between Boot-Pre_fetch to Boot-sessioninit-phase? These are 21 seconds.

Basically I’d like some guidance here as to what I should do/try

I should also note that i found that:
'autochk.exe' starts all the time. I’ve already tried to disable it using chkntfs /X C: D: E: F: (all my drives) and I see that under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager the autocheck for these drives is disabled

What happens between Boot-Pre_fetch to Boot-sessioninit-phase? Which process is causing the delay as i can't find anything in the report.

Memory usage is at 100% from boot start to winlogon? See the 2nd snapshot.

There are 'unkown items' in the Disk Usage report (e.g. 4 sec usage in the last snapshot)

I have coreI7, Asus PRIME H370 MB, Geforce 1080TI Another input is that I have 2 SSDs and 3 HDD connected to my PC as well as multiple USB devices I’ve uploaded the recorded boot here:
link to boot recording

Thanks for any help.

Welcome to the Forum

Do a disk check on ALL your drives. Open a CMD window as administrator and type:
chkdsk X: /f (replace X by the drives letters)
For the C: drive, type chkdsk C:
If it finds issues, type:
chkdsk C: /f
It will say it is in use and if you want to schedule to next start =yes

Do a clean boot
Run msconfig and disable all non M$ services and disable all start up programs. Restart and see what are the results.

In my computer, antivirus is the most time consuming on start and shutdown.

Thank you,

As for clean boot, i forgot to mention this but I already did a clean boot with only windows services and while all statup program were disabled. There was no change in boo time, that is for the main-boot-path.

Have you had a chance to look at the graphs i attached or at the actual recording?
Is there anything there which can shed some light on this?

I will check all the disks. as you suggested later on.

A problematic disk can slow down start up.
With a SSD as boot disk, boot times should be around ~25 sec.

Hi,
Scanning the disks showed no errors.
However, the fact that 'autochk.exe' starts all the time despite the fact that I’ve already disable checks using chkntfs /X C: D: E: F: led me to try something else.
I disconnected all my hard drives and all usb devices apart from the boot drive.
With only one drive Boot Main Path took less than 20sec
I then reconnected all the drivers - one by one and the problem did not reappear.

Windows performance Analyzer initially showed that the delay was related to 'autochk.exe' which was very helpful.

Have you got "Fast Start-up" switched OFF? If so then try it in the ON position. You can always switch back if it doesn't help.

Glad you fix it.
Thanks for the feedback

Thank you for your replay.
I will certainly check what you suggest to reduce the chances of errors in the future.
In which report did you observe this problem?
How did you know these were problematic? After all there are other entries int eh snapshot you sent with HDD\00000?



However, as I sated earlier in this thread:
Scanning the disks showed no errors.
However, the fact that 'autochk.exe' starts all the time despite the fact that I’ve already disable checks using chkntfs /X C: D: E: F: led me to try something else.
I disconnected all my hard drives and all usb devices apart from the boot drive.
With only one drive Boot Main Path took less than 20sec
I then reconnected all the drivers - one by one and the problem did not reappear.

Windows performance Analyzer initially showed that the delay was related to 'autochk.exe' which was very helpful.