Solved Fast Start up depression

Hi, for my entire Wondows 10 life I had either: 1) a red X windows was not shut down properly in logs. or 2) turn off fastboot and feel like I was missing out.

That was my last PC which was a i7 4790k, turns out the problem was a Haswell refresh on my particular Asus board.

Then Windows 11 came along and I've had Fast start up enabled and no longer feel like a lepar.

But

A week or so ago I turned on PC which took a while, then got an error message from Nvidia asking me to send a crash report. booted safe mode, ran DDU, reinstalled latest driver, ran DISM, all seemd fine, except when I turned off PC the screen turned off but the tower didn't

For a week I've been trouble shooting and I thought I'd found it, but after working great for four days, it won't turn off again, just error 41, it's not actually logging a problem because it doesn't know there is one, except me pressing the restart, I left it for hours.

So I guess I need to disable Fast start up once again. I, even tried a OS re-install, that's what fixed it for four days. I just feel defeated as it's worked great for 5 years and there's not been a driver updated that I havn't tried rolling back, re-installed Windows, installed drivers, fine for four days, then breaks, only updates in the last 3 days Defender definations.

Is there something I havn't tried? I even refreshed my Bios as there was an update.

There are no issues when running or starting, it just wont turn off with FS enabled?

Thanks

Hi. It appears you have a vVME disk - a SSD.

Fast Startup is intended for hard drives, so is redundant. You should not see any noticeable startup benefit with it enabled.

Cross-check- how long does it take for a cold boot to reach the lock screen?

2) turn off fastboot

Click to expand...

- I'm guessing you meant fast startup.

hi, yeah I did, it's fast enough. just seems a little more fully loaded with it enabled, just seconds, and the shutdown was nearly instant. I'll get used to it again, as I said, I just feel beaten! Hate not being able to find the culprit. thanks again.

It's a different issue I guess, with 4790 it shut down but logged a red X every other boot, this one wont turn off at all, and the PC doesn't seem to realise

It's quite well recognised that in some cases Fast Startup can cause problems. As you don't need it.. it's one problem you can simply set aside.
And if you don't use hibernation - you could disable that and save some disk space as both use hiberfil.sys. But then, you have a large disk...

yeah, guess I'll accept it, after a decade of issues, you'd think I learn my lesson, got a slight feeling HP updated my network printer driver and app via Store around the time this started, I was looking at device manager but didn't see it as printer was off, I removed it as there was loads of junk HP helper and sdk were 2 new additions, I may renable hibernate to check when I'm bored. It does seem fragile though so maybe I wont. I'll just pretend I fixed it, but want it off.
thanks guys

wrogg said:

I just feel beaten! Hate not being able to find the culprit.

Click to expand...

Don't feel beaten as you are not alone. Fast startup (and sleep and other power-related issues) issues have caused problems for many users for years. When it works, it works well, but with so many hardware configurations in the wild, getting to the root of problems in individual devices is difficult and sometimes downright impossible. Windows Fast Startup is widely known to conflict with various hardware drivers, external devices, and deep-learning software running locally on a Windows machine.

For example, in your case it could be your Nvidia which introduced NVIDIA Dynamo Snapshot. While Nvidia Dynamo and Windows fast startup operate in completely different environments , there is no direct link between the two technologies, and nothing has thus far been documented, disabling fast startup might be one's only option if he has sleep issues, crashes, and other power related issues.

Another user may not have Nvidia but experience the same problem. In his case it is usually some conflict between hardware he does have (or the drivers or firmware for that hardware) and windows.

As users, once we have exhausted efforts to trouble shoot the issues we encounter, we do what we gotta do. Disabling fast startup is one of the first steps.
interesting reading - Windows Fast Start-up is still causing problems in 2026, and everyone should disable it

Thanks for that! I know, Windows does amaze me really running so well on so many different systems. Mad me feel better! cheers.

for anyone Googling a solution, I literally tried everything on this including re-flashing BIOSs, reinstalling. PC would not shut down to sleep or hibernate.

Fix was unticking network adaptor, properties, power management , allow device to wake PC.

No idea at all, pretty sure this was always on, driver hasn't been updated for ages, connected by RJ45 no idea, computers are weird.

there were no entires in powercfg, requests either?

I finally resolved my issues with S3 sleep and other random issues by replacing...... my mouse. Somehow or another the mouse was corrupting the USB driver and causing issues from resuming from sleep to the mouse cursor disappearing randomly on screen to odd WHEA errors with spontaneous reboots for nearly a month. Since replacing the mouse, a Corsair M65 Ultra two weeks ago, I've not had a single error. So yeah, computers can be weird.

glasskuter said:

As users, once we have exhausted efforts to trouble shoot the issues we encounter, we do what we gotta do. Disabling fast startup is one of the first steps.
interesting reading - Windows Fast Start-up is still causing problems in 2026, and everyone should disable it

Click to expand...

For people that boot from fast storage like NVMe or SATA SSD drives, fast startup provides minimal benefits, but a ton of potential issues. I had it enabled when I first did this build, and it saved me about two seconds over a 20 second cold boot time. By the time you scratch your ear, that time difference has disappeared! If you have a bog slow machine and/or drive, you might save a few more seconds, but so what? How many people really reboot often enough for this to be a factor? Most of my reboots are when a new Windows update comes along.