Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
What is - very - necessary when you re-install is that you run the 'Verify Integrity of Game Files' utility BEFORE you try to use or even start FSX so don't be tempted and run the utility to be 100% certain that the installation is ACTUALLY complete.
https://steamcommunity.com/app/314160/discussions/0/1813170373221711244/
Just take your time and be very meticulous paying attention to detail.
"The devil is always in the detail."
https://dovetailgames.kayako.com/knowledgebase/article/View/78/0/how-do-i-reinstall-microsoft-flight-simulator-x-steam-edition
I went thru the full process on the official Dovetail link. I also went through the verify integrity of game files, which was ok. started up the game and the problem still exists
Tell me what type and size of drives your rig has and I might come up with a better solution.
E.G.
I have a 500GB SSD with a 150GB partition for FSX SE and a 2000GB HDD for all documents, videos, drive images and other, very large files to keep them apart from the OS and other programs.
I have been using this layout for many years and it is largely trouble free.
You might have better luck installing to a partition IF there is something wrong with your installation which might be causing this to occur due to a conflict of some kind.
OTOH someone might come up with an easy solution.
I can't think of one offhand.
Joe
Hello Joe, and thank you,
Quite often, even with a new computer, the OS installation can be incomplete and therefore faulty.
The corporate policy here is to run the DISM commands followed by sfc /scannow immediately after the initial installation as three out of four new laptops were found to be faulty.
Not only that but, the four had different partitioning; one with six, two with seven and another with eight partitions.
To get them right I extracted all the OEM software and deleted all the partitions, including the OEM recovery partition, formatted the drives, and clean installed Windows 10 v1809 so that all four had just four partitions apiece.
Two weeks ago they were successfully updated to Win 10 v1903.
Next month I'll be taking out the 1000GB HDDs and replacing them with 250GB Samsung EVO SSDs as they only have i3 CPUs and take an age to reach the desktop.
Running disk cleanup took up to an hour, after updating to the latest version.
Good luck on getting the radio stack to show up again.
I done a windows 10 re-installation and it fixed the problem :)
Thanks again Joe.
That was fast work re-installing and all, in that space of time.
Nice job.