Windows 10: Unable to write to newly mounted drive

I have just added a second drive (1TB SSD) to my PC running Windows 10 Pro. The new drive is formatted as a single NTFS filesystem and mounted at C:\Games. I am now trying to move the former contents of G:\Games (currently renamed Games.temp) to it, but I am unable to do so; every time I try to drag the folders from C:\Games.temp to C:\Games, Windows Explorer crashes. If I look at the permissions on C:\Games it is apparently in a superposition of read-write and read-only (read-only box has a black square). No matter what I do, I cannot clear this state. I have followed the procedure of clear read-only, set read-only, apply, and read-only then shows as on, until I close and re-open the properties dialog, which then shows a black square again. I cannot set security permissions on the mountpoint C:\Games or do anything else to it whatsoever. Yet, the Steam client can and does create C:\Games\steam.dll, and I can create a folder C:\Games\test and copy files to there, but if I try to move the copied files back up to C:\Games where I need them to be, Windows Explorer crashes again.


This behavior occurs regardless of whether I create C:\Games prior to mounting the drive, or during the mount process. I've just performed a full format of the drive to see if that resolves the problem. (It didn't.) I've also just manually updated Windows from build 1803 to 1809 to see if that would resolve the problem. (It didn't.) The notification center has given me a prompt to "finish installing device software", but nothing happened when I clicked that notification and I can't figure out what "device software" it wants me to finish installing. Device manager shows both drives, and says both are working properly; it also shows the new drive's mountpoint C:\Games as a "portable device" and says that it cannot start. If I remove the "portable device" and scan for hardware changes, Windows recreates it, but insists it can't find a driver for it. I cannot even begin to guess what is going on with that.

I can create new empty folders in the root of the mounted drive (C:\Games\localdata for example). I can created files (C:\Games\test.txt) and edit them. But I absolutely cannot copy files from the old drive to the new drive. If I try to copy, by ANY means, an empty folder from C:\Games.temp on the old drive to C:\Games, Windows Explorer crashes. I can create a folder in C:\Games (for example C:\Games\test) and drag-and-drop move files from C:\Games.temp into that folder. But the moment I try to move them from C:\Games\test to C:\Games, whee, Explorer crashes again.


I am utterly baffled here. Can anyone shed any light on this problem? What am I missing? How can Windows possibly make such a simple task so difficult? What is going on with the superposition of read-only and read-write? Most importantly, how do I fix this and make this mountpoint work as it should? Or did someone at Microsoft decide that this is how mountpoints are supposed to "work"?

:)

 

Unable to write to newly mounted drive

I have just added a second drive (1TB SSD) to my PC running Windows 10 Pro. The new drive is formatted as a single NTFS filesystem and mounted at C:\Games. I am now trying to move the former contents of G:\Games (currently renamed Games.temp) to it, but
I am unable to do so; every time I try to drag the folders from C:\Games.temp to C:\Games, Windows Explorer crashes. If I look at the permissions on C:\Games it is apparently in a superposition of read-write and read-only (read-only box has a black square).
No matter what I do, I cannot clear this state. I have followed the procedure of clear read-only, set read-only, apply, and read-only then shows as on, until I close and re-open the properties dialog, which then shows a black square again. I cannot set security
permissions on the mountpoint C:\Games or do anything else to it whatsoever. Yet, the Steam client
can and does create C:\Games\steam.dll, and I can create a folder C:\Games\test and copy files to there, but if I try to move the copied files back up to C:\Games where I need them to be, Windows Explorer crashes again.

This behavior occurs regardless of whether I create C:\Games prior to mounting the drive, or during the mount process. I've just performed a full format of the drive to see if that resolves the problem. (It didn't.) I've also just manually updated Windows
from build 1803 to 1809 to see if that would resolve the problem. (It didn't.) The notification center has given me a prompt to "finish installing device software", but nothing happened when I clicked that notification and I can't figure
out what "device software" it wants me to finish installing. Device manager shows both drives, and says both are working properly; it
also shows the new drive's mountpoint C:\Games as a "portable device" and says that it cannot start. If I remove the "portable device" and scan for hardware changes, Windows recreates it, but insists it can't find a driver for it. I cannot
even begin to guess what is going on with that.

I can create new empty folders in the root of the mounted drive (C:\Games\localdata for example). I can created files (C:\Games\test.txt) and edit them. But I absolutely cannot copy files from the old drive to the new drive. If I try to copy, by ANY means,
an empty folder from C:\Games.temp on the old drive to C:\Games, Windows Explorer crashes. I can create a folder in C:\Games (for example C:\Games\test) and drag-and-drop move files from C:\Games.temp into that folder. But the moment I try to move them from
C:\Games\test to C:\Games, whee, Explorer crashes again.

I am utterly baffled here. Can anyone shed any light on this problem? What am I missing? How can Windows possibly make such a simple task so difficult? What is going on with the superposition of read-only and read-write? Most importantly, how do I fix
this and make this mountpoint work as it should? Or did someone at Microsoft decide that this is how mountpoints are
supposed to "work"?

 

Error when mounting ISO files

Hi,



Thank you for writing to Microsoft Community Forums.



I understand when you are trying to delete/rename/move the ISO files after mounting it you get an error message. It could be possible that the ISO file is mounted and that is the reason you are unable to modify it.



I suggest you to eject the ISO file and then try to modify it. Please follow the steps mentioned below:

1. Press Windows key + E, to open
   File Explorer.
   
2. Click on This PC on the left pane, you will find the mounted ISO file.
   
3. Right click on the ISO file and click on Eject. Try modifying the ISO file now.
   

Please reply with the status of the issue, we will be glad to help you further.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

How To Format A Write Protected Flash Memory ?

¿You already tried this one?...

Run CMD


1. diskpart
2. list disk

Then in the 3º step, put the correct number of disk in the list for the usb flash (if it's listed in disk 3, then you'll have to write select disk 3).

2. select disk #
3. clean
4. create partition primary
5. select partition 1
6. active
7. format fs=fat32
8. assign
9. exit

with that commands you will format the flash drive in fat32, if you have a large drive you can select also "format fs=ntfs" in step 7.

good luck!