My Book World Edition

[Mark Vincett]

hi just install windows 7 7057 64bit and i cannot get it to see my book world 1TB drive on the network
I think its to do with 128-bit encryption i have not come across this before
thanks for any help :huh:

 

[robbyralarsen]

MyBookWorld

I am having same problem.

I have a 1 TB MyBookWorld, two Windows Vista machines, a Windows XP and a few other devices on my home network. When I built a 7100 Windows 7 machine (64 bit) this weekend, and added it to my home network, the MyBookWorld NAS drive was no longer visible from any of my computers. To get it to work, I had to shutdown my Windows 7 computer and restart the MyBookWorld NAS. I tried it several times and the same thing happen. I updated the MyBookWorld firmware but still the same behavior. I have not had a chance to change Windows 7 encryption from 128 bit to 40/50 bit, but will try that tonight.

I will post here again if I find a solution.

 

[robbyralarsen]

As I continue to search for a solution, I found this posted to Windows Vista forum: Vista 64-bit and WD MyBook World edition - Vista Forums

I am seeing the same behavior with Windows 7 64 bit. So would appear that WD MyBookWorld does not work with 64 bit OS.

Very sad!

Still looking for possible solution.

 

[johnnytactic]

My Book World 1TB Edition Networked Working

Looked everywhere for something on this topic couldn't find anything helpful. Somehow without really trying I was able to access my data via mapped drive in Windows 7 x86 (cant browse to it though - only mapped). Don't know exactly what does the trick but just letting you guys know to see if it works for anybody else.

First off I always have the same network name for all my home networks. My workgroup name is the same for XP, Win7 and My Book...(if there is a setting for that in My Book I would have set that back in the day) So that never changes for any of my systems or drives, if that makes a diff.

When I checked out the computers in my network via Win7 I could not see My Book as an actual listed computer. I then went into Computer and tried to add a mapped drive. I remembered the name and paths of some of the directories. I added the path that I knew... \\YOURMYBOOKNAME\FOLDER\ANOTHERFOLDER.

Naturally it did not recognize or allow me to map to the drive. So sometime later I went back to map a different drive on another computer and I then saw the name of my My Book with the rest of the other home computers. Waaa? Although when I tried to view it via Network it still did not appear.

Next I just went back to Computer and tried to map the same shared folder from there again and it allowed it. Arrrh? Would also note that I setup my permissions for My Book to allow anybody on the network to access and change the contents. If permissions is a key factor then you should be able to access your My Book by looking up the IP via your router and browser into it to make permisson the changes. Try the other stuff first and if it still does not work then try the permissions bit (just to see whats behind viewing a networked My Book via Windows 7)

Somebody try it out and let me know as I'm very interested to see if it works anybody else. Good luck.

 

[johnnytactic]

Also I turned on Network Discovery via the Network and sharing Center> Advanced Sharing settings.

 

[yowsurs]

any workarounds yet

I too have MBWE II 2tb, trying to install on Win 7 64bit OS. Spoke with WD tech, they said their "might" be fix in future, and just to keep on checking their website. I asked them to notify me, they said they couldn't, I just have to check their website. Thats a crock. Asked them to take back this hard drive and give me something that works w/ Win 7, no dice. However to be fair, they did say they will swap out the same exact Hard Drive for me.

 

[peter140]

I have even more severe problem with MyBook incompatibility with W7/64 bit --
Initially W7 recognized MyBook fine and I was able to access it without any visible problem. But I started to experience strange problems with W7 not willing to shutdown or go to sleep (I have Lenovo T500 and use it at home and in the office). Finally I noticed that if I physically disconnect MyBook from network, all my "shutdown" problems are gone! So I keep it disconnected and I do not think it is an intended use of this "paper press".

Cheers,
Peter

 

[salwaldo]

Windows 7 & WD MyBook World Edition II

I had the same problem setting up my husband's new Dell laptop. Windows 7, 64 bit. I personally use a Mac. Couldn't understand why I could see and access files perfectly with my Mac and all of our old PCs running Windows XP. In fact I am running a virtual machine in my Mac with Windows 7 (32 bit) and it works fine.

I got the run around from Dell, told me to call Microsoft. Microsoft told me to call Dell, after trying to blame the router. Long story went nowhere.

Finally with the help of a quick assistance code (eternally grateful to my son-in-law who works at Microsoft) I got some assistance.

First as I kept reviewing all my networking settings in Windows 7 machine I mapped the drive (Z changed the encryption from 128 bit to 40//50 bit. I think that is what allowed me to access the WD MyBook World without having to login every time. I could then see and open files. However, I still was not able to save files (access denied) or even create a new one and save it to the drive.

What Microsoft tech did for me was to go to a Dos prompt and grant rights to essentially everything on my Z drive. Didn't get whole command, but it was something like this Z: icacls *.*/grant everyone: f/t/c It successfully processed 23, 163 files and failed to process 4,733. Whole process took probably an hour and a half.

Hope this is helpful to others struggling out there with similar issue.

 

[pejx72]

Problem Solved

For me, at least: From reading the various forum discussions on this I surmise that the Win 7 64 shutdown problems are caused by Windows waiting for the hard drive to respond that it is powering-down. Under the Network Tab of Windows Explorer, my Windows 64 setup seems to recognise the MyBook as a "Storage Device" and as a "Computer". The "Storage Device" element doesn't work properly, but the Computer one does (I can access all my MyBook directories from there - I also mapped them to Drive letters just in case...). This means the "Storage Device" is unnecessary, right? So I went to Device Manager and "Disabled" the MyBook as a Hard Drive. Since then everything has worked perfectly: No shutdown problems; constant visibility of the MyBook as a "Computer" on my home network. I guess all the issues were caused by a bad/wrong driver for the MyBook as a *Hard Drive*, and by preventing Windows 64 seeing it as a Hard Drive I have fixed my problems.

Let's see how long before it goes wrong again...

Let me know if this worked for anyone else?

 

[WeedySeaDragon]

Problem solved via Firewall

Hi. Setting up new Dell laptop with Windows 7 Pro 64bit and couldn't see my MyBookWorld (whereas wife's new Dell laptop with Windows 7 Pro 32 bit can. Read this thread but couldn't get it to work. Looked up logs on MyBookWorld administration and saw that my new computer was getting logged on and then very quickly logged off. Made me suspect the firewall.

Opened Trend Micro Internet Security, clicked Home Network & Firewall Controls and then Check Network. Trend searches the network and lists all the "computers" it can find and they are all by default Not Trusted (marked "Do Not Trust"). I found the one that is my MyBookWorld drive (right-click MyBookWorld in Windows Explorer and it's listed in the device homepage) and clicked Trust button. This changes the status to Trust. This didn't work! (even after restarting pc and drive) :huh:

SOLUTION: Next I just turned off Trend Micros firewall and turned on Windows firewall. Bingo! All of a sudden I've got my My Book World drive as well as the Windows HomeGroup computers I couldn't get to work!

I wish Dell had offered me the opportunity to get Norton IS which is what I got with my wife's Dell only 3 months prior. NIS seems to work really well as far as I'm concerned. And I bought a 3 year licence with Trend.

Anyway, happy it all works now.

 

[Bit64z]

Windows 7, 64 bit - recognizes all my HW. So far so good. Except for the following: I have had problems with one of my My Books being slow to wake up, or respond after periods of inactivity. This results in apps and components of windows being unresponsive for extended periods, like 5 minutes max I waited. If I am patient the drive wakes up and everything starts to work again. But that is still pretty damn bad behavior.

Does anyone else think that their issues are related? Sometimes My Book has been missing when I started 7, turn the drive off and on physically it comes back, but again, might take quite some time to "wake up".

Forgot to mention, both my external drives are connected via eSata, not USB or FW.

 

[PerfectPirate]

Windows 7 Shutdown with MyBook NAS Online

I too was going nuts with my 64-bit Windows 7 freezing up on every attempted shutdown, if the MyBook World Edition II was powered up. Like Pejx72 (see earlier posting), I came to the conclusion that file system handling was causing the system to freeze as it waited for a shutdown acknowledgment from the MyBook which, of course, it was not going to get.

My particular MyBook appears only as a storage unit and a media device under the 'Network' tab in Windows Explorer. However, it also shows up in the "Disk Drive" category of the Device Manager window. I pulled up the context menu in Device Manager (right-click on the "MyBook World Edition Network Storage" entry) and selected "Disable" from the menu. At this point, Device Manager appeared to hang up, with the cursor stuck as an hourglass. I then went into the web page for the MyBook and powered it down, which freed up the hourglass in the Device Manager window.

After a reboot, the partitions on the MyBook are still accessible through the WD Discovery program and reconnect automatically in Windows Explorer. However, the disk has a "Disabled" status in Device Manager and my Windows shutdowns (Sleep, Hibernate, Shutdown or Restart) appear to be working normally.

My conclusion is that Windows was treating the MyBook as an internal drive, thanks to its entry in Device Manager, and this was causing the system to hang up when shutting down. I'll post here again if my solution doesn't stick. Interestingly, other computers who only accessed the network through WiFi did not appear to have the same shutdown problem. Perhaps this has to do with the sequence of shutdown activity, with WiFi going down before the file system tries to.

 

[BHarris83]

WD My Book - Unable to access drive

Just tonight I noticed I was unable to access my H: drive which is my WD My Book. This was of great concern to me as I back EVERYTHING up to it. It had been working perfectly fine just a few days ago.

The first thing I did was eject it, and plug it into another USB port. It came back, but I was still "denied access". I checked the Drive Manager and while it was showing as healthy, I was unable to check the properties of the drive after hitting Populate on the Volumes tab of the drive properties. It simply did nothing at all.

If I did the same on another drive it came up with the Backup, Defrag, Sharing, and all that other information. But NOTHING on the My Book.

I restarted and the problem still persisted. I have changed absolutely nothing on my computer in the past week and somehow this pest of a problem cropped up on it's own.

What I ended up doing and what ultimately worked was to go to the drive's security tab in properties and make myself the sole owner of the drive. Now everything is working just as before.

I have absolutely no idea how it changed it's owner to something that an administrator cannot even access, but it did and changing the owner back fixed the issue.

 

[simianu]

Windows 7 Ultimate X64, My Book World Edition II Ethernet.

Discovery on network worked poorly, most of the time did not work. When I opened the link to the hard drive in Total Commander, it open an Explorer window, usually to the My Documents folder, rarely to the MBWE.

I used the ethernet hard drive at the office where it was set up for that network, on XP.

Browsing through the setup of the hard drive (using an internet browser and the hard drive's ip adress) I found the network settings and changed the network name to my current network name which was set up on my router (SSID).

It works perfectly now.

Hope this helps!

 

[DrHouseFan]

Worked for me too.

For me, at least: From reading the various forum discussions on this I surmise that the Win 7 64 shutdown problems are caused by Windows waiting for the hard drive to respond that it is powering-down. Under the Network Tab of Windows Explorer, my Windows 64 setup seems to recognise the MyBook as a "Storage Device" and as a "Computer". The "Storage Device" element doesn't work properly, but the Computer one does (I can access all my MyBook directories from there - I also mapped them to Drive letters just in case...). This means the "Storage Device" is unnecessary, right? So I went to Device Manager and "Disabled" the MyBook as a Hard Drive. Since then everything has worked perfectly: No shutdown problems; constant visibility of the MyBook as a "Computer" on my home network. I guess all the issues were caused by a bad/wrong driver for the MyBook as a *Hard Drive*, and by preventing Windows 64 seeing it as a Hard Drive I have fixed my problems.

Let's see how long before it goes wrong again...

Let me know if this worked for anyone else?

I didn't have the shutdown problem.
WD Link could see my drive in the devices found window.
The Drive Map Section was completely blank.
As soon as I disabled "My Book Live Network Storage" in the disk drive section of device manager my shares appeared and I was able to access the drive.

Thanks for your help.