Windows 10: Windows 10 Anniversary update problems, not recognizing external hdd

I updated my Windows 10 using media creation tools, after ~3hrs the update completed, but I had a problem. The OS couldnt access my external hdd. Because of that I decided to rollback, my hdd worked again. After checking that the update was in fact the problem, I did a clean installation of the anniversary version, but the problem persisted. I noticed that it is in fact recognizing the partition as RAW instead of NTFS.
How can I solve that problem?

:)

 

External Hard Drive

Are you getting a specific error message? Checkout these links: Windows 10 Anniversary Update common problems and how to fix them and Windows 10 Anniversary update problems, not recognizing external hdd - Page 3 - Windows 10 Forums

 

External hard drive not compatible with Windows 10

Hi,

Have the same problem.

Method 1, the external hdd works fine on another computer (non windows 10) & other external hdds work fine on this Windows 10 computer.

Method 2, troubleshooter recognized this as a driver problem but failed to update & solve the problem. I think this is probably due to unavailability of a newer driver.

The external hdd is Seagate Expansion 2TB (SRD0NF1). In devices & printers, it is recognized as "Unspecified".

Please update ASAP.

 

I don't know, but I think some other users had similar problems with disks apparently losing partition information when upgrading.
It's good to know that the rollback cured the problem though.

 

I have 2 external drives and it didn't affect either. I've noticed better noticeable better performance after the Anniversary update.

 

I think I also suffer it and here you have a link to the very same problem reported by other user in reddit forums

I suffer those exact symptoms:

• HDD Seagate External Portable Drive 1TB USB 3.0 P/N:1D6ADD-500 S/N: NA484299. It doesn't matter if I use either 2.0 or 3.0 ports.
• chkdsk perfectly sees the NTFS partition.
• Piriform Recuva perfectly sees the NTFS partition.
• But neither Explorer nor Disk Administrator see it. Disk Administrator sees a "RAW" partition.
• I've also used this HDD in a Samsung Smart TV which perfectly sees the drive contents too.

I suppose I'll roll-back to Windows 10 build 1511 ASAP.

THIS IS A SERIOUS BUG I THINK.

 

Agreed, and some folks posted similar problems on the big Anniversary Update thread.

It's good to know that, even though Windows 10 reports it as 'RAW', the drive contents are still unaffected.

One suggestion I have is to use the Feedback app to report it. It needs a Microsoft Account and probably involves Microsoft looking at your computer's configuration, which I know some folks wouldn't be happy with, but on the other hand it increases the chance that Microsoft will fix it.

 

It's sad but I'm not going to EVER fill up a Microsoft Account... (and less because of this reason).

Nevertheless I've checked that when you press the roll-back option in windows configuration you get a feedback survey. I'll provide the link to these threads there...

More info: Although chkdsk perfectly sees the drive/partition, the rest of cmd does not seem to. I mean, if I type "g:" in order to go to that conflictive drive I get a "Solicitud no compatible." answer. (That's Spanish. In English it would be "Incompatible request" or something like that). "dir g:" gets the very same answer.

More info (and 2): If I connect the HDD to my router (it offers this option), I can access it from Windows as a LAN drive ...

I'm tired, reverting to 1511 NOW.

More info (and 3) after reverting:

Wow, the revert process has been pretty fast. I'm on 1511 again.

I can confirm that I can access the drive again. When I've plugged the drive I've got the typical "the drive has errors" message which is not unexpected as I've hot-plugged / -unplugged it several times in several places...

Nevertheless I've used the Repair tool (which is chkdsk in disguise). I copy the result report in case some of it can offer some insight about this trouble (sorry it's in Spanish):

Code: - <EventData> <Data>Comprobando el sistema de archivos en G: La etiqueta de volumen es Seagate Expansion Drive. Etapa 1: Examen de la estructura básica del sistema de archivos... 160000 registros de archivos procesados. Comprobación de archivos completada. 0 registros de archivos grandes procesados. 0 registros de archivos no válidos procesados. Etapa 2: Examen de la vinculación de nombres de archivos... 186268 entradas de índice procesadas. Comprobación de índices completada. CHKDSK está examinando los archivos no indizados para volver a conectarse a su directorio original. 0 archivos no indizados recuperados en su directorio original. CHKDSK está recuperando los archivos no indizados restantes. Objetos perdidos está en \found.000 Etapa 3: Examen de los descriptores de seguridad... Liberando 1 entradas de índice no usadas del índice $SII del archivo 0x9. Liberando 1 entradas de índice no usadas del índice $SDH del archivo 0x9. Liberando 1 descriptores de seguridad no usados. Comprobación de descriptores de seguridad completada. 13135 archivos de datos procesados. CHKDSK está comprobando el diario USN... Se ha completado la comprobación del diario USN. Corrigiendo errores en el atributo de mapa de bits de la tabla maestra de archivos (MFT). CHKDSK detectó espacio disponible marcado como asignado en el mapa de bits del volumen. Windows ha hecho algunas correcciones en el sistema de archivos. No se requiere ninguna otra acción. 976759807 KB de espacio total en disco. 188724652 KB en 74787 archivos. 48608 KB en 13137 índices. 255791 KB en uso por el sistema. El archivo de registro ha ocupado 65536 kilobytes. 787730756 KB disponibles en disco. 4096 bytes en cada unidad de asignación. 244189951 unidades de asignación en disco en total. 196932689 unidades de asignación disponibles en disco.</Data> <Binary>007102007C570100F44502000000000023000000000000000000000000000000</Binary> </EventData>[/quote]

 

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 ?

 

I wouldn't do that. The problem is in Windows not in your drive. And in this thread at least one user has said that even formating the drive hasn't solved the issue.

 

So there's no solution at the moment for this problem ?

 

Roll back to 1511 while you can.

 

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

 

Did that once in W7, it screwed everything (local searches, slow pc etc...) Will it work fine here ?

 

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.