woensdag 2 januari 2019
Windows 10 freezes after a few minutes of being idle (and can only be rebooted the hard way)
At the moment I am having an issue with Windows 10 that is being mentioned these days (and before) all over the internet.
Since a week or so, Windows 10 freezes the mouse, the keyboard and the screen after being left idle for some minutes. The only action that can be taken is: give the computer a hard reboot with the power button. Sometimes this is not needed: Windows 10 then reboots on its own.
A zillion ‘solutions’ can be found on the internet, but I still haven’t found one that works for me.
Of course there are the hardware guys who suggests it may have something to do with the cooling, the power supply, with the motherboard or some faulty USB socket. No, it has nothing to do with that. My Acer desktop PC is a month old and works perfectly fine. I can work on it for hours without any problems. I just should not leave the PC alone for some minutes, because then it crashes, and all my unsaved work is lost.
Then there are the people who say it must be a software problem. I agree, so far. They suggest you need all the new drivers – well, I’ve got them. Or some settings may be wrong: disable sleep mode and screensaver. Did all that – no solution. Forbid Windows to shut down on its own: I did that with several settings, but Windows 10 freezes and in the end shuts down anyway.
Another suggestion is: make a clean reinstall of Windows 10. I did that twice and it looked like a solution. But then, all of a sudden, the issue reappears, even when there is hardly any other software installed on my machine.
Let’s face it, Microsoft: the problem is with Windows 10 itself. Somewhere there is a bug on one of the updates (an update that keeps returning, whatever you do) and that makes my computer crash. Only when it’s standing idle. In this idle time, Windows 10 is starting a process (defragging, checking software, I don’t know) and it stumbles upon a problem it can’t handle.
Event Viewer mentions the same critical error time and again with the Kernel Power. Duh! That’s me or Windows 10 spontaneously shutting down!
But then there is also a warning popping up about Hello for Business, saying:
Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Not Tested
User has logged on with AAD credentials: No
Windows Hello for Business policy is enabled: Not Tested
Windows Hello for Business post-logon provisioning is enabled: Not Tested
Local computer meets Windows hello for business hardware requirements: Not Tested
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Not Tested
Machine is governed by none policy.
Hello for Business is some kind of security software for facial recognition and fingerprints. It comes with an update – time and again. You can make a clean reinstall- in due time Hello for Business returns, and since I don’t have Windows 10 for Business, but only the Windows Home version, I can not shut Hello for Business down – there are just no options to do that. What is Hello for Business doing in Windows Home software anyway? I don’t have a camera, I don’t have a fingerprint pad. I don’t need Hello for Business, I don’t want Hello for Business! It is only making Windows 10 crash in idle time!
I don’t really need a response to this, because I already read them all. Most are crappy or completely beside the point, some are incomprehensible, a few are technically dangerous – and nothing, literally nothing works. The only thing that will work is: Microsoft providing us with a new Windows 10 update as soon as possible that either solves this problem with idle time, or kills Hello. Preferably both.
P.S. Pretty soon I got the solution for this problem by Andre on the Microsoft forum - an update that Microsoft didn't offer me automatically. Read all about it here: https://answers.microsoft.com/en-us/windows/forum/windows_10-update/windows-10-freezes-after-a-few-minutes-of-being/f53f5f63-27ec-4186-8000-e31d5bc80895?tm=1546435750385&auth=1