VMware Fusion BootCamp detection not working with Windows 10 Creators Update (1703)

[greybaron]

The issue is quite obvious and already pretty clear from the title. Using the previous Windows 10 version "Anniversary Update" (1607) VMware Fusion would detect the Boot Camp partition without an issue. After clean installing the new Windows 10 with the Creators Update, it would not get detected by Fusion and only report that no Boot Camp partition was found. Reinstalling Windows 10 1703 did not change anything, only a reinstall using the older 1607 version would fix the issue.

VMware Fusion therefore probably just needs an update to be able to detect the new W10 Creators Update.

[Mikero]

Yep, this is our bug and a known issue. Expect a patch soon.

[fulles]

Any news on when we can expect this patch?

[admin]

Hi there,

We are still investigating the root cause of this issue but can you please try below workaround which has been proved to work by some other customers? Thanks.

Create a blank boot.ini file in Drive C in native Boot Camp.

[fulles]

Yes that works.  Thanks.

[realdannys1]

Why is has this gone through two updates without being patched properly. The black boot.ini helps but now you get the message that VMware thinks it's installing a "guest operating system" and to download the tools separately as it's not seeing it as Win 10 Pro.

This works fine in Parallels why are you guys having such a hard time with it?

[chrisbunnett]

This does not work for me... any other things I can try?

CB