Delayed reaction from Windows when no unusual activity is detected
Delayed reaction from Windows when no unusual activity is detected
When I power on my computer, Windows appears very slow. The task manager opens only after about a minute, and shutting down or restarting takes nearly as long. All applications launch slowly. I've looked into CPU, RAM, and storage usage—everything looks normal. No unusual spikes. Could be something else causing the delay? It works fine with a restart, but needing to restart each time isn't ideal.
I initially imagined a thirsty startup app, but I expected consistent performance with clear resource consumption data—like full CPU usage. It might help to inspect what Windows is attempting to launch via Start -> Startup Apps. While that could be part of the issue, it’s unlikely the whole story. You could also check Event Viewer for any spammy warnings or errors, navigating to: Start -> Event Viewer -> Windows Logs -> System (Application or Security). Use 'Filter Current Log' to focus on Warnings & Errors, which often provide more actionable insights. The info logs tend to be overwhelming and difficult to parse.
I didn't think about it at first. After reviewing now, nothing seems connected to what you mentioned. The only issue I noticed was: "The server {****} failed to register with DCOM within the expected time limit." The rest doesn't align with the boot process.
I thought the same thing. I turned it off now, in hope it resolves the issue.
Use windows resource monitor instead of task manager on the disk section to clarify slow performance. Clicking the read (kbytes/s) tab helps sort active disk reads and reveals what windows are doing. It would be great if Linux offered a similar, user-friendly way to view this data.
Update coming, looks like the problem persists. Needs to restart the PC to resolve it. Unclear if anything seems out of place—just notice CompatTelRunner loads most smoothly, which isn’t unusual. All other components appear normal. R5 5600x with 3060 Ti, 16GB RAM, 3200MHz dual channel (probably a hyperX model, memory unclear). Windows runs on a Kingston NVMe drive.
Have you attempted turning off Wi-Fi or other network links to halt telemetry transmission entirely, then allowed the device to sit idle for some time?