Critical update fail 8/19/12
This event indicates the fact that the Windows boot time took an unusual long time. The time is recorded in milliseconds. For example, a 130912 ms boot time, means approx. 130 seconds, or 2 minutes and 10 seconds. This is quite a long time to boot and it may be an indication of a problem. This event in itself does not record the reason why the boot took that long, just that it happened. Other events in the logs may point to the cause of the problem. In many cases, the culprit is the hard disk. A Chkdsk should be run against all the drives in order to detect and fix corrupted files (it may not fix that particular problem but it doesn't hurt, either) This event report seems irrelevant to your update. Can you post WindowsUpdate.log or more details about error information?Your Name TechNet Community Support
August 21st, 2012 5:54am

my father installed sevral critical updates on 8/19/12 about 9:30am pacific time when the whole system needed to be restored. i was not present until the last few min so i dont know exactly what happened but i got a report from the event viewer, need help making heads or tails of the report, help please? Log Name: Microsoft-Windows-Diagnostics-Performance/Operational Source: Microsoft-Windows-Diagnostics-Performance Date: 8/19/2012 9:38:05 AM Event ID: 100 Task Category: Boot Performance Monitoring Level: Critical Keywords: Event Log User: LOCAL SERVICE Computer: EDNA-PC Description: Windows has started up: Boot Duration : 168577ms IsDegradation : false Incident Time (UTC) : 2012-08-19T16:34:58.640400200Z Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}" /> <EventID>100</EventID> <Version>2</Version> <Level>1</Level> <Task>4002</Task> <Opcode>34</Opcode> <Keywords>0x8000000000010000</Keywords> <TimeCreated SystemTime="2012-08-19T16:38:05.870949700Z" /> <EventRecordID>530</EventRecordID> <Correlation ActivityID="{00000000-C8C4-0000-AA5C-9192287ECD01}" /> <Execution ProcessID="1484" ThreadID="1496" /> <Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel> <Computer>EDNA-PC</Computer> <Security UserID="S-1-5-19" /> </System> <EventData> <Data Name="BootTsVersion">2</Data> <Data Name="BootStartTime">2012-08-19T16:34:58.640400200Z</Data> <Data Name="BootEndTime">2012-08-19T16:38:02.314143400Z</Data> <Data Name="SystemBootInstance">30</Data> <Data Name="UserBootInstance">25</Data> <Data Name="BootTime">168577</Data> <Data Name="MainPathBootTime">98477</Data> <Data Name="BootKernelInitTime">29</Data> <Data Name="BootDriverInitTime">11276</Data> <Data Name="BootDevicesInitTime">5395</Data> <Data Name="BootPrefetchInitTime">44584</Data> <Data Name="BootPrefetchBytes">258879488</Data> <Data Name="BootAutoChkTime">0</Data> <Data Name="BootSmssInitTime">40424</Data> <Data Name="BootCriticalServicesInitTime">896</Data> <Data Name="BootUserProfileProcessingTime">874</Data> <Data Name="BootMachineProfileProcessingTime">0</Data> <Data Name="BootExplorerInitTime">13741</Data> <Data Name="BootNumStartupApps">6</Data> <Data Name="BootPostBootTime">70100</Data> <Data Name="BootIsRebootAfterInstall">false</Data> <Data Name="BootRootCauseStepImprovementBits">0</Data> <Data Name="BootRootCauseGradualImprovementBits">0</Data> <Data Name="BootRootCauseStepDegradationBits">0</Data> <Data Name="BootRootCauseGradualDegradationBits">0</Data> <Data Name="BootIsDegradation">false</Data> <Data Name="BootIsStepDegradation">false</Data> <Data Name="BootIsGradualDegradation">false</Data> <Data Name="BootImprovementDelta">0</Data> <Data Name="BootDegradationDelta">0</Data> <Data Name="BootIsRootCauseIdentified">false</Data> <Data Name="OSLoaderDuration">3608</Data> <Data Name="BootPNPInitStartTimeMS">29</Data> <Data Name="BootPNPInitDuration">5443</Data> <Data Name="OtherKernelInitDuration">4673</Data> <Data Name="SystemPNPInitStartTimeMS">8431</Data> <Data Name="SystemPNPInitDuration">11228</Data> <Data Name="SessionInitStartTimeMS">21345</Data> <Data Name="Session0InitDuration">30966</Data> <Data Name="Session1InitDuration">2394</Data> <Data Name="SessionInitOtherDuration">7062</Data> <Data Name="WinLogonStartTimeMS">61769</Data> <Data Name="OtherLogonInitActivityDuration">22090</Data> <Data Name="UserLogonWaitDuration">7025</Data> </EventData> </Event>
Free Windows Admin Tool Kit Click here and download it now
August 21st, 2012 1:28pm

What does WindowsUpdate.log file says? Any trace in Event log(s)? If nothing has bee found in WindowsUpdate.log, you can boot into Safe Mode and return to previous restore point. Rgds Milos
August 21st, 2012 3:52pm

This event indicates the fact that the Windows boot time took an unusual long time. The time is recorded in milliseconds. For example, a 130912 ms boot time, means approx. 130 seconds, or 2 minutes and 10 seconds. This is quite a long time to boot and it may be an indication of a problem. This event in itself does not record the reason why the boot took that long, just that it happened. Other events in the logs may point to the cause of the problem. In many cases, the culprit is the hard disk. A Chkdsk should be run against all the drives in order to detect and fix corrupted files (it may not fix that particular problem but it doesn't hurt, either) This event report seems irrelevant to your update. Can you post WindowsUpdate.log or more details about error information?Your Name TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
August 22nd, 2012 3:58am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics