Thanks for your contribution, I appreciate it! I think the ntbtlog.txt file only contains a list of drivers that are loaded when booting? I haven't checked but I think it's a subset of the files listed in the "%SystemRoot%\Prefetch\Layout.ini" file.
Isn't that what you need when you want to optimize the boot?
As far as I could see you are right it is a subset of layout.ini. The charm of it is that it contains only the bootfiles, and that it will not bring never used files to the front. The drawback is that there are more files than those loaded at boot that influence your experience of boot-speed. P.E. the *.lnk files on the desktop.
Actually, no, it isn't what you want to optimize the boot.
In this context, there is absolutely no distinction
between running an application and reading the exe to get the icon out of it. Both involve finding the file, seeking to its start, reading, moving on to process the next file.
Even if the exe is only wanted so that you can pull an icon out of it, you still need to seek all the way to the file and back.
If you want to optimize boot, then you need all
those files close together, not just the drivers.
That said, I agree that the layout.ini file doesn't know when to stop, i.e. doesn't know when boot is over and operation of the PC has started, which is incredibly broken of it.
However, why are people so interested in optimizing boot. Sure, if I move winword.exe into the boot zone it may shave 1/10th of a second off my bootup time, but it will add that 1/10th of a second onto the time it takes to run word, which I do way more than once per reboot.
Personally, I optimize for operation of the computer. On the rare occasions when I reboot, I go and get a coffee