Windows 10: Lost access to drive - "Access is Denied"
I WARN you, the risk you LOSE all your Data is very high.
A short story of what happened to me:
Upgrade from 8.1, all external HDD were working ok, also in W10.
In W10 I was doing a System Backup to external HDD, almost at the end there was an Error, at same time i saw in Windows Explorer the Drive getting unrecognized/RAW/Unformated.
Tried to FIx/Chkdsk resulted that Windows Picked up the 2nd. FAT Table, wich was very old had entries from 1 year ago, also finding a lot of errors / bad entries / lost chains / lost Dir / etc..
At the end, I got Drive back but when I looked into Data it was all scramble, unusable, only 2 files were OK, all other Data was trash.
So, be careful .
If I was you, I would not try anything else, trying to Fixing it, just would install a Win Version which your Drives were working OK.
Last edited by Adalwar; 12 Oct 2016 at 03:51.
I appreciate the concern but what am I supposed to do? Leave them inaccessible? How does that help me in any way? They're already borked. At this point I needed to get access to the drives (which I have done) and assess the damage. Installing a new operating system is absolutely out of the question. I just spent months setting up my new Windows 10 install on my new PC. I will not trash all that hard work because of a hardware incompatibility issue with an enclosure.
So I pulled all my hard drives out of all my enclosures (I have many smaller ones that pile up over the years so I have a bunch of 4-bay enclosures). I put each one separate in my PC directly and ran chkdsk through the properties option. The good news - almost all my hard drives test perfectly with no file errors and no issues. So most of the enclosures, including a couple Icy Docks, were intact.
The bad news is all 4 that were in my problematic Icy Dock were corrupted to some degree. All 4 test fine now that repairs have been made by chkdsk but the damage has been done. Two drives just lost a few files. No big deal - they can be replaced easily enough. One drive I lost 1 full TB of data since chkdsk deleted a third of the drive's contents. I spent all night in Recuva restoring them to another internal drive. Most of them are perfectly fine according to Recuva - no overwritten data - and a few zip files I've tested so far test fine. The worst part is I had a ton of smaller files organized into subfolders and though the file names are intact the original folder names were lost, so they are all thrown into one gigantic folder now and I have to sort through them all as best as I can and put them back where they belong. Some of them I think I have backups for but a lot of this stuff hasn't been backed up yet unfortunately.
So the only drives that were messed up were the ones in that one problematic Icy Dock enclosure. But I still don't know what happened:
- Did I trigger the corruption by copying with teracopy? I doubt it since I've been using it all through setup of my PC and I had no issues teracopying internally from drive to drive and from USB thumb drive to internal drive.
- Did I inadvertently have both USB 3.0 and esata interfaces plugged in at the same time? Maybe - i have been switching back and forth with the connections all week because these enclosures have not been playing nice. First the USB 3.0 enclosures don't get recognized, but esata does. Then it's the opposite. Sometimes i can eject the esata drives through the Hoghpoint RAID management portal in the browser, and sometimes they won't eject. So lots of enclosure issues all week. Only this one Icy DOck enclosure corrupted my data thankfully.
- Could it be due to one of the drives in that enclosure being a WD Green drive and the intellipark feature screwed things up? If so the obvious thing is just not to use the green drives via esata any more. But I don't know if that was what caused the issue. Their web page specifically mentions this possibility at the top of the product page. Indeed the lights on the enclosure were going nuts as if the enclosure kept dropping the drives. Remember I also had those error messages in the event viewer about "same disk identifiers as one or more disks connected to the system". Could that be what happened?
So what do I check for now? I'm scared to death to put my healthy drives back in any of the enclosures now. Obviously I need to be able to use my drives. But what caused all this? Do I avoid my esata card? Do I avoid using my motherboard's USB 3.0 ports? That makes no sense - the USB ports work fine with my USB 3.0 thumb drive. I don't know at this point where to begin troubleshooting. Maybe that particular enclosure just developed a fault? All I know is the moment I tried copying files to it yesterday, all hell broke loose. Just minutes earlier I was zipping up some files in one of the drives in the enclosure to my internal drive. No issue. Lightning fast. The moment I tried copying back to the drive, things fell apart. How should I proceed? Buy all new enclosures that specifically say they support Windows 10? I don't have that kind of money.
Also worth mentioning - I don't believe I tried copying to any of the drives in the other enclosures. Only that one that has caused all the issues. So none of the other enclosures corrupted any drives or files when turned on while connected to my new PC. Only the one I tried copying to. Sorry for all the details but I'm just trying to figure out what went wrong so I don't go through this again. I need to use my drives but at this point I don't know how to connect them or what to do.
Also - several reviews of this Icy Dock drive on Newegg talk about corruption:
"- after a year it corrupted 3 of my drives, i was able to salvage two of them by formatting them then using recuva, but the data on one of them was lost and i had to retrieve it from a backup. only the drives contained in this were corrupted."
"I lost 6 different drives to corrupted data before I replaced with Thermaltake ST0020U. It's possible I was doing something wrong with setup, but I fail to see how."
"-Could only get 1 drive to be recognized at a time (because I could only get eSATA to work)
-USB interface would not work at all. Plugging in the USB gave me a glowing brick."
"I have lost 2 - 3TB drives in this ICY DOCK and some data that I could not recover from either drive."
So it may be just a poorly-designed enclosure or poor interface. They looked like very good enclosures. I am very hesitant to use any of my Icy Dock drives now which is a shame because I have 3 which cost close to $400. One I got for Christmas last year. Now I feel I should just toss them out. Very upsetting. What should I be looking at for multi-bay external enclosures that play nice with Windows 10 and USB 3 and supports large (4-6TB) drives? Keeping in mind I'm not a rich businessman - this is just for personal use.
Interesting follow up, rivre. I didn't realise you had so many Tb of stuff at risk!
Certainly looks like the Icy Dock enclosure is the likely culprit given your experience and that of the people quoted above. What I find hard to comprehend, though, is any link with win 10 as USB and Sata are very old and well understood interfaces. Just had a look at my disk drivers and all are dated 2006 except for the USB 3.0 ones that are dated 3/10/2016.
Perhaps you need to try again to get Icy Dock to help?
Perhaps you could try an enclosure with a drive that was expendable and try to trash it? Try it with another OS?
Good luck and best wishes. This is a very troubling experience for you.
Thanks. Yeah, this is a very upsetting experience for sure. Especially frightening when I don't have everything backed up like I know I should. My drives are a mix of old (500GB/640GB) and newer (3TB-5TB). Some things just aren't organized the way I need them to be on my disks and so I keep putting off backing up. Space is also an issue. I do have some of it backed up.
I'm leaning more and more towards the enclosure being the culprit here. There aren't a whole lot of choices out there for external 4-bay enclosures. I'm looking at a Mediasonic on Amazon. They have been making them for years. They say they support up to 8TB per drive. The thing is I tried one with a USB 3 interface years ago on Windows 7 and it didn't like my USB 3.0 card at the time so I returned it. I have an older one that connects via esata only and it's never caused any issues for me. Their current model supports esata and USB 3.0. I'm considering giving it a shot. I'm not sure if their current USB 3.0 interface is more compatible now or if it works well with Windows 10. I need something to put my drives in and I no longer trust these Icy Docks. Money wasted.
Icy Dock was useless when I called last week about the initial connection issues I was having with my enclosure. I wouldn't expect any better with this issue.
I'm still not sure what to think about the multiple "Disk X has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue." errors.
Looking back in my event viewer I now see I was getting these errors for a while now but it's only since I tried copying data to the Icy Dock enclosure the other day that the drives got corrupted. I may have also been getting this error with another enclosure by a different manufacturer - this one connected via esata. So...is my esata card at the root of this corruption/error message? It used to work great in my Windows 7 PC. Or is it something else causing this error? I don't remember now if the actual corruption during copying happened via USB 3 or esata since I was going back and forth with the connections trying to get the drives to get recognized. I tend to use the Icy Docks via USB 3 since that's why I bought them. I do know these error messages were being logged in event viewer long before I ran into this corruption, and the Icy Dock drives were not connected to both USB 3 and esata ll that time. So I highly doubt the issue was due to both connections being plugged in simultaneously as I don't think that was the case.
My event viewer is full of those exact same messages day after day, each time I turned on an enclosure, until the corruption finally hit when I started copying files to the Icy Dock. That's when I realized I had a serious problem.
I was making a full disc backup to a different enclosure (not Icy Dock) the night before my 4 drives got corrupted in the Icy Dock, and the backup software (Acronis) kept locking up at the start of the backup, taking several minutes to continue. Once it unfroze it continued the backup and the verification completely successfully so I didn't worry too much about it. I think during that time in the event viewer I was getting those "same disk identifiers as one or more disks connected to the system" errors for that enclosure.
Icy Dock specifically mentions not connecting esata and USB to the same enclosure at the same time. I'm absolutely certain I didn't do this with the other brand's enclosure I was doing the backup with, because it only supports esata. Yet it looks like that one also may have thrown up these errors. I can't tell for sure since event viewer is so cryptic.
How do I go about troubleshooting this error message and it's cause? Is USB 3 on my motherboard (Gigabyte Z170x gaming 7) not playing nice with my enclosures the issue? But as I said some of my enclosures are esata only. Is it my esata card? Is having the esata card installed in the system enough to screw up all my enclosures? I think this message may be at the heart of my problem but I don't know what to look at as a culprit. I'm not convinced at this point that it is the Icy Dock at fault. I know this is a very technical and detailed issue I'm posting about. I just think the more info I post the better to help figure this out. I'm really stuck here and I have a pile of healthy drives now that I'm not comfortable plugging in again until I have a good idea what happened.
- I had fast startup enabled by default until I just discovered it was causing shutdown errors in event viewer so I've disabled it now. Is it possible fast startup was somehow causing a malfunction with my esata card being recognized and that caused havoc with my enclosures? I used to get a non-RAID boot screen for my RocketRAID 622 esata card at each startup on Windows 7 but I don't get that on Windows 10. Just a stab in the dark but I'm really stuck here.
- Could it be the "Allow the computer to turn off this device to save power" option that is enabled by default for my USB 3 ports are to blame? Maybe the ports were cutting out while copying data and that caused the corruption? Just another stab in the dark.
- Could it be the intellipark issue with the WD green drive that was in the Icy Dock? But I don't have a green drive in every enclosure. There was one in the Icy Dock and that's one of the drives that was corrupted. I have WD blue and black drives too and rumor has it some of those drives have intellipark also. I have no idea if that's playing a part. Icy Dock warns about this. They highly recommend disabling intellipark. many forums highly recommend against it as disabling it causes issues. All I know is I never had issues with enclosures until Windows 10.
Note: this is what Microsoft says about KB2983588:
This problem may be caused by any one of several different situations. The two most common situations are the following:
- If multiple paths to the same physical disk device are available, but Microsoft Multipath I/O (MPIO) is not enabled, the device is exposed to the system by all paths that are available. This causes the same device ID data (such as Device Serial Number, Vendor ID, Product ID, and so on) to be exposed multiple times.
Last edited by rivre; 13 Oct 2016 at 11:36.
I just talked to Icy Dock tech support over the phone. He has never heard of this situation before. He will look into it on his end with other tech support members but he suggested I try to rule things out on my end by using other enclosures, try esata and USB 3, try removing my esata card to rule that out, etc., but I don't have any spare test drives to risk losing at this point and I'm sure not going to start testing with any of my important drives with data on it. He said there's a lot of possible things at play here and it's going to be tough to narrow it down. I don't even know where to start.
Would you guys advise if I should uninstall all the USB listings under device manager and let Windows find them again and install the drivers it needs? maybe that would sort the issue out? That error message suggests that Windows is getting confused by the multiple drives in the enclosures. I think that's what led to the copy failure and corruption.
Under device manager I have:
- Generic Superspeed USB Hub
- Generic USB Hub
- Generic USB Hub
- Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
- Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft)
- USB Composite Device
- USB Composite Device
- USB Root Hub (xHCI)
- USB Root Hub (xHCI)
Do I just right-click each one and select "uninstall" and reboot and let Windows take care of it? I believe if I remember correctly when I was first building my PC and doing a fresh install of Windows 10 I installed all my Gigabyte motherboard drivers from Gigabyte's site. Maybe I should let Windows find what it needs for the USB ports?
I hate to mess with them though if that's not the problem. My USB thumb drive has been working fine for months with my new PC, so it's only the external multi-bay enclosures that are having issues over USB 3/esata.
Last edited by rivre; 13 Oct 2016 at 20:36.
Unless I have a specific problem I let windows do its own thing with drivers. Usually turns out fine with my mobo.
Like I said earlier, all my USB drivers, except USB 3, are windows ones dated June 2006! The date shows a certain stability! The USB3 is a windows driver with very recent date. My SATA dvrs are same 2006 date as well.
What drivers do yours show?
I would right click each and click update driver and see what you get.
new to PCs in general. Wanted to change some setting in order to get a game running (at the end of video)- Prince Of Persia 2008 : How To Set Resolution And Fix The Loading Problem - YouTube
but when going into /C drive where the game is...
My problem in short: With Remote Desktop Connection I Get the error: “the requested session access is denied” with enhanced mode trying to login into my non-admin account on a VM. I can connect fine using non-enhanced mode.
So I am running...
So I bit the bullet and "upgraded" my laptop from Windows 7 to 10. I expected to find a few things that didn't work anymore, but not so soon as this. I keep it in sync with my desktop PC (running XP) by net-sharing its hard drive, with...
You don't have permission to access "http://steamcommunity.com/id/Fazy_aka_TaZx/home/invites/" on this server.Reference #18.b1f31502.1439008845.47ab9a03
I use steam. So basically what's happening...
Unable to delete folder, unable to change permissions, and unable to get One Drive to read to Documents folder correctly. I have attempted five times and each time it fails. So I try to delete the One Drive folder so I can reboot and try again,...