ANAVEM
Languagefr
Windows Event Viewer displaying boot performance monitoring data and system metrics on administrator workstation
Event ID 900InformationKernel-GeneralWindows

Windows Event ID 900 – Kernel-General: System Boot Performance Monitoring

Event ID 900 tracks Windows boot performance metrics, recording system startup times and boot phases. Generated by Kernel-General during system initialization to monitor boot duration and identify performance bottlenecks.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
18 March 20269 min read 0
Event ID 900Kernel-General 5 methods 9 min
Event Reference

What This Event Means

Event ID 900 is generated by the Windows Kernel-General component as part of the built-in boot performance monitoring system. This event serves as a comprehensive record of system startup metrics, capturing timing data for various boot phases including pre-boot, kernel initialization, service startup, and user session creation.

The event data typically includes total boot time measured from power-on to desktop ready state, along with breakdowns of individual boot phases. Modern Windows versions use this data for internal performance optimization and to populate boot performance reports accessible through Performance Monitor and Windows Performance Toolkit.

In enterprise environments, Event ID 900 becomes particularly valuable for baseline establishment and performance trending. System administrators can collect this data across multiple machines to identify outliers, track performance degradation after updates, and validate the effectiveness of boot optimization efforts. The event also integrates with Windows Analytics and Microsoft Endpoint Manager for centralized boot performance monitoring.

Windows 11 22H2 and later versions include enhanced boot performance tracking that provides more detailed phase timing and can identify specific drivers or services contributing to boot delays. This makes Event ID 900 an essential tool for maintaining optimal system performance in modern Windows deployments.

Applies to

Windows 10Windows 11Windows Server 2019/2022/2025
Analysis

Possible Causes

  • Normal system boot completion triggering performance measurement recording
  • Windows Performance Monitoring service collecting boot timing data
  • System startup reaching desktop-ready state after successful initialization
  • Boot performance baseline establishment during initial system setup
  • Scheduled boot performance measurement cycles in enterprise environments
  • Fast startup or hybrid boot completion generating performance metrics
  • System recovery from sleep or hibernation states with boot-like initialization
Resolution Methods

Troubleshooting Steps

01

View Boot Performance Data in Event Viewer

Access the boot performance information directly through Event Viewer to understand your system's startup metrics.

  1. Open Event Viewer by pressing Win + R, typing eventvwr.msc, and pressing Enter
  2. Navigate to Windows LogsSystem
  3. In the Actions pane, click Filter Current Log
  4. Enter 900 in the Event IDs field and click OK
  5. Double-click any Event ID 900 entry to view detailed boot performance data
  6. Review the General tab for boot time summary and Details tab for raw performance metrics
  7. Note the boot duration values and compare against your baseline performance expectations
Pro tip: Create a custom view for Event ID 900 to easily track boot performance trends over time without manual filtering.
02

Extract Boot Performance Data with PowerShell

Use PowerShell to programmatically collect and analyze boot performance metrics from Event ID 900.

  1. Open PowerShell as Administrator
  2. Run the following command to retrieve recent boot performance events:
Get-WinEvent -FilterHashtable @{LogName='System'; Id=900} -MaxEvents 10 | Select-Object TimeCreated, Id, LevelDisplayName, Message
  1. For detailed boot timing analysis, extract specific performance data:
$bootEvents = Get-WinEvent -FilterHashtable @{LogName='System'; Id=900} -MaxEvents 30
$bootEvents | ForEach-Object {
    [PSCustomObject]@{
        Date = $_.TimeCreated
        BootTime = ($_.Message -split '\n' | Where-Object {$_ -match 'boot time'})
        EventData = $_.Properties
    }
} | Format-Table -AutoSize
  1. Export boot performance data to CSV for trend analysis:
Get-WinEvent -FilterHashtable @{LogName='System'; Id=900} -MaxEvents 100 | 
Select-Object TimeCreated, Message | 
Export-Csv -Path "C:\temp\boot_performance.csv" -NoTypeInformation
Pro tip: Schedule this PowerShell script to run weekly and automatically track boot performance trends across your environment.
03

Analyze Boot Performance with Performance Monitor

Leverage Windows Performance Monitor to create comprehensive boot performance reports and establish performance baselines.

  1. Open Performance Monitor by typing perfmon in the Start menu
  2. Navigate to ReportsSystemSystem Performance
  3. Right-click System Performance and select NewData Collector Set
  4. Name it "Boot Performance Monitoring" and select Create manually
  5. Add the following performance counters:
    • System\System Up Time
    • Process(*)\Elapsed Time
    • LogicalDisk(*)\% Idle Time
  6. Configure the data collector to start automatically at system startup
  7. Correlate Performance Monitor data with Event ID 900 timestamps for comprehensive analysis
  8. Create custom reports combining boot event data with system performance metrics
Warning: Continuous performance monitoring can impact system performance. Configure appropriate sampling intervals for production systems.
04

Configure Advanced Boot Performance Tracking

Enable enhanced boot performance monitoring through registry configuration and Windows Performance Toolkit integration.

  1. Open Registry Editor as Administrator
  2. Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager
  3. Create or modify the DWORD value EnableBootPerfTracing and set it to 1
  4. Navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Diagnostics\DiagTrack
  5. Verify that TelemetryEnabled is set to 1 for boot performance data collection
  6. Install Windows Performance Toolkit (WPT) from Windows SDK
  7. Use Windows Performance Recorder (WPR) to capture detailed boot traces:
wpr -start GeneralProfile -start CPU -start DiskIO
  1. After system restart, stop the trace and analyze with Windows Performance Analyzer:
wpr -stop C:\temp\boot_trace.etl
  1. Correlate WPA trace data with Event ID 900 timestamps for comprehensive boot analysis
Pro tip: Use WPA's boot analysis templates to automatically identify boot performance bottlenecks and correlate them with Event ID 900 data.
05

Enterprise Boot Performance Monitoring and Alerting

Implement enterprise-scale boot performance monitoring using Event ID 900 data collection and automated alerting systems.

  1. Configure Windows Event Forwarding (WEF) to centralize Event ID 900 collection:
winrm quickconfig
wecutil cs subscription.xml
  1. Create a subscription XML file for Event ID 900 forwarding:
<Subscription xmlns="http://schemas.microsoft.com/2006/03/windows/events/subscription">
    <SubscriptionId>BootPerformanceMonitoring</SubscriptionId>
    <Query>
        <Select Path="System">*[System[EventID=900]]</Select>
    </Query>
</Subscription>
  1. Set up PowerShell-based alerting for boot performance degradation:
$threshold = 120 # seconds
$recentBoots = Get-WinEvent -FilterHashtable @{LogName='ForwardedEvents'; Id=900} -MaxEvents 5
$slowBoots = $recentBoots | Where-Object {$_.Message -match 'boot time: ([0-9]+)' -and [int]$Matches[1] -gt $threshold}
if ($slowBoots) {
    Send-MailMessage -To "admin@company.com" -Subject "Slow Boot Alert" -Body "Boot performance threshold exceeded"
}
  1. Integrate with System Center Operations Manager (SCOM) or Microsoft Sentinel for advanced monitoring
  2. Create automated remediation workflows triggered by boot performance anomalies
  3. Establish performance baselines and trend analysis dashboards using collected Event ID 900 data
Warning: Ensure proper security configuration for event forwarding in domain environments to prevent unauthorized access to boot performance data.

Overview

Event ID 900 from the Kernel-General source is a boot performance monitoring event that Windows generates during system startup. This event fires as part of the Windows Performance Monitoring infrastructure, specifically tracking boot duration and system initialization phases. The event appears in the System log and provides valuable telemetry about how long your system takes to complete various boot stages.

This event is particularly useful for system administrators monitoring boot performance across enterprise environments or troubleshooting slow startup issues. Windows 11 and Server 2025 have enhanced this event with additional performance counters and more granular timing data. The event typically contains boot phase durations, total boot time, and sometimes identifies components that contributed to boot delays.

Unlike error events, Event ID 900 represents normal system behavior and indicates that Windows successfully completed its boot performance measurement cycle. However, analyzing trends in the data this event provides can reveal performance degradation over time or help identify systems that need optimization.

Frequently Asked Questions

What does Event ID 900 mean and why does it appear in my System log?+
Event ID 900 is a boot performance monitoring event generated by the Windows Kernel-General component. It appears in your System log every time Windows completes its startup process and records timing metrics for various boot phases. This is normal system behavior and indicates that Windows successfully measured and logged boot performance data. The event helps administrators track system startup times, identify performance trends, and troubleshoot slow boot issues. Modern Windows versions use this data for internal optimization and performance reporting.
How can I use Event ID 900 to troubleshoot slow boot times?+
Event ID 900 provides valuable boot timing data that helps identify performance bottlenecks. Examine the event details to see total boot time and phase-specific durations. Compare recent boot times against historical baselines to identify performance degradation. Look for patterns in the timing data that correlate with recent system changes, driver updates, or software installations. Use PowerShell to extract and analyze multiple Event ID 900 entries to establish trends. Combine this data with Windows Performance Toolkit traces for detailed analysis of specific boot phases and components causing delays.
Is Event ID 900 related to any security concerns or system errors?+
No, Event ID 900 is not a security concern or system error. It's an informational event that represents normal Windows boot performance monitoring functionality. The event indicates successful completion of the boot process with performance measurement. However, the timing data it contains can be useful for security monitoring in enterprise environments, as unusual boot patterns might indicate unauthorized system modifications or malware activity. Administrators should focus on the performance trends rather than treating individual Event ID 900 entries as problems requiring immediate attention.
Can I disable Event ID 900 if I don't need boot performance monitoring?+
While Event ID 900 can be suppressed through registry modifications or event log filtering, it's generally not recommended to disable it completely. The event provides minimal system overhead and offers valuable diagnostic information. If you need to reduce event log volume, consider configuring log retention policies instead of disabling the event entirely. In enterprise environments, this data is often valuable for performance baselines and capacity planning. If you must disable it, modify the registry key HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\EnableBootPerfTracing to 0, but be aware this may impact other boot performance tools and diagnostics.
How does Event ID 900 differ between Windows 10, Windows 11, and Windows Server versions?+
Event ID 900 has evolved across Windows versions with enhanced performance tracking capabilities. Windows 10 provides basic boot timing information, while Windows 11 22H2 and later include more detailed phase breakdowns and driver-specific timing data. Windows Server 2022 and 2025 versions include additional enterprise-focused metrics and better integration with management tools like System Center and Microsoft Endpoint Manager. Server versions also provide more granular service startup timing and role-specific boot performance data. The core event structure remains consistent, but newer versions offer richer diagnostic information and better correlation with other system performance events.
Documentation

References (2)

Emanuel DE ALMEIDA
Written by

Emanuel DE ALMEIDA

Senior IT Journalist & Cloud Architect

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...