Bitdefender is running on both machines, but nothing non-standard. I have tried disabling Bitdefender, but no joy. Krita still creates a Windows error event log each time I try to open Krita.

Hm, in my experience, bitdefender _is_ icky. The other thing is that the backtraces you reported actually all aren't startup crashes; they are crashes that can only happen if Krita is already running and is loading or has loaded an image.

Did you also try to run Krita as administator? And can you check whether you're running Krita in some kind of Windows compatibility mode?

I'm really puzzled and would like to get to the bottom off this... Last time someone had Krita crashing on all their hardware, it turned out that they had installed HP printer drivers on all their systems, which installed a broken icc profile that Krita crashed on -- that crash has been fixed, of course.

But they had to make a stripped down vm of their windows installation and share it with me before I could figure that out!

Hi

I did reply to your last post, but it has not appeared in the list for some reason. Briefly:
1. I realised that the crash log I sent you dated from 2017. It must be from an earlier installation of Krita. Sorry about that, but it does mean a crash log is NOT being created on either of my machines when I try to run Krita 4.2.1.
2. I disabled Bitdefender and tried to run Krita. Nothing different, and just to be clear even the Krita splash screen does not appear, nothing happens.
3. Tried running Krita as administrator and from the command line. Just the same.

Regards

Keith

If you don't get the splash, that almost sounds like something in Windows completely forbids you from running Krita... Does task manager show a krita process at all when you try to start krita?

Could you get DebugView (https://docs.microsoft.com/en-us/sysint ... /debugview) and check whether Krita prints any error messages when you start krita?

Hi
The Processes tab in Task Manager shows krita.exe briefly ( a few seconds) in the processes list. CPU usage rapidly drops to zero and memory usage is about 44,000K.

DebugView generates the following:
00000001 0.00000000 [6424] FTH: (6424): *** Fault tolerant heap shim applied to current process. This is usually due to previous crashes. ***
00000002 2.52433252 [6424] create: Could not initialize EGL display: error 0x3001
00000003 2.52442908 [6424] create: When using ANGLE, check if d3dcompiler_4x.dll is available
00000004 2.52862048 [6424] Failed to load opengl32sw.dll (The specified module could not be found.)
00000005 2.52868795 [6424] Failed to load and resolve WGL/OpenGL functions
00000006 4.86425734 [6424] create: Could not initialize EGL display: error 0x3001
00000007 4.86433268 [6424] create: When using ANGLE, check if d3dcompiler_4x.dll is available
00000008 4.86696815 [6424] Failed to load opengl32sw.dll (The specified module could not be found.)
00000009 4.86700773 [6424] Failed to load and resolve WGL/OpenGL functions

I searched my C:\ drive for opengl32sw.dll and it does not exist. Have not tried to reinstall it yet. Perhaps you may have some advice on that.

Hope this helps.

Keith

Is this on the Windows 7 or on the Windows 10 system? Windows 7 doesn't, afaik, support Angle, but Krita should recognize that and fall back to opengl or the CPU canvas automatically. If this is on Windows 10, then it looks like something completely messed up your CPU's driver's installation. Try to reinstall the display drivers and direct3d drivers... I haven't had this problem myself, but I only use my windows systems to test Krita, so they're relatively clean

This is my desktop machine running Windows 7 32bit which is up-to-date.

Are there opengl drivers available for the GPU for that system? I've checked, and all these messages come from Qt, which is our development platform. It's part of an elaborate system trying to find fallbacks, and then apparently failing. This might be a bug in Qt on systems on which there isn't even a fallback software-based opengl engine available.

If you add

useOpenGL

to the top section of the kritarc file, Krita might start in this case, but I'm not sure even of that -- Qt might still want to probe your system and fail to come up with something.

It would also be interesting to look at the debugview output on your Windows 10 system, because that should be different after all.

Tried modifying the kritarc file as suggested, but with no effect.

My laptop is currently at the menders as the CD drive has failed (I was trying to set up Virtual Box to try Krita in there) and won't be back until tomorrow at the earliest. I'll look at the output from debugview as soon as I get it back.

Regards

Keith

No it is not hardware, I have installed 4.2.1 on my OS Win 10 version 1809 build 17763.557 laptop and it will not run, uninstalled and reinstalled, same result.
(apologies just found this topic, have posted my problem on Krita 4.2.1 will not run on Win 10)

keithd wrote:No it is not hardware, I have installed 4.2.1 on my OS Win 10 version 1809 build 17763.557 laptop and it will not run, uninstalled and reinstalled, same result.
(apologies just found this topic, have posted my problem on Krita 4.2.1 will not run on Win 10)

Well, check with DebugView whether you get the same kind of output Keith Jeram has? It's simply not the case that Krita 4.2.1 does generically not run on Windows 10, because I've tested on three different computers, and it ran on all of them. So there must be something different, but without digging deeper, it won't be possible to figure out what that is.

This is the output from Debugview.
[1356] QWindowsEGLContext: Failed to create context, eglError: 3005, this: 0x577ef00

Yes, that looks similar. You apparently don't have working opengl/direct3d drivers on your system, which, for Windows 10, is extremely weird. Krita should fallback to the CPU renderer, but apparently that's broken. It's one of the things that very hard to test because, well, none of the developers have systems without working drivers. I'll make a bug report to remind ourselves to investigate this: viewtopic.php?f=139&t=161175&p=418872#p418830

https://bugs.kde.org/show_bug.cgi?id=408872

This may or may not help with regression, 4.1.7 runs without issue.