The story so far... (OS X 10.10.5, MBAir MId 2003 13", 8GB Ram, 500GB SSD, Parallels 11 Desktop PRO) Bootcamp failed to create partitions that Windows 10 setup was able to convert to NTFS and use to install Windows 10. After lots of jiggery pokery (including two 350GB OS X Time machine restores) I repartitioned the drive into 400 OSX and 100GB (exFAT), Bootcamp, using disk utility because the Bootcamp partitions were not being usable by the Windows Setup process. Prepped a Windows USB installer disk with Win 10 on it, and got it finally be able to install windows 10 onto my 100GB partition, ie it was finally able to convert the ExFAT partition into a suitable NTFS partition during Windows setup, where Windows 10 Windows Setup had failed many times before. Installed a game, 32 GB worth of download etc. Played the game a bit (1-2 hours) machine seemed solid. Numerous reboots back and forth no drama. Bought and installed Parallels 11 (Windows 10 compatible!) Created a VM, pointed at Bootcamp, VM failed to first boot (boot disk not found), tried PXE etc, repeat fails. Thought F*ck it, I'll just native boot. But Native booting now has the same error message, the Win 10 partition will not startup, despite showing in the OS X Startup Disk Preferences. I no longer see the Windows Boot partition in the Option key process when booting from the off state however. In OS X I can see the files (ie still read the NTFS volume), including the temp folder with Parallels tools in it (so it could write). Does Parallels muck around with the EFI booting in some fashion? I have 370 days of phone and email support, however there is no phone number listed in MY ACCOUNT for me to be able to make use of this - WTF? I'm supposed to be working, yet have wasted 2 hrs trying to get this VM sorted, less than impressed. Please advise.
