

It should be noted that if you have a Windows 7 or 8 Home license, you can only update to Windows 10 Home, while Windows 7 or 8 Pro can only be updated to Windows 10 Pro. Microsoft is encouraging Windows 7 users to upgrade to Windows 10 now support for the former has ended. When the upgrade is complete, go to Settings Update & Security > Activation, and you should see a digital license for Windows 10. (If you're upgrading a different machine, choose Create installation media for another PC, and save the installation files.)ĥ. Choose Upgrade this PC now, assuming this is the only PC you're upgrading. Under Create Windows 10 installation media, click Download tool now and Run.ģ.

Once done, MoUsoCoreWorker.exe should no longer prevent the sleep mode on your laptop or 2-in-1.Here's how to get Windows 10 for free, if you're currently running a licensed and activated copy of Windows 7, Windows 8 or Windows 8.1 Home or Pro:ġ. It’s worth noting that this is a temporary solution and a proper workaround is not yet available. Install the pending updates and reboot your device. Go to Windows Update and click on Check for updates.Click on the same entry again and select ‘Start’ and then select ‘Restart’.Click on Windows Update and select ‘Stop’.In the Services window, look for ‘Windows Update’ service.If you’re unable to fix the sleep mode issues by tweaking your update schedule, you can also try these advance steps:

Once done, you would need to reboot your computer and try the sleep mode again. One way to fix the problem is by using Windows Update’s Settings to schedule those updates and reboots and prevent the update service from running at odd hours. How to fix sleep mode issues on Windows 10 after version 2004 Now, less than a month later, the same problem with Windows 10 has reappeared, though it may not be affecting everyone.Īs we mentioned at the outset, it appears that Windows Update is a fickle beast here and you may be able to solve this problem easily by diagnosing Windows Update. The problem with sleep mode was first reported after the release of Windows 10’s May 2020 Update and it was fixed with Windows 10 KB4568831.
