Quote:
Originally Posted by Rockin Robbins
Says the only one doing the bitching! Yikes, buy a vowel! And analyzing systems without information is voodoo, not helping. You don't know anything about what drivers he's trying to run on his machine and can't truthfully make the statement you made.
The only possible truthful answer is the generic one I gave. There was a problem of unknown nature with the Windows Explorer system. It had a problem, shrugged its shoulders and checked out. There's a possibility that the user ran out of patience before the system could correct itself. Possibly the system was hung. The possibility of a driver is very unlikely since the machine has been running normally for some time before the incident.
Since he rebooted and the system now works normally it is no longer possible to diagnose the exact nature of the malfunction. Even error codes set are usually generic in nature and can point at effects rather than causes.
As to Windows 10 updates, a widely known problem, even with the very few updates so far. I suggest following Infoworld's Woody on Windows column and Susan Bradley's Windows Secrets website, both of which are required reading in today's atmosphere of defective and sometimes deceptive updates.
And finally, when rebooting a system after a similar transient and inexplicable error it's best to make sure you do a cold boot and not a warm one. Turn the machine completely off, don't just do a restart. Then power the machine back on from completely dead. The cold boot process is different from the warm boot process and will rectify more situations.
|
If you were a 100% about what you are saying you would know that the problem this user posted about is caused by cold booting but with the wake by lan still turned on
