MSFS2020 Crashes to Desktop before opening simulator in Windows 11 steam

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

NO

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

Yes with and without community folder

Brief description of the issue:

Game is on F SSD drive and works when using M2 nvme with Windows 10. When using other M2 mvme with Window 11 it crashes on desktop at about 90% load

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version (Learn how to find your current graphics card driver version):

ALL DRIVERS UP TO DATE

PC specs and peripheral set up:

Windows 11, gpu 3080, CPU i7-13700,

If on PC, Fault Bucket ID - Instructions [here]
(How to find your Fault Bucket ID after a crash [PC]) - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:
1326424845907649988, type 5

Build Version # when you first started experiencing this issue:

suddenly started to crash on desktopafter a Windows 11 update that freezed so I had to restart with power button


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Have started new steam install (partial instal see: https://www.youtube.com/watch?v=S4wbHxPhGvU - copied saved content of official folder i of steam Library.

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons: