This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Since I installed Windows 10 2004 Update, Windows doesn’t wake up from sleep mode correctly.
I can login as expected, display and cursor are reactive until I try to open the first program/app the blue circle/wait animation lights up shortly but nothing happens. When I try to open a second program or the same program again, the computer freezes completely. Only a hard shutdown pressing the power button for several seconds will help. When I’m able to press restart, restart will eventually execute but takes awfully long (10 minutes).
For now, I found the following workaround: Set sleep to ‘Never’ and set what closing the lid/power button does to ‘Hibernate’.
It’s not optimal but for now I’ll wait what future Windows patches and driver update bring. I am not planning on reinstalling Windows or creating a new user account.
Is there anything else I could try?
UPDATES:
A short static of incidents, two weeks into this thread:
I usually put my computer into sleep around 4-5 times per day. After two weeks of changing from sleep mode to hibernation, I only had the same issue once, and not as severe (after 5-6 hours of hibernation). Programs wouldn’t run, but I was still able to restart my machine normally in that case. Hence, hibernation is a viable workaround.
User Rednax35 identified Malwarebytes as the culprit. After trying it for 24 hours, this solution worked for me, too. That’s why accepted it as valid solution being aware that****it couldn’t fix the problem for all users! I should have checked for antivirus-related causes right away, as they are frequent candidates when things come to an unexpected halt. It would be interesting to hear, if other users had different third-party antivirus programs installed. Some privileges could have been revoked from the OS side with the feature update. I also noted some hiccups with the fingerprint reader which wasn’t always ready when resuming after sleep, which could be worth investigating.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Alright so it's a few days later, and I don't know if this will apply to any of you guys, but apparently what was causing the sleep issues for me was Malwarebytes. I reinstalled Windows and the issues were gone, but as soon as I installed Malwarebytes they came back. Once I uninstalled it, they were gone.
I don't know if this will apply to you guys, but if you do have Malwarebytes I'd say temporarily uninstall it and see if that fixes the issue, since that's what fixed it for me.
For those running Malwarebytes the company has just released a fix.
Updated to Version 4.1.2 and now have no issues.
Same symptoms on desktop platform ASUS PRIME Z370-A, BSOD starts after installation of latest
Microsoft Windows 10 Pro Insider Preview Build 20221
BSOD with error "Unexpected_Kernel_Mode_Trap" appears during boot time, directly after login procedure.
As well BSOD appears after long sleep mode period (more than 10-15 minutes) of the monitor.
ASPM in BIOS, system sleep mode, hibernation, fast boot mode was disabled in OS initially.
Additionally, my system use CG - Credential Guard and HVCI - Hypervisor-protected code integrity.
AV software - ESET Internet Security and Malwarebytes for Windows 4.2.1 with Premium subscription.
Copy of the bugcheck messages from Event Viewer:
0x1000007f (0x0000000000000008, 0xfffff8003e53fe50, 0xfffff406d2538fe0, 0xfffff8003f6aa55b)
0x0000007f (0x0000000000000008, 0xffff828148325e50, 0xffffc984b46befe0, 0xfffff807510bf55b)
Dump file analysis in WinDbg application introduce crash in services.exe process as primary reason of BSOD:
BUGCHECK_CODE: 7f
BUGCHECK_P1: 8
BUGCHECK_P2: fffff8003e53fe50
BUGCHECK_P3: fffff406d2538fe0
BUGCHECK_P4: fffff8003f6aa55b
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: services.exe
However, nothing help to prevent BSOD, PC was restart in "Clean Boot" mode - only Microsoft services allowed,
Malwarebytes protection module was disabled from automatic start.
Until Malwarebytes software component was completely uninstalled, BSOD still appears.
Copy of my feedback in Feedback Hub:
Analysis of the dump file after BSOD was sent to Microsoft via this feedback,
support case request to Malwarebytes company as well.
I have just added an update in response to @Sim_001's reply, but I meant to say that even though those tips didn't work for me, thank you anyway for taking the time to post them.
And I spent something like a couple of hours (or at least it felt that long) earlier today with a MS support technician trying to solve the problem - checked drivers, changed settings, reset power plan, disabled fast start and hibernate, ran some reports, seemingly everything in the textbook but you guessed it... I'm no further forward. And in fact, as I had half suspected, I just ended up having lost my settings with nothing to show for it. No matter what we tried, when we instigated sleep mode, the PC would shut off for perhaps a second and then spontaneously start right back up again.
I tried to explain to the technician that this seems to be a problem brought about by Feature Update 2004 and even cited this forum thread, but it seems it hasn't hit the 'known update issue' radar as he was just trying the standard troubleshooting steps; I suppose if he hasn't been briefed on the problem and a potential fix then there's nothing else he could do.
So - goodness knows what it is that happened with that update, but the timing certainly seems to tie in for me and for lots of other people by the looks of it. I would rather not have to try and roll back (I have no suitable system restore point for one thing) as I know that is not without risk and potential disruption - it would be nice if MS could figure it out and issue a fix ASAP!
