PA 28R ARROW III for MSFS "Security Failure"

Thrunkx

@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

@Thrunkx

You have some weird folder structure. N:\Packages Have you tried to rename it N:\Microsoft Flight Simulator? Dont forget to change to the same foldername in UserCfg.opt

Thrunkx

@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

@Thrunkx So N:\Packages\Official\Steam is where all your MSFS data is stored now, and N:\Packages\Community is where the community add-ons are stored?

Thrunkx

@Cygnific yes

Gilandred

@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.

Thrunkx

@Gilandred yes that's exactly what I think

Gilandred

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

@Gilandred Yes I know, was just wandering why it would be called Packages instead of something like Microsoft Flight Simulator.

Cygnific

I think more people would complain if it was a Steam AppData\Roaming problem and they only check AppData\Local.. But who knows. You can check that by making a folder in Appdata\Local

Gilandred

@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.

Cygnific

@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).

Cygnific

So, to be sure, make a AppData\Local folder pointing to F:\MSFS and N:\Packages for @Thrunkx

AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache
Here goes the UserCfg.opt

Gilandred

@Cygnific Worst case scenario is I ask for a refund and then buy again when it comes to the MS Marketplace, but I still hope tech support can get this sorted.

Cygnific

@Gilandred Yes, but there is a change that you can't modify .xml, .cfg files then though, due to drm.

Craig

The most likely cause that we have seen for this issue is that the account you are using MSFS on does not have full administrative rights.

If you have more than one account on your PC please make sure that ll accounts are administrators and not just users

Gilandred

@Craig my user account (only one on PC) has full administrative privileges and the installer was also ran as administrator. Must be something else.

terrycornwall

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.

Steffen1030

I am also the only user on the PC and have full admin rights.
I don't think it's the steam version either. I have the MS Store version.
it has something to do with that damn registration process.
then some admin writes here, this is not a support forum and refers to the support ..... but this does not even answer.
Super Service

terrycornwall

@Steffen1030 I suppose they do their best as I nearly gave up on MSFS more than once. I do agree like you I am the only user for this pc and have MSFS on an M2 SSD apart from p3dv5 all on its lonesome. I have heard the SDK kit is very difficult to work with and it will take time. However it doesn't help us at the moment as was looking forward to a decent prop aircraft as the ones with MSFS aren't particularly good.