There are two options available once the program has been identified. A quick Google search revealed that it is a driver used by Daemon Tools. Look at the path of the entry that is using that much boot time, the driver name is located at the end of the path. The example above shows a gap of almost 16 seconds between the two marked entries. Gaps of a few seconds need to be analyses, everything else is usually not worth analysis. All you need to do now is to locate gaps between events. This lists the load time for all operations. The important part is to look at the time of day column. Now add the following two filters to the list:Ī click on ok will only display the entries that match both filters that have been added.

Locate the filter Process Name is System Exclude and remove it from the list of filters. This is a huge log file and the first thing that needs to be done is to filter for entries that are related to system drivers. Load that boot log afterwards using or File > Open. You will be asked to save the boot log to a directory on the hard drive. Restart the computer afterwards and start Process Monitor once the operating system has loaded. This makes Process Monitor log the next boot process of the operating system. Select the Options menu at the top and the Enable Boot Logging option in that menu. The program can however be used - with some expertise - to locate problematic drivers that slow down the boot process. It will log everything which usually results in boot logs that are larger than 100 Megabytes. Process Monitor comes with an option to log the Windows boot process.

Process monitor boot logging