We posted a thread in the forum here https://communities.intel.com/thread/97541, however we didn't get any response. I guess the thread actually belongs here, since it is kind of technical. I hope we may get in touch with a engineer, that may help us track what appears to be a bug in Intel HD Graphics 3000 and 4000 driver.
Several users have reported problems with Intel HD Graphics 3000 and 4000 series, when using our software. They have in common, that the OpenGL renderer that we find is the GDI generic (OpenGL core v. 1.1) renderer, even though glview says there exist an Intel renderer (OpenGL core v. 3.2).
We haven't had similar problems with other vendors or versions. So we have made some tests to troubleshoot the underlying issue. We have tried a bunch of both simple but also far fetched things, based on the fact that there are reports of weird behavior in this graphic series (OpenGL Discussion and Help Forums). However we haven't found the issue yet. All our tests have supposedly worked well on our users failing computers (GL context have reported right renderer and version). Some of these tests have bootstrapped OpenGL and the window as close to our software as you may get it, however with the only major difference that everything were bootstrapped from one assembly(exe). In contrast to our software, where our main application calls into a dynamic library, that calls in to a second dynamic library which bootstraps a Windows Form with a GL context within it. We don't know if it is related to where things are bootstrapped(e.g in a dll), however we feel we have tried everything with no success. So we would really appreciate some technical insight about cases that may trigger your driver to fallback to the software driver included in Windows.
Also should be noted that the users that have reported the issue so far, are using Windows 10.