Windows 10 (2004) Unresponsive After Waking


  1. Posts : 103
    Windows 10
       #1

    Windows 10 (2004) Unresponsive After Waking


    I am running Windows 10 (2004) on a custom built machine, mobo ASRock Z370 Pro4 with the latest BIOS. I've never had problems updating Windows 10 to the latest until the May 2020 update. Now whenever I wake the system from sleep or, it seems, I switch between users, the system becomes very sluggish to borderline unresponsive. The only thing I can do to fix the problem is to reboot the system.

    I've checked to make sure I have the latest drivers installed and I've tried running the troubleshooter but nothing comes up as being broke. I can't rollback to the previous version because I stupidly cleaned up the old version thinking everything was working fine.

    Does anyone have any suggestions on how to possibly resolve the problem?
      My Computer


  2. Posts : 43,003
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    What does your task manager show when the system is sluggish?
    - screenshot Windows 10 (2004) Unresponsive After Waking-untitled.png

    Look for excessive resource usage


    How much free space do you have on C: ?

    Hopefully you've followed the forum's oh so frequent advice to use disk imaging routinely e.g. Macrium reflect - free/paid
    If so, all you have to do to restore your previous build is to restore a previously created disk image.
      My Computers


  3. Posts : 2,554
    Windows 10 Pro 64bit
       #3

    Do you have Malwarebytes installed?
    It seems the current version isn’t exactly compatible with 2004 & is causing slowdowns.
    https://forums.malwarebytes.com/topi...ndows-10-2004/
    https://forums.malwarebytes.com/topi...ndows-10-2004/
    https://forums.malwarebytes.com/topi...ot-responding/

    Upgrading to the beta version seems to be the only solution currently.
      My Computer


  4. Posts : 103
    Windows 10
    Thread Starter
       #4

    Thank you to @dalchina and @bastet for your comments but I ultimately re-installed Win10 last night after I realized my D: drive wasn't been seeing any more. I do have Malwarebytes installed on all my systems but the other systems didn't experience the same issue. I think the update was just borked because when I tried to run a CHKDSK it hung up at 100%, and when I ran DISM it "completed" at 84.9%. It seemed something else was wrong. Considering I haven't done a clean install since Win 10 came out I just decided a fresh install was best. So far no problems.
      My Computer


  5. Posts : 43,003
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #5

    Thanks for letting us know. Now, since some corruption was present on your disk, it would be wise to check the disk itself.

    Try HD Tune v2.55 (free) Health and Error scan tabs.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:41.
Find Us




Windows 10 Forums