Vista and Boot Performance Monitoring

[jasonlynn]

My laptop has been taking a while to boot as of late with Vista Business. So I opened Event Viewer and navigated to the Applications and Services\Microsoft\Windows\Diagnostics-Performance\Operations log to look at my boot times and get some more info. Problem is, the entry in that log is from November 27th of 2007. It has not been logging since. I have been Googling this problem for over an hour all to no avail. Any one have any suggestions as to what may have stopped this from logging?

[cluberti]

Well, first things first, running the boot logging utility will give you better information:

http://www.msfn.org/board/Trace-Vista-boot...an-t117154.html

As to the logging issue, first make sure the log isn't disabled (right-click on Operational and make sure "Disable Log" isn't checked). Assuming it's not disabled, look at the properties to make sure that the "enable logging' box is checked, the log size is a reasonable size (like 1028) and that "Overwrite events as needed (oldest events first) is selected. Then, I'd click the "clear log" button and reboot.

[jasonlynn]

Well, I checked the options you said to check, all was well. I disabled it and then re-enabled it, then cleared the log. I'll see what happens on the next reboot. As far as the boot logging utility, looks interesting. I will play around with it as well, but I still want to know why the "Boot Performance Monitoring" stopped in the first place. Gotta love vista.... I'll let ya know if disabling/enabling and clearing got it working again.

[cluberti]

Well, I checked the options you said to check, all was well. I disabled it and then re-enabled it, then cleared the log. I'll see what happens on the next reboot. As far as the boot logging utility, looks interesting. I will play around with it as well, but I still want to know why the "Boot Performance Monitoring" stopped in the first place. Gotta love vista.... I'll let ya know if disabling/enabling and clearing got it working again.

Note that things like kernel filter drivers and disk/chipset drivers can affect windows boot logging, as the counter interfaces used to query these do get some of the info from the drivers themselves directly. Not saying it's what happened, just saying it is possible.