No, you don't need to uninstall MSFS. It won't help if that host file is the problem.

The google map mod erases the lines that don't begin with # if you when you exit MSFS the proper way. If you exit MSFS by clicking the X in the window or something like that the host file (which is a windows file, not a FS file) keeps those line and does not erase them. You will never get MSFS to run if the host file is not a proper one.

My MSFS is already uninstalled ...

Once the file name host is correct, then MSFS will probably boot. It makes no difference which you do first, reinstall windows or fix the host file. It can be done in either order, can do either one first.

If you go to the file named host (the name of the file is just host, it is not host.xxx), it is a simple text file and can be read in windows notepad. If there is a line at the bottom of the file that does not begin with # then that was and still is your problem. If all lines begin with #, then that was not your problem at all and still is not your problem.

The google mod adds those lines whenever you boot up MSFS. And the google mod takes them back away again if you exit Windows properly. If you exit windows improperly, then MSFS will never start again until you erase the lines yourself in notepad. Once the improper lines are erased, MSFS will boot up fine.

 

 

 

 

 

15 hours ago, Beardyman said:

Yes, i have used Google mod, but what do u mean'check your host' ? - what and where shall i check ?

Sorry, it was late and didn't mean to abandon you.  I guess if you had used the mod I assumed you had read the documentation and knew what the host(s) was and where it was located.  Being confident this was your issue, I'm glad someone else came to your rescue.

15 hours ago, abrams_tank said:

Wow, that Google mod has caused so many problems for so many people.

A matter of semantics, but the mod works fine and doesn't cause the issue - it's operator error where people don't fully understand how to use it successfully or back out of it.  Personally, I haven't felt compelled to even try it as the benefits don't seem worthy of any potential issues.  I'm perfectly happy with a nice simple sim. 

5 hours ago, irocx said:

Sorry, it was late and didn't mean to abandon you.  I guess if you had used the mod I assumed you had read the documentation and knew what the host(s) was and where it was located.  Being confident this was your issue, I'm glad someone else came to your rescue.

A matter of semantics, but the mod works fine and doesn't cause the issue - it's operator error where people don't fully understand how to use it successfully or back out of it.  Personally, I haven't felt compelled to even try it as the benefits don't seem worthy of any potential issues.  I'm perfectly happy with a nice simple sim. 

 

9 hours ago, Fielder said:

Once the file name host is correct, then MSFS will probably boot. It makes no difference which you do first, reinstall windows or fix the host file. It can be done in either order, can do either one first.

If you go to the file named host (the name of the file is just host, it is not host.xxx), it is a simple text file and can be read in windows notepad. If there is a line at the bottom of the file that does not begin with # then that was and still is your problem. If all lines begin with #, then that was not your problem at all and still is not your problem.

The google mod adds those lines whenever you boot up MSFS. And the google mod takes them back away again if you exit Windows properly. If you exit windows improperly, then MSFS will never start again until you erase the lines yourself in notepad. Once the improper lines are erased, MSFS will boot up fine.

 

 

 

 

 

Irocx & Fielder - happy to report that thanks to ur help my sim works well again.

Indeed i had some extra lines in pointed area.

Much appreciate, u are valuable members of this community ! 👍

I had to learn this myself back when first trying out the google map mod.

And I had no clue why your MSFS did not boot until Irocx posted about the google mod. I figured yep that had to be it.

For the record, I had a similar failure to start recently. It would get past the checking for updates screen and move on. 15 seconds later it would CTD.

I went thru these official MSFS failure to start 1-8 steps, but it did not help.

https://flightsimulator.zendesk.com/hc/en-us/articles/4406039624338-All-versions-Loading-issues-Checklist

 

Step 9 is 'return sim to vanilla state' and that cured the problem.

link to return to return to vanilla sate info (step 9):

https://flightsimulator.zendesk.com/hc/en-us/articles/4408886545938

The first thing was 1 to rename community forum (I had already done that).

2. Remove peripherals did not help.

The next thing was 3. UNINSTALL FREEWARE, PAYWARE, AND PERIPHERALS

I followed instructions, wen to the Official folder where I sorted folders by date, and deleted the top folders (latest folders) which were fs-base-nav, the BEE GEE racer, the G1000 gps, and Fokker Vii folders, all 4 of which which came with the Sim Update 9 and the purchase of the Bee Gee the same day.

At that point MSFS would boot up fine, checking for updates restored fs-base-nav and content manager restored the BG racer, G1000, and the Fokker Vii

So anyway, the 2 links above by MSFS/Asobo help desk did the trick. Had I not done all that, then probably verify MSFS on steam would have done the same thing but would have been slower to reinstall the whole sim instead of just few little folders.

 

 

Edited April 29, 20224 yr by Fielder