| 1 | | JLB, you are completely right. I tested this once again, meanwhile on the current 1803 Windows 10 guest and host with the same results. Then I looked into the copied folder (a portable apps installation folder) and saw an “.nomedia” file here. As soon as this file was deleted and after reboot of the guest a could copy the folder from guest to the host without any problems. Afterwards it wasn’t a problem to copy this folder back. So all of this hidden Linux files and folders with period in the front of the name causes right now file operation problems in the Windows guests. |
| | 1 | JLB, you are completely right. I tested this once again, meanwhile on the current 1803 Windows 10 guest and host with the same results. Then I looked into the copied folder (a portable apps installation folder) and saw an “.nomedia” file here. As soon as this file was deleted and after reboot of the guest a could copy the folder from guest to the host without any problems. Afterwards it wasn’t a problem to copy this folder back. So all of this hidden Linux files and folders with period in the front of the name causes right now file operation problems in the Windows guests. |
| | 2 | |
| | 3 | In my case the whole shared folder subsystem stays in the error state till the next reboot afterwards. So no file operations with shared folders could be executed til the guest reboot, even the ones without period files and folders in it. |
