Windows 10 Anniversary update problems, not recognizing external hdd

Page 2 of 9 FirstFirst 1234 ... LastLast

  1. Posts : 1
    Windows 10 64bit
       #11

    Rolling back fixed it. Thanks you so much for this thread. Hours have been spent searching.
      My Computer


  2. Posts : 9
    W10
       #12

    arspr said:
    Roll back to 1511 while you can.
    Did that once in W7, it screwed everything (local searches, slow pc etc...) Will it work fine here ?
      My Computer


  3. Posts : 5,478
    2004
       #13

    anthorama said:
    I have the exact same problem with a 500GB Western Digital device. Not recognized by Windows 10, but work perfectly on WIndows 7.

    I managed to transfert all the data from the 500GB WD to a PC with Windows 7. What will happen now if I format the external drive with Windows 10 ? Will it solve the problem as Windows 10 will be able to recognize the drive then ?
    If it works the same as my iomega external drive the answer is no - it still will not work on 10. My drive works on 7 and OSX but not on 10.

    As far as I can figure out UAS drivers were written by Intel in Windows 7 but in 10 they are written by Microsoft. They don't work quite the same and some drives don't work.

    I have tested the drive in another enclosure (LaCie) and it works so perhaps a USB to SATA cable is the answer but I've not tried it yet.
      My Computer


  4. Posts : 5
    Windows 10
       #14

    Since this post is active I'll add my HDD issues on here.

    Prior to the Anniversary update I had created a HDD Pool using the built in Microsoft Storage Spaces and had 5 WD Black 1TB HDDs plugged in. The storage pool worked fine but once I upgraded to the Anniversary update the Storage Pools started acting up. It started showing 1 drive as "Reduced resiliency; check the Physical drives section" and it suggested replacing the HDD. But the thing is the drive is only one month old and was working fine prior.

    In the end I did as Storage Spaces suggest and removed the drive (physically removed it from PC as well). I then checked the HDD for issues and nothing was wrong with it so I simply formatted the drive and plugged it back in. At this point all the HDDs in the Storage pool were listed as OK, including the one that was previously showing as consider replacing.

    Everything was going well but then the next day I started getting another notification from Storage Spaces that showed more errors on the Storage Pool. It then showed that 2 HDDs had "Reduced resiliency" and then it eventually went to show "Inaccessible" for another drive which added up to 3 HDDs. At this point it was just ridiculous since all the drives were bought at the same time and were new. What was even more ridiculous was that once I shutdown the computer and unplugged all the HDDs, booted Windows on its own HDD, shutdown and reconnected the 5 HDDs and booted Windows again they all showed as OK on the Storage Space.

    That fix was short-lived for the problem returned and it then listed one of the drives in a red "error" icon and then the entire Pool just vanished, to which I had to disconnect and reconnect all the drives to fix the issue. And as before it then listed all the drives as OK which is just insane and drives me crazy.

    What I am currently doing is backing up all my data onto my external drives and will try to recreate the pool from scratch. But I am considering doing a fresh install of the Anniversary update to see if it will fix any of the issues by creating the storage space after the fresh install. If it will work I have no idea but I do hope it does fix the issue.


    Overall the HDDs were randomly going into low power mode I believe and so the Storage Manager couldn't detect the drives which is why it was listed as either Reduced Resiliency or Inaccessible. I could be wrong of course but it is a case for the disappearing Hard Drives.

    If anyone has suggestions I would greatly appreciate any help. Thanks.
      My Computer


  5. Posts : 9
    Windows 10 64 bit - 1511 build (roll back from 1607 because NTFS to RAW bug)
       #15

    As posted in TweakGuides.com, there are updates for W10 including 1607 (Anniversary edition):
    https://support.microsoft.com/en-us/...update-history

    Nothing is explicitly mentioned about this issue so I don't expect anything solved, but it would be nice if people affected by this issue who continue in 1607 build, could re-test their drives. Does 1607's KB3176495 do anything relevant for us?

    (BTW, I can confirm I've received 1511's KB3176493).

    BTW 2: there's much discussion about this in this thread in reddit.
      My Computer


  6. Posts : 236
    Win10 Pro x64
       #16

    I have KB3176495 installed (Windows is now version 14393.51), I just tried my external HDD again and no dice. Maybe in the next group of fixes we'll get some love :P Until then my laptop will stay on 1511 so i have access to my drive
      My Computers


  7. Posts : 1
    Windows 10
       #17

    Same problem here, rolling back fixed it for now.
    Microsoft is still trying to figure out what is causing it, they know about the problem. They are even active on Reddit.
    If anyone wants to help out, then contact the MS guy on the MS forum by sending him a PM: http://answers.microsoft.com/en-us/w...1-f1872b7b4ba1

    He sent me some scripts for data collection but im not really comfortable with amount of data that is collected, the logs basically contain all filenames from the user directories that were moved during the upgrade process and even some fragments(real content) of private data from random sectors... I sure won't send such data for fun, that is just lazy, they could have excluded some logs that are CLEARLY not needed for analysis. I wouldn't mind him connecting to my PC to try to figure it out, but with blind data collection with irrelevant private data I just have to say no thanks, I will rather stay on the old version.
      My Computer


  8. Posts : 9
    Windows 10 64 bit - 1511 build (roll back from 1607 because NTFS to RAW bug)
       #18

    A bit off-topic but nevertheless...

    To your comment:
    volta9e said:
    He sent me some scripts for data collection but im not really comfortable with amount of data that is collected, the logs basically contain all filenames from the user directories that were moved during the upgrade process and even some fragments(real content) of private data from random sectors... I sure won't send such data for fun, that is just lazy, they could have excluded some logs that are CLEARLY not needed for analysis. I wouldn't mind him connecting to my PC to try to figure it out, but with blind data collection with irrelevant private data I just have to say no thanks, I will rather stay on the old version.
    I answer with an auto-quote:
    arspr said:
    It's sad but I'm not going to EVER fill up a Microsoft Account... (and less because of this reason).
    It's sad, but Microsoft really should revise the image they project about privacy intrusion... I wouldn't share ANYTHING with them either. I can fully understand you.
      My Computer


  9. Posts : 1
    Windows 10 Pro x64
       #19

    Upgrading to 1607 caused the second *internal* HDD on one of my PCs to be inaccessible as RAW format.
    I connected the HDD to another PC running 1607 and was able to access the data, although I had to import foreign disk in Disk Management.
    I then backed up all the data, replaced the HDD in the original PC, deleted the RAW partition, formatted it and copied the data back on. Now it works.
    Was quite scary for a while...
      My Computer


  10. Posts : 16
    windows 10
       #20

    here are my issues with the 1607 update. I have 2 WD my passport external drives and both show up as RAW. however on a laptop with 1511 version both these drives work as expected showing NTFS. I also have 2 seagate external slim drives. Both of those drives work on the 1607 update. For me the problem appears to be with the WD drives. I contacted WD , their solution is to reformat, but i wont do that since they work perfectly on earlier versions of windows. For information only I also have 2 WD blue internal drives and they are working fine on the windows 1607 build. Also have installed the latest updates to 1607 but the drive issues still remain.

      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:30.
Find Us




Windows 10 Forums