See full discussion at #12956 more details after this comment.

kmshell -s means 'silent' so that means no UI is intended to be shown there... We could change that to kmshell.exe -boot, but we'd have to fixup existing installations -- we'd need to make sure that that change was applied during the upgrade (this is quite doable, just more work and testing).

I think that'd be good because it'd be clearer than the current -s which could be used any time and is ambiguous.

Originally posted by @mcdurdin in #12956 (comment)

A registry key is set Windows run location to have -s this will need to change to -boot.
initprog.pas will handle -boot. Then an audit of how -s runs and how we in most cases will want -boot to follow the same execution path. At least one exception will be prompting the user to install and update if it is available and ready to install. There may be other checks in the RunKMCOM call also.