Fusion share is read/write but the Windows 10 Folder properties is always Read-Only

[leisurehound1]

I have VMWare Fusion 12.2.5 and a guest Windows 10 on macOS 12.2.6 host where I've created a share in Fusion and specifically made the share read/write.

I can drag and drop files in Windows file explorer between the guest and the share on the host without issue.  However, when look shared folder properties from the guest the Attributes - Read Only is checked.  When I uncheck and apply that change, there is a progress bar of applying those changes.  Note that on the host side, the permissions of the folder is Everyone -> Read/Write.  

When I open the Shared Folder properties again (in Windows Explorer) the 'Attributes - Read Only' is once again checked.  

This is not so much of a problem when dragging a dropping, but when using Aoemi Backupper to create a real-time sync between guest and host, its repeatedly complaining about not having write permissions.  I believe Aoemi runs as an admin service and not as the Guest user.  

Is there another setting to allow other users write to a share from the guest to the host?

[Technogeezer]

If you've set permissions on the host folder appropriately and set the shared folder to be read-write in the Fusion folder sharing property of the VM, there's not much else you can do to get rid of that read-only attribute in the VM. That appears to be a function of the VMware hgfs folder sharing driver.

However, if Explorer is working fine, what other error message is your AOEMI Backupper displaying? What file is it complaining about being read-only. 

You might want to bounce this by the AOEMI developers to find out why they're complaining about this when Explorer isn't.

There are instances where VMware (Fusion and Workstation) folder shares don't behave exactly like Windows/SMB file shares or NTFS file systems. There are some applications that have had issues with the VMware shared folders (some of the MS Office applications come to mind). Perhaps that's part of the issue too.

Have you tried configuring your destination folder using macOS File Sharing (making sure you enable Windows file sharing) and mounting the folder in the VM through Windows network file sharing (using the IP address of the Mac). 

[leisurehound1]

Thanks.  I was able to create the same from macOS System Preferences Share, enabling SMB and enabling the user account (which apparently stores the password less securely). Was able to use the Mac name instead of IP since I'm often on DHCP on various networks.

AOEMI Backupper did challenge me for the user name/password even tho in macOS 'everyone' was set for drop box, but it would not allow me to connect anonymously.  Not sure its the ideal solution security wise but should be ok.  

Thanks for your helpful response.

[RDPetruska]

I'm pretty sure "everyone" does not include anonymous logon... but only any/every userid which is created.  Anonymous logon requires"guest" IIRC.

[Technogeezer]

---

@RDPetruska wrote:

I'm pretty sure "everyone" does not include anonymous logon... but only any/every userid which is created.  Anonymous logon requires"guest" IIRC.

---

That's right. macOS does require a user credential for connection to the share. The "Guest" user must be enabled in macOS in order to log in anonymously. That's a security risk so it's advisable not to enable the guest user and to use an identified credential instead.