TARGET GUI stopped working

[sbach34]

Anybody having issues with target not working lately. I’m guessing not, or someone would probably have already addressed it in here. But for the last week or so, target wont launch. Gives me the good old Windows message, “TARGETGUI has stopped working” when it tries to load up. I think it has something to do with a recent windows update, but not sure. Anyone else have, or ever have, issues like this.

[Shadow]

I have but it was a long time ago, & I dont remember what the fix was. Sorry!

Have you tried Uninstall/reinstall ?

Some more info would be useful. OS ?, other running apps, is TS3 running? etc.

Is the antivirus interfering ?

[Terminator]

I’m running Target on Win8, no issues on my side, are you using Win10?

[Frederf]

I have this too. TARGET Script runs, TARGET GUI runs if given a profile file in command line, but TARGET GUI crashes on launch as well (Win10). It didn’t always but just as I got TARGET working reliably I must have broken the GUI.

I just reinstalled and… no change. Script works GUI doesn’t.

[sbach34]

I’m running windows 10. I uninstalled Afterburner and Riva but still the same problem. They were installed when I first started using Target and it was fine. I completely uninstalled/deleted everything Thrustmaster and reinstalled but that didn’t help. I’m not sure what TS3 is? I do have Norton antivirus running but its always been running. I dont think thats interfering. (just turned it off, still no workie)

Kinda frustrating since I just bougt this set up in December, used it for a couple weeks and now I cant run my profile.

[sbach34]

New update…

If I unplug my HOTAS usb connectors, GUI will run.

[Frederf]

I get the same. I get a crash if I try to edit or create a new GUI project with or without replugging in the controllers after GUI start.

However! If you just want to run your .tmc or .fcf profile then you can do it even if GUI crashes. Make a shortcut and change the Target: field to:
“C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETGUI.exe” -r “C:\PathToProfile\ProfileName.fcf”

This works for running TargetGUI.exe and the profile without crashing. I can’t do any editing or viewing with TargetGUI but at least I can run a profile with that exe using this method.

[sbach34]

Yeah its frustrating when you spend that kind of money and the stuff dont work right. But, If I unplug HOTAS, start GUI, plug HOTAS back in, then run the script, it works. Haven’t tried editing anything or creating a new one though.

[TheDude]

Ive had the same problem, like it is described in this thread. Yesterday my computer suffers a crash including bluescreen. That crash was not related to any target-issues - i did something completely different. Wathever: after windows finished the "automatic repair" i tested Target GUI and it worked well and still does. So, it seems so that this whole thing has something to do with any kind of windows problems (by the way, im using windows10). It all started right after an major upgrade.

[hoover]

For all you folks suffering from TARGET bugs & failures maybe the vjoy / joystrick gremlin might pose a valid alternative for you?

All the best, Uwe

[Mud]

Delete (with backup), or rename the following file.

C:\Program Files (x86)\Thrustmaster\TARGET\x64\DeviceManagementApp.exe

I believe this is caused by both TARGET and W10 fighting over the device.

See if that improves your situation.

Mud

[Frederf]

All disabling DeviceManagementApp.exe does for me is prevent it from even trying to hide the devices. Thus I get all three devices: TARGET, joystick, and throttle.

[DocWW]

I have this exact issue with my Windows 7 machine. TARGET works fine for me on Windows 10 but not Windows 7. I have been shutting down background programs and still no joy. I am not running Afterburner or Riva apps on either machine. I have tried all the compatibility settings and running as admin but it still gives the “TARGET is not Working error” with no reason as to why. There should be a law against an error message that doesn’t give the user a clue. It use to work on both machines. I wonder if a Windows Update patch is causing this. Any clues guys would be appreciated.

Thanks,

DocWW