OK, that's fine and dandy, but it would be nice to get some sort of confirmation that something is happening. How many are going to check task manager for something that should routinely execute right away?
Anyway hopefully Microsoft gets this sorted. If it's going to float to the background while scanning that's fine, just tell me something, and two minutes is way too long.
Anyway now I know.
OK, got a sleep problem with Win 10 version 9879 (Everything worked fine until this particular update). Ay-yi-yi. It sleeps and wakes OK, but my hard drives don't like it ( my boot SSD is fine). I would get directories to hang up and either refuse to show the files or show the files after a long time. Disk management would not work and just sit there hung. I have to restart to reset the drives. The restart takes FOREVER to do.
To test, sleep the computer, wake it up, and then restart. If the restart takes much longer than usual, you have the bug.
I tried different drives, different SATA ports, BIOS update, none of these helped. So far, the one thing that has made a difference in access to the drives is to turn indexing of the drives back on. Does not help with the slow restart though.
Anyone else seen this? or do I once again have the computer from hell that is still having issues with sleep.
It's not much slower than in Win8, it's just that it doesn't show any signs of life for long time while it sits there and "thinks" (actually collecting data ). That I consider a bug.
To be clear, I'm talking about startup, not cleanup. On Window 10 it takes about 2 minutes to start, on Win 8/8.1 it's nearly instantaneous. That's the issue.
Yes, cleanup is about the same on 8 & 10, on startup Win 8 blows 10 away.
Running a Video server (Mezzmo) for a long time (> 1 day / 24 hrs) causes a problem when trying to shutdown the computer. The mezzmo server is fine and ends / exits normally but then when shutting down the PC you get a message "Your PC ran into a problem and needs to re-start". Pc shuts down OK -- and re-starts next time without any problems so I'm just ignoring the message.
The message only seems to happen if the PC (It's a laptop) is left running for > 1 day. No hardware problems on laptop such as overheating etc.