Mypassport For Mac On Windows 10

There are ways to extract the drives since they are no different then any others just slapped into a tightly fit housing. With model changes and still the possibility it wasn't a 3.0 model to begin with while it may have worked on 7 it simply may end up not being able to on 10. You have to remember that 10 is three versions newer then 7 and has seen a number of changes in between. That plus the UEFI factor possibly being the source of this can't be ruled out either! Just like trying to boot from a 10 stick may run into problems the WD model there could also be running into that as well.

Feb 11, 2016 - If you're switching from a Mac to a PC, you'll probably need to bring all the files you've. Casey February 11, 2016 10:24 am.

I have a suspicion you could be running into that rather any driver issue where this time you need to configure things for Legacy instead of UEFI in order to get 10 to detect it on 3.0. How to selectively remove stored passwords in chrome for mac. True there is a lot we do not know yet with this PC or Drive, but Ultra's are both 3.0 & 2.0 as posted in links here from WD, so i suppose i am just speculating on what was shown so far here.

I would not suggest him/her opening this WD and i see no screws so either snapped together or glued. As i have this drive and UEFI. I think has to do with where is it being plugged in which USB ports as i see a listed PCI USB Controller card. Asked about updated system drivers, chipset,etc. Here is my Device Manager. Well that decision would come when there is no longer any option for returning the drive under factory warranty which might be still an option. But having actually removed a drive from one of the earlier models it requires a little patience but can be done and even see the drive put back in while the idea is to utilize a different bus entirely.

Still got to use usb on a laptop but if your desktop pc has the eSata ports that would be an upgrade since you would be seeing the drive plugged directly into the port on the board by way of an internal extension cable. At one time you might have seen a 1394 Firewire type adapter before eSata was available. Plus the issue of not being detected when plugged into a 3.0 port is not isolated with the Ultra model on just 10 alone ruling the version as the cause. I suspect the model is older or has a problem and why 10 isn't detecting as you see there from having an older chip inside as another possible cause despite having the same model name.

Sometimes you need a firmware update in order to get something to work. Computer Type: Laptop System Manufacturer/Model Number: Acer Aspire 5630.

(Amongst others, but this is the one with most recent BSODs.) OS: Windows 10 Pro (32-bit) 16299.15 CPU: Intel(R) Core(TM)2 CPU T5500 @1.66GHz Motherboard: Acer Grapevine Memory: 4 GB, 3GB usable Graphics Card: NVIDIA GeForce Go 7300 Sound Card: High Definition Audio Device Monitor(s) Displays: Built-in display Screen Resolution: 1280 x 800 x 32 bits ( colors) @ 60 Hz Hard Drives: Hitachi HTS541212H9AT00 ATA Device Antivirus: Left as default/ Defender Other Info: It's old. Originally bought with Win XP and upgraded OS a few times. I think i see you have a PCI slot USB controller. Try filling in as much system specs here as you can in your profile this helps us more to help you.Well nope, I aint having PCI Slot USB ports in my PC.

My Mobo is (upgraded Bios): Asus Z97 Deluxe, What is essentially happening is, when plugged for the first time. A pop-up window comes saying installing drivers and then it installs and pop window disappears.

That one time I can see my HDD on 3.0 port. From, the next time I plug in nada nothing happens and HDD is not detected.

PS: I have checked health of HDD via HDtune and other software as well and its perfectly healthy + the cable is all good to go. Plus the issue of not being detected when plugged into a 3.0 port is not isolated with the Ultra model on just 10 alone ruling the version as the cause. I suspect the model is older or has a problem and why 10 isn't detecting as you see there from having an older chip inside as another possible cause despite having the same model name. Sometimes you need a firmware update in order to get something to work.I again checked with Win 7 and its working there, so I can confirm its windows 10 issue.