Thrustmaster FAST service is not running and cannot be started.

[Scotters]

I keep getting this message when I try to load up Rybo’s profile for the Warthog. Yesterday it worked after restarting the computer, and I plan on doing that again right now, but I just wondered if anyone else had this problem and had a solution. I used Windows 10. I also went to the folder for Target and made sure that I had full security permission.

[Mud]

For what it’s worth:

I’m not fond of the newest version of TARGET. I’ve had problems with that one as well. Once I reverted back to the old one, my issues were gone.

Unfortunately they’re not offering the old version for download anymore on their site, but in case you wanna give it a go I’ve got one saved on my Google Drive: https://drive.google.com/file/d/0BwfZYeE6BsF1NFEtaW0tcThlODg/view?usp=sharing

[Scotters]

Mud, thanks.

I really don’t want to change, and then have to do the setup again for the profile and all of that, but if this keeps happening, I may have to.

And btw, restarting the computer works, but of course we don’t want to have to do that every time we want to play BMS.

[Mud]

I also found this on the DCS forums, but I don’t know if this applies to your case:

So, I know this isn’t the Thrustmaster forum. However, it is a very common problem and DCS certainly sees a lot of the Warthog and other Thrustmaster devices.
Do you experience a problem when the Thrustmaster TARGET Software stops a script? Does it prevent your computer from successfully shutting down or restarting normally without having to press the reset switch? Have you spent hours on forums and testing different solutions your self?

ALAS!!! I have found the solution. I too have been dealing with the same issue. However, the problem isn’t directly Win 10 or TS causing the problem. It’s actually the Thrustmaster. Now, before we I tell you what to do, confirm the same symptoms. I was also noticing a coincidental timing between TARGET and TS. However not as frequent, I have been able to reproduce the issue without the use of TS. So, here are the steps:
1. Start the TARGET
2. Run Script
3. Stop Script until it fails/freezes
4. Open Task Manager
5. Navigate to “Details”
6. Sort by author/maker? (forgive me I’m at work while writing this and therefor don’t have WIN10 to give exact verbiage)
7. IF, the issue is the same as mine you should see 2 services from Thrustmaster

• FAST Service
• DeviceManagementApp< this is the criminal who must hang for his crime against the SIM community
  If you attempt to stop this service, you will find that Access Denied slaps you in the face. This is the same service that is preventing safe restart/shutdown of our beloved SIM portals of joy. (or anger depending on how good you are) Next, we will discuss what and why.

What is it?
The purpose of this little devil is to reallocate the Thrustmaster USB devices back into individual units once the Script is stopped.
Why is it being so mean to me?
Essentially, it’s not. My assumption is that this USED to be a required application. When it works correctly, you will see this service start and then immediately stop and disappear from the list. The problem is Win 10 already understands how to reassociate the devices once the script is stopped. So, its basically a race between WIN 10 and Thrustmaster on who will complete the task first. When Windows wins the race, the service hangs and thus our headache has arrived. When Thrustmaster wins, all runs as designed.
What is the damn solution, already!?!?!?!
Navigate to Program Files (x86)\Thrustmaster\TARGET\x64 and find the DeviceManagementApp and……

DELETE IT!!!

ALL works well and the SIM world involving the Thrustmaster products resumes its enjoyment to the fullest!.

Good Luck and hope this helped!

[Scotters]

I backed up that app in a different folder just in case and I deleted it. Ran target with no problems, but we will see over the course of time if this pops up again. However, I have a feeling that this was the solution. Thanks Mudd, this really helps.:D

[ZeeMan90]

I had a similar problem. I started TARGET Script Editor, loaded and run Mud’s script. Everything went fine. Controls have been recognized and worked flawlessly.
After my session I closed TARGET which seemed to be a mistake as the stick showed up driver errors.
How did I notice? I launched Arma and flew a bit inside the A-10. The stick wasn’t responding to my input. To test its effects I enforced TARGET to load the
script and did a test run. Despite driver errors(Windows said so in the device manager) it worked in BMS. Afterwards I clicked on “stop” to stop the script
which caused a Blue Screen “IRQL_LESS_THAN_EQUAL” After reinstalling the Stick everything was good. But yesterday I had another issue with DeviceManagement.
It stopped my rig from to shutting down. Had to reset it. I have now deleted the the DeviceManagementApp and will see in a few hours if this works.

[Scotters]

Well now everything is screwed up. Rudders dont work, lots of the buttons on the warthog don’t respond. Its like I lost Rybos profile, even though I loaded it.

Any clue what I should do? Put back that deleted file?
–—
I just put back the deleted file and everything is back to normal, but I’m sure when I turn off the computer and turn it back on I will get that same error again.

[Guest]

Try Morphine’s profile? I’ve not tried Rybo’s so I’m not sure what about it is attracting you to use it…

[Mud]

Yeah, or use the old version of TARGET. I don’t really see what the new version brings for the Script Editor apart from (imo) an uglier UI

[Scotters]

Thanks for all the advice! I found the solution in another thread about issues with the Target Script. I just need to run the program as an administrator.

Thanks again guys.