New
#71
how do i get full specs?
shud i also post the p/n and s/n numbers on the back of the drive? Attachment 103850
update:: i reset my pc thinking itd go back to previous builds that was a mistake.. still same issue
Last edited by progenitor04; 14 Oct 2016 at 12:35.
+1
I held off on installing the AU for a long time for fear of this issue as I use multiple external devices to backup and transport files between several PC's, most of which are now updated to Win10.
I keep checking these threads, and those on the MS Community Forums for the promised announcement that these issues are believed to be resolved, but find none. Example:
http://answers.microsoft.com/en-us/w...on=14720421474
I keep checking the bug fixes listed in each of the humongous cumulative updates released so far, but find no documentation which specifically and explicitly addresses this issue.
Yet I keep reading in this, and other threads here, that the issue (causing NTFS partitions on external, and sometimes internal drives to be reported as "RAW") is presumed to have been patched. Has it? Pointer please ... or status report? Anyone?
Last edited by mike s; 14 Oct 2016 at 07:35.
new build jus came out hopefully it fixes theses issues
I'm in the same boat. See my post at Is the Anniversary Update Missing Drives Problem Solved?. I'm not inclined to try the AU and waste my time sorting out problems until I see clear confirmation that this bug has been fixed.
Rolling back from v1607 to v1511 scares me -- a can of worms perhaps. But after multiple troubleshooting and driver checks, etc. for my Samsung SSD T1 not being recognized, I forgot to remove it before a reboot, and it was recognized and fully functional. A fluke? No. It works every time, on my HP laptop and Dell PC. Just plug it in and startup. Fortunately it's the only Windows 10 glitch that I have run into on the laptop and PC, so you can understand my reticence.