New
#11
@man00
Select: Applications&Services>Microsoft>Windows>Diagnostics-Performance>ID100>Details
Long delay loading desktop
-
-
-
-
New #14
+ System
- Provider
[ Name] Microsoft-Windows-Diagnostics-Performance
[ Guid] {cfc18ec0-96b1-4eba-961b-622caee05b0a}
EventID 100
Version 2
Level 2
Task 4002
Opcode 34
Keywords 0x8000000000010000
- TimeCreated
[ SystemTime] 2024-01-16T18:26:45.8082183Z
EventRecordID 360
- Correlation
[ ActivityID] {508fba07-48a9-0002-f1c5-8f50a948da01}
- Execution
[ ProcessID] 4356
[ ThreadID] 5196
Channel Microsoft-Windows-Diagnostics-Performance/Operational
Computer DESKTOP-6QP5BHJ
- Security
[ UserID] S-1-5-19
- EventData
BootTsVersion 2
BootStartTime 2024-01-16T18:24:59.9120391Z
BootEndTime 2024-01-16T18:26:44.1367681Z
SystemBootInstance 124
UserBootInstance 123
BootTime 69337
MainPathBootTime 20737
BootKernelInitTime 57
BootDriverInitTime 339
BootDevicesInitTime 592
BootPrefetchInitTime 0
BootPrefetchBytes 0
BootAutoChkTime 0
BootSmssInitTime 6334
BootCriticalServicesInitTime 497
BootUserProfileProcessingTime 447
BootMachineProfileProcessingTime 135
BootExplorerInitTime 11369
BootNumStartupApps 0
BootPostBootTime 48600
BootIsRebootAfterInstall false
BootRootCauseStepImprovementBits 0
BootRootCauseGradualImprovementBits 0
BootRootCauseStepDegradationBits 0
BootRootCauseGradualDegradationBits 0
BootIsDegradation false
BootIsStepDegradation false
BootIsGradualDegradation false
BootImprovementDelta 0
BootDegradationDelta 0
BootIsRootCauseIdentified false
OSLoaderDuration 740
BootPNPInitStartTimeMS 57
BootPNPInitDuration 1243
OtherKernelInitDuration 122
SystemPNPInitStartTimeMS 1352
SystemPNPInitDuration 292
SessionInitStartTimeMS 1658
Session0InitDuration 5141
Session1InitDuration 86
SessionInitOtherDuration 1107
WinLogonStartTimeMS 7993
OtherLogonInitActivityDuration 791
UserLogonWaitDuration 1904
-
New #15
That is exactly that what you need to know. The numbers are [ms] milliseconds.
In America they use strange units like pounds, gallons, inches °F and so on. I don't know if they know what seconds are. Maybe a unit from sunrise to sunset devided by pi.
-
New #16
Would adding 8gb more ram help in any way right now has 8gb
-
New #17
If you're looking at event logs you need to create a custom view:
Win 10 Event Viewer Info
Also see:
Use Windows 7 Event Viewer to track down issues that cause slower boot times - TechRepublic
So you'd be looking at Boot Degradation in the Custom Views then checking Event ID's 101 through to 110
Typically you might find that security software is the culprit. Just look for the high figures in milliseconds.
-
New #18
Services and or drivers at startup could be a problem. Or explorer.exe itself. You can try these for explorer:
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Serialize]
"ProcessCPUPercentMax"=dword:0000005f ;(0x64/100) 95/0x5f
"SteadyTimeNeededInMSec"=dword:000000fa ;(0x12c/300) 0x1f4/500 0xfa/250
"ProcessWaitTimeoutInMSec"=dword:00001388 ;(0x2710/10000) 0x1388/5000 0x7530/30000 wait 30 sec before show not responding?
"StartupDelayInMSec"=dword:00000000 ;(10000)
For services:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control]
"AutoStartDelay"="180" ; 3 min start wait time for delayed services
"ServicesPipeTimeout"=dword:0000ea60 ;(30.000) 60.000 1 minute for services to complete startup
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power]
"DisableIdleStatesAtBoot"=dword:00000001
In the older XP days there was BootVis.exe to visualize boot times per item. Maybe there is modern version or method for Windows 10 somewhere?
-
Quote
Related Discussions
