Latest Update: Even some newly downloaded files that I path directly to the new drive either don't open or only open with some glitches or corrupted spots.
I think I purchased a bad drive here and it is a case of my own stupidity. It was on a bit of a sale but the price was high enough that I didn't think it would be an issue, but I believe I have made a dumb purchase this time around.
Update to include some additional information:
The laptop helping to connect the external drives to talk to each other is an old ASUS X556UAK model from 2017.
Version 10.0.19045 Build 19045
Intel i5-7200U CPU @ 2.50 GHz and 8GB memory
It's running Windows 10 Home
The old external drive (where all the files work as intended) is a Western Digital passport. I believe it is 07A8 as this is what its properties tells me and images seem to reflect this when I search for it.
The new thumb drive is Wasisen which, admittedly, I have not heard of and perhaps I got a bad brand here.
Additional info I noticed that may be helpful:
Even among the files that transferred "successfully" to the thumb drive from the passport, not all of those files will open or activate. The ones that do will show the same thumbnail that the files on the passport drive show. The ones that don't just show generic application thumbnails associated with the files.
Upon unplugging and replugging the new thumb drive, Windows detects errors. I allow it to repair the drive, which it does. This does not cause the problematic files that did transfer to activate. However, if I move/replace some of those files again, this time they will open fine as they would have if they had been copied successfully the first time. This doesn't apply to the files it simply refuses to take, but it does replace the "unusable" ones it copied over with successful versions now that Windows repaired the errors. The drive had errors yesterday too, but I didn't try to recopy files that wouldn't open then as I did today.
Perhaps the new drive (the USB thumb drive) is bad, although it is transfering some but not all data. I can try to put some of this data on another WD passport that I have and see if it goes over without issues. I don't have an independent hub to try this without using the computer as an interface, but I did use a USB cable to transfer files to the tablet in the past, so perhaps I'll just have to stick with that method.
End update
Hi everyone,
I recently purchased a 1tb USB C thumb drive to make it easier to move some content from my laptop to my tablet. This mostly works fine, but there are some files that are getting the above error message. The computer claims that it cannot read the file from the source disk. In this case it is a separate external hard drive. It's one of the "0x" error messages but I don't recall the full one just now. I'm writing because it has given me the same error today as I am currently trying to copy the files again for a second time. The message will probably pop up again soon because the problem appears to be specific files.
Out of about 1,300 small-ish files, around 100 or so had this problem yesterday, When I got the drive, it was exFAT, which I did not change. The other drive is NTFS. I thought perhaps this could be the issue, so I reformatted the new thumb drive to be NTFS as well. Sadly, today it runs into the same problem with the same files regardless. I thought it would be corrupted file data, which would make sense.
However, the files open/display/play without any problems or glitches. The files work, so I am not sure if it could be corruption. The computer lists no errors in the drive that it needs to fix when I scan it. Although, this doesn't necessarily mean the drive is not somehow damaged, I suppose. The drive on which the data exists now is several years old.
I've tried to rework the permissions on the files as some posts on the internet said that might help, but to no avail. The files are not hidden or blocked. I thought perhaps the new drive was the issue, but these problematic files typically can't be copied to a different location (like somewhere in C drive) or deleted either--although perhaps I could do this on a fresh restart of the system, I've not yet tried.
The problem persists if I boot in safe mode and try it that way as well. This has happened with a few much newer files (from the past few days or so) as well, but I can't figure out what might be the cause. I thought it was just somewhat old files that might have some corruption despite seeming to work fine. What the system can or cannot copy over seems to be random, at least to an average user like myself. When the drive reaches the point where it gives me the exact error message number I will update this in case that might be relevant.
I guess I could just leave the small number of files on the old drive, but I was hoping to copy full folders and remove that data. Since it can also happen with newer files, I'm not sure that's a great solution anyway.
Thank you for reading, and I'd very much appreciate any suggestions.
I think I purchased a bad drive here and it is a case of my own stupidity. It was on a bit of a sale but the price was high enough that I didn't think it would be an issue, but I believe I have made a dumb purchase this time around.
Update to include some additional information:
The laptop helping to connect the external drives to talk to each other is an old ASUS X556UAK model from 2017.
Version 10.0.19045 Build 19045
Intel i5-7200U CPU @ 2.50 GHz and 8GB memory
It's running Windows 10 Home
The old external drive (where all the files work as intended) is a Western Digital passport. I believe it is 07A8 as this is what its properties tells me and images seem to reflect this when I search for it.
The new thumb drive is Wasisen which, admittedly, I have not heard of and perhaps I got a bad brand here.
Additional info I noticed that may be helpful:
Even among the files that transferred "successfully" to the thumb drive from the passport, not all of those files will open or activate. The ones that do will show the same thumbnail that the files on the passport drive show. The ones that don't just show generic application thumbnails associated with the files.
Upon unplugging and replugging the new thumb drive, Windows detects errors. I allow it to repair the drive, which it does. This does not cause the problematic files that did transfer to activate. However, if I move/replace some of those files again, this time they will open fine as they would have if they had been copied successfully the first time. This doesn't apply to the files it simply refuses to take, but it does replace the "unusable" ones it copied over with successful versions now that Windows repaired the errors. The drive had errors yesterday too, but I didn't try to recopy files that wouldn't open then as I did today.
Perhaps the new drive (the USB thumb drive) is bad, although it is transfering some but not all data. I can try to put some of this data on another WD passport that I have and see if it goes over without issues. I don't have an independent hub to try this without using the computer as an interface, but I did use a USB cable to transfer files to the tablet in the past, so perhaps I'll just have to stick with that method.
End update
Hi everyone,
I recently purchased a 1tb USB C thumb drive to make it easier to move some content from my laptop to my tablet. This mostly works fine, but there are some files that are getting the above error message. The computer claims that it cannot read the file from the source disk. In this case it is a separate external hard drive. It's one of the "0x" error messages but I don't recall the full one just now. I'm writing because it has given me the same error today as I am currently trying to copy the files again for a second time. The message will probably pop up again soon because the problem appears to be specific files.
Out of about 1,300 small-ish files, around 100 or so had this problem yesterday, When I got the drive, it was exFAT, which I did not change. The other drive is NTFS. I thought perhaps this could be the issue, so I reformatted the new thumb drive to be NTFS as well. Sadly, today it runs into the same problem with the same files regardless. I thought it would be corrupted file data, which would make sense.
However, the files open/display/play without any problems or glitches. The files work, so I am not sure if it could be corruption. The computer lists no errors in the drive that it needs to fix when I scan it. Although, this doesn't necessarily mean the drive is not somehow damaged, I suppose. The drive on which the data exists now is several years old.
I've tried to rework the permissions on the files as some posts on the internet said that might help, but to no avail. The files are not hidden or blocked. I thought perhaps the new drive was the issue, but these problematic files typically can't be copied to a different location (like somewhere in C drive) or deleted either--although perhaps I could do this on a fresh restart of the system, I've not yet tried.
The problem persists if I boot in safe mode and try it that way as well. This has happened with a few much newer files (from the past few days or so) as well, but I can't figure out what might be the cause. I thought it was just somewhat old files that might have some corruption despite seeming to work fine. What the system can or cannot copy over seems to be random, at least to an average user like myself. When the drive reaches the point where it gives me the exact error message number I will update this in case that might be relevant.
I guess I could just leave the small number of files on the old drive, but I was hoping to copy full folders and remove that data. Since it can also happen with newer files, I'm not sure that's a great solution anyway.
Thank you for reading, and I'd very much appreciate any suggestions.
Last edited:
Facebook
Twitter
Instagram