Fusion 10.0.1 & Windows 10 Fall Creators Update

[jrschoenberger]

I installed the Windows 10 Fall Creators Update on a VM running under Fusion 10.0.1 and High Sierra 10.13 on a MacBook Pro (Retina, 13-inch, Early 2015) with Intel Iris Graphics 6100 1536 MB. Since then I've experienced two problems:

1) When attempting to save files from MS Word 2016 for Windows to folder shared between the Windows VM and the Mac (such as the Mac desktop), I get the following error message: "There has been a network or file permission error. The network connection may be lost." I've attached a screenshot. This error is new since the Fall Creators Update. The file appears to save despite the error message. I have no problem copying files natively between Mac and Windows from the Windows File Explorer.

2) The second issue I'm having since the Fall Creators Update is that switching between windowed and full screen mode causes terribly unusable graphic distortion of the Windows' display upon returning from full screen to windowed mode. Graphics work fine in full screen mode. If I start the VM in windowed mode and keep it there, the graphics are fine. But, any change between the two leaves windowed mode FUBAR until I restart the guest operating system.

I have tried reinstalling VMware tools in the hope that it would solve both problems. It did not fix either.

I would appreciate any advice.

Thanks!

[Arcadius1]

The claim is that it takes a while to receive certification from Microsoft for updates. It looks like it took VMWare a couple of months even to acknowledge the issue even existed. It has been a very frustrating experience from what should be an industry leader. There is competition in this space, like Parallels, for example, which does not appear to have this issue. Trouble is, we've all dumped money into Fusion and are still awaiting a fix for what should have been an issue they identified early in the game.

[alphasupremicus]

Glad to know it just wasn't me. Everyone in the office was thinking I was a bozo for not saving. I WAS SAVING but the dang tool (Visio) wasn't complaining and was saving a zero byte file each time I hit save. Really bad!

[sfjogger]

It seems strange that this problem has persisted since late October and there is still no update from VMWare? Anyone know when they will figure this out? Reinstalling Tools doesn't help.

[cdrv]

Not to be snide, but VMware appears to be less concerned about the future of their virtualization products:

VMware axes Fusion and Workstation US devs • The Register​

So now might be a good time to evaluate alternatives to Fusion and move elsewhere.

[nes888]

I have been keeping track the "progress" of this blog hoping for some good news.

I myself have had the same issue ever since the Windows 10 Fall Creators Update was released, and had applied it to one of my Fusion 8.5.8 VMs to this latest Windows 10.  I had tried with different version of VMWare tools, updated to the latest Fusion 8.5.9, latest Office 2016 with no results.  I have posted about this issue on the Microsoft site and never got any satisfactory response.  There was some "hope" when Steven Goddard and another VMware employee blog mentioned that the issue is with the VMWare tools and that the resolution is with the next VMware tools.  It is disappointing for another blogger to mention that it will not be fixed in Fusion 8.5.x..

What is more disappointing as I agree with another previous post here that VMWare is a partner of Microsoft.  Changes to the Falls Creator that broke and introduced this issue in the tools would have had been incorporated in Falls Creator Update for a long time.  VMWare developers would have had this (Falls Creator alpha->beta->release) in their hands for further development and testing so it is somehow beyond belief that this basic function (of opening a file on the Shared Folders, updating the file and saving the file) is not part of the rigorous regression testing.

It is also disappointing that this issue is also in VMWare Fusion 10 as reported by others.  I wonder if VMWare still do QA on their product !!!

I read about another blog referencing layoffs.  This is past news (dated January 2016), so I don't think this is the case.  Although anyone would think this could be a consequence!.

I could suggest anyone who have this issue to post on VMWare's facebook and other social media site to query the progress on this issue.

[PeterSinclair]

I've just installed VirtualBox 5.2.2 (and VB guest additions) on my MacBook Pro and installed 64-bit Windows 10 Pro ver 1709 and Office 2016. Excel and Word now work fine, happily saving files to my Mac filesystem.

VirtualBox is from Oracle but is open source and distributed under GPL v2.

[Scott9191]

Does anyone know the phone number to call VMWare about this issue?  I would be happy to call to try to get some resolution.  The waiting period for help on this is really getting ridiculous at this point. 

[VirtualAwarenes]

The workaround is basically to create a shared folder for each folder you save files to.  VMware will walk you through the procedure.  Cust Svcs. #: 1 (877) 486-9273.  What astounds me is they won't commit to a release date for the 10.0.2 patch and come on to this thread to announce it.

[Arcadius1]

Problem is, that workaround doesn't actually work. There have been a few on this thread that have tried it, myself included. I'm very disappointed in VMWare. Since I'm basically stuck waiting for this patch that every other VM platform seems to already have (as all of us are), I will spend my time blasting them on the web and hoping some folks decide not to buy this product in the future.

[riccoho]

Now I realized why Parallels can charge Mac users on every machine every year. Their support is much more efficient.

[VirtualAwarenes]

Hmm, workaround didn't work for you, eh?  Wish I captured all the steps so I could share, but I didn't.  All I can say is: I'm running 8.5.9, I called up VMWare support, they ran me through the procedure.  it worked for me with the caveat being you must edit/save files from the shared folders you just created:

Anyway, this whole deal still sucks regardless of whether this workaround works or not.

[HackerKitty]

I am a former Paralles user.

Indeed their product is slightly nicer.

If I give 100 points to Paralles, Fusion will score 95 for userinterface and functionality.

But Paralles has a major drawback.

While VMware is a cross platform, Paralles runs only on Mac.

For majority of the people, it sould not present any problem, but I also use Linux machine.

Fusion cretaed VMs will run without any modification under WMware Worstation under Linux.

[aluisiof]

Steve and VM Guys,

Still no patch? WTF?!

How unprofessional is this????

This is a critical BUG! It should have been addressed in hours... its been SEVERAL weeks!

Come on guys. what the hell you doing? Take your fingers out of your ass and get this done. Enough already.

[gevli]

Maybe off topic: but I have got exactly the same error when saving MS Word 2016 documents since the Windows 10 Fall Creaters Update. Instead I am using Windows 10 as main OS and Windows 10 virtual images (with MS Word) with VmWare player 14 and latest VmWare tools installed. This is probably the same issue I guess?

[Arcadius1]

Very interesting. Since VMWare tools is installed inside the VM, it makes sense, too. Both on Fusion and VMWare Player, the VMs were running Windows 10 CU, and I'm guessing that the version of Tools would be similar. I agree what was said previously about this being a critical defect, and it certainly shows the poor QA performed on VMWare products, as of late.

[Benjamin1Carrol]

I found a fix that worked for me in Windows 10 Enterprise 1709 on a MacBook Pro (15 inch-2017) running High Sierra 10.13.1.

1. I went to to the "File Explorer" in the "Windows System Folder".

2. I selected "This PC" from the left navigation menu.

3. I right clicked on "Documents".

4. I selected the "Sharing" tab.

5. I selected "Share" button.

6. I selected my user name.

7. I selected the "Share" button.

8. Done.

This allowed me to save and share Office files to the Documents folder and access it in Office on both the Windows and Mac sides of my computer.  I hope this helps.

[HeiderSati]

Hi All, I created a new case with Fusion support, I have some more information to share on the nature of the problem:

Dear Support

For the past 3 days I have been unable to edit any document created with Microsoft Office on my MAC when MyDocument is shared (i.e. stored on Network Location, provided by the VmWare Share)

I can open the document fine, but when saving I receive the following error:

There has been a Network or or file permission error. The network connection may be lost.

I also tried to debug the issue, and can see that when saving, I get the following:

FileSystemsIOControl - INVALID DEVICE REQUEST - Caused by: IOCTL_LMR_DISABLE_LOCAL_BUFFERING

QuerySecurityFile - INVALID DEVICE REQUEST - Caused by: DACL

SetSecurityFile - INVALID DEVICE REQUEST - Caused by: DACL

FileSystemControl - INVALID DEVICE REQUEST - Caused by: FSCTL_DELETE_OBJECT_ID, FSCTL_GET_OBJECT_ID

FileSystemControl - INVALID DEVICE REQUEST - Caused by: FSCTL_WRITE_USN_CLOSE_RECORD

These implementations are new, probably Microsoft Updates again trying to WoW us... again,..!.

It's not a pleasant issue as I can no longer save any existing document any more, this only started occurring 3 days ago and I'm not sure what's behind this.

I checked with Microsoft Support but they are now referring me to you as it seems to be a VMFusion problem.

I would appreciate if you could please let me know how to fix this

Kind Regards

Heider

[openmic62]

HeiderSati​, VMWare has had a fix for 36 days. but they won't give it to us. Read back a few replies to see how pissed off people are about this.

[HeiderSati]

I think if everyone creates a support case against this bug then they would escalate this.

I was happy until 3 days ago, before clicking "Go Ahead" to Windows Update...

But, for all, if you can, please create a case against VM support, this will put more pressure and get this done quicker.

I'm trying to help everybody including myself!

Kind Regards

Heider

[neilt17]

I can't actually see a way of contacting VMWare about this issue. I just wanted to ask them which course of action I should take:

Purchase an upgrade from VMWare version 8 to version 10 (other posts suggests this doesn't solve the issue);

Revert Windows Creators update and wait for a new version of VMWare tools;

Use another virtualisation product.