cgbart

Oops...11:39pm and saw your post about this...sorry! but went right to answering. Maybe someone else can try this. If I see anything else, I'll post here.

Frank, here is the fix: to resolve this issue, try reinstalling the Gaming Services app on your Windows 10 device: Right-click the Start button  in the lower-left corner of the main screen, and then select Windows PowerShell (Admin). In the Administrator: Windows PowerShell screen, type the following command and press Enter: Get-AppxPackage *gamingservices* -allusers | remove-appxpackage -allusers In the same window, type the following commands and press Enter: Remove-Item -Path "HKLM:\System\CurrentControlSet\Services\GamingServices" -recurse Remove-Item -Path "HKLM:\System\CurrentControlSet\Services\GamingServicesNet" -recurse Restart your device. Right-click the Start button  in the lower-left corner of the main screen, and then select Windows PowerShell (Admin). In the Administrator: Windows PowerShell screen, type the following command and press Enter: start ms-windows-store://pdp/?productid=9MWPM2CQNLHN Install the app on that page, and then select Yes when you receive the User Account Control (UAC) prompt. Try to install or launch the game again. Hope this helps you and anyone else with same issue...solved my startup!

Frank, as a fellow meteorologist (not in the position anymore though) I'll be glad to help unless someone beats me to it. I have the fix back home on the desktop and later this afternoon when I get home I'll share with you and the community. You need to un-install a windows app and re-install....that's it. No major surgery. Will post later to this thread.

Over the years with Win10 if I've learned anything, I've learned that even though your account may be at administrative level, you should still (if you know the app is from a reputable source) choose the option to "run as administrator" ! Many smooth installs using that thinking.

All, Read the following and take note: https://wccftech.com/nvidia-hints-at-rtx-3080-graphics-card-with-20gb-memory I'm in the same boat and waiting so to speak.

Ian, Managing many (~300) desktops running 1909 and 2004, I have learned that every update before 2004 must be run first. Attempt to do a check for updates and be absolutely sure that you have run every update. Try that first and let us know. Best of luck... Chris

As a general rule, MS should concentrate on the main engine and provide simple ATC and AI for users to start with. The SDKs should provide for third parties to let the program shine for those that wish to have more accurate traffic and ATC. They (MS) probably can't do everything in the time frame provided. With that said, some of the better third party applications can then expand upon the controller concept. Win win situation for all involved!

I find it hysterical how a discussion about some possible tech aspects of a new flight simulator always leads to drama and hysteria! Enjoy the teases out of MS, read the updates and go for the ride and hope for the best! Chris

Tony, Please try this...remove power plug from PC and press the on button to discharge the M/B and capacitors. Then plug back in and restart. If it starts and runs OK, it's most likely the main board. Also make sure you have a fresh battery on the mainboard. Sounds like the M/B or maybe power, but most likely the M/B. To make life easy, get another exact same board and swap out to allow system transparency.

Many years ago I was fortunate to attend multi-day seminars in Boston at Harvard hosted by John Donovan discussing the three-tiered approach to computing. Back-end servers, middle-layer processing and front-end presentation. This in effect is what I believe will be the approach as you have spelled out, as well as a previous post describing Azure processing in the background as we reap the benefits of flying in a very realistic world. Interesting to see what comes about. My feeling is that this will be an Ala-carte solution based on the amount of data to be made available. We'll wait and see. Exciting times ahead! Chris

Sorry for the late reply as I just saw this, but if I can help others with the same problem, so be it..... I too have had this issue for quite some time. Appeared out of nowhere one day on my Win10 ver1809 build. I ctrl-alt-del and shut down the instance of FSX running then restart it again and have no issues for that session from then on. I run nothing out of the ordinary that isn't mainstream here and keep my system at peak performance, even though I still run an Intel 2500K and a FTW1070 for graphics. Sorry you had to rebuild, but at least problem solved for you.

Rob, Try this site...I use it for trying different combinations of hardware before I "dream" of my new system.....http://thebottlenecker.com/#home Interesting results often times. Regards.....Chris

TrentXWB, As an answer to your original question, and a clarification, if you are adding then get the F4-3200C14D-16GVR and not the 32GVR. The 32GVR set is 32gig in 2 or 4 sticks. The 16GVR is 2 8 gig sticks that can be added in the spare slots, as long as your M/B comes with 4 memory slots! Everything else that other members said about quantity of memory is still valid. 32gig will help if using the PC especially for photo or video applications, etc... Hope that helps.

Tom, Experienced same if not similar until I found out it was my video cable...went from a display port to an HDMI (did not have a dual DVI) and have never had the problem again. Hope this helps as it was quite frustrating as well. FYI... this was on a P68 board running an i5-2500K and an AMD card. Now using a FTW1070. Chris

I'm in a similar situation with an i2500K. Waiting to pull the trigger on new hardware real soon but as a reference for bottlenecks I use http://thebottlenecker.com From what I have seen, the bottleneck with your updated system would be the m/b and cpu running such a high-end gpu. Even my system running a EVGA FTW1070 gets a 30% bottleneck because of my motherboard, an ASRock P68 and the i2500K. BUT...my FSX is still stutter free. I fly the QW 757 with lots of ORBX, UTX NA and AS16 on SSDs, not mechanical HDs. Regards