Windows 10: Fast boot no longer working

HP notebook 250 G5

seems caused by autoupdate of the corporate antivirus (sophos endpoint) same day the issue begin

all was working fine, doing every day start->shut down->shut down the next update worked with fast boot

now i have no errors but the system is started every day with the "long" boot

looking the event viewer, i can see that when it was working fine when i choosed to shut down the system recorded event 42 (category 64) "starting activating suspension", then the day after i can see event 107 (102) "system is reactivated from suspension" and obviously type of boot 0x1 (event 27/33) (fast boot)

now it does not work: when i choose shut down i see event 109/103 "transaction of shutdown started by kernel power" and then the day after i see event 12/1 "system started at system time xxx" and type of boot 0x0 (normal boot)

note that both hybernation and suspension works if done manually

just tryed to turn on and off fast boot many times in the power menu without luck

:)

 

Windows 10 fast boot no longer working after update to Version 1511

I've run all those commands, "no damage detected" in all of them. I believe this is something up to Microsoft and not something users can fix.

 

Windows 10 fast boot no longer working after update to Version 1511

Hello Arturo,

Thank you for your response.

I appreciate your time.

If the computer still boots to the desktop without fast startup, I would suggest you to
run DISM commands from command prompt and check. Please follow these steps:

a. Press Windows + X keys and click command prompt(admin).

b. Type the following commands in command prompt one by one and press Enter after each command.

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

Windows corruption errors may prevent Windows updates and service packs from installing. For example, an update might not install if a system file is damaged. "DISM" tool may help you to fix some Windows corruption errors.

Please keep us updated.

Thank you

 

Hi ninja750

Have you contacted your Corporate Support desk.

They may have invoked some group policies along with the update or may have set Sophos to force a full shutdown. (Not sure if Sophos has that capability).

As you can directly tie the change in behaviour to the update / change in Sophos that your company enforced that is where I would start.

 

yes I have contacted both my corporate's and sophos support on their site, no solution found so far as they say it is not intenctional

i think the problem is when shutting down, when it was working the system did every time event 42/64 "activating system suspension" but now it does event 109/103 "shutdown transaction started by kernel"

 

Interesting that you would be the only person with issue. ( I think this is BS )

Through your IT group can they check if there are now any Sophos updates or hot fixes.

I would also see if Windows Fast Startup is still enabled. If so I would disable, and restart. Then go back in and enable, restart and test.

 

I am not the only one, two for sure, the others have an SSD with the function intentionally set OFF someone else is still on windows7. the trick to disable and then enable is one of the first i've tryed, and sadly the antivirus updated itself one week ago and the issue is still there

hope that next big build of windows will solve it *Sad

 

You could also try removing then recreating the hibefil.sys that is required for Fast Start-up to work. In a Command Prompt (Admin) use POWERCFG /HIBERNATE OFF followed by POWERCFG /HIBERNATE ON