Flightgear 2020.3.13 on Windows 7

[FoxtrotCC]

Does Flightgear Windows 7 support ends with Flightgear 2020.3.13? When I install Flightgear 2020.3.13 on Windows 7 64 Bit and start it, the following Message appears:



With Flightgear 2020.3.12 everything is ok. Does Flightgear no longer supporting Windows 7?

Greets Foxtrot

[V12]

Download and install Win7 update from http://www.microsoft.com/download/detai ... 7b0a9ccc63
More info about update - https://support.microsoft.com/en-us/top ... 7930f3560c

[FoxtrotCC]

Thanks for your reply! Yes, I have installed the Win 7 CRT update KB2999226 (09/15/2015). Also the CRT Update KB3118401 (02/15/2016). But the message still appears.

KB2999226 (09/15/2015)
https://support.microsoft.com/en-us/topic/update-for-universal-c-runtime-in-windows-c0514201-7fe6-95a3-b0a5-287930f3560c

KB3118401 (02/15/2016)
https://support.microsoft.com/en-us/topic/update-for-universal-c-runtime-in-windows-322bf30f-4735-bb94-3949-49f5c49f4732

Greets Foxtrot

[V12]

Then I'm out od ideas

[wkitty42]

check your system and make sure you do not have another CRT dll file floating around that FG is finding before finding the one it really wants... especially check your FG install directory... i don't know the actual name of the dll file or i'd tell you exactly what to look for...

[FoxtrotCC]

I check the System the hole Sunday but I can´t find the issue. Again I make a clean install with Flightgear 2020.3.13. No way, Flightgear won´t start. Monitor the whole start with ProcessMonitor, but cant find any unusual behavior (But I am not an expert with these Tool). Check the Windows System with sfc and dism. Everyting is good. Install Flightgear 2020.3.12. No Problems. Then update Flightgear with Web Installer to V13. Flightgear wont start. Change Fgfs.exe from 2020.3.12 (save the bin directory before) to 2020.3.13. Flightgear starts (V12). Check both Bin directorys (12 & 13) with WinMerge. No missing DLL´s between the Versions. Maybe the compiler use an Library that don´t work for Windows 7? I am out of Ideas... But, ok, Win 7 is very is a very old System...

[wkitty42]

i've reported this to the mailing list... hopefully one of the devs will drop by shortly with more questions or suggestions...

[FoxtrotCC]

Thanks wkitty42!

[wkitty42]

the first reply from the mailing list is:

Delete ucrtbase.dll from C:\Program Files\FlightGear\bin\

but i thought you said you looked and didn't find anything in there to remove??

[FoxtrotCC]

Delete/rename/replace the urctbase.dll in the bin directory. Great! That works, now Flightgear 2020.3.13 start again!

I was looking for missing files, not for deleting files... Thanks to all!

Greets Foxtrot

[wkitty42]

yeah... i didn't exactly say to delete but that was the goal in this particular case... especially since the file being referenced was too old and your OS level updates should have fixed the problem... since they didn't, the problem must be FG finding the wrong file before it finds the right one... and OS level updates don't do anything with files outside of the OS directories... my apologies, i should have been more specific in my suggestion to look at the files in the FG installation directories to find the bad file(s)...

[FoxtrotCC]

Yes, Flightgear find an old reference Crt Dll in his own directory and use it. Imho this behaviour was absolute correct. First look in the own directory and then look at the search path. I didn´t know that the ucrtbase.dll was the key to all those Files and don´t look at it (and its date). So no problem, you/we all find a working solution! Great!

[wkitty42]

yes, FG was correct in what it was doing looking first in its install directory... the problem was the packaging error that included ucrtbase.dll in the first place... it has been there for a while and only just recently discovered as a problem... the installation of 2020.3.13 was also supposed to remove it from the install directory but something went awry there and is being looked into so it can be truly fixed in the future...

thank you for posting about your problem and bring it to our attention

[agnasg]

Hello, just to inform everybody this problem also happens in Windows 8.1 and the solution is the same, remove/delete/replace/rename the file urtbase.dll from the Flightgear bin folder, and you will be very happy!