• Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning old domain name stealing credentials

  • Special Server Maintenance

    Just when you think you have everything running some what better...

    You get a message from the Hosting company. Short story they need to move us to a new server. I have been working with them to plan a good date for all concerned. Here is what we have come up with as a schedule.

    1. November 4th 17:00 -5UTC shut off the forums and start backup proceedures. During this time there will be no access to the forums or the Resource Section.
    2. November 5th Continue with Backups and download same until complete.
    3. November 6th 7:00 turn over server to hosting company to move system to new server
    4. November 7th - 8th restore backups and upgrade forum software.

    If all goes well we should be back online on November 8th.

    To keep you updated Tom Clayton has offered to post updates on AVSIM forums.

    Thank you for your support.

Failed to read from file error

Hageneezz

Members +
I have encountered this strange error for the first time today. It only occurs when starting a flight from an airfield in the Toronto (Canada) region. FSX ctd with the following message: 'Failed to read from file'

I have browsed the internet but nothing that resembles this particular situation comes up.

Hope someone here can help!
 
The "Failed to read from file" error in Microsoft Flight Simulator X (FSX) typically points to corrupted game files, permission issues, or a missing dependency like the Microsoft Visual C++ 2005 Redistributable. [1, 2, 3]

Immediate Fixes
  • Verify Integrity (Steam Edition):
    If you are using the Steam Edition, right-click FSX in your Library, select Properties > Installed Files, and click Verify integrity of game files. This will automatically redownload any missing or corrupted files. [1, 2, 3]
  • Run as Administrator:
    Right-click your FSX shortcut or fsx.exe and select Run as administrator. Lack of administrative privileges is a common cause for read/write failures. [1, 2]
  • Install Visual C++ 2005 Redistributable:
    FSX requires specific versions of the Microsoft Visual C++ 2005 Redistributable. Steam users can find these installers in:
    ...\Steam\steamapps\common\Steamworks Shared\_CommonRedist\vcredist\2005
    Run both the x86 and x64 versions. [1, 2, 3]

Troubleshooting Specific Scenery or Config Errors
  • Check scenery.cfg:
    This error often occurs if FSX tries to load a scenery folder that no longer exists. Check your scenery.cfg file (found in %AppData%\Microsoft\FSX) for invalid paths. [1, 2, 3]
  • Clear the Logbook:
    A corrupted logbook.bin can prevent the game from reading startup data. Try renaming or deleting logbook.bin in your Documents\Flight Simulator X Files folder to see if it fixes the crash. [1]
  • Event Viewer:
    If the game crashes immediately, check the Windows Event Viewer under Windows Logs > Application. Look for "Error" entries with fsx.exe as the source to identify the specific file or module causing the failure. [1, 2, 3]

Amazon FSx (Cloud Storage)
If you are seeing this error while using Amazon FSx for Windows File Server, it usually indicates a connectivity or permission problem with Active Directory: [1, 2]
  • Permissions: Ensure the Active Directory user has the necessary NTFS ACL permissions for the shared folder.
  • Network: Verify the instance is in the same VPC and that DNS settings are enabled for the file system mount. [1, 2]
 
I have encountered this strange error for the first time today. It only occurs when starting a flight from an airfield in the Toronto (Canada) region. FSX ctd with the following message: 'Failed to read from file'

I have browsed the internet but nothing that resembles this particular situation comes up.

Hope someone here can help!
found the following over @ avsim for the error "failed to read from file" and CTD:

appears to be a memory related error; for starters, check the event log and follow the troubleshooting guidelines as posted by @MrZippy
 
Back
Top