Jump to content

How to fix PFPX runtime problems

Recommended Posts

  • Deputy Sheriffs

PFPX, like many other Windows applications, makes use of the so called Microsoft Visual C++ Redistributables. These are function libraries and are fixed to the development environment a program was developed (compiled) with. The current version of PFPX was build with the Microsoft Visual Studio 2017, hence it requires the Microsoft Visual C++ 2017 Redistributables


There are 4 known problems that might occur with your installation of these packages, which can all be fixed by the instructions in this topic.


  1. The installer of PFPX comes with these packages (for 32bit and 64bit Windows systems) and installs them. In rare cases it happens, that the installation fails and when you afterwards try to start PFPX you end up with an error message that one of the following files is missing (or even both):

  2. The MC++ Redist Packages somehow are getting corrupt and lead PFPX to crash from time to time within the NTDLL.DLL file (as revealed by the Windows Event Logs).
  3. You are unable to add a new aircraft into the PFPX aircraft database, because the menu item is grayed our or nothing happens when clicking it.
  4. Some of the PFPX windows miss the buttons in the toolbar on top of the window.



To fix all the problems you have to re-install the MSVC redist package(s). The following is a step-by-step guide to do this. 


  1. Open the Windows Control Panel and then Add/Remove Programs respective Programs and Features
  2. Locate the item(s):
    1. Microsoft Visual C++ 2015/2017/2019 x86 Redistributable
    2. Microsoft Visual C++ 2015/2017/2019 x64 Redistributable
  3. Right click them and select uninstall
  4. Reboot your system
  5. Download the following two installers directly from Microsoft:
  6. Install both packages as Administrator. Do so by right clicking each file and select "Run as Administrator"
  7. Reboot your system



Don't worry if you do not find both but just one packages being installed on your system. It is only that version (32bit or 64bit) needed which matches to your Windows version, which is either 32bit or 64bit. If you are not sure it doesn't harm to install both packages.


Now everything should be fine again.


If not, you can also try the Microsoft .NET Framework Repair Tool:


(this topic replaces a previous outdated one, which couldn't be updated anymore and was therefore removed)


Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...