Update README with msixbundle install instructions

[smholvoet]

Summary of the Pull Request

Added instructions on how to install the .msixbundle file for users who install Terminal manually.

References

/

PR Checklist

• CLA signed. If not, go over here and sign the CLA
• Tests added/passed
• Documentation updated. If checked, please file a pull request on our docs repo and link it here: #xxx
• Schema updated.
• I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

[DHowett]

I'm concerned about the instructions. While they work, they're not the most expedient way to install Terminal . . . the msixbundle is double-clickable in the vast majority of cases, isn't it?

[smholvoet]

@DHowett Thanks for the feedback.

.msixbundle files don't seem to be double clickable, at least on my (corporate) machine:

I really think this would benefit people who don't have access to the Windows Store (or can only download a specific set of apps).

Example of a related issue: #6468

[TobiasSekan]

Hello,

I'm concerned about the instructions. While they work, they're not the most expedient way to install Terminal . . . the msixbundle is double-clickable in the vast majority of cases, isn't it?

When the Hidden-App App-Installer is not longer present or the file-extension msixbundle is set to a other program or removed a user can't no longer install a msixbundle with a single/double-click.

The App-Installer can removed by (when user don't like store things)

• O&O AppBuster
• via powershell command

Edit: I'm not really sure, but I think msix files need the App-Installer too.

[WSLUser]

I prefer this PowerShell method for offline usage. Unfortunately we still have a "network" issue in trying to running the installed application, usually requiring changing to .zip and extracting until we can launch WindowsTerminal.exe directly. So we may need a powershell method written for that scenario as well.

[zadjii-msft]

I think I'd rather that this text suggested that the user first try just double clicking the .msixbundle, and fall back to the command only if double-clicking didn't work.

[zadjii-msft]

Suggested change

	Download the `Microsoft.WindowsTerminal_<versionNumber>.msixbundle` file from the **Assets** section.
	Run the following command in order to install the `.msixbundle` file you've just downloaded:
	Download the `Microsoft.WindowsTerminal_<versionNumber>.msixbundle` file from the **Assets** section. To install the app, you can simply double-click on the `.msixbundle` file, and the app installer should automatically run. If that fails for any reason, you can try the following command instead:

[ghost]

This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.