- Jan 29, 2005
- 5,201
- 214
- 106
Hey guys.
So I'll try to make this relatively short and concise.
1) Running Windows 11, updated.
2) Got a new SSD drive, M.2 WD Black 850, works well, checked for errors, all is green, nothing wrong (newly formatted, recognized in Windows).
3) Now trying to Cut / Paste various files that are located on my C drive, to my new M.2 drive.
4) The files I'm trying to move over are not Windows / Operating System files. They are, instead, Games-related, such as my Steam folder, and other folders containing games.
5) The files are not located inside Program Files, or Program Files (x86). They are, instead, located in a separate folder I simply named "Games". That folder, however, is located on the C drive path (regular path, just C:\Games\).
6) Of course, both the C drive and my new M.2 drive are formatted with NTFS (in case it's important).
Now here is what's going on:
A) Taking my Steam folder as an example (and considering I followed the instructions on the Steam site when it comes to transferring the games to a new drive, deleting most files except the Steamapps / Userdata and Steam.exe files, etc), when I Cut and Pasted the whole thing to my new drive, it started to move over a bunch of files... but at some point the operation was interrupted and stopped with a "Can't read from source file or disk" pop-up screen. From there, I could at least ignore the problem for the files that were 'affected', and with the checkbox to apply that for all the operation; which I did (not much of a choice).
When I did that, Steam was closed (obviously), so that the application wasn't using any game files, and Steam services were stopped as well (just to be sure). Now, MOST files did actually move over to my new drive, but about 40'ish GB worth of files from various games were ignored and remained on the source (C) drive (as expected after I selected to ignore the situation for the impacted files).
B) Without trying to do much from that point I was curious enough and tried to Cut and Paste another games folder (not Steam), to a new drive, to see if the issue might be just about some Steam games. Nope, it turns out the same problem also happened with SOME files contained within specific games folders that were not moved over (with the same pop-up window), for instance Battle.net games (which are inside their own respective folders) such as Diablo 2, Heroes of the Storm or Overwatch, etc (I.E. MOST files from those games were moved over, but some files were left behind, so to speak).
What I tried next...
Alright so at this point, I did the basics, which were the following steps:
1) Restarted the PC, still no go after I simply did that, same issue (those files that were left behind, still refuse to move over after the restart).
2) I thought ok... maybe restart in Safe Mode, instead; where most services / apps that might be using folders and/or files are not running. Again, no go even if I try to Cut / Paste in Safe Mode.
3) Went back in 'normal' Mode. I then right-clicked on the Steam folder (the main one, not the individual games folders) and un-checked "Read Only" in the Properties, AND additionally went to the Security tab and made sure "Full Control" was checked (it wasn't initially). I did that for the Steam folder and all other games I tried to move over. The result - surprisingly - is the exact same. Still no go, those damn files remove to budge one atom of binary space.
4) Then I read somewhere (Google search) that maybe simply adding the 'stuck' files to a .RAR / .ZIP archive and moving that archive over to the new drive would work... NOPE... didn't. It cannot even create the archive because the files cannot apparently be accessed.
5) OK... I thought alright, maybe my still-pretty-new Samsung SATA SSD C drive has faulty sectors / or other types of drive errors... so let's perform a Check Disk on the drive... guess what? NO ERRORS found, all green.
At this point, all I can think of as of this typing is quite simply WTF.
So, any recommendations?
Side note: It's not like I ever encountered actual issues either while playing those games in the first place; by that I mean everything from starting up those games, to playing them, was fine. If it had been actual Disk errors, something wrong would have happened when specifically running games that would have been located on a faulty sector. Such as games not actually starting up, or at some point a map wouldn't load, or some kind of error would have occurred during gameplay. But THAT never happened. Which is why I do 'agree' with the Check Disk's result, it tells me the drive is all good and dandy and works well... and yeah, I concur, it does work well. So why are those files 'stuck' on C?
If you feel like playing Investigation 101 on this issue with me please do feel free to, I'd appreciate.
Thanks.
So I'll try to make this relatively short and concise.
1) Running Windows 11, updated.
2) Got a new SSD drive, M.2 WD Black 850, works well, checked for errors, all is green, nothing wrong (newly formatted, recognized in Windows).
3) Now trying to Cut / Paste various files that are located on my C drive, to my new M.2 drive.
4) The files I'm trying to move over are not Windows / Operating System files. They are, instead, Games-related, such as my Steam folder, and other folders containing games.
5) The files are not located inside Program Files, or Program Files (x86). They are, instead, located in a separate folder I simply named "Games". That folder, however, is located on the C drive path (regular path, just C:\Games\).
6) Of course, both the C drive and my new M.2 drive are formatted with NTFS (in case it's important).
Now here is what's going on:
A) Taking my Steam folder as an example (and considering I followed the instructions on the Steam site when it comes to transferring the games to a new drive, deleting most files except the Steamapps / Userdata and Steam.exe files, etc), when I Cut and Pasted the whole thing to my new drive, it started to move over a bunch of files... but at some point the operation was interrupted and stopped with a "Can't read from source file or disk" pop-up screen. From there, I could at least ignore the problem for the files that were 'affected', and with the checkbox to apply that for all the operation; which I did (not much of a choice).
When I did that, Steam was closed (obviously), so that the application wasn't using any game files, and Steam services were stopped as well (just to be sure). Now, MOST files did actually move over to my new drive, but about 40'ish GB worth of files from various games were ignored and remained on the source (C) drive (as expected after I selected to ignore the situation for the impacted files).
B) Without trying to do much from that point I was curious enough and tried to Cut and Paste another games folder (not Steam), to a new drive, to see if the issue might be just about some Steam games. Nope, it turns out the same problem also happened with SOME files contained within specific games folders that were not moved over (with the same pop-up window), for instance Battle.net games (which are inside their own respective folders) such as Diablo 2, Heroes of the Storm or Overwatch, etc (I.E. MOST files from those games were moved over, but some files were left behind, so to speak).
What I tried next...
Alright so at this point, I did the basics, which were the following steps:
1) Restarted the PC, still no go after I simply did that, same issue (those files that were left behind, still refuse to move over after the restart).
2) I thought ok... maybe restart in Safe Mode, instead; where most services / apps that might be using folders and/or files are not running. Again, no go even if I try to Cut / Paste in Safe Mode.
3) Went back in 'normal' Mode. I then right-clicked on the Steam folder (the main one, not the individual games folders) and un-checked "Read Only" in the Properties, AND additionally went to the Security tab and made sure "Full Control" was checked (it wasn't initially). I did that for the Steam folder and all other games I tried to move over. The result - surprisingly - is the exact same. Still no go, those damn files remove to budge one atom of binary space.
4) Then I read somewhere (Google search) that maybe simply adding the 'stuck' files to a .RAR / .ZIP archive and moving that archive over to the new drive would work... NOPE... didn't. It cannot even create the archive because the files cannot apparently be accessed.
5) OK... I thought alright, maybe my still-pretty-new Samsung SATA SSD C drive has faulty sectors / or other types of drive errors... so let's perform a Check Disk on the drive... guess what? NO ERRORS found, all green.
At this point, all I can think of as of this typing is quite simply WTF.
So, any recommendations?
Side note: It's not like I ever encountered actual issues either while playing those games in the first place; by that I mean everything from starting up those games, to playing them, was fine. If it had been actual Disk errors, something wrong would have happened when specifically running games that would have been located on a faulty sector. Such as games not actually starting up, or at some point a map wouldn't load, or some kind of error would have occurred during gameplay. But THAT never happened. Which is why I do 'agree' with the Check Disk's result, it tells me the drive is all good and dandy and works well... and yeah, I concur, it does work well. So why are those files 'stuck' on C?
If you feel like playing Investigation 101 on this issue with me please do feel free to, I'd appreciate.
Thanks.
Facebook
Twitter