Hi all,
For context, my current Fusion VM has the following specs:
My VM Microsoft Windows 10, for this update, is going from "Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4041676)" to "Version 1709".
It was about a ~2GB download/update.
After the VM restarted several times to update the MS Win10 OS (which to me means it was a big update), I found that my VM no longer allows me to write any type of file to the Fusion Mac Host. For example: my files are saved on the Mac OS desktop (for my own reasons) so the VM accesses those files like they normally did using the Shared Folders setting. For the record, my VM always successfully wrote to the Fusion Mac Host.
So, example, when I open a Microsoft Excel spreadsheet that is stored on the Host Mac desktop, I edit it, when I try to save it says something like "cannot save". When I try it with MS Word, the error is different in that it says something like "connection to the remote folder was lost, please check your network file share connection".
I haven't taken the time to "Uninstall" the update to see if it will revert back, I basically blow away the VM instance and restore from a backup VM running Version 1703.
Thoughts?
This appears to be the same problem as the one listed here:
Fusion 10.0.1 & Windows 10 Fall Creators Update
Please note that there are a few work around's available. It is specific to Windows 10 Fall Creators update (1709) combined with Microsoft Office file-saves. Engineering is working on a patch / new release to resolve this issue.
We just checked in the fix, so expect it to be in the next update assuming everything goes ok in QA.
Sweet, keep us informed. I just started out with VMWare, but I'm having to go back to Parallels until this is fixed.
-Peter
Any word on the date for release of this? It seems like too critical an issue for us to "have to wait for QA for the next release". When are we going to see this released?
Hi,
There's a new VMware Tools out that has this fixed.
and the readme has this bit under "resolved issues"
This issue is resolved in this release
Eventually that VMware Tools will make it into a VMware Fusion release.
If OTOH you don't want to wait, you can install the update from the link above.
--
Wil
Confirmed that this works. (at long last!)