Hello @Halifax Crosby ,
To allow your MSIX packaged app to run as Administrator, you might want to consider combining both of the manifest modifications you mentioned. From my understanding, you would first need to add the <rescap:Capability Name="allowElevation" /> restricted capability to your Package.appxmanifest, and alongside that, it seems you also need to keep the <requestedExecutionLevel level="requireAdministrator" uiAccess="false" /> in your WinForms app.manifest so that the UAC prompt can be successfully triggered.
Regarding your question about Store acceptance, it is generally unlikely that an app forcing elevation on launch will pass the standard certification. The allowElevation capability is heavily restricted, and as noted in the App capability declarations documentation, such submissions are usually subject to very strict review criteria. If you believe your system app has a strong justification, you could try emailing reportapp@microsoft.com for pre-approval before submitting it to the Store.
Alternatively, if Store publication becomes a hurdle, there are a couple of other approaches you might explore. For instance, Microsoft often suggests splitting the application by keeping the main UI in user mode and moving only the specific admin tasks into a secondary executable or service. On the other hand, if keeping it as a single EXE is required and Store distribution is not mandatory, you might look into granting identity to non-packaged apps. This approach allows your classic WinForms executable to retain MSIX features like modern APIs while still running outside the strict container, making it easier to require admin rights.
I hope this points you in the right direction! If you found my response helpful or informative, I would greatly appreciate it if you could follow this guide for your confirmation.
Thank you.