PA 28R ARROW III for MSFS "Security Failure"
-
@Cygnific No, no change, still can't use the PA-28R, I've tried everything I knew, but unfortunately without success.
I started the installation as admin from the beginning and even later I gave myself super admin rights to make sure that it wasn't because of that, but as I said, unfortunately no result.
Then I did a readout and sent the support but unfortunately I haven't gotten any reaction from them so far, I'm slowly losing interest in the plane and I'm starting to think about asking for the money back.
I have been waiting for a solution since Saturday and have not been able to test the aircraft until now.
My readout:
Checking for MSFS installation
Checking for steam version
usercfg.opt file located
C:\Users\Thrun\AppData\Roaming\Microsoft Flight Simulator\usercfg.opt
reading usercfg.opt file
InstalledPackagesPath entry found
InstalledPackagesPath "N:\Packages"package path - N:\Packages
configs path - C:\Users\Thrun\AppData\Roaming\Microsoft Flight Simulator
working path - C:\Users\Thrun\AppData\Roaming\Microsoft Flight Simulator\packages
flights path - C:\Users\Thrun\AppData\Roaming\Microsoft Flight Simulator
official path - N:\Packages\Official\Steam
sdk path -
Updating registry settings -
@Cygnific yes I tried that too, because MSFS is already 617GB with me, I created a new livery on Steam only for MSFS that is used on an external SSD hard drive. the structure you see there is what Steam created when I installed MSFS on steam.
-
@Cygnific Actually that’s a common structure if you install the Steam version of MSFS to another harddrive. The “official” and “community” folders will install to the other harddrive, while the MSFS executable and other folders will install to steamapps/common/microsoftflightsimulator. This is similar to what I have, and I suspect Justflight’s installation or license check does not account for this somehow.
-
Here is my structure for reference.
Checking for MSFS installation
Checking for steam version
usercfg.opt file located
C:\Users\Owner\AppData\Roaming\Microsoft Flight Simulator\usercfg.opt
reading usercfg.opt file
InstalledPackagesPath entry found
InstalledPackagesPath "F:\MSFS"package path - F:\MSFS
configs path - C:\Users\Owner\AppData\Roaming\Microsoft Flight Simulator
working path - C:\Users\Owner\AppData\Roaming\Microsoft Flight Simulator\packages
flights path - C:\Users\Owner\AppData\Roaming\Microsoft Flight Simulator
official path - F:\MSFS\Official\Steam
sdk path -
Updating registry settings -
@Cygnific During the installation process MSFS will let you install it to a folder of your choosing so your able to name it whatever you want. Looks like this might be the common issue for installation issues, but is not terribly widespread as I suspect most people use only one drive.
-
@Gilandred I doubt, the folder is written correctly in UserCfg.opt and that is checked by the installer. My problem was that it only read the AppData\Local folder and forgot the AppData\Roaming where I have another install for Steam.. (I have Store and Steam versions installed).
-
-
I have the same problem and even the planes yoke is not coordinating with my joystick just lays on oneside to the left but won't move left or right. hope they can fix it as it is a great bit of work other than these bugs. I also am the only user on this pc and it has administrative rights. I am sure it will be sorted.