{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
5/31/2020 11:45:22 PM
6
Hi there!
Can you please provide your system specs? Also, you should run the system file checker utility in command prompt. Do NOT do this while Destiny 2 is running.
1. Open a Command Prompt as an Administrator
2. Type 'sfc /scannow'
3. Allow the process to run. This may take a few minutes
Please reply with the results.
English
-
I have the same issue, I suspect it's due to the fast ring windows 10 insiders build. Running sfc /scannow shows no corruption.
-
If you are running the 2004 version, then yes, it's probably best to roll back as there are several known issues with that version in general.
-
I have same issue, running on Windows 10 2004. This is a major W10 release, rollback is not a solution
-
You do have the capability to roll back major Windows 10 releases. Go to Settings, then go to Update & Security, then click on Recovery. There should be an option to uninstall the 2004 version. This will roll you back to the last Windows 10 version you are on. This option should be available for 10 days, according to the Microsoft Knowledgebase articles I'm flipping through.
-
I realize that it is possible to rollback, but that is not a solution, that’s a workaround. 2004 is official release and bug with chat should be addressed
-
Bearbeitet von RurouniDante: 6/3/2020 11:50:50 PMThe error code reported by the OP points to a specific issue with a Windows module. While the 2004 version is an official release from Microsoft, it has been held back for most devices due to a number of known issues with a multitude of drivers and applications. This could very well be one of these issues, or a different problem stemming from a known issue. If you had to apply the update using the Media Creation or Update Assistant, then it is highly likely that your machine was one of the machines that could've been affected by these known issues. I have never stated that this was a solution. However, as part of the troubleshooting process, you should be able to roll that update back and see if the issue persists. Due to the number of known issues with this current release, I would roll back and see if the crash issue is resolved.
