The Environment for the records:
Mac 10.13.1 (HPFS) - not converted to APFS
Win10 Pro 1709
VmWare 8.5.9
Similar issues that Office 2013 is unwilling to save a file opened on a file share using VmWare - confirmed (Office opens the file but not save)
I have observed that VmWare creates multiple .smb(xyz) instances with a hidden flag for MacOsX. MS Explorer shows them all.
What is possible?
Working all file commands on MacOSX via share - open, copy, paste, rename
Working all file commands on Win10 via share - open the file, copy the file, paste, rename
What is the Error Message looks like?
The error message returns, that there is a network or file access issue. The network share is no longer available.
What is the problem?
Office 2013 does not save the updates on the file on the share.
This error message is wrong. It happens if you try to save the file, the same one, you have opened via the file share.
What has been done?
What is the current workaround?
I'll just add for the record that Mac High Sierra is not supported with Fusion 8.5. Whether that's the cause, possibly, but you're not in a supported configuration to begin with.
I did now an update to VmWare 10.0.1. - no changes - issue still there - Big impact now. It got worse.
My file system creates evertime a new shadow ".smbdeleteAA12" and many more.
My disk space will explode.
I am dealing with hundreds photos per day, each 8MB. I must delete files and CANNOT!
I am in a critical path now.
Support Request Confirmation Number: 17635970111
update:
Downgrade Mac OS X Server 10.13.1 back to 10.12.6 - same issue
I can say that the faced problemes are bullet proofed, that VmWare + Win10 generates the issues.
Unfortunately, that article was not successful for me: