Odd Goings On

falcon409

Moderator
Staff member
I have a new error when launching MSFS. This one is easily correctable but repetitive with each subsequent launch attempt.

The first launch of the day (via the XBox App) goes as it should. Later on I go to launch again and the error appears. . .soooooo, I bring up the Task Manager and select the XBox App and "end task", do the same for Gaming Services. Close the Task Manager and go back to the XBox App and the launch goes normally. From that point on, if I close the Sim and go back to do another launch the results and the "corrective Action" are the same.

I have updated the App when necessary and used the Gaming Services troubleshooting tool as well. It works for one Launch then the error is back thereafter. Thankfully I can fly as much as I want but I must run my little "Fix-It" to get all the stars to align so I can get off the ground!
 
Sadly, once this kind of stuff happens, the best solution is just backing up everything important, formatting the boot drive, and reinstalling Windows from scratch. Sucks that nearly 30 years after Windows 95 that’s still the case, but when I did that earlier this year, it was like having a brand new PC. (And not just because I had to reinstall everything. :) ) If your MSFS data is on a second drive (or backed up/restored), you only have to reinstall the base sim and point it back to that folder.

Glad you found a workaround for now, though!

1732482108677.png
 
There is easier than reinstalling Windows to every big problem.

As far as I am concerned, I have installed Windows (Windows 7 Pro => Windows 10 Pro upgrade), the main applications and drivers for the devices.
Then I made a "clone" of my system disk with Marcium Reflect launched from a USB drive with a Windows10 that loads in RAM memory.
My C:\ use 60 Go. The time to start Windows from the USB key and deliver the last backup is about 10 minutes

The majority of applications are installed as portable applications when I can and on separate disks from disk C:
FS20 and FS24 are on separate SSD (F:\ and I:\)
 
Yeah, but if you don't have a clone of the pre-hosed system...

Lagaffe's technique is great if you create a clone right after setting things up.
 
I noticed (of course I never actually read the entire error message) that the error message suggests closing the app and retrying. In every instance now that's what I do. If I don't get a good launch at first I just close the app, reopen and launch as normal. Reloading Win11 wouldn't work as I upgraded recently from Win10 Pro which was already loaded when I got the computer so I don't have a working copy of either OS.
 
I think motherboards have a license burned into them now. You can also get your current license via command prompt with elevated privileges. Run the command prompt as an admin, then enter the following:

wmic path softwareLicensingService get OA3xOriginalProductKey

After a second or two, you'll get your 25-digit license code that you can copy/paste into a text file or simply print.

Thank you Google!
 
After a second or two, you'll get your 25-digit license code that you can copy/paste into a text file or simply print.

Thank you Google!
lol, Tom this is what I got back after typing that command string. . . .
"OA3xOriginalProductKey"
 
Interesting... I get your results on my big box, but my laptop gives me a code. I'm guessing then that the motherboard may have the key embedded. Not sure...
 
I was able to find that my activation was done with a digital license linked to my Microsoft Account
 
Interesting... I get your results on my big box, but my laptop gives me a code. I'm guessing then that the motherboard may have the key embedded. Not sure...
I think that, if and when you have an OEM license, and log in for the first time with your Microsoft account, then that replaces the activation key. On the other hand, if you do like I always do and do not use a Microsoft account (they know enough of me already!), then only the key will activate windows.

If you've bought a copy from a shop or from M$ directly, then it is the key that will handle the activation. A bit like at work, only at work, we use MAK's (multiple activation keys).

Cheers,

Priller
 
Back
Top