SOLVED

MSIX self heal issue

%3CLINGO-SUB%20id%3D%22lingo-sub-1608571%22%20slang%3D%22en-US%22%3EMSIX%20self%20heal%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1608571%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20converted%20and%20MSI%20%22Northgate%20Information%20client%205.1.1%22%20app%20to%20MSIX.%3C%2FP%3E%3CP%3Ethe%20MSIX%20app%20installs%20fine%20but%20when%20i%20launched%20the%20shortcut%20the%20package%20tries%20to%20self%20heal.%3C%2FP%3E%3CP%3Ethe%20self%20healing%20operation%20get%20stuck%20and%20does%20not%20do%20anything%20further.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22santosh94_0-1598290224502.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F214366iD503FE11EE0B2E68%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22santosh94_0-1598290224502.png%22%20alt%3D%22santosh94_0-1598290224502.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethe%20installer%20does%20do%20the%20necessary%20operation%20and%20have%20to%20kill%20it%20from%20task%20manager.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Enot%20sure%20if%20MSIX%20allow%20the%20installer%20to%20self%20heal%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eany%20help%20would%20be%20really%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1608873%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20self%20heal%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1608873%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F738929%22%20target%3D%22_blank%22%3E%40santosh94%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMSIX%20does%20not%20support%20apps%20self-healing%20or%20updating%20themselves.%20That%20is%20because%20MSIX%20apps%20are%20installed%20to%20a%20protected%20folder%20that%20does%20not%20allow%20writes%20to%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20recommendation%20when%20converting%20applications%20to%20MSIX%20with%20the%20packaging%20tool%20is%20to%20disable%20these%20behaviors%20during%20the%20conversion%20process%20if%20possible.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20that%20does%20not%20work%20you%20can%20also%20try%20to%20find%20out%20what%20triggers%20the%20self-heal%20to%20prevent%20it%20from%20happening.%20For%20example%2C%20it%20may%20be%20that%20the%20application%20is%20checking%20a%20registry%20key%20with%20information%20about%20the%20installation%20and%20you%20need%20to%20delete%20or%20modify%20it%20in%20your%20packaged%20app.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1613007%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20self%20heal%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1613007%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F738929%22%20target%3D%22_blank%22%3E%40santosh94%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20old%20MSI%20installer%20should%20be%20completely%20out%20of%20the%20picture%20once%20you%20converted%20it%20to%20MSIX.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20self-repair%20probably%20triggers%20because%20you%20have%20both%20the%20MSI%20and%20the%20MSIX%20version%20of%20the%20application%20installed%20on%20the%20machine%20(and%20something%20from%20the%20MSI%20wasn't%20correctly%20installed).%20Try%20installing%20the%20MSIX%20package%20on%20a%20clean%20machine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20as%20a%20good%20practice%2C%20it%20is%20recommended%20you%20always%20use%20a%20clean%20virtual%20machine%20to%20convert%20a%20package%20to%20MSIX.%20You%20can%20use%20the%20native%20Hyper-V%20support%20from%20Windows%2010%20or%20any%20other%20VM%20provider%20(Vmware%2C%20VirtualBox%2C%20etc...).%20This%20will%20ensure%20greater%20accuracy%20for%20the%20contents%20of%20your%20new%20MSIX%20package%20and%20also%20better%2Fclear%20test%20results%20for%20the%20new%20MSIX%20package.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi,

 

I have converted and MSI "Northgate Information client 5.1.1" app to MSIX.

the MSIX app installs fine but when i launched the shortcut the package tries to self heal.

the self healing operation get stuck and does not do anything further.

santosh94_0-1598290224502.png

 

the installer does do the necessary operation and have to kill it from task manager.

 

not sure if MSIX allow the installer to self heal ?

 

any help would be really appreciated.

 

2 Replies

@santosh94 

MSIX does not support apps self-healing or updating themselves. That is because MSIX apps are installed to a protected folder that does not allow writes to it.

 

The recommendation when converting applications to MSIX with the packaging tool is to disable these behaviors during the conversion process if possible.

 

If that does not work you can also try to find out what triggers the self-heal to prevent it from happening. For example, it may be that the application is checking a registry key with information about the installation and you need to delete or modify it in your packaged app.

Best Response confirmed by John Vintzel (Microsoft)
Solution

Hi @santosh94 

 

The old MSI installer should be completely out of the picture once you converted it to MSIX. 

 

The self-repair probably triggers because you have both the MSI and the MSIX version of the application installed on the machine (and something from the MSI wasn't correctly installed). Try installing the MSIX package on a clean machine.

 

Also, as a good practice, it is recommended you always use a clean virtual machine to convert a package to MSIX. You can use the native Hyper-V support from Windows 10 or any other VM provider (Vmware, VirtualBox, etc...). This will ensure greater accuracy for the contents of your new MSIX package and also better/clear test results for the new MSIX package.