Hi Bernd,
The workaround that you've found, that is, running a second instance of the PixInsight core executable, is really weird to say the least. Needless to say, I have absolutely no idea why this is happening. However, if that works for you and solves the issues you are experiencing, then I am glad to know and have nothing else to say. As I have said many times, problematic graphics drivers may cause really odd problems, which in occasions may appear like magic. This looks like one of these cases.
According to Intel, HD Graphics 3000 supports Open GL 3.1. Please tell me whether Open GL 3.1 is sufficient for PI or not.
OpenGL 3.1 should be sufficient for PixInsight 1.8.6 (although any decent graphics driver should be providing OpenGL 4.0 at the very least today). The problem is not with the OpenGL version supported, but with the OpenGL implementation. In the case of Intel HD graphics drivers on Windows, these implementations are often defective. This happens frequently on Windows 7—which we no longer support as one of our mainstream platforms—, and rarely on Windows 10 with the latest driver versions. Of course, none of these problems exist on Linux and macOS, where OpenGL implementations are correct and up-to-date in virtually all cases.
Unfortunately, PixInsight 1.8.6
requires a working, fully standards compliant and fully operative OpenGL implementation (in theory, OpenGL 2.1 should be enough, although version 3 or higher is recommended). The difference with respect to version 1.8.5 is that the new version depends on more OpenGL features and hence is more demanding in this regard. Unfortunately, some Windows 7 machines, especially laptops and tablet-like machines with integrated Intel graphics, do not provide valid graphics drivers. This explains all of these weird problems on Windows. I'm afraid there is nothing I can do, besides recommending running the application on different machines and/or upgrading to Windows 10 with the latest graphics driver versions installed.