Microsoft Store Gets a Command Line Power Users Can Now "Store Install" via CLI

Microsoft Store Goes Pro: New CLI Tool Allows App Management via Terminal.

Linux users have long been accustomed to installing software via the command line (CLI), with Graphical User Interfaces (GUIs) acting as a secondary layer for convenience. In an interesting turn of events, Microsoft is moving in the opposite direction. The company has officially introduced a native Command Line Interface (CLI) for the Microsoft Store.

Simple, Direct, and Efficient

Named straightforwardly as the Store CLI, this tool allows users to bypass the traditional Microsoft Store app interface entirely. By using simple commands, power users and administrators can manage applications with high precision.

• Core Commands: Users can execute commands like store install or store update.

• Identification: Instead of searching by name, the CLI utilizes the specific Product ID of an application to ensure the correct version is retrieved and installed.

The Distinction: Store CLI vs. WinGet

It is important to note that Microsoft already has a robust package manager called WinGet (which was famously inspired by AppGet). However, these are distinct tools:

• WinGet: A comprehensive package manager for Windows that handles various software sources, including .exe and .msi installers from across the web.

• Store CLI: Exclusively dedicated to managing applications hosted within the Microsoft Store ecosystem, providing a more direct link to the Store’s backend.

The Store CLI makes it much easier for IT staff to script the installation of essential apps from the Store (such as Calculator, Photos, or enterprise apps) onto hundreds of computers simultaneously, eliminating the need to click on each machine individually.

For versions of Windows without a GUI (such as some types of Windows Server), the Store CLI is the primary way the system can directly retrieve apps from the Store.

Command-line installations often provide more detailed error logs than GUI installations, allowing developers and advanced users to immediately analyze why an app failed to install (e.g., licensing issues or insufficient storage space).

Using a Product ID (e.g., 9WZDNCRFJBMP for a specific app) reduces the risk of typing the app name and encountering fake or counterfeit apps that often lurk in Store search results, enhancing installation security (identity verification).

 

Notepad No Longer "Safe"? Microsoft Patches Remote Code Execution Flaw in February Update.

 

 Source: Microsoft

 

💬 AI Content Assistant

Ask me anything about this article. No data is stored for your question.

Microsoft Store Goes Pro: New CLI Tool Allows App Management via Terminal.

Linux users have long been accustomed to installing software via the command line (CLI), with Graphical User Interfaces (GUIs) acting as a secondary layer for convenience. In an interesting turn of events, Microsoft is moving in the opposite direction. The company has officially introduced a native Command Line Interface (CLI) for the Microsoft Store.

Simple, Direct, and Efficient

Named straightforwardly as the Store CLI, this tool allows users to bypass the traditional Microsoft Store app interface entirely. By using simple commands, power users and administrators can manage applications with high precision.

• Core Commands: Users can execute commands like store install or store update.

• Identification: Instead of searching by name, the CLI utilizes the specific Product ID of an application to ensure the correct version is retrieved and installed.

The Distinction: Store CLI vs. WinGet

It is important to note that Microsoft already has a robust package manager called WinGet (which was famously inspired by AppGet). However, these are distinct tools:

• WinGet: A comprehensive package manager for Windows that handles various software sources, including .exe and .msi installers from across the web.

• Store CLI: Exclusively dedicated to managing applications hosted within the Microsoft Store ecosystem, providing a more direct link to the Store’s backend.

The Store CLI makes it much easier for IT staff to script the installation of essential apps from the Store (such as Calculator, Photos, or enterprise apps) onto hundreds of computers simultaneously, eliminating the need to click on each machine individually.

For versions of Windows without a GUI (such as some types of Windows Server), the Store CLI is the primary way the system can directly retrieve apps from the Store.

Command-line installations often provide more detailed error logs than GUI installations, allowing developers and advanced users to immediately analyze why an app failed to install (e.g., licensing issues or insufficient storage space).

Using a Product ID (e.g., 9WZDNCRFJBMP for a specific app) reduces the risk of typing the app name and encountering fake or counterfeit apps that often lurk in Store search results, enhancing installation security (identity verification).

 

Notepad No Longer "Safe"? Microsoft Patches Remote Code Execution Flaw in February Update.

 

 Source: Microsoft