Unable to run kicad-nightly-9.99.0.2573.g5895c27f4a-x86_64

I wanted to test today’s kicad-nightly-9.99.0.2573.g5895c27f4a-x86_64.exe release. It installs fine, but doesn’t run. Kicad.exe appears only for about a second in Windows task manager, then disapppears. Could someone else confirm this? Thanks.

I can open a project, schematic and pcb normally with it. Windows 11, a bit older laptop.

You can try closing KiCad, renaming %appdata%\kicad\9.99\ and opening KiCad again to see if it’s about some non-default setting.

1 Like

In my environment it started normally.
Platform: Windows 11 (build 26100), 64bit edition, 64 bit

Version: 9.99.0-2573-g5895c27f4a, release build

I’m testing it on old PC with Windows 10 64-bit which I keep for such experiments. I tried deleting all KiCad-related directories in /Users/, but it didn’t help. That’s not suprising, because they were already empty, as I uninstalled the previous version with “remove config files” option. I tried installing today’s kicad-nightly-9.99.0.2590.g9fcee70827-x86_64.exe and it doesn’t run either. Windows crash dumps say the problem occurs in kicommon.dll.

Of course, they’re just develompment builds and some wrinkles can be expected with so many additions lately. (I’m particularly hyped about the latest lasso selection feature and multi-unit symbol placement fix.) If it persists in a few next nightlies, I’ll make a bug report on Gitlab.

If you start cmd.exe with administrator privileges and attach the following execution results, you may be able to get more details.

wevtutil qe Application /c:5 /f:Text /rd:true "/q:*[System[(EventID=1000)]]"

dir %appdata%\kicad
dir %LOCALAPPDATA%\CrashDumps

sfc /scannow

If you get WinDbg and provide the traceback information of the crash dump, you can visualize the sequence of function calls and the cause of the abnormal termination.

Install only WinDbg from here. (Win10) Windows SDK - Windows app development | Microsoft Developer

Select the file saved in the %LOCALAPPDATA%\CrashDumps folder with Open Crash Dump and run the following command to get more details:

k
!analyze -v

Ex.

In addition to the above, it would be helpful if you could also provide information about the operations and steps to generate a crash dump.
For example:

2 Likes