AutoFPS (0.4.4.5) was working OK in sim (2024 Beta) when the sim ended normally.  The AutoFPS box disappeared from the screen seconds after the sim terminated - just as always.

I made some changes to my community file and tried to restart AutoFPS but it keeps telling me there is a copy of the program already running.

I used Task Manager to find and terminate the MSFS_AutoFPS.exe process but found none.  I then used the DOS Command TASKKILL to terminate any process beginning with MSFS_Auto*.  This is done with a batch file (run as administrator) I have used for the last year or so and it has never had a problem terminating AutoFPS.

This time, the Taskkill command told me it could not terminate the tasks with a pid of 11020 and 7152 because they were daughters of pid 28032.  TaskList and Taskkill both tell me that no such PIDs (tasks/processes) exist.  

I then tried to use the MSFS_AutoFPS Installer to remove the application but it too tells me another copy of MSFS_AutoFPS is already running. 

How do I get out of this situation?  MSFS_AutoFPS is not an application that can be uninstalled.  I can't use Task Manager or Taskkill to terminate it.  Is a reboot of Windows the only way out?

And..why did this happen?  I use AutoFPS everytime I start the sim and it has been working flawlessly and is much appreciated. 

 

24 minutes ago, TacomaSailor said:

AutoFPS (0.4.4.5) was working OK in sim (2024 Beta) when the sim ended normally.  The AutoFPS box disappeared from the screen seconds after the sim terminated - just as always.

I made some changes to my community file and tried to restart AutoFPS but it keeps telling me there is a copy of the program already running.

I used Task Manager to find and terminate the MSFS_AutoFPS.exe process but found none.  I then used the DOS Command TASKKILL to terminate any process beginning with MSFS_Auto*.  This is done with a batch file (run as administrator) I have used for the last year or so and it has never had a problem terminating AutoFPS.

This time, the Taskkill command told me it could not terminate the tasks with a pid of 11020 and 7152 because they were daughters of pid 28032.  TaskList and Taskkill both tell me that no such PIDs (tasks/processes) exist.  

I then tried to use the MSFS_AutoFPS Installer to remove the application but it too tells me another copy of MSFS_AutoFPS is already running. 

How do I get out of this situation?  MSFS_AutoFPS is not an application that can be uninstalled.  I can't use Task Manager or Taskkill to terminate it.  Is a reboot of Windows the only way out?

And..why did this happen?  I use AutoFPS everytime I start the sim and it has been working flawlessly and is much appreciated. 

 

You didn't just  try restarting the PC when the problem first occurred?

1 hour ago, Bobsk8 said:

You didn't just  try restarting the PC when the problem first occurred?

It happens repeatedly now and I really don't want to have to boot everytime I try to get AutoFPS to run.

Removed 0.4.4.5 and installed 0.4.4.4 and problem seems to fade away

 

My testimony : I m using MSFS Addons Linker to start MSFS and I set it to also launch and close MSFS_AutoFPS 4.4.5 on MSFS start and no issue so far

11 hours ago, TacomaSailor said:

It happens repeatedly now and I really don't want to have to boot everytime I try to get AutoFPS to run.

People reboot when 99% of the time all they need to do is log off on again. Windows terminates most /all user apps and processes and gives you a clean start. A full reboot is only usually needed to reset physical hardware and device drivers. 

Log off and on again, quick and effective before any sim session. 

I disagree, many issues reported in forums are because people do NOT restart their rig after messing around with installations, updates, driver replacements etc. I mean, restarting with a full SSD build having the OS installed on a m.2 drive takes how long? 30 seconds max? 

5 hours ago, sloppysmusic said:

People reboot when 99% of the time all they need to do is log off on again. Windows terminates most /all user apps and processes and gives you a clean start. A full reboot is only usually needed to reset physical hardware and device drivers. 

Log off and on again, quick and effective before any sim session. 

Just restart it, one click and you're done. If that is too complicated, you shouldn't be flying an aircraft. 

4 hours ago, Bobsk8 said:

Just restart it, one click and you're done. If that is too complicated, you shouldn't be flying an aircraft. 

So.. If a light bulb is flickering instead of just cycling the switch on and off you should reset the entire house breakers on and off first? Neither is difficult but one is just wasting time to do the same thing. 🙂

On 2/3/2025 at 8:47 AM, TacomaSailor said:

AutoFPS (0.4.4.5) was working OK in sim (2024 Beta) when the sim ended normally.  The AutoFPS box disappeared from the screen seconds after the sim terminated - just as always.

I made some changes to my community file and tried to restart AutoFPS but it keeps telling me there is a copy of the program already running.

I used Task Manager to find and terminate the MSFS_AutoFPS.exe process but found none.  I then used the DOS Command TASKKILL to terminate any process beginning with MSFS_Auto*.  This is done with a batch file (run as administrator) I have used for the last year or so and it has never had a problem terminating AutoFPS.

This time, the Taskkill command told me it could not terminate the tasks with a pid of 11020 and 7152 because they were daughters of pid 28032.  TaskList and Taskkill both tell me that no such PIDs (tasks/processes) exist.  

I then tried to use the MSFS_AutoFPS Installer to remove the application but it too tells me another copy of MSFS_AutoFPS is already running. 

How do I get out of this situation?  MSFS_AutoFPS is not an application that can be uninstalled.  I can't use Task Manager or Taskkill to terminate it.  Is a reboot of Windows the only way out?

And..why did this happen?  I use AutoFPS everytime I start the sim and it has been working flawlessly and is much appreciated. 

 

If you had raised this in the AutoFPS thread here I would have seen it and responded earlier than now.

In any case, nothing changed between 0.4.4.4 and 0.4.4.5, or for many versions for that matter, in the way the app is installed, run or terminated.  When starting up, AutoFPS uses a standard windows function called Process.GetProcessesByName(); to check whether any process named "MSFS2024_AutoFPS" already exists and terminates if it does. When terminating, AutoFPS uses another standard windows function called Application.Current.Shutdown();, which is has used ever since the app was first created over a year ago.

The fact that you have had to do this for so long when the vast majority of users do not:

Quote

I then used the DOS Command TASKKILL to terminate any process beginning with MSFS_Auto*.  This is done with a batch file (run as administrator) I have used for the last year or so and it has never had a problem terminating AutoFPS.

suggests to me there are deep-seated issues with your windows installation that, if you also experience similar issues with other apps, may be best served by reinstalling Windows from scratch one day.

Before such a drastic measure, there are a few other possible reasons why the app isn't terminating correctly, namely:

• Pre-requisite software has become corrupted. Try downloading and installing/repairing “Microsoft Visual C++ 2015 - 2022 Redistributable” from here and here. Try downloading and installing/repairing the NET desktop runtime from here and here.
• Your MSFS_AutoFPS config file has become corrupted. Try reinstalling the app with the clean install option checked.
• You installed MSFS_AutoFPS at a privilege level without the necessary permissions to terminate correctly. Try reinstalling and running the app normally and, if that doesn't work, as admin.
• Third-party interference. Other software on your system (like antivirus or other security software) could be interfering with the application's shutdown. Temporarily disabling these programs might help identify if they are the cause.

If none of that works, message me your latest log file, located in %appdata%\MSFS_AutoFPS\log, and I'll take a look and see if anything looks out of place.

 

 

Edited February 3, 20251 yr by Reset XPDR