That’s the bit that makes no sense.
If you use the sim, turn the computer off for 5 minutes, restart the PC, and the sim launches fine, then that 5 minutes may as well be six months from the computers perspective as nothing has changed except the time.
Identifying what, and if, something is getting refreshed would be relevant. The Internet has to be used to update the sim to current versions, so at some point that has to happen.
If it were just a power issue, then the setup shouldn’t work at all, no matter how short a time between sessions they were left off.
If it weren’t for the fact that it sometimes works, and works offline, I would have suggested it could be a networking issue, and possibly there is an issue with seven machines on the same network trying to launch MSFS, behind the same NAT router.
@FAVEB What happens if you fire up one system in isolation, get it to the main menu, then start the second, and so on?
It would also be worth knowing what the error message is in the event log.
This PowerShell command will give you a list of all relevant events, essentially where FlightSimulator.exe has generated an event with id 1000, and print out the date stamp, so we could see how often this occurs, as well as the related message, which will show the exception code.
(Get-EventLog -LogName Application -InstanceId 1000 | Where-Object {$_.Message -like "*Flightsimulator.exe*"}) | select-object TimeWritten,Message | fl *
I don’t have MSFS installed here at work, but this is what I see if I change the command to look for Chrome. You will see there were two occurences, both with code “0xc0000005”:
TimeWritten : 26/09/2023 12:56:37
Message : Faulting application name: chrome.exe, version: 116.0.5845.188, time stamp: 0x64fb8b6a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000180001444
Faulting process ID: 0x5790
Faulting application start time: 0x01d9e7b965829d5e
Faulting application path: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Faulting module path: unknown
Report ID: fb6c2eb9-b379-43b7-822a-6b5117a24120
Faulting package full name:
Faulting package-relative application ID:
TimeWritten : 26/09/2023 12:56:35
Message : Faulting application name: chrome.exe, version: 116.0.5845.188, time stamp: 0x64fb8b6a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000180001444
Faulting process ID: 0x3c90
Faulting application start time: 0x01d9e7b91fab8338
Faulting application path: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Faulting module path: unknown
Report ID: 9bc9e5d6-602a-4e07-972c-90c6242cadd7
Faulting package full name:
Faulting package-relative application ID:
``
