The only fix I found for it was to access the registry and make a change to point to the correct drive during boot. It apparently either changes the drive letter of the System Boot Drive to a different letter or at least changes the registry to have the boot process point to a different drive letter. Just a word of caution.Īfter some Googling I learned that the problem is in the Win10 'fix' for the WD device. I've found myself wondering if perhaps a few of the problems reported in this forum regarding BSODs may have been caused by this or something similar - in no way related to Macrium Reflect at all, obviously. I most certainly wish I'd have done that to begin with instead of trusting that Windows would properly fix the issue without rendering my system not bootable. After restoring I simply disabled the 'MyWorld' device from within Device Manager and haven't been bothered with notifications from Action Center since. I had no idea how to change the entry using binary data, hence restoring to an old backup. HOWEVER, the information I found showed to just change D: to C: and even after booting to rescue media and loading the hive that registry entry was in binary format. After some Googling I learned that the problem is in the Win10 'fix' for the WD device. There was no way around that I was able to figure out besides going back to a two-week-old Reflect backup. But when I finally did install some drivers which required a reboot my computer stopped the boot process at a BSOD. After all, if something odd happened I could just uninstall the device or undo what I had done some other way, right? WRONG! A problem was created which I didn't notice for two weeks because I had not rebooted my system. (Sigh) So I finally just gave in and chose 'fix problem' in the Device Manager. HOWEVER, with the release of Win10 Creator's Edition I was constantly being deluged with warnings from the Alert Center. I've seen this happen in the past and didn't want to mess with 'drivers' or such related to a NAS which shouldn't need drivers or to be listed in the Device Manager at all. I was able to access the shares on the drives just fine.

After installing the Creator's update for Windows 10 (64 bit) I noticed the device listed in Device Manager had a yellow exclamation by it, meaning the OS was having an issue with the device which needed to be addressed. It is a network storage device which connects to my network via a CAT5 cable. I use a 'NAS' device called the Western Digital My Book II World Edition.

Wd my book drivers windows 10