I think I've discovered what the source of the problem. Since VirtualBox 4.2.0, the VBoxGuestAdditions install a new graphic driver for Windows 8, VBoxVideoW8. The old WDDM driver's INF file for Vista and W7 (VBoxVideoWddm) contained in the registry keys for OpenGL ICD, but in the new INF file that are missing. After adding the registry keys manually to the file (new file VBoxVideoW8OGL.inf attached) everything works fine.

I then had to disable driver enforcement through advanced start-up options. Finally under Device Manager I told it to update the driver and went though the steps that let me choose "Have Disk" and picked the modified .inf file. After rebooting the OpenGL extension program now shows 2.1 with a vendor of Chromium or something strange like that.

The final step will be to try running MakerBot Desktop when I get a chance tonight and see if it still crashes.

I just wanted to provide an update that even though OpenGL diagnostic tools show OpenGL 2.2 it did not make a difference with MakerBot Desktop and in fact it won't start at all with 3D acceleration enabled. Bummer.

Another way to add OpenGL support without disabling disable driver signature enforcement. Use the respective attached .reg files to add OpenGL to W8 and W10 VirtualBox guests. It works after reboot. VirtualBox Guest Additions must be installed before.

Walked through the process given by entalpia2. Sadly, it didn't work.
Before I did anything, I could start programs without any issue, but then would encounter fatal errors when trying to render 3D data.

After trying the steps above (like 20 times in 20 different ways, using the registry patch alone, using the driver patch alone, together, separate and so forth) it is clear that this hack doesn't work on my system either.

Now when I start the software, it pops an error that says my system has OpenGL1.1
If I check in AIDA64, it is clearly showing 2.1 support.

So I've gone from bad to worse, because now the software won't even load...

It just seems like a registry issue to me, as the software just checks the registry for compatibility and if it isn't found, it pops the error and shuts down.