Could not probe Opengl....
This is a common complaint seen by the casual opengl user, especially with 3D printer slicer software like Ultimaker's Cura, or Flashforge's Flashprint. As a hobbiest 3D printer
person, an old VB6 officionado, and as an Arduino user, this problem is common and seems to constantly plague me and millions of other people, especially software developers!! I am not sure that I
know how this nightmare began, probably in a late nite staff meeting at Microsoft, "We need security on those drivers, see to it!" Or how it was first solved (probably in a late nite staff
meeting at Microsoft :), but here is a workaround that works for a lot of applications, Cura and Flashprint, and VB6, and probably a hundred other programs!!! Place a copy of the
appropriate 32 or 64 bit opengl32.dll driver into the file folder that contains cura.exe or flashprint.exe, etc. The newer driver is then read first instead of the windows driver, hence
superceding the older disfunctional windows driver that is so highly protected that it requires special software just to replace it. Note that replacing that old driver would be preferable but it is a pain because
you have to unseal and then reseal the security on all dll files in order to replace just that too soon antique and disfunctional opengl32.dll file (which will be in either the sys32 or the syswow windows directories depending on 32 bit or 64 bit usage.)
Here are a couple of sources. these are versions of the driver that do not depend on Your graphics card, but are based on the Mesa3D project, and can be found here.
( i.e. Fool's disclaimer: they worked for me, so I didn't look any deeper!! ) Warning, many old drivers are not to be messed with as thousands of old programs depend on them,
but in an age of touchscreens, 3D models, identity theft, and new internet protocols, many old drivers need an occasional, albeit ownership and time dependent, upgrade, a new
face... i.e. SMILE...
PS - Dear Cura supervisors,
the problem is not in your stars or with Microsoft but in your own programmers for not adequately testing and fixing your software!! Shame on you! And, note that "not my problem" attitude aside,
your programmers are WRONG and probably should be threatened appropriately for closing repair tags and trying to blame the other guy for something they could have fixed... That's my job... oops!