How do I fix the 'Access remote image server' error in MSFS Map Enhancement?
Fix the Access remote image server error in MSFS Map Enhancement, including Google failures, C# sidecar code 11, firewall and hosts checks.
The 'Access remote image server' error in MSFS Map Enhancement means its Windows helper cannot fetch imagery or complete local redirection. Test another imagery source first. If one source fails, switch or wait; if all fail, restart the helper, verify its build, then check firewall, VPN, DNS, hosts-file and sidecar faults.
What do 'What? Try again' and 'remote data could not be fetched' mean?
These are generic Map Enhancement connection messages, not precise Microsoft Flight Simulator error codes. The decisive clue is whether one imagery source fails or every source fails.
- Only one source fails: that provider may be unavailable, limiting requests or no longer compatible with the installed Map Enhancement release.
- Every source fails: suspect the helper, an old executable, firewall filtering, VPN, proxy, DNS filter, hosts-file redirection or a sidecar startup failure.
- Default Microsoft Flight Simulator imagery also fails: investigate the simulator's online services and the wider internet connection.
If Google is the only failing source, select another source supported by the installed release and retry Google later. A normal Google webpage loading in a browser does not prove that the imagery endpoint is available. Do not bypass provider rate limits, certificate checks or access controls.
Fix the Access remote image server error in this order
The fastest route is to establish whether the fault belongs to one provider, the local helper or Microsoft Flight Simulator itself.
- Close the active flight. Do not change providers while MSFS is requesting tiles unless the installed release explicitly supports switching in flight. Close the simulator if the error began during a source change.
- Try one other supported source. If it works, the helper and local redirection are broadly functional. Keep the working configuration and wait for the failed source to recover or receive compatible support.
- Stop and restore the helper cleanly. Use its Stop, Restore or equivalent command if one exists, then close all Map Enhancement processes and restart Windows. Repeatedly ending the helper through Task Manager can leave redirection active with nothing listening locally.
- Verify the executable being launched. Check the shortcut target and file location. Remove obsolete extracted copies and shortcuts so an old front end cannot start alongside newer sidecar files. If the application came in an archive, extract the complete package before running it.
- Disconnect VPNs and proxies. Disable the system-wide connection rather than only a browser extension. Filtered DNS, parental controls and HTTPS inspection can block imagery while ordinary websites still work.
- Check Windows security. Allow the exact Map Enhancement executable and its documented companion processes through the firewall on the network profile in use. Check antivirus quarantine for files from the verified package; do not restore an unidentified file or leave protection disabled.
- Correct the clock and refresh DNS. An incorrect Windows date, time or time zone can break secure requests. Restart the router and PC, then run
ipconfig /flushdnsfrom an elevated Command Prompt to clear the Windows DNS cache. - Use a second network for one short test. If the helper works through a mobile hotspot but not the normal connection, inspect the router, DNS service or network filtering. Disconnect after the result is clear because streamed imagery can use substantial mobile data.
- Test default MSFS streaming. Restore Map Enhancement's networking changes, close it and load the same area with normal online world data. If default imagery works, do not reinstall the simulator.
- Clear caches only after connectivity returns. Use the helper's own cache control first. Recreate the MSFS rolling cache only if old or blank tiles remain; deleting a cache cannot repair a blocked remote request.
Which failure pattern identifies the cause?
The scope and timing of the failure usually distinguish a provider outage from a broken local installation.
| What happens | Most likely cause | Best next step |
|---|---|---|
| Only Google or one other source fails | Provider outage, throttling, changed access rules or source-specific incompatibility | Use another supported source and retry later |
| Every source fails after an update | Mixed application files, an old shortcut or incomplete extraction | Keep one complete, compatible installation |
| Every source fails but ordinary internet access works | Firewall, VPN, proxy, DNS filter, hosts entry or helper fault | Restore redirection and inspect local filtering |
| A private RPC or sidecar error appears before source selection | The local companion process did not start or communicate | Repair the helper installation rather than changing imagery providers |
| It works on a second network | Router, DNS, ISP or home-network filtering | Inspect the normal network instead of reinstalling MSFS |
| Default MSFS imagery also fails | Simulator online-service or wider connection problem | Troubleshoot MSFS connectivity separately |
| The error disappears but tiles stay blank or old | Stale helper cache, rolling cache or disabled online data | Restore streaming first, then rebuild the relevant cache |
Why did the error suddenly appear?
A previously working setup can fail when an imagery provider changes access rules, a helper update leaves mixed files, security software quarantines a companion process, or an interrupted shutdown leaves stale redirection behind.
A single-source failure is rarely a reason to delete caches or reinstall Microsoft Flight Simulator. If every source stopped after updating Map Enhancement, verify the executable path and package contents before changing Windows networking.
Is the installed release compatible with MSFS 2024?
Use a Map Enhancement release that explicitly lists Microsoft Flight Simulator 2024 support; compatibility with MSFS 2020 does not prove compatibility with MSFS 2024.
Our MSFS 2024 setup and default-imagery restoration checks cover source selection, cache handling and the correct role of the external helper. Do not put that helper in the Community folder unless its own documentation specifically requires it.
These executable, firewall and hosts-file steps apply to Windows PC. The Windows helper cannot be installed inside the Xbox or PlayStation 5 editions of MSFS 2024, so do not apply PC networking instructions to those consoles.
What about MSFS 2020?
MSFS 2020 requires a release documented for that simulator and the same clean separation between the external helper and simulator add-ons.
If there is doubt about the original placement or launch order, follow our clean Map Enhancement setup procedure for MSFS 2020 rather than combining instructions from several releases.
Does this fix apply to an X-Plane 12 map enhancement?
No. X-Plane 12, often shortened to XP12, uses a different scenery system, and these MSFS redirection, rolling-cache and hosts-file instructions should not be copied into an unrelated X-Plane map enhancement.
Use only the documentation for the exact X-Plane add-on involved. A similarly worded remote-server message does not prove that it uses the same helper or networking method.
What does 'failed to detect private RPC endpoint from C# sidecar' mean?
This message means the Map Enhancement interface could not establish local communication with its C# companion process, often before any remote imagery server was contacted.
Here, RPC refers to communication between parts of the application. It does not mean that a router port must be opened or that a private service should be exposed to the internet.
How do I fix sidecar error code 11?
The message 'C# sidecar exited before startup completed (code 11, signal null)' says that the sidecar ended before announcing its local endpoint. Code 11 is the process exit code in this message; without the build's documentation or log, it does not identify one universal cause. Signal null means no separate termination signal was recorded.
- Restart Windows. This clears duplicate helper processes and releases local endpoints held by an abandoned instance.
- Keep one complete installation. Delete obsolete extracted copies only after confirming which folder the shortcut launches. Do not mix a newer interface with older sidecar files.
- Check quarantine and application control. Confirm that security software has not blocked a documented companion component. Restore it only when its origin and identity are certain.
- Use a consistent privilege level. Start the application as its documentation directs. Running one component as administrator and another in a different security context can prevent local communication.
- Do not launch the sidecar manually. Let the main application start its companion process unless the release documentation says otherwise.
Do not download a standalone sidecar fix, install an unknown certificate or open router ports. Persistent code 11 failures with one verified package usually need the helper log and diagnosis from the add-on developer.
Can the hosts file or local proxy cause the error?
Yes. A stale hosts entry or stopped local proxy can send simulator requests to a local address where no helper is listening.
Use Map Enhancement's Restore or Reset function first. If manual inspection is unavoidable, the Windows hosts file is at C:\Windows\System32\drivers\etc\hosts. Back it up and remove only lines that can be positively attributed to Map Enhancement; never replace the entire file or alter entries belonging to other software.
If the helper says an address or port is already in use, close duplicate instances and restart Windows before changing any port setting. Another proxy or abandoned helper process may own the endpoint. After restoring the documented entries, flush the DNS cache and test default MSFS imagery with the helper closed.
What if the suggested settings are not present?
Map Enhancement controls and labels vary between releases, so an older guide may describe options that the installed build does not have.
Check the version and file location shown by the executable that is actually running. A missing Stop, Restore, cache or source control can mean either that the interface changed or that an old shortcut launched another copy. Do not substitute random file edits for a missing control; use the shutdown or removal method documented for that exact release.
Why is the scenery still blank after the error is gone?
Blank scenery after the connection recovers usually points to stale tiles, disabled online world data or an incomplete source response.
- Stop the helper and clear only its documented tile cache.
- Restart the helper and begin a new flight instead of resuming the failed session.
- Recreate the simulator rolling cache if old tiles remain.
- Confirm that MSFS online world data is enabled.
- Compare the same location with default imagery and another supported source.
If default imagery is also missing in MSFS 2020, use our steps for restoring Bing streaming, online data and rolling-cache behaviour.
Do I need to reinstall Microsoft Flight Simulator?
No. Reinstalling MSFS rarely repairs an unavailable provider, blocked helper, stale hosts entry or sidecar startup failure.
If normal streamed scenery works after Map Enhancement is stopped and its networking changes are restored, the simulator installation is functioning. If default MSFS 2024 streaming also fails, use our MSFS 2024 server-versus-local-network checklist to separate a simulator-wide service fault from this add-on error.
What if that did not help?
Escalate the problem when every supported source fails on two networks with one verified installation and default networking fully restored.
Record the following before reporting it to the Map Enhancement developer:
- the complete error text, including any private RPC, code 11 or signal null message;
- the selected imagery source and whether every other supported source failed;
- the Map Enhancement version and exact executable location;
- whether the simulator is MSFS 2020 or MSFS 2024, plus its installed build information;
- the result with default MSFS imagery and the result on a second network;
- the relevant helper log, but only when that release documents its location.
Do not upload credentials, unrelated personal files or hosts entries belonging to other applications. If one source alone fails, wait or use another supported source; if all sources fail with a repeatable sidecar error, the evidence usually points to a helper build or local startup problem rather than Microsoft Flight Simulator itself.