CutControl won't run

MR-1
1

First… I’ve read every post on this forum that mentions a fix for issues running CutControl and I have tried every fix. Nothing has worked.

The error shows itself as one of three different behaviors.

  1. Failed to “Failed to launch JVM”
  2. The UI screen flashes for about 300 milliseconds then closes.
  3. Just nothing visual at all.

I’ve tried installing versions 24.1.1 and 25.1.2, several times, in forward and reverse order. I have uninstalled and reinstalled as well.

I’ve installed Java, both 64-it and 32-bit. (because Java recommended it as a troubleshooting step)

I’ve added, deleted and updated JAVA_HOME environment variables.

I’ve replaced the \.CutControl folder with the one Langmuir provides as a fix.

I’ve tried on three different laptops, with both Intel and AMD processors.

The only machine I can get it to work on is a big Ryzen work station that is not in my shop.

Not that it should require 30 years of hardware and software experience to troubleshoot a simple application start error… but I’m one of those.

Honestly, such poor software behavior associated with such a badass machine is truly remarkable.

At wit’s end. Thanks for any advice y’all have to share.

2

What windows version are you running? Is the application being run as an administrator?

Also you had your unit rained on. Was the main computer box also rained on (never mind reread your post it was not)? Are both your switches in back turned on and your fuse still good?

3

Thanks for your response, @salemlakesarmory.

Two of the computers are windows 10, one is windows 11. All machines are current RE updates. I haven’t tried running the app as admin. That’s a good idea. I’ll give it a try. That said, I wasn’t running the app as an admin on the workstation where the app did run.

The rain turned out to be a nothing burger. As you noted, the control box was indoors and their wasn’t even a computer hooked up to the machine.

Actually, something you said… “Are both your switches in back turned on…” Does CutControl need to see the MR-1 connected in order to boot up? Still, the one machine where the software runs wasn’t connected to the machine. Hmm…

4

Yes cut control needs to see the board. So both (or rather just the small one)switches need to be on. The large one is for the spindle small one is for the board. I was thinking initially that was your issue until you said you got it to run on your one computer but it could be a fluke that it booted without being connected.

On the computer that booted cut control, do you have any other hardware on that, that cut control may see as a compatible board? I once got Detroit diesel diag software to run on a cummins engine for after treatment issues, cummins at the time was making all the dpf and scr stuff for on highway equipment so that prolly why it worked. Was a total fluke i forgot what engine it had in it. (Fleet work)

5

Very interesting. I’m going to mess around with that. Stay tuned….

6

Alas, no love. I plugged the machine into one of the laptops and cutcontrol flashes it’s splash screen then goes away quickly. Run as admin didn’t help either.

@langmuir-zack Can I get an assist here?

Is there documentation on CutControl that describes what it needs to run… beyond the system requirements because I meet all of them.

Does cut control have any error logs I can look at?

Is there a ‘safe mode’ I can run under?

7

The only logging that is done that I am aware of is the CutControl.log that is stored in the .CutControl folder, it’s severely lacking and as far as I’m aware it doesn’t properly initialize before the JVM launch error occurs. I’m finally back to working on some more updates on CutControl as the XF/MR-1/Apollo tech work seems to be hitting a slower period (hopefully) so I should have time to look into this in more detail and figure out what may be causing this error on your end.

Fresh installs shouldn’t have this issue, and older versions of CutControl run just fine with the newer settings so the JVM crash happening on the older version is concerning. Does this happen after a complete reinstall of 24.1.1 (Uninstall + Deleting .CutControl)?

I’ll do my best to at least get back to you with a response on some more paths of action. And if a solution is found I’ll do my best to remember to post it here as well. Reaching out to support@langmuirsystems.com and adding an ATTN: Zach H should get the ticket routed to me and is also the fastest way to get any software problems in front of me.

1 Like
8

AI suggestions…

Since your friend is on Windows 11 and seeing a splash screen that immediately disappears, the program is likely crashing the moment it tries to initialize its main window or connect to a driver.

Here is a quick troubleshooting checklist you can send them to narrow it down:

1. Check the Event Viewer (The “Black Box”)

This is the fastest way to see exactly why it’s failing.

  • Right-click the Start button and select Event Viewer.

  • Go to Windows Logs > Application.

  • Look for an “Error” or “Warning” at the exact timestamp the program crashed.

  • Look for: Faulting module name. If it’s a .dll file, that usually points to the specific problem (like a graphics driver or a missing C++ Redistributable).

2. Check for “Ghost” Processes

Sometimes a program crashes but leaves a “zombie” process running in the background, which prevents a new instance from opening.

  • Press Ctrl + Shift + Esc to open Task Manager.

  • Go to the Details tab.

  • Look for the program’s name. If it’s there, right-click it and select End Task, then try opening it again.

3. Compatibility and Admin Rights

Windows 11 can be picky with older software or specific permissions.

  • Right-click the program shortcut and select Properties.

  • Go to the Compatibility tab.

  • Check “Run this program as an administrator.”

  • You can also try checking “Run this program in compatibility mode for:” and selecting Windows 8.

4. Graphics & Scaling Issues

If the splash screen loads but the main UI doesn’t, it might be a resolution conflict.

  • In the same Compatibility tab from Step 3, click “Change high DPI settings.”

  • Check “Override high DPI scaling behavior” and set it to “Application.”

  • This is a common fix for older programs on high-res Windows 11 monitors.

5. Anti-Virus False Positives

Windows Defender or third-party AVs sometimes let the splash screen load but kill the main .exe once it tries to access the internet or a system folder.

  • Have them temporarily disable their firewall/antivirus and try to launch it once. If it works, they just need to add an “Exclusion” for that folder.
1 Like
9

Thanks, @Richarddbeck83, good instinct. Although, I think you might have meant ProcMon?

I captured the process log for both a successful start up on the workstation and a failed start up on the laptop I want to use. Here are the logs in both ProcMon native format (easiest to analyze) and CSV format.

CutControl-Logfile-Success.CSV

CutControl-Logfile-Fail.CSV

CutControl-Logfile-Success.PML

CutControl-Logfile-Fail.PML

@langmuir-zachary Zach, I will also send these to the @support email with your attention.

Thanks everyone!

10

This is what AI says. Dont know if it helps but its something

The main difference is that the “Fail” log shows CutControl.exe (a Java/Swing app) crashing shortly after launch with a JVM fatal error, while the “Success” log shows a normal, complete run.

Key Observations from the Logs

1. Crash in Fail Log (PID 8340)

The application starts normally (loads DLLs, reads CutControl.cfg, starts Java runtime).

It creates a child process (another CutControl.exe PID 8340).

It crashes quickly (~8 seconds after start).

Evidence of JVM crash:

Writes a large hs_err_pid8340.log (HotSpot error log) — classic JVM fatal error report.

Process Exit with Exit Status: 1 (abnormal termination).

High resource usage before crash (Private Bytes ~397 MB, Working Set ~369 MB).

The parent process (PID 8756) also exits shortly after with status 1.

2. Success Log

Runs much longer (from 2:29:12 PM to at least 2:29:19+).

Successfully loads many more modules (JavaFX, LWJGL, various JARs like cutcontrol-24.1.1.jar, Bluetooth/serial drivers, etc.).

Performs extensive operations: Bluetooth device enumeration (BthEnum.sys), serial ports (COM ports), graphics, etc.

Ends cleanly (normal process profiling/exit, no hs_err crash log).

Root Cause Indicators (Most Likely)

The crash is almost certainly a Java Virtual Machine (JVM) fatal error (native crash inside the JRE).

Common causes based on the logs:

Java version / native library incompatibility (bundled JRE in runtime/ folder).

Graphics/GPU issue (loads JavaFX, LWJGL/OpenGL, common-controls, etc. — frequent crash source on some hardware/drivers).

Bluetooth/Serial (jSerialComm) initialization — the success log shows heavy activity here.

Memory/heap issue or corrupted JAR/native libs.

Different environments:

Fail: User bobcr on DESKTOP-2VBQ9SE (AMD Ryzen, fewer cores?).

Success: User Garage on GARAGE (more powerful 12-core AMD).

Quick Diagnostic Steps

Check the crash log:BashC:\Users\bobcr\AppData\Local\CutControl\hs_err_pid8340.logLook at the top for the exact error (e.g., EXCEPTION_ACCESS_VIOLATION, SIGSEGV, problematic native library like javafx, lwjgl, or jSerialComm).

Compare environments:

Graphics driver (AMD on both?).

JavaFX / LWJGL native libs.

Bluetooth stack.

Workarounds to try:

Update AMD graphics drivers.

Run with -Dprism.order=d3d or software rendering.

Disable Bluetooth/serial features if possible.

Use a different JRE.

1 Like