Is Windows 10 faking boot degradation times?

6

6pack

Level L
See these examples:
1:
Windows Explorer seems to have took longer to start up
Code: 
This application took longer than usual to start up, resulting in a performance degradation in the system startup process:
  File Name     :   explorer.exe
  Friendly Name     :   Windows Explorer
  Version     :   10.0.10586.0 (th2_release.151029-1700)
  Total Time     :   3446ms
  Degradation Time   :   2012ms
  Incident Time (UTC)   :   ‎2016‎-‎09‎-‎02T05:29:19.794543500Z
See boot time for this date:
Code: 
Windows has started up:
  Boot Duration     :   33043ms
  IsDegradation     :  false
  Incident Time (UTC)   :  2016‎-‎09‎-‎02T05:29:19.794543500Z

It says degradation is false but still gives error in Event Viewer!

See this second example of boot time of today. No application degraded the boot time today yet it took more than a minute to start up.
Code: 
Windows has started up:
  Boot Duration     :   65035ms
  IsDegradation     :   false
  Incident Time (UTC)   :   ‎2016‎-‎09‎-‎04T05:35:26.951437700Z

Seems like major degradation of boot times to me from 33 seconds to double of that. Yet it says no boot degradation. Wtf is this event viewer doing? Seems we can't trust even event viewer now.
 
What about the "Last BIOS Time" shown in Task Manager's STARTUP tab? Does that vary a lot and contribute to the boot time maybe? (And Win10 is counting it but doesn't consider BIOS POST/boot time into it's "degradation" flag?)[DOUBLEPOST=1472971476][/DOUBLEPOST]Also, are you looking at boot times with "warm" (re)boot versus "cold" boot (full shutdown then startup)?
 
All of these are cold boot times. Last boot time was around 34 seconds. I don't know how windows 10 counts boot times. It probably starts from when its boot loader starts.
Today it (Windows) was stuck at the loading screen for long time so i looked at event viewer and saw this ridiculous boot time.
 
Back
Top