Windows 11 Insider build - Suddenly cannot start QtCreator

[JonB]

To be clear: neither Creator nor any Qt app you have (perhaps already compiled) will run? If you invoke from a Command Prompt do you get any kind of messages? For Creator there is a command line argument to put it into debug/diagnostic mode, but I don't know what it is, Googling would tell you.

Btw, changing to WSL is a fair sized step, quite different from running/compiling for Windows.

[ldraconus]

In order: No Qt based app will run, except the installer. From the Command Line: I start it, I get the prompt back and .. nothing.

I'll try and find the debug mode.

I've developed under Linux professionally and used WSL on my laptop before so not a big deal I am aware of the pitfalls and benefits there-in.

I'm going to see how well WSL deals with multiple desktops and if that works, just run the linux apps from a window manager there.

[ldraconus]

Ok, it looks like it doesn't even fully start before something happens. I get absolutely no change no matter what I put on the command line.

[JonB]

Not getting any output at all sounds odd. In your Command Prompt enter set QT_DEBUG_PLUGINS=1 as a command and then try running a Qt program or Creator from there, still no output?

My understanding (could be incorrect) is that Creator comes with its own self-contained Qt libraries, so whether it runs or not ought be independent of whether a Qt program you have built runs or not, I didn't think they shared an environment. Which might indicate a system problem?

Worth checking Windows Event Viewer for anything?

[ldraconus]

Ok, this is interesting, but how to fix it:

Faulting application name: qtcreator.exe, version: 15.0.84.0, time stamp: 0x67bdb829
Faulting module name: d3d9.dll, version: 10.0.27802.1000, time stamp: 0x3e395b13
Exception code: 0xc0000005
Fault offset: 0x0000000000016121
Faulting process id: 0x48D4
Faulting application start time: 0x1DB8D13FD9638C3
Faulting application path: D:\ProgramFiles\Qt\Tools\Qt Creator 16.0.0-rc1\bin\qtcreator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll
Report Id: fbd2b50a-88b6-443f-a637-2219ab5ab361
Faulting package full name: 
Faulting package-relative application ID: 

[hskoglund]

Crash in d3d9.dll huh? Just guessing but it reminds me of an old bug with MSI Afterburner och Riva Tuner, to get around it you had to change the setting from low to off.

[ldraconus]

I saw those reports when I looked up that particular crash, and the only app that was running was some killer stuff (bad ACER bloatware) for the network, and I re-nuked those processes and set them to not start (again, really improves the network bandwidth).

As a side note, the nvidia settings app is also crashing now when I select the performance tab ... hmm. Going to try and reboot and see what happens. Maybe the things that got messed with will be miraculously reset (or fixed from the fiddling... me thinks a reboot is required).

[ldraconus]

Whelp. When I told windows to run qtcreator with the motherboard graphics only, it works. This might be a slight pain to do for each Qt application, but it did work.

[jsulm]

@ldraconus said in Windows 11 Insider build - Suddenly cannot start QtCreator:

Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll

There seems to be an issue with the graphics driver.
Did you try to install latest graphics driver?

[ldraconus]

Good call. Frustrated, so I didn't even think of it... Time to visit Nvidia...

[ldraconus]

... and that wasn't it. Installed the latest drivers, still no beans...

[JonB]

@ldraconus
You said "Insider build", right? Isn't https://forum.paradoxplaza.com/forum/threads/stellaris-doesnt-start-anymore.1730338/ from one day ago reporting the same? An Insider build issue??

[ldraconus]

@JonB Yup, that's the issue. By re-installing an manually telling it which driver to user, it works ... for every application that fails to run.