I can not use properly my hardware because drivers don't work with this game

[O07LLeisBon]

I can not use my Logitech Gaming Sofware to configure keys to my mouse in this game (it as a lot of buttons that I need to configure). The reason of the problem is because NO PERMISSION TO OPEN THE FILE (I am trying with C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe).
This problem only happen with this game, and this by far the game that needs more the use of a profile. I fly with my left hand on a joystick and the right put on the mouse to view and I need remap mouse buttons to essential very used functions (otherwise I must leave the mouse and use the keyboard, and that is a pain).

I think this problem is present to many people, and I want to know if there is already a solution.

No only the Logitech driver, but also others 3rd party programs to remap buttons need access to the exe of the game.

[MichaMMA]

@Macaco000

if there is already a solution.

just use the in-game device settings

In case you need forced rights to the WindowsApps folder, there are existing topics… but not recommended.

EDIT:
and you already mentioned that and we dont like duplicate posts

I need to get rid of MS Store. I want the Steam version of the game

Is it possible to return the MSFS game that I bought in the MS Store a couple of months ago? I just want to use properly the drivers of my hardware (joysticks and mouse basically) and it is impossible because drivers can not access to the exe of the game. I have search for solutions and people say that the folder is harshly protected and it is not possible. People say that the only real solution is to buy the Steam version of the game. I just want to get rid of any MS Store game (MSFS is the o…

[NottheTagiwant]

They need the profiler software because the buttons aren’t “buttons”. They need to have keys or macros assigned to them inside LGS.

The problem seems related to MS Store Apps being in protected folders. Kinda odd though because LGS should only really be looking for the process to be running in order to switch profiles.

In any case, I think there are ways to resolve these kind of permission issues…which you appear to have added to your post.

[MichaMMA]

just still third-party-app issue which is not ready for that

The OP got allready answers in its duplicate thread and I pointed to the same:

I need to get rid of MS Store. I want the Steam version of the game

This is not true. Yes its easy in the Steam version. But you can also acces the .exe files in the MSFS Store version. But you have to give the directory |(and the files within) the rights to read/write the files. Google how to do that. Its not to difficult.

[NottheTagiwant]

None of which were particularly helpful. Though this might be…

I found an easy way to use Logitech Gaming Software / Logitech G HUB profiles with UWP apps. It is enough to create a profile and point to ApplicationFrameHost.exe (C: \ Windows \ System32 \ ApplicationFrameHost.exe). This profile will be used for all UWP apps (even the Windows Store). This is the fastest and easiest way.

https://www.reddit.com/r/LogitechG/comments/mnum6e/logitech_gaming_software_profiles_for_uwp_apps/

Bit of a fudge way of doing it but if it works, it works.

[MichaMMA]

I found same link just in this moment

Helpfull is the forum search how get rights for windowsapps folder:

Take ownership of the Windows Apps folders

The biggest difference between Steam and MS Store versions of MSFS is the access to folders. Many have expressed concern that they cannot link outside add-ons to the Flight Simulator .exe file when required by that add-on. In an attempt to ensure that software installed by the MS Store is secure and safe, MS implemented the WindowsApps Trusted Installer protocol. For users that insist on having administrative control over their computer this protocol can be overcome. Couple of important points…

May be that will offer the ability to access the .exe…

By the way: which real airplane have buttons with macros ?

PS.: and now whats happen, we doing a discussion in parallel thread and an reported issue which isnt a MSFS issue