Windows 10: Slow boot time on SSD 6-mins OS loading screen

Horakti said:

http://i65.tinypic.com/2zsqnaw.png

These updates installed today ,My Windows version is still 1709 , Windows updates is deactivated from service.msc again .

OK thanks.

BTW, yesterday i switched from MBR/BIOS to GPT/UEFI to see if it helps, but it didnt change anything, apart from the OS indicating it is running under UEFI bios and that secure boot is ON.
Of course the UEFI boot partition was created which is used for the booting process.

What i did notice when booting via GPT/UEFI and not MBR/BIOS is that the ASUS logo is printed into the booting partition, so now i see the ASUS logo hanging before windows kicks in, instead of the Blue windows logo circle (i read that you can change that in BIOS but don't really care about that).

EdTittel said:

According to what I find online, the OEM logo display during early boot phases is typical for UEFI configurations. Here are some sample items on this topic you may find interesting. Doesn't seem to be cause for concern, though, especially if you don't care about disabling it in UEFI/BIOS.
Change Boot Logo - Windows 10 Forums
UEFI boot logo shows up on windows loading screen in windwos 8? - Windows Support - Neowin
Boot logo shows twice on starts up - [Solved] - Storage
HTH,
--Ed--

Yes, since i had the problem with the MBR/BIOS configuration and still having it with the GPT/UEFI configuration, which is just supposed to be supporting more partitions, higher capacity drives and advanced security options.

Oh well, i'm running out of ideas here.

Could it be due to usage of NVMe M.2 storage? perhaps this issue is not on SATA controllers?

Hi ArtsArts, two things to test:

- Change your boot loader from Grub to BCD (Windows OS loader) temporarily. If this solves your problem, simply add an entry for Ubuntu into BCD boot menu.

- Restart from Windows, not from Ubuntu. If this boot time is normal, then you can suspect Ubuntu - it probably keeps some filesystems open, which is evaluated as "dirty shutdown" by Windows and repair actions follow (log replaying etc).

hmm going for something i found few months ago and ditched.
Windows Event Viewer is displaying critical errors for code 101 (boot time degradation) for "Devic" file name and "C:\Devic" path.

Not sure why its truncated as obviously none has such a path, but seems like according to Windows 10, this is the problematic factor.. and no.. it cant be a peripheral USB as i disconnected everything and it still takes time to load.

@muchomurka Just tried that, unfortunately no changes. Only thing I have not tried at this point is, full format of both disks + clean windows install.

Any update here?
Were you able to resolve it?