Forum
Important Notice for New User Registrations
To combat an increasing number of spam and bot registrations, we now manually approve all new user registrations. While this may cause a delay until your account is approved, this step is essential to ensure the quality and security of this forum.
To help us verify your registration as legitimate, please use a clear name as user name or an official email address (such as a work, university, or similar address). If you’re concerned that we may not recognize your registration as non-spam, feel free to email us at with a request to approve your username.
Installation problem – Repost
This is a repost of another problem i posted in general discussion, i thought it would be more appropriate to report here (i did’t notice it at first).
I just noticed that the QBlade Community Edition version 2.0.8.6 executable isn’t working on Windows 11 (24H2). I reported this issue a while ago, but I haven’t received any response as of today. There’s no error message—sometimes the QBlade logo appears briefly, but nothing else happens.
Hello Rick,
based on our experience, QBlade runs reliably on the vast majority of Windows installations, including Windows 11. The kind of issues you’re encountering are very rare and typically stem from environment-specific factors where QBlade is being executed.
QBlade relies on several shared libraries, and such issues are most likely caused by conflicts related to these dependencies.
To investigate further, we recommend launching QBlade using the free Dependency Walker tool. This utility monitors the loading of all dynamic libraries during QBlade’s startup and can help identify any conflicts or missing dependencies. This could help you to narrow down and fix the issue on your side.
Unfortunately, there’s nothing we can do on our end to directly address such environment-specific problems.
Best regards,
David
Hello,
I just wanted to say that at least 4 of us are having the same problem. We are running 4 different laptops with the latest Windows 11 installed, and we only see the splash screen briefly, then nothing. I have used the Dependency Walker tool, and it seems there are hundreds of libraries that the software cannot access or find.
Is there a known fix for this? It seems to be a fairly common issue…
Kind regards,
Reece
Hi Reece,
I would respectfully disagree with your statement that this is a very common issue. If that were the case, we would expect significantly more feedback from users experiencing similar problems – which we haven’t observed. These kinds of issues remain quite rare. Im wondering however that you observed this to happen on 4 different PC’s. Do you maybe have any idea what these machines could have in common? Did you sucessfully run QBlade on a different machine at all?
Now, regarding Dependency Walker:
It’s normal to see a large number of DLLs flagged within the folder structure shown in Dependency Walker. However, the key diagnostic information comes from profiling QBlade during startup. To do this, open the executable via File → Open, then start profiling by selecting Profile → Start Profiling, and simply click OK in the dialog that appears.
Dependency Walker will then launch QBlade and provide detailed output about the DLLs and other modules being loaded – similar to to marked text you can see in the attached image.
If QBlade crashes (which I assume is the case if you don’t see anything beyond the splash screen), the output should indicate which DLL caused the failure. Feel free to share that output here, and we’ll be happy to help you further.
Best regards,
David
Uploaded files:
- You need to login to have access to uploads.
Hi David,
The only thing I can think of that the laptops have in common is Intel processors, Windows 11, and no dedicated graphics. We have, however, been able to get the software working on university desktop computers with a dedicated graphics card and Windows 10.
I am unable to get Dependency Walker to start profiling. When I go to open the exe, the program hangs for quite a while and returns the following errors in the area you highlighted in the image:
“Error: At least one required implicit or forwarded dependency was not found.
Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.”
Start profiling is greyed out, and no matter what I do, I can’t seem to get it to start profiling.
Any help/ideas will be greatly appreciated 🙂
Kind regards,
Reece
Hi Reece,
Based on the information you provided, this could be an OpenGL related issue with Intels internal GPU. Such issues can cause QBlade to crash during startup if the OpenGL context creation fails.
You could try reinstalling the graphics drivers on your laptop – make sure to use the official Intel drivers.
Im also wondering why Dependency Walker doesnt load the executable. The loading process can sometimes take quite a while, so maybe try waiting a bit longer?
Best,
David
Hi David,
Well, I think we can definitely narrow it down to the graphics. I tried another laptop with a dedicated NVIDIA graphics card, and it worked perfectly fine. I have tried various driver versions, and the same issue keeps cropping up. It does look like Intel has had some OpenGL issues in the past…
Regarding Dependency Walker, nothing I do seems to get it to load QBlade. The program crashes for a few minutes and then spits out the error codes, oh well.
I think, for now, I will just have to wait for Intel to update their drivers further and fixes the issues. Thanks for the help 🙂
Hi Reece,
when starting QBlade from the command line do you get some debug output before it fails?
I have added a few more checks during OpenGL initialization, which might improve behavior on your system with the next release 2.0.9.4.
Best,
David
Hi David,
Sorry about the delay. I have tried opening 2.0.9.4 through the command line, and all that happens is the splash screen shows for longer, no debug output.
Thanks anyway,
Reece
Hi,
it seems the MS driver issue is not correctly detected then. We will try a different approach in the next release.
BR,
David
