Latest W10 update or hardware failure?

After the latest cumulative update, my data drive E: (WDC 2TB) would not allow access to some of its folders. Seems I no longer had permission, access was denied. Added "take ownership" to the context menu, pointed to the folders and was able to now open them. Did a reboot to recheck, now windows does not recognize the 2TB drive. Disk management says it is now RAW rather than NTFS??

System error log shows, "A corruption was discovered in the file system structure on volume E:", and detailed description "A corruption was found in a file system index structure. The file reference number is 0x100000000001d. The name of the file is "\$Extend\$RmMetadata\$TxfLog". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".

Reformatted/checkdisk the drive and it acted normal. This morning when I turned it on, W10 said my 2TB drive needed repair, repair returned it to operation. Reboot did the same thing. WDC utilities say the drive "passed"

So? does this sound like a W10 update problem or hardware problem. HDD is about 3 weeks old. Never had that problem until the latest update. Coincidence or?? Opinions appreciated.

2GigaByte or 2TeraByte? You may made a typo as far as the size of the drive which sounds like a flash drive at 2gb not a hard drive at 2tb!

The first question will be are you set to start receiving Insider builds in the Advanced option of the Start>Settings>Security&Update section by chance? Even when an update sees a bad install it generally won't effect the partition table on any drive ruling the Cumulative for whichever build of 10 you have out there. Being a new drive only three weeks and seeing problems would tend to suggest you may have to return it under manufacturer's/dealer type warranties for an exchange or refund since it could well have a defect! If this on an SSD or mechanical drive?

Have you tried going into the Disk Management tool to see if you could initialize the drive in there at all? Often with any OS change or new drive being added in that will be where it will be seen while nowhere else until you right click on the volume to use the Change drive letter option or go upto the menu option and select the rescan option. The rescan is used when nothing is seen for a drive just added on.

The LifeGuard tools are generally quite accurate being one thing I have found when using them at times over the years. In fact the one and only Green drive I still have in use here is the 1tb back up drive kept in an external usb enclosure on the second build used for test purposes mostly. That enclosure had also seen a WD Black edition Sata 3 drive thought to be going DOA on me working fine suddenly as I was going to mention earlier but will indicate now as a drive thought to be bad seems to be working out just fine in a new fan cooled usb/eSata enclosure that I so far have been seeing immediate access to compared to how it would be a task to open up to view or download to while still internal! The same identical twin drive however previous the primary backup storage drive while that had been the secondary now runs 7 on the test build having been split to see a second backup partition and added in as a second OS and backup drive onto the other mini case there. That only allows for two HDs being compact and having a carrying handle for portable use like Lan parties,etc. NZXT "Vulcan" micro atx case

On a prior Vista build that was first to see the Windows 7 beta and RC builds by then having said good bye to Vista for both the 32bit and 64bit builds at the time I had pulled a 500gb WD out of the factory usb enclosure that lacked any sufficient air ducts and a commonly seen problem at the time when self contained external drives were just coming out was added in on the old build as the 3rd for storage. Never had a problem while the present build was planned out to see performance model drives not Raptors however put to use and except the one Sata 3 having an unknown problem and tested by the LifeGuard tools found to be good.

I never seem to have WD drives fail on me and that one was still good and still in use. Yet I have had a few instances where a drive didn't show up right away where I automatically had to go into the Disk Management tool in order to get things sorted out. Mostly for any clean install of the OS that was to simply see the desired drive letters put into effect since there wasn't any detection problem seen. As I can recall only one instance in the 7 beta and previously on XP more times there but still corrected in the Control Panel.