-
Notifications
You must be signed in to change notification settings - Fork 45
Update freshness and remove v1.x configs #324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,20 +1,16 @@ | ||||||
| --- | ||||||
| description: This article explains how to get started using the PowerShell Gallery and the PowerShellGet cmdlets | ||||||
| ms.date: 09/09/2025 | ||||||
| ms.date: 01/28/2026 | ||||||
| ms.topic: get-started | ||||||
| title: Get Started with the PowerShell Gallery | ||||||
| --- | ||||||
| # Getting Started with the PowerShell Gallery | ||||||
|
|
||||||
| The PowerShell Gallery is a package repository containing scripts, modules, and DSC resources you | ||||||
| can download and leverage. You use the cmdlets in the [PowerShellGet][03] module to install packages | ||||||
| can download and use. You use the cmdlets in the [PowerShellGet][03] module to install packages | ||||||
| from the PowerShell Gallery. You don't need to sign in to download items from the PowerShell | ||||||
| Gallery. | ||||||
|
|
||||||
| > [!NOTE] | ||||||
| > It's possible to download a package from the PowerShell Gallery directly, but this isn't a | ||||||
| > recommended approach. For more details, see [Manual Package Download][18]. | ||||||
|
|
||||||
| ## Discovering packages from the PowerShell Gallery | ||||||
|
|
||||||
| You can find packages in the PowerShell Gallery using the **Search** control on the PowerShell | ||||||
|
|
@@ -43,13 +39,13 @@ Because DSC resources are always delivered as part of a module, you still need t | |||||
|
|
||||||
| ## Learning about packages in the PowerShell Gallery | ||||||
|
|
||||||
| Once you've identified a package that you're interested in, you may want to learn more about it. You | ||||||
| can do this by examining that package's specific page on the Gallery. On that page, you'll be able | ||||||
| to see all the metadata uploaded with the package. This metadata is provided by the package's | ||||||
| author, and is not verified by Microsoft. The Owner of the package is strongly tied to the Gallery | ||||||
| account used to publish the package, and is more trustworthy than the Author field. | ||||||
| After you select a package, you may want to learn more about it. Examine the package page on the | ||||||
| Gallery. The package page includes the metadata uploaded with the package. The metadata is provided | ||||||
| by the author of the package. Microsoft doesn't verify this information. The Owner of the package is | ||||||
| associated with the Gallery account used to publish the package. The Owner account is more | ||||||
| authoritative than the Author field. | ||||||
|
|
||||||
| If you discover a package that you feel isn't published in good faith, click **Report Abuse** on | ||||||
| If you discover a package that you feel isn't published in good faith, select **Report Abuse** on | ||||||
| that package's page. | ||||||
|
|
||||||
| If you're running `Find-Module` or `Find-Script`, you can view this data in the returned | ||||||
|
|
@@ -66,63 +62,62 @@ We encourage the following process when downloading packages from the PowerShell | |||||
|
|
||||||
| ### Inspect | ||||||
|
|
||||||
| To download a package from the Gallery for inspection, run either the `Save-Module` or `Save-Script` | ||||||
| cmdlet, depending on the package type. This lets you save the package locally without installing it, | ||||||
| and inspect the package contents. Remember to delete the saved package manually. | ||||||
| To download a package from the Gallery for inspection, use the `Save-Module` or `Save-Script` | ||||||
| cmdlets on the package. These commands save the package locally without installing it. Inspect the | ||||||
| package contents. Remember to delete the saved package manually. | ||||||
|
|
||||||
| Some of these packages are authored by Microsoft, and others are authored by the PowerShell | ||||||
| community. Microsoft recommends that you review the contents and code of packages on this gallery | ||||||
| before installation. | ||||||
| Some packages are authored by Microsoft, and others are authored by the PowerShell community. | ||||||
| Microsoft recommends that you review the contents and code of packages on this gallery before | ||||||
| installation. | ||||||
|
|
||||||
| If you discover a package that you feel isn't published in good faith, click **Report Abuse** on | ||||||
| If you discover a package that you feel isn't published in good faith, select **Report Abuse** on | ||||||
| that package's page. | ||||||
|
|
||||||
| ### Install | ||||||
|
|
||||||
| To install a package from the Gallery for use, run either the `Install-Module` or `Install-Script` | ||||||
| cmdlet, depending on the package type. | ||||||
|
|
||||||
| `Install-Module` installs the module to `$env:ProgramFiles\WindowsPowerShell\Modules` by default. | ||||||
| This requires an administrator account. If you add the `-Scope CurrentUser` parameter, the module is | ||||||
| installed to `$HOME\Documents\WindowsPowerShell\Modules` . | ||||||
| By default, `Install-Module` installs the module to `$env:ProgramFiles\WindowsPowerShell\Modules` | ||||||
| location by default, which requires an administrator account. If you add the `-Scope CurrentUser` | ||||||
| parameter, the command installs the module in `$HOME\Documents\WindowsPowerShell\Modules` . | ||||||
|
|
||||||
| `Install-Script` installs the script to `$env:ProgramFiles\WindowsPowerShell\Scripts` by default. | ||||||
| This requires an administrator account. If you add the `-Scope CurrentUser` parameter, the script is | ||||||
| installed to `$HOME\Documents\WindowsPowerShell\Scripts` . | ||||||
| By default, `Install-Script` installs the script to `$env:ProgramFiles\WindowsPowerShell\Scripts` | ||||||
| location, which requires an administrator account. If you add the `-Scope CurrentUser` parameter, | ||||||
| the command installs the script in `$HOME\Documents\WindowsPowerShell\Scripts`. | ||||||
|
|
||||||
| By default, `Install-Module` and `Install-Script` installs the most | ||||||
| current version of a package. To install an older version of the package, add the `-RequiredVersion` | ||||||
| parameter. | ||||||
| `Install-Module` and `Install-Script` installs the most current version of a package. To install an | ||||||
|
||||||
| `Install-Module` and `Install-Script` installs the most current version of a package. To install an | |
| `Install-Module` and `Install-Script` install the most current version of a package. To install an |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Redundant phrase 'by default' appears twice in the same sentence. The phrase 'location by default' should be simplified to just 'location' since 'By default' already appears at the beginning of the sentence.