[Problem] MPF 2.4-1033 NET 6.0 x64 just shuts down #499

Closed
opened 2026-01-29 16:17:27 +00:00 by claunia · 4 comments
Owner

Originally created by @Ragowit on GitHub (Feb 25, 2023).

Originally assigned to: @mnadareski on GitHub.

Version

  • WIP release (2.4-1033 NET 6.0 x64)

Build

  • .NET 6.0 running on Win 11, 22H2

Describe the issue
MPF just shuts down when I try to start it. WIP MPF 2.4-1033 NET 4.8 works just fine.

To Reproduce

  1. Double click the MPF.exe
  2. See the MPF window for a brief second before it shuts down.

Expected behavior
MPF window to stay open

Originally created by @Ragowit on GitHub (Feb 25, 2023). Originally assigned to: @mnadareski on GitHub. **Version** - [x] WIP release (2.4-1033 NET 6.0 x64) **Build** - [x] .NET 6.0 running on Win 11, 22H2 **Describe the issue** MPF just shuts down when I try to start it. WIP MPF 2.4-1033 NET 4.8 works just fine. **To Reproduce** 1. Double click the MPF.exe 2. See the MPF window for a brief second before it shuts down. **Expected behavior** MPF window to stay open
claunia added the bug label 2026-01-29 16:17:27 +00:00
Author
Owner

@mnadareski commented on GitHub (Feb 26, 2023):

Partially addressed as of 2a544676e6

This is more of a temporary mitigation than anything. Still investigating otherwise.

@mnadareski commented on GitHub (Feb 26, 2023): Partially addressed as of https://github.com/SabreTools/MPF/commit/2a544676e6288ebf0ae1ad7f41f7046da8cda8f8 This is more of a temporary mitigation than anything. Still investigating otherwise.
Author
Owner

@mnadareski commented on GitHub (Apr 25, 2023):

The culprit, after a lot of debugging was Microsoft.Management.Interface. Interestingly, it would function perfectly fine if I didn't run dotnet publish, so local runs would all succeed. The issue stemmed from how MMI decided to bundle its native DLLs, that is, by much more specific runtime identifiers. Because of that, I have decided to move to the more granular runtime identifiers across the board. These changes are reflected in b428bc0ba0

Please try out the AppVeyor build that corresponds to your system and please report back.

@mnadareski commented on GitHub (Apr 25, 2023): The culprit, after a lot of debugging was `Microsoft.Management.Interface`. Interestingly, it would function perfectly fine if I didn't run `dotnet publish`, so local runs would all succeed. The issue stemmed from how MMI decided to bundle its native DLLs, that is, by much more specific runtime identifiers. Because of that, I have decided to move to the more granular runtime identifiers across the board. These changes are reflected in https://github.com/SabreTools/MPF/commit/b428bc0ba0573d86cb85211227d4b0513cdddcb2 Please try out the AppVeyor build that corresponds to your system and please report back.
Author
Owner

@Ragowit commented on GitHub (Apr 25, 2023):

I tried win10-x64 (1107) on my Win 11 22H2, and it works lovely! Did a verification with it as well: http://forum.redump.org/post/108988/

It did however choose DVD for my PS3 disc, but that is probably another issue.

Also, I believe you can revert 2a544676e6

@Ragowit commented on GitHub (Apr 25, 2023): I tried win10-x64 (1107) on my Win 11 22H2, and it works lovely! Did a verification with it as well: http://forum.redump.org/post/108988/ It did however choose DVD for my PS3 disc, but that is probably another issue. Also, I believe you can revert https://github.com/SabreTools/MPF/commit/2a544676e6288ebf0ae1ad7f41f7046da8cda8f8
Author
Owner

@mnadareski commented on GitHub (Apr 25, 2023):

I'm counting this as fixed, then. I'll definitely go back to single file as soon as I can since that wasn't the actual issue.

@mnadareski commented on GitHub (Apr 25, 2023): I'm counting this as fixed, then. I'll definitely go back to single file as soon as I can since that wasn't the actual issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SabreTools/MPF#499