Why does Microsoft keep doing these things? My home server (a Windows 10 box) ran perfectly fine, and woke up when requested. And then, suddenly, it doesn't respond to a WOL anymore.
Possible reason: Windows 10 decided that their limited default Windows-provided driver was better than the custom, certified driver provided by Asrock.
Unfortunately, re-installing the original driver did NOT restore WOL functionality. Why, Microsoft, oh why... Anybody help?!?
No comments:
Post a Comment