![]() ![]() Outside of doing that, the changes made seemed to stick permanently.Im hoping that "unlocker" will be able to delete these corrupted files next reboot and then everything will work right.just have to wait for another program to finish running before rebooting. I'm trying to use an Ubuntu 16.04LTS client to do partitioning, cloning, and other related things on disks. I still got the same behavior but ONLY when I tried to modify delete one of the ~15 corrupt files on the card. The operation on file \\.\PhysicalDrive1 failed I'm running VMware Workstation Player 15 on a Win7 host. I think I might have fixed it though by adding a registry key that tells windows to disable/ignore write protection. However, within a few minutes the change would dissapear and the original files would return. In case you (or anyone else) is interested, the code is here.Īs far as write access - Windows thought it had write access, and and write operation appeared to be successful. ![]() ![]() bashrc file, so hopefully this will automatically mount things like this for me in the future. I ended up actually writing a function to automatically attempt to mount any drives that were assigned a drive letter in windows but were missing from WSL (i.e., not in /mnt/*), and then attempt to automatically mount them using the way you describe in your reply.
0 Comments
Leave a Reply. |