MSIX version tearing causes instability and crashes #13998

Open
opened 2026-01-31 03:58:04 +00:00 by claunia · 3 comments
Owner

Originally created by @miniksa on GitHub (May 27, 2021).

This bug represents a class of issues with the MSIX platform running mixed versions of our package at the same time. This violates fundamental assumptions of our code and causes instability and crashing in a variety of ways.
We are pursuing this issue internally with the MSIX platform, but this main bug will represent any other issues that get root-caused to this situation.

Originally created by @miniksa on GitHub (May 27, 2021). This bug represents a class of issues with the MSIX platform running mixed versions of our package at the same time. This violates fundamental assumptions of our code and causes instability and crashing in a variety of ways. We are pursuing this issue internally with the MSIX platform, but this main bug will represent any other issues that get root-caused to this situation.
Author
Owner

@miniksa commented on GitHub (May 28, 2021):

OOP COM Server object activation tearing - MSFT:33501832
AppExecutionAlias pointing to wrong version after upgrade (Old EXE running with new DLLs inside) - MSFT:31709999 - Resolved

@miniksa commented on GitHub (May 28, 2021): OOP COM Server object activation tearing - MSFT:33501832 AppExecutionAlias pointing to wrong version after upgrade (Old EXE running with new DLLs inside) - MSFT:31709999 - Resolved
Author
Owner

@zadjii-msft commented on GitHub (May 28, 2021):

Terminal - unable to find the selected font error at startup - MSFT:32337657 was also sorta related to this. That was the font bug that I think we tried working around. The workaround is now causing #10211. That's less about a torn state, and more about a botched upgrade.

@zadjii-msft commented on GitHub (May 28, 2021): Terminal - unable to find the selected font error at startup - MSFT:32337657 was also sorta related to this. That was the font bug that I think we tried working around. The workaround is now causing #10211. That's less about a torn state, and more about a botched upgrade.
Author
Owner

@miniksa commented on GitHub (May 28, 2021):

OOP COM Server object activation tearing - MSFT:33501832

This is being investigated internally, but this question was proposed internally. If anyone is seeing this and willing to capture this data, please let us know so we can connect you with the platform team investigators:

"If you encounter this can you export the contents of HKCU\Software\Classes\PackagedCom? I want to check the pattern against what I see on my machine."

@miniksa commented on GitHub (May 28, 2021): > OOP COM Server object activation tearing - [MSFT:33501832](https://task.ms/33501832) This is being investigated internally, but this question was proposed internally. If anyone is seeing this and willing to capture this data, please let us know so we can connect you with the platform team investigators: "If you encounter this can you export the contents of HKCU\Software\Classes\PackagedCom? I want to check the pattern against what I see on my machine."
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13998