Hello, I recently noticed that my PC takes a very long time to boot. It usually turned on in less than 30 seconds, but now it's closer to 2 minutes. The startup (and restart) process is pretty fast at all stages, except when it comes to the motherboard's loading screen.
So what I mean is, this is the startup process (what I see on screen):
1) Opening ASUS screen with the usual BIOS options (3s)
2) ASUS loading screen (>1min)
3) Lock screen (immediate)
The second step in the process takes forever compared to what was normal.
The motherboard has all the latest drivers and BIOS. A few months ago I disabled the Win10 fast boot option just because I wanted my PC to actually shut down when I shut it down, and the boot was still working normally afterwards.
I regularly update, but I don't have a clue what exactly could trigger this problem because I restart or shutdown my PC only about once a week on average. I noticed this problem last week (I think).
What I tried:
1) Updated GPU drivers. Nothing's changed.
2) I went to Task Manager > Startup > and I disabled some stuff with a High Startup impact. Didn't do anything.
3) I went to Event Viewer > Applications and Services Logs > Microsoft > Windows > Diagnostics-Performance > Operational
And there are a lot of Warnings with Boot Performance Monitoring (Event ID: 100) and Shutdown Performance Monitoring (Event ID: 200). Also an occasional Error with Event ID: 101.
4) I ran the Windows Performance Analyzer (I followed this tutorial).
I have no idea how to read all this but, at first glance, this long red line in the System Activity (subtitle UI Delays) seems to be the most suspicious thing. The only process there is ShellExperienceHost.exe.
For what it's worth, here's the basic hardware:
PSU: Corsair RM850
MBD: ASUS ROG Strix B350-F Gaming
CPU: AMD Ryzen 7 1700X Eight-Core Processor, 3400 Mhz
RAM: 32GB; 4x 8GB G.Skill TridentZ DDR4, 3200Mhz
GPU: Nvidia MSI GeForce GTX 1080 GAMING X 8G
SSD: Samsung 830 256GB
HDD: WD BLUE 1TB (WD10EZEX) & Samsung 1TB (HD103UJ)
Windows 10 Pro 64-bit
Any help is appreciated.
Edit 1: I should add that the problem persists in Safe mode. I'm saying this because I've seen some reports about the problem disappearing in Safe mode.
So what I mean is, this is the startup process (what I see on screen):
1) Opening ASUS screen with the usual BIOS options (3s)
2) ASUS loading screen (>1min)
3) Lock screen (immediate)
The second step in the process takes forever compared to what was normal.
The motherboard has all the latest drivers and BIOS. A few months ago I disabled the Win10 fast boot option just because I wanted my PC to actually shut down when I shut it down, and the boot was still working normally afterwards.
I regularly update, but I don't have a clue what exactly could trigger this problem because I restart or shutdown my PC only about once a week on average. I noticed this problem last week (I think).
What I tried:
1) Updated GPU drivers. Nothing's changed.
2) I went to Task Manager > Startup > and I disabled some stuff with a High Startup impact. Didn't do anything.
3) I went to Event Viewer > Applications and Services Logs > Microsoft > Windows > Diagnostics-Performance > Operational
And there are a lot of Warnings with Boot Performance Monitoring (Event ID: 100) and Shutdown Performance Monitoring (Event ID: 200). Also an occasional Error with Event ID: 101.

4) I ran the Windows Performance Analyzer (I followed this tutorial).
I have no idea how to read all this but, at first glance, this long red line in the System Activity (subtitle UI Delays) seems to be the most suspicious thing. The only process there is ShellExperienceHost.exe.

For what it's worth, here's the basic hardware:
PSU: Corsair RM850
MBD: ASUS ROG Strix B350-F Gaming
CPU: AMD Ryzen 7 1700X Eight-Core Processor, 3400 Mhz
RAM: 32GB; 4x 8GB G.Skill TridentZ DDR4, 3200Mhz
GPU: Nvidia MSI GeForce GTX 1080 GAMING X 8G
SSD: Samsung 830 256GB
HDD: WD BLUE 1TB (WD10EZEX) & Samsung 1TB (HD103UJ)
Windows 10 Pro 64-bit
Any help is appreciated.

Edit 1: I should add that the problem persists in Safe mode. I'm saying this because I've seen some reports about the problem disappearing in Safe mode.