#A32NX Installation Problem

8 messages · Page 1 of 1 (latest)

cunning tundra
#

Error: FragmenterError(PermissionsError): EPERM: operation not permitted, mkdir 'D:\flybywire-externaltools-simbridge'
at ao.createFromError (file:///C:/Users/fried/AppData/Local/Programs/fbw-installer/resources/app.asar/webpack/renderer/renderer.js:2:278408)
at R.<anonymous> (file:///C:/Users/fried/AppData/Local/Programs/fbw-installer/resources/app.asar/webpack/renderer/renderer.js:14:11896613)
at Generator.next (<anonymous>)
at i (file:///C:/Users/fried/AppData/Local/Programs/fbw-installer/resources/app.asar/webpack/renderer/renderer.js:14:11886060)

This Problem happens as soon as I try to install the A32NX, I just downloaded Msfs yesterday and exept shared cockpit I dont have any mods installed. I also dont have Msfs open while im trying to install the Plane.

image.png
hard swanBOT
#
Stickied Message

If you have an issue with the Installer, prior to posting your issues, please search for similar issues using the text search and tags.

A32NX Support
Use the following channels for support questions with the A32NX:

  • #a32nx-support for general support with the A32NX (Stable, Development and best-effort for Experimental)
  • #1046906298815488100 for Experimental VNAV and cFMS issues

Useful Links:
Download the latest installer
Install Guide
Known Issues
Beginner Guide

FlyByWire only supports the installer, not the 3rd party add-ons themselves.

stuck oracleBOT
#
FlyByWire A32NX | Reported Issues

Your issue is in our reported issues list. Please try the possible solutions in the following link(s) and report back if they didn't help. Include all the steps you tried.

Installer Permission Problems

Link to reported issues section

elfin yacht
cunning tundra
#

I did and it still doesnt work

#

the community folder is completely empty

hollow juniper
#

same issue- trying with a VPN now.

paper atlas
#

The error message says you're trying to install simbridge on your D: drive and the installer doesn't have permission to do that for some reason, can you try installing directly to your MSFS community folder and see if that produces the same error?