One thing that I find annoying is the Home edition not supporting Remote Desktop which I use to access a headless Windows 10 WAMP server (a Mac mini). I must say Windows 10 is very nice and simple to use after decades of hating Windows with a passion I actually enjoy using it, albeit only on a Mac and my Mac Pro cylinder runs Steam and the likes of GTA V very well indeed.
The easiest by far was a new Mac Pro cylinder which literally did everything unattended up to where the Windows welcome screen takes over. All good fun but not one Mac I used was the same procedure. This I cured by actually removing the partition Boot Camp had created using Terminal and allowing Windows to see a area of 'free space' which it then formatted correctly and went well after that. Each Mac seems to have different methodologies and some such as my Mac mini 2012 failed at the last stage due to an EFI issue according to the Windows installation setup. trying to run SSE2 code on Pentium 1 will cause instant crash). If you will use code which is not checking whether CPU has some feature from more modern CPUs, it'll cause instant crash (e.g.
I've added Boot Camp and Windows 10 to a whole bunch of Macs ranging in age I would add that a MacBook Pro 2010 cannot use an iso insisting on using an optical disk. Use Windows dxdiag to check what CPU is installed physically, and use MacOS X equivalent for the same, compare whether VirtualBox is not detected wrong CPU.
