Post by AceOfAces in Not starting (no error)

Viewing post in Not starting (no error)

Hello, crniorao05!

Looking at the .NET docs, .NET 9 (the version used for building the app) should support it. Double check that every file from the zip file were extracted. If they were and the app still doesn't open, please do the following:

Open the Event Viewer (you can find it via Windows Search) and look into Custom View -> Admin Events and check the error events for any information regarding the tool.
Head to the Temporary Files folder (Press Windows Button + R -> type %TEMP% -> Press Enter) and find every log file that is called CompilerSession-DXGUI-yyyyMMdd-hhmmss.log and check for line that say "Exception!".

crniorao05126 days ago

Thank you for the reply!

I've triple checked everything. All the .NET runtimes are up to date and all the files are there.

Opening up the event viewer I found this error:

------------------------------------------------------------------------------------------------------------------------------------------------------

Faulting application name: Dragonhouse.RMCookToolDeluxe.GUI.exe, version: 6.1.4.25234, time stamp: 0x68768fdd

Faulting module name: KERNELBASE.dll, version: 10.0.19041.1381, time stamp: 0x433f9d32

Exception code: 0xc0000602

Fault offset: 0x000000000010b302

Faulting process id: 0x3b40

Faulting application start time: 0x01dc14f40483cfa1

Faulting application path: D:\Users\Admin\Desktop\RMCookToolDX-Windows-20250822\RMCookToolDX\Dragonhouse.RMCookToolDeluxe.GUI.exe

Faulting module path: C:\Windows\System32\KERNELBASE.dll

Report Id: e0297afa-d57a-4865-9d68-a9843bc05ddd

Faulting package full name:

Faulting package-relative application ID:

------------------------------------------------------------------------------------------------------------------------------------------------------

As for the temp folder, there are no logs left behind with that name.

AceOfAces123 days ago

This took longer than anticipated, as the exception code gave me two to three potential issues. Just to narrow it down, check if there are corrupt files in the OS. You can do this by following this guide: Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support

I can also send you an experimental version of the tool, to rule out any build issues on my side.

crniorao05122 days ago

Thank you so much for the reply.

My windows 10 is an LTSC version and a custom one at that, so some features are disabled, such as updates and because of that when I run sfc /scannow it will say that there are corrupted files, but it will not specify or repair those "corrupted" files because the updates are disabled (permanently on this custom OS).

Can you please send me the experimental version so we can check? (though I highly doubt that it is an issue on your end)

If this doesn't work, I guess I'll just have to re-install windows some time in the future.

And once again, sorry for taking up your time!

AceOfAces120 days ago

I've sent a link for the build in your email. Let me know if it works.

crniorao05118 days ago (2 edits)

Thank you for sending me the experimental version, I've downloaded and tried to open it but same thing happened again (crashed without error), however this time the error in event viewer is different and there are two this time.

First one:

Exception code: 0xc0000005

Fault offset: 0x00000000000e013c

Faulting process id: 0x13b8

Second one:

Exception code: 0xc0000005

Fault offset: 0x00000000000e013c

Faulting process id: 0x3cd0

------------------------------------------------

Previous one was:

Exception code: 0xc0000602

Fault offset: 0x000000000010b302

Faulting process id: 0x3b40

itch.io

Viewing post in Not starting (no error)

First one:

Second one:

Previous one was: