System Tips

Android | Windows |

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

ON
PRT
OFF

Look Inside Data

Conditions:
Order:

Title

Windows

Bluetooth Action

bluetooth taskbar

Bluetooth Icon In The Task Notifications

Search for "bluetooth and other devices" -> open it -> Make sure Bluetooth switch is turned on -> scroll down and click "More Bluetooth settings" -> tab "option" check "Show bluetooth icon in the notification area" -> "Apply" or "OK"

Bluetooth Troubleshooting

search box type "Services" -> scroll down to "Bluetooth Support Service" -> enter -> tab "General" -> change "Startup type "Automatic" -> Apply then OK -

01/05/2026

Windows

Fix Slow Boot Up

boot slow

Slow startup is mostly fixable, but guesswork is not the right approach. Windows already logs why your PC starts up slowly. The log records how long it took and the cause of the slow boot. Once you know where to look and how to make sense of the log details, you can eliminate guesswork in fixing Windows slow start times.

Windows already records what slows your startup

The hidden diagnostics log that tracks every boot

The hidden performance report that Windows records whenever your computer starts slowly is in the Event Viewer. It's tucked within the Diagnostics-Performance log. This is a very comprehensive Windows log that you can locate by navigating to Applications and Services Logs -> Microsoft -> Windows -> Diagnostics-Performance -> Operational.

Within this log, the structured events are Windows boot events, and of these, the most consequential for slow boot times is Event ID 100. It's a summary recorded after Windows starts up, including the total startup duration. What makes it especially handy is how it separates startup into the time to reach a usable state and the time spent loading startup apps and background services. You will find most triggers for a slow-booting system in this second phase.

Event ID 100 holds a lot of actionable information. One of the most significant items is flags for specific apps or processes delaying startup. These are accurate measurements of each process’s impact (in milliseconds).
The Diagnostics-Performance log holds other events as well, and each one necessitates a different action:

The Diagnostics-Performance log holds other events as well, and each one necessitates a different action:
Event ID > > What it shows > > What you should do with it
100 > Total boot time, split into system load phase and startup app phase > > Use this to understand your overall boot duration and which phase is running long
101 > The specific app or process that delayed boot, with exact milliseconds added > > This is your primary troubleshooting entry — it names the culprit directly
102 > Confirmation that the boot was completed without failure > > Reference only — no action needed unless boot issues are intermittent

You don't need any special configuration to collect this. It's a Windows default, but just buried deep within the Event Viewer.

How to find and interpret slow boot events

The fastest way to pinpoint what's actually slowing things down

When you locate Diagnostics-Performance in the Event Viewer, click on the Filter Current Log option in the right pane, then filter with Event ID 101 to cut off the noise.

Each of the 101 events now presented includes a single delayed boot. When you click one, the first two fields to consider are File Name (exact executable responsible) and Degradation Time (the number of milliseconds it adds). With both values, you have an idea of the problem and its extent.

You can get additional context by looking at the boot duration when you pull up a 101 event for the same boot. There isn't a universal cutoff for fast or slow boots, but delays in the range of 1000 to 3000ms should raise eyebrows, and anything above 3000ms should be concerning; it's a noticeable drag on your startups.

However, you should take note of patterns more than single numbers. While a single spike may not mean much, if you notice a single app adding an extra 2000ms to startup consistently, that becomes a significant data point. So I generally look out for repeated offenders and prioritize the highest delays when I review entries.

Fixing startup delays without breaking your system

What to disable, delay, and when to leave things alone

You should be careful not to spend time on everything flagged in the log. Some are not as valuable for fixing slow boot times. I have a specific way of handling flags from the Event Viewer.

When it's a startup app, I navigate to the Startup tab of the Task Manager to find and disable the app. This way, it remains on my computer but no longer runs at startup. In the Task Manager, I can also see the impact label of the app (Low, High, or Medium). This may also give a clue as to which apps add the most time to startup.

The services flagged in the Event Viewer are often more consequential, even if less obvious. I typically locate the services in Services.msc and observe their startup type. The safest mode for non-critical services is to switch from Automatic to Automatic (Delayed start). This way, they only start when the desktop is ready and reduce startup drag.

Then, when Event Viewer flags hardware-related software, like my printer utilities or RGB lighting controllers, I update them, or if I no longer use the device, I uninstall the software. However, if any of these belong to Windows or a core service, I avoid tampering with them unless I'm certain it's a safe process.

You don't have to solve all delays because some of them, like antivirus tools or cloud sync, may be doing really important work during startup.
Mapping your entire boot timeline with advanced tools

In my experience of using the Event Viewer, there are certain occasions when the culprit isn't clear. This could be because the boot times vary too much, or there are multiple processes involved. In such cases, I default to more advanced Microsoft tools.

With Windows Performance Recorder, I can capture a detailed boot process trace, while the Windows Performance Analyzer allows me to visualize the trace in real time. I can observe when processes ran, their duration, and where there were overlaps with different activities.

Of course, there are several ways to cut boot time, but a thorough analysis before taking any action is very effective.

04/16/2026