March 11, 20233 yr So after 2 years of faultless operation my trust in the MSFS store version has been betrayed by a requester coming up after the "signing in" and "checking for updates" phases, saying "Something went wrong launching your game - Error code: (0x80004005)" and the program exiting. Interestingly in the xbox app the program shows up with a frown-face icon instead of the play button. Did all the stuff I read about, such as updating xbox/store, logging out an in again, repairing the app and dism/sfc. Still the same. However the program runs fine if run as an administrator, I didn't even lose my settings. So it's clearly a permissions issue and all the files are still there and intact. However I'm not keen on running as admin, particularly if an update has to be installed (what permissions will the new files have?) Anyone seen this before and/or have any suggestions? If not I'm probably up for a reinstall before SU12 drops (I'm not on the beta).
March 11, 20233 yr I've personally never seen that problem. But if your files are intact and MSFS is working fine for you, then I wouldn't worry about having to run MSFS as administrator. I think the PMDG Operations Center used to (or still does) require that as well. I doubt that Microsoft is going to include any files in future sim updates that affect anything outside MSFS. Remember that your Windows operating system is a Microsoft product as well. So I personally wouldn't bother reinstalling the entire sim just because it wants to be run as administrator. Processor: Intel i9-13900KF 5.8GHz 24-Core, Graphics Processor: Nvidia RTX 4090 24GB GDDR6, System Memory: 64GB High Performance DDR5 SDRAM 5600MHz, Operating System: Windows 11 Home Edition, Motherboard: Gigabyte Z790 Aorus Elite AX, LGA 1700, CPU Cooling: Corsair H100i Elite 240mm Liquid Cooling, RGB and LCD Display, Chassis Fans: Corsair Low Decibel, Addressable RGB Fans, Power Supply: Corsair HX1000i Fully Modular Ultra-Low-Noise Platinum ATX 1000 Watt, Primary Storage: 2TB Samsung Gen 4 NVMe SSD, Secondary Storage: 1TB Samsung Gen 4 NVMe SSD, VR Headset: Meta Quest 2, Primary Display: SONY 4K Bravia 75-inch, 2nd Display: SONY 4K Bravia 43-inch, 3rd Display: Vizio 28-inch, 1920x1080. Controller: Xbox Controller attached to PC via USB.
March 11, 20233 yr I began getting that every time, when I upgraded my game-ready Nvidea drivers. I couldn't find any option to roll them back, so I loaded the Studio drivers, and they seem to work ok.
March 26, 20233 yr Author For the record, the latest on this is that installing the SU12 update has fixed the issue. Thanks to those who contributed suggestions. Edited March 26, 20233 yr by lzamm
Archived
This topic is now archived and is closed to further replies.