This is the error I get.
Since it’s a Breakpoint I assume there is some left over error catching going on that they forgot to take out?.
ox80000003 Errors ← Link
I have also suddenly started to get these, in the last 2 weeks, when I very seldom ever use to.
Prior to the two in the past 2 weeks, the only other time I have had this in 2023, was back on Oct 30th with an earlier SU ? (or maybe SU14 beta )
He’s not having a 0x00000003 error, I don’t think. It’s 0x80000003.
My bad, I forget the leading 8 . will correct my posting errors with an edit
#####################################
REPAIR
#####################################
C:\Windows\System32>Dism.exe /online /Cleanup-Image /CheckHealth
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.2861
No component store corruption detected.
The operation completed successfully.
C:\Windows\System32>Dism.exe /online /Cleanup-Image /ScanHealth
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.2861
[==================100.0%=================]
No component store corruption detected.
The operation completed successfully.
C:\Windows\System32>Dism.exe /online /Cleanup-Image /Restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.2861
[================100.0%=================]
The restore operation completed successfully.
The operation completed successfully.
C:\Windows\System32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Windows\System32>Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.2861
[===========================99.4%========================= ]
Component Store (WinSxS) information:
Windows Explorer Reported Size of Component Store : 14.12 GB
Actual Size of Component Store : 13.52 GB
Shared with Windows : 7.09 GB
Backups and Disabled Features : 4.43 GB
Cache and Temporary Data : 1.99 GB
Date of Last Cleanup : 2023-12-12 21:54:07
Number of Reclaimable Packages : 1
Component Store Cleanup Recommended : Yes
The operation completed successfully.
C:\Windows\System32>Dism.exe /Online /Cleanup-Image /StartComponentCleanup
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.2861
[===== 10.0% ]
[===================100.0%=================]
The operation completed successfully.
— FINISHED -----
It FIXED something !!! I will watch with interest to see if that stops the errors ?
1 Like
I will try this. This is a freshly formatted and Win11 install.
Actually, all the more reason to run ALL those integrity tests, after a fresh install, or a image restore,.
They will often find errors in a FRESH install, as well as errors after windows updates.
I run those test once a week, and often they will find at least one thing to fix… AS IT DID ABOVE
C:\Windows\System32>Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792Image Version: 10.0.22631.2861
[===========================99.4%========================= ]
Component Store (WinSxS) information:
Windows Explorer Reported Size of Component Store : 14.12 GB
Actual Size of Component Store : 13.52 GB
Shared with Windows : 7.09 GB Backups and Disabled Features : 4.43 GB Cache and Temporary Data : 1.99 GBDate of Last Cleanup : 2023-12-12 21:54:07
Number of Reclaimable Packages : 1
Component Store Cleanup Recommended : YesThe operation completed successfully.
MSFS does not have the Monopoly of flakey updates !!
1 Like
Found stuff … thanks
Microsoft Windows [Version 10.0.22631.2861]
(c) Microsoft Corporation. All rights reserved.
C:\Windows\System32>DISM /Online /Cleanup-Image /CheckHealth
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.2861
No component store corruption detected.
The operation completed successfully.
C:\Windows\System32>DISM /Online /Cleanup-Image /ScanHealth
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.2861
[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.
C:\Windows\System32>Dism.exe /online /Cleanup-Image /Restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.2861
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
C:\Windows\System32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
C:\Windows\System32>Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.2861
[===========================99.5%========================= ]
Component Store (WinSxS) information:
Windows Explorer Reported Size of Component Store : 13.88 GB
Actual Size of Component Store : 13.29 GB
Shared with Windows : 8.80 GB
Backups and Disabled Features : 3.88 GB
Cache and Temporary Data : 605.13 MB
Date of Last Cleanup : 2023-12-12 13:02:01
Number of Reclaimable Packages : 1
Component Store Cleanup Recommended : Yes
The operation completed successfully.
C:\Windows\System32>Dism.exe /Online /Cleanup-Image /StartComponentCleanup
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.2861
[===== 10.0% ]
[==========================100.0%==========================]
The operation completed successfully.
C:\Windows\System32>
Unfortunately … still having the crashes.
Not sure if related or not but all of a sudden the last two flights I tried froze while passing 20,000 feet.
But probably less going forward, than you would have had, if you had not run those repair tools. 
1 Like
Make sure to reboot the PC after running those commands.
Go through each of the following steps one at a time. Copy each line, one at a time , paste it into the Dos window (crtl + V) and press return
and it will then run. Wait until each runs and finishes before you move on to the next one.
When you are completely finished, Restart your computer and then try to see in MS2020 will start and run properly
Dism.exe /online /Cleanup-Image /checkhealth
Dism.exe /online /Cleanup-Image /scanhealth
Dism.exe /online /Cleanup-Image /Restorehealth
sfc /scannow
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
Dism.exe /Online /Cleanup-Image /StartComponentCleanup
RESTART your computer as the last step. Then go for a test flight.
1 Like
Did you figure the issue out I’m having the same problems happen