Having issues with start up on my rig.

Hey you pro's,

So about 2 months ago I did a fresh install of windows 11 pro on my rig. I am on 25H2 OS build 26200.7840 and Kb5077181.

Specs: 14900k
Strix Z790 wifi 2
32 gigs of ram
asus tuff 5090
Bios 2107


With that being said, my rig takes a bit of time to start up, it will go to the lock screen but it takes a good minute for the log in tab to come up. Sometimes the log in tap will come up fast, lets me log in but cannot do anything for a good minute? I never had issues like this before, this all started up with the new updates that MS have released.

I have tried rolling back the bios, same issues, I have enabled and disabled fast start up in windows and bios settings, same issues.

All my settings that I use are the same in my bios and windows, I am not using any save files for my settings, always just start out new, takes time but I do it anyway.

Start up apps are minmal, 2 are enabled, before I did the fresh install it took abot 10 to 12 seconds for my rig to start up.

So wondering if this could be a MS update that messed things up or maybe a setting in bios I am missing??

Any advice on this matter would be apprecatied.

Thanks in advace guy's.

Hello pinkfloyd1173, assuming you have already run the necessary tests and troubleshooting like DISM and or SFC this is what I would do:
1-Set your BIOS to the optimized default in the Exit menu.
2- Disconnect any external USB device
3- Configure " powercfg /hibernate on "

In this video, we delve into the common issue of slow boot times in Windows and how to effectively troubleshoot it using Process Monitor.

Gas said:

Hello pinkfloyd1173, assuming you have already run the necessary tests and troubleshooting like DISM and or SFC this is what I would do:
1-Set your BIOS to the optimized default in the Exit menu.
2- Disconnect any external USB device
3- Configure " powercfg /hibernate on "

Click to expand...

Hey Gas,
I tried that all ready. I still have not tried the video that FreeBooter replied, will try that when I get home.

I think I figured it out, it is my anti-virus, bitdefender. It's a known issue and they are coming out with a update to fix it, next week.