@Archana2612
I have found it necessary to use the Package Support Framework (PSF) as a solution to migrating traditional installers that create shortcuts pointing to non-exe files, as well as those that have command line arguments.
I extended the PSF to support these use cases earlier this year. In essence, your shortcut (perhaps we should use the term "entry point", although I think the ultimate result is called a "start tile") would point to a copy of PsfLaunch and a config.json file would be used to tell PsfLaunch what to do.
If you are a developer building a MSIX package, these are just components to add in, although if you want an icon for that start tile you'll have to add it into PsfLaunch executable.
If you are repackaging an existing installer into an MSIX package (something IT Pros do), you use a packaging tool like the Microsoft MSIX Packaging tool (or one from a Microsoft partner such as above that includes a version of the PSF). With the Microsoft tool, you'll need to add the PSF yourself, but up in the Microsoft Store you can also find an additional tool I built to help called PsfTooling.
This free tool is used while in monitoring mode of the packaging tool to inject and configure the PSF for you. You run the traditional installer for your package, then run PsfTooling. In PsfTooling select the shortcut wizard and pick your shortcuts. It automatically will figure out how to launch the original intent of your shortcut in MSIX land. While there are options to inject additional fixups in that wizard, you won't need those if all you want is to fix these shortcut issues. Apply the changes, then finish off the recapture.
