Cannot launch due to: "Here’s the error code, in case you need it: 0x87E10BC6"

Same here. MS Store Windows 11.

It’s something almost every week lately…Oh well.

5 Likes

No need to on this one as it’s already being investigated.

1 Like

a bit of an embellishment on the Half Million PC remark! This will get worked out, hopefully soon, but it is nice to know it is being confirmed and looked into. Probably a faulty upgrade push that was due out. A little fix of the code and all will be well.

1 Like

All will be well… Quando, Quando, Quando Quando…

1 Like

Im also on windows 11

“Maybe tomorrow… maybe someday…”

2 Likes

Same in Canada …

1 Like

This issue is not helping to get the A330 out to us any faster

That wouldnt suprise me in the least. It most likely is something really minor and got over looked. It is usually the simple things that slip by the programmers eyes.

I am new here and did not realize that sarcasm got automatically flagged and hidden by the forum. A very harmless post that contained no swearing or mature content. Yet I see other topics in this forum where people are criticized for not having a “proper gpu or specs” and no one (or computer) intervenes.

Yeah, it’s ironic to have a Mac user complain about hardware pricing. :grin:
Especially an IT person that, in the same breath, comments on how no Mac product offers the same visual fidelity.

Nevertheless, reliable CDN (Azure) and authentication services seemingly should be core competencies for a large cloud provider, right?

1 Like

At very least the error message is a slight improvement on past error messages.

Instead of putting the problem on the user, it admits the problem is on “our end” (ie, MS / Asobo) and provides an error code.

I would recommend adding some reassurance and useful info such as, “You don’t need to troubleshoot, the issue has been reported to Microsoft, and you can find status updates on forums dot flightsimulator dot com”

2 Likes

Same in Brazil

The sim works OK for me. Just made a short flight.

PC, Steam version, no Beta, Windows 10

There are well informed rumors, telling it was a cleaner who tripped over a wire in the MSFS server room and nobody noticed so far which wire to plug back in.

2 Likes

YOOO Chile gang

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

yes

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

Log Name: Application
Source: Windows Error Reporting
Date: 2/22/2023 7:41:09 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: DESKTOP-AUA78NV
Description:
Fault bucket 1732471290321938094, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: AcPowerNotification.exe
P2: 1.0.5.14
P3: fca0c742
P4: PresentationCore
P5: 4.8.9139.0
P6: 63997485
P7: 1b70
P8: 1c
P9: System.ArgumentException
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.23d645fa-bbc8-4828-8329-bc021c6dde77.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9cc88af6-d4be-4680-951e-7c5016455c7d.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.66b6e1d8-599d-4c32-aa34-d63b15b854c1.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f34bd626-2f7a-403c-a1a9-55877e37aa60.tmp.txt
\?\C:\Users\seraf\AppData\Local\Temp\WER.9ac1ab20-e621-46d3-9861-83b950d98ca7.tmp.appcompat.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.359e31c8-ca2e-49fa-87d4-2b8694295e43.tmp.xml

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_AcPowerNotificat_d148c8c02a6e479f55b9a2d91ec8d2b8e02274af_e634ccd8_2fbc0530-3b9d-4165-a496-feccff48e2c5

Analysis symbol:
Rechecking for solution: 0
Report Id: 46abff8a-c5eb-4e18-a3e6-8e2245d8d2f4
Report Status: 268435456
Hashed bucket: 3ee1ef4baea0f8a5280af975a333a6ae
Cab Guid: 0
Event Xml:



1001
0
4
0
0
0x8000000000000000

9979


Application
DESKTOP-AUA78NV



1732471290321938094
5
CLR20r3
Not available
0
AcPowerNotification.exe
1.0.5.14
fca0c742
PresentationCore
4.8.9139.0
63997485
1b70
1c
System.ArgumentException



\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.23d645fa-bbc8-4828-8329-bc021c6dde77.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9cc88af6-d4be-4680-951e-7c5016455c7d.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.66b6e1d8-599d-4c32-aa34-d63b15b854c1.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f34bd626-2f7a-403c-a1a9-55877e37aa60.tmp.txt
\?\C:\Users\seraf\AppData\Local\Temp\WER.9ac1ab20-e621-46d3-9861-83b950d98ca7.tmp.appcompat.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.359e31c8-ca2e-49fa-87d4-2b8694295e43.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_AcPowerNotificat_d148c8c02a6e479f55b9a2d91ec8d2b8e02274af_e634ccd8_2fbc0530-3b9d-4165-a496-feccff48e2c5


0
46abff8a-c5eb-4e18-a3e6-8e2245d8d2f4
268435456
3ee1ef4baea0f8a5280af975a333a6ae
0

If relevant, provide additional screenshots/video:

The Steam version isn’t affected by this. Only MS Store and Xbox consoles.

4 Likes

So how are the forum servers holding up now since we can’t play :wink:

1 Like

We shall now all fly vicariously through you. We will tell you what to do and you’ll report back what you see. Sounds good? :crazy_face:

1 Like