For MSFS (as it stands today) should we be updating our Windows 10 to 2004, or try to maintain it at 1909 ??
I see reports of MSFS issues with 2004, (and I am still on 1909.)
My fear is that Windows 10 will automatically update one night, and I will be stuck with the new version that “may” have issues with MSFS
(Or more Precisely, MSFS has issues with 2004 )
Upgrade yes, no issues at all.
definitivly it will auto-update “somewhen” …
I have 2004… worst release ever… check all intel-drivers before, deinstall rapidstore-drivers e if not realy necessary for a raid-systems … and disable selective usb energy saving… then, with luck, your windows 2004 will not completly crash ( bluescreen ) or simple reboot randomly.
I needed lot of time and now it seems I won the fight to the bluescreens 
( just check some forums , some others poeples with AMD too have/had similar issues since 2004 )
thus… no issues with MSFS , but possible still issues with Windows 10/2004 itself…
Thanks for your input… will take it under advisement when I have more opinions to make a decision from.
“Edition Windows 10 Home
Version 20H2
Installed on 6/17/2020
OS build 19042.546
Experience Windows Feature Experience Pack 120.2212.31.0”
The above information is available at: Notifications/All settings/windows update/OS Build Info - System Info gives a different type of report.
This is what I’m running “Insider Preview Build Member”, and no problems. I run only Intel/Nvidia hardware, and buy the top of the line hardware when purchasing new. I used to build them (desktops) and always tried to be on the leading edge because the “desk life” is at least 18 months before technology just forces you to upgrade. But for 20+ years, built them, fixed them, tested them, Intel has stood the test of time and way less work in my opinion to get working, keep working.
No prob with 2004 here, on 5 computers, and no prob with MSFS.
same for me, no issues on 2004 with multiple pcs, one running msfs2020
Here also no problems with Win10Pro Version 2004 (Build 19041.546)
Am currently on 2004, have done one voluntary uninstall prior to Patch No. 2 (not problem related - I needed a break) and am back, updated to latest Patch in place, all stable. I’ve had two CTDs (checked Windows Application Log - they’re both the ones that can’t be troubleshooted because the faulting module points back to FS. Other than those two incidents, it’s been smooth flying.
I’ve been running 2004 since June, no issues here.
As I said…
2004 on all machines at work.
1909 on my flight sim machine.
Here’s a list of Known Issues
Your system should auto update if you are on the “safe list.”
I guess it’s not only Asobo that has a list of things to fix…
– At the moment, I do not leave my gaming machine running when I am not actively using it, and it is set not to update during the time I might be using it … so I “think ??” I am reasonable safe from an unexpected update,
There again, that’s a double edged sword … it also is not backing up every night either, like all my other devices do, (because it is OFF !!! )
Sounds like they’ll be removing the safeguard hold in the next few weeks…
I’m in2004 and no issues or crashes here. Keep VFR Map opened (minimized if you want)
Have had no issues with 2004 and even the insider dev build (I’ve since reverted back to preview builds on that pc) were all stable.
This is all great news! I’ve been holding off here at home; at work we’re all at Version 2004.
I just did this last week and had no problems
What I did for insurance was create a system drive image to a USB drive just in case I need to revert back
Have also got 2004 and haven’t had any ctd with the sim in normal game mode apart from the current issue with vfr maps but that is a known issue with the last sim update. Only ever had ctd with developer mode.
I very much doubt your any more likely to run into issue’s than you are with 1909.
I just purchased MSFS and my PC was at 1909. I could not download the app. It would error and give a meaningless (at least to me) error code. I was fortunate to get MS Support to help and was suggested to update to 2004. I did, and after that was able to download MSFS. So far (it’s been only one-day) MSFS is running ok.
