When you installed a fresh copy of windows 10 did it remove everything from your computer? I guess I can backup all my files to USB but I’m trying to avoid this although it seems like the only option at this point.
Were you regularly using these machines until last week? Typical update cycle is the 2nd Tuesday of the month. I assume it was the most recent update cycle that killed this.
My main PC I have been using from day 1 (almost 3 years 60+ hours of cutting time on my pro). I repurposed any old laptop a few months ago to keep from running back and forth to the table. Both started having Firecontrol issues a weeks ago, maybe 2 weeks now.
So far I have tried all of these things in this order.
- Reinstall FireControl
- Install the compatibility version of FC
- Undo as many windows updates as I could
- Update the BIOS on my PC
- Factory reset and reinstall Windows 11
- Install Windows 10
So far nothing has worked, the closest I got was after installing Windows 10 FireControl actually opened and gave me a graphics compatibility error so I closed FireControl and tried to open it again and it crashed immediately. I’m not sure but I think when I’m installing these versions of Windows it is the most updated version and I don’t know how to get an older version.
Lenovo T495: AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx, 8 cores, 13G, Windows 10 , 64 bit Build 19041 (10.0.19041.1889)
Completely uninstall fire control. Then download 20.6.2. Give it a try it should work as long as you are not running a xr or a pro with limit switches
I finally got mine to work again I couldn’t go back from the windows 11 update, so I wiped the computer clean and reinstalled windows 10… I then downloaded the 21.1.5 and it still wouldn’t work I then downloaded the 20.6.2 and it worked. I also cut a sheet worth on my crossfire pro since I got it working again. I forgot to back up my tool set on sheet Cam so hopefully that helps someone else remember.
I am also having the exact same issue. Dell G15 Ryzen Edition 5000 series 7 with nvidia geoforce rtx. Windows 11 Home Edition Build 10.0.22621. I also believe this begun after the latest Windows update. I supposedly have the “Pro Service” Helpdesk with Dell and after they did some checking on my computer, they passed the buck stating it’s a software problem with Firecontrol, contact your software vendor. I wasn’t surprised they were no help whatsoever. After reading this topic I contacted them back with additional information. They again did some checking with Windows and my computer and again passed the buck to Langmuir. I too have uninstalled, reinstalled, restored back 10 days ago, etc… without success. Has anyone found a permanent fix to this?
Hey Guys, I was having the same issue after updating windows. I was able to correct it by uninstalling firecontrol 21.1.5 and downloading the FireControl 21.1.5-compatibility For older graphics hardware My system is now back up and running. Hope it helps someone else out there.
I’m using a DellI Gaming G15 5515. I tried the “Compatibility” Ver with Windows 11 and it still crashed. I then uninstalled Windows 11 and installed Windows 10 Ver 10.0. but again had the same issue. I then installed 21.5 “COMPATIBILITY “ version of FIRE-CONTROL and using Windows 10 I have completed several test cuts including using my limit switch upgrade without issue. I hope this helps.
Thank you to everybody helping me with this issue, I appreciate your assistance.
I’m on a Lenovo Ideapad Gaming labtop with the 5000 series AMD Ryzen. Fire control worked yesterday and today is giving me the Child process fault. I have uninstalled all recent updates. tried every version of fire control and the only way I can get anything to work is by using the v21 compatibility version. Hoping someone has an update for this problem.
welcome to the forum…glad to have you here…
so just for future help there is a magnifying glass in the top right corner…if you click on it and type in key words you often find the answers…
to help I typed “Child Process” and came up with this…I think it answers your problem.
You posted a link to to the thread we are discussing.
hahahahaah…I did didn’t I…hahahahaha…
so the answer is in the thread…
I purchased a brand spanking new laptop today with fresh windows 10 pro update for more than 1000 bucks especially for fusion and firecontrol…and had the same issues. I was about to kill something! I did as patriot pits suggested and BANG it running! I am yet to find out what the compromise will be… At least the program is running! THANKS!!
@ langmuire…what is the difference in code?? What will the compromise be? I also purchased THC and limit switches, but I am setting up things now so have no idea what IT-stuff will follow??? I can design/build/produce/fix any mechanical thing but hate anything with an electrica wire…or software…hahahah
same thing here. Try patriot pits message
Curious was this an Intel processor? Which graphics card?
This is what I have…
AMD Ryzen 3 5400U with Radeon Graphics 2.60 GHz
Windows 10 Pro version :22H2
updated: 1/25/2023
Langmuir suggest it’s an amd thing with the power saving cpu. However I picked up a lenevo legion 7i running intel and an nvidia graphic card with win11 and it still had issues crashing fire control. Fusion wasn’t much better, ran fast but still did it’s normal annoying glitches so I returned it and went back to just running my thinkpad with the amd hardware and the compatibility version of fire control. It’s annoying, I’m sure Langmuir is working on a patch, even though they’ll say it’s a windows issue or a hardware issue. Fact is their software doesn’t work with the latest version of windows. Wish they would just grow a set and say it exactly like that.
I am also having this same exact issue! I have read all of the threads and done most of what everyone has tried. Please let me know if anyone has come across another solution.
Thanks in advance!
I uninstalled the latest version of Firecontrol and then downloaded the Firecontrol 21.1.5 compatibility version and so far it seems to be working. The program opens and has not shut down and given me the error message yet. Good luck to everyone and I hope that Langmuir finds a permanent solution to this software issue.