Lost access to drive - "Access is Denied"

Anybody? I really need some help here. Right now I can't access my drive and I have no idea how to get it back. And I have no idea why this even happened or why I had these problems copying over to the enclosure.

I do not want to frighten you, but you should not FORCE Windows by no means to access Drives.
A lot of people had issues with Drives, some showed like RAW. There is something wrong and I think nobody knows exactly what is the Problem.
I myself lost one HDD with 1TB Data on it, just trying to get access to it, because it was working normal under W8.1 and Drive was like new, very little usage.
From my point of view, the best is to roll back to your previous OS. If you have another PC, try to access Drives there.
But, the decision is of course yours.

Adalwar said:

I do not want to frighten you, but you should not FORCE Windows by no means to access Drives.
A lot of people had issues with Drives, some showed like RAW. There is something wrong and I think nobody knows exactly what is the Problem.
I myself lost one HDD with 1TB Data on it, just trying to get access to it, because it was working normal under W8.1 and Drive was like new, very little usage.
From my point of view, the best is to roll back to your previous OS. If you have another PC, try to access Drives there.
But, the decision is of course yours.

I can't roll back - I installed Windows 10 fresh from a Windows 10 retail USB thumb drive.

Anyways, somehow I managed to create an "autenticated users" entry and gave it permissions and it finally allowed access to the drive. It took many tries before it somehow worked. I then ran a chckdsk and it found a whole bunch of problems and corrupted files.

"Found corrupt basic file structure"
"Found an unneeded link"
"Found a bad index"
"Found corrupt security descriptor entry"

Among other errors. It took 2 attempts but Windows repaired the drive. I then checked all the files referred to in the chkdsk logs. Some have backup files thankfully so to be safe I will replace them. Some also had repair files I created for this very reason so I can repair them myself (par2). A couple I just deleted since they're not important and I have no idea if they are intact or not.

But the big question now is...what happened? Why did Windows freak out this morning and corrupt the drive trying to copy files over? Now I'm scared to death to try copying again untiI I know what happened. Is it linked to my issues with the enclosures not playing nice with USB 3 last week? These enclosures always worked fine until I tried them recently with Windows 10.

Can anyone help me figure out what's going on with my external drives? Another drive just did the same thing in the enclosure. I just got through scanning my enclosure drives using chkdsk and one drive that was okay an hour ago is now inaccessible. I was adding one drive at a time back in my enclosure. Now I added the 4th and last drive in and now a previous drive that checked out okay is inaccessible. Something really bad is going on and I have no idea what. This enclosure is now connected via esata by the way - connected to my esata internal PCI card. Earlier I had it connected to my motherboard's built-in USB 3. ports. I never had these issues with my Windows 7 PC. All hell is breaking loose with my external drives - esata, USB 3 - one minute esata works and USB 3 doesn't, next minute esata doesn't but USB 3 does. Sometimes when I turn on the enclosure the drives are detected, sometimes not. And now the drives are getting corrupted and inaccessible. What could possibly be happening here?

If you have one enclosure with four drives giving problems, and you have tried two interfaces, I would be suspecting the enclosure hardware. The fact that it worked with win 7 tells us nothing as this was probably because the hardware hadn't developed the fault then.

I would be looking at taking the enclosure out of the equation. Can you hook the drives to an internal mobo sata port to run chkdsk? Unfortunately, it looks like the drives are corrupted but at least removing the enclosure will be helpful in isolating the cause.

Good luck.

Well all 4 drives in the enclosure have suffered various levels of corruption. I lost access to a 2nd drive after it tested ok earlier today. After regaining access to the drive, I've got over 1TB of data gone from the 3TB drive - and the worst is I have no idea what is lost. I had lots of random files on there waiting to be backed up. Windows did an automatic chkdsk and deleted a ton of stuff and the chkdsk log tells me nothing about which files were deleted or corrupted. I see lots of folders with half the files missing. I'm scanning the drive with Recuva deep scan hoping to at least find out what was lost, but I'm not hopeful.

Any idea of a way I can see a list of files that were removed? They were just there a few hours ago so they are likely still on the drive (corrupted of course) but just removed from the index by chkdsk. Recuva is taking forever to do a deep scan. The normal scan gave me nothing useful. At least if I knew what I've lost I can try to recover it from another drive because some of it is definitely backed up, but the question is what files are gone? This is what I get for being disorganized and not knowing what's on which drives.

I noticed on Icy Dock's site they say this:

"Note: WD Green and WD Red hard drives have a feature called Intellipark. This feature makes the drives automatically park themselves after being idle for 8 seconds. There is a small chance that certain drives may appear offline to the USB host of the MB174U3S-4SB and can cause the USB host to refresh. This could cause the remaining drive(s) to power cycle, interrupting any data transfer and potentially causing data corruption on the drives. We recommend WD Green and WD Red drive users to disable the Intellipark feature to prevent this issue."

They also warn against having both the USB 3.0 and esata ports connected at the same time to avoid corruption. I had a WD green drive in the enclosure. I can't remember if I had both interfaces connected at one point during the week during my testing. I may have. And I also noticed I had warnings in my event viewer about "Disk 3/Disk 4/Disc 5 has the same disk identifiers as one or more disks connected to the system" - this is what I was having trouble with last week - Windows wasn't recognizing the drives Then suddenly it seemed to work. I don't think the interfaces of these enclosures play nice with Windows 10, even though the tech told me on the phone the other day they should be fine. So I have no idea what exactly went wrong but now I am very uncomfortable turning on the other Icy Dock enclosures out of fear of losing more drives.

Sorry, but I can't be of much help but your mention of same disk identifiers rings a loud warning bell. That does indicate that you had two interfaces connected. I can imagine that would seriously stuff things up e.g. read part of a file from one disk and wrote it back to another etc!

With large disks any recovery program will take a loooong time. I would still be making sure I was dealing with a known by hooking one drive at a time direct to the mobo sata port.

All I can say is I wish you luck with the recovery.