
docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/get-module
Preview meta tags from the docs.microsoft.com website.
Linked Hostnames
7- 9 links todocs.microsoft.com
- 6 links tolearn.microsoft.com
- 3 links togo.microsoft.com
- 2 links togithub.com
- 1 link toaka.ms
- 1 link totechcommunity.microsoft.com
- 1 link towww.microsoft.com
Thumbnail

Search Engine Appearance
Get-Module (Microsoft.PowerShell.Core) - PowerShell
The Get-Module cmdlet lists the PowerShell modules that have been imported, or that can be imported, into a PowerShell session. Without parameters, Get-Module gets modules that have been imported into the current session. The ListAvailable parameter is used to list the modules that are available to be imported from the paths specified in the PSModulePath environment variable ($Env:PSModulePath). The module object that Get-Module returns contains valuable information about the module. You can also pipe the module objects to other cmdlets, such as the Import-Module and Remove-Module cmdlets. Get-Module lists modules, but it does not import them. Starting in Windows PowerShell 3.0, modules are automatically imported when you use a command in the module, but a Get-Module command does not trigger an automatic import. You can also import the modules into your session using the Import-Module cmdlet. Starting in Windows PowerShell 3.0, you can get and then, import modules from remote sessions into the local session. This strategy uses the Implicit Remoting feature of PowerShell and is equivalent to using the Import-PSSession cmdlet. When you use commands in modules imported from another session, the commands run implicitly in the remote session. This feature lets you manage the remote computer from the local session. Also, starting in Windows PowerShell 3.0, you can use Get-Module and Import-Module to get and import Common Information Model (CIM) modules. CIM modules define cmdlets in Cmdlet Definition XML (CDXML) files. This feature lets you use cmdlets that are implemented in non-managed code assemblies, such as those written in C++. Implicit remoting can be used to manage remote computers that have PowerShell remoting enabled. Create a PSSession on the remote computer and then use the PSSession parameter of Get-Module to get the PowerShell modules in the remote session. When you import a module from the remote session the imported commands run in the session on the remote computer. You can use a similar strategy to manage computers that do not have PowerShell remoting enabled. These include computers that are not running the Windows operating system, and computers that have PowerShell but do not have PowerShell remoting enabled. Start by creating a CIM session on the remote computer. A CIM session is a connection to Windows Management Instrumentation (WMI) on the remote computer. Then use the CimSession parameter of Get-Module to get CIM modules from the CIM session. When you import a CIM module by using the Import-Module cmdlet and then run the imported commands, the commands run implicitly on the remote computer. You can use this WMI and CIM strategy to manage the remote computer.
Bing
Get-Module (Microsoft.PowerShell.Core) - PowerShell
The Get-Module cmdlet lists the PowerShell modules that have been imported, or that can be imported, into a PowerShell session. Without parameters, Get-Module gets modules that have been imported into the current session. The ListAvailable parameter is used to list the modules that are available to be imported from the paths specified in the PSModulePath environment variable ($Env:PSModulePath). The module object that Get-Module returns contains valuable information about the module. You can also pipe the module objects to other cmdlets, such as the Import-Module and Remove-Module cmdlets. Get-Module lists modules, but it does not import them. Starting in Windows PowerShell 3.0, modules are automatically imported when you use a command in the module, but a Get-Module command does not trigger an automatic import. You can also import the modules into your session using the Import-Module cmdlet. Starting in Windows PowerShell 3.0, you can get and then, import modules from remote sessions into the local session. This strategy uses the Implicit Remoting feature of PowerShell and is equivalent to using the Import-PSSession cmdlet. When you use commands in modules imported from another session, the commands run implicitly in the remote session. This feature lets you manage the remote computer from the local session. Also, starting in Windows PowerShell 3.0, you can use Get-Module and Import-Module to get and import Common Information Model (CIM) modules. CIM modules define cmdlets in Cmdlet Definition XML (CDXML) files. This feature lets you use cmdlets that are implemented in non-managed code assemblies, such as those written in C++. Implicit remoting can be used to manage remote computers that have PowerShell remoting enabled. Create a PSSession on the remote computer and then use the PSSession parameter of Get-Module to get the PowerShell modules in the remote session. When you import a module from the remote session the imported commands run in the session on the remote computer. You can use a similar strategy to manage computers that do not have PowerShell remoting enabled. These include computers that are not running the Windows operating system, and computers that have PowerShell but do not have PowerShell remoting enabled. Start by creating a CIM session on the remote computer. A CIM session is a connection to Windows Management Instrumentation (WMI) on the remote computer. Then use the CimSession parameter of Get-Module to get CIM modules from the CIM session. When you import a CIM module by using the Import-Module cmdlet and then run the imported commands, the commands run implicitly on the remote computer. You can use this WMI and CIM strategy to manage the remote computer.
DuckDuckGo
Get-Module (Microsoft.PowerShell.Core) - PowerShell
The Get-Module cmdlet lists the PowerShell modules that have been imported, or that can be imported, into a PowerShell session. Without parameters, Get-Module gets modules that have been imported into the current session. The ListAvailable parameter is used to list the modules that are available to be imported from the paths specified in the PSModulePath environment variable ($Env:PSModulePath). The module object that Get-Module returns contains valuable information about the module. You can also pipe the module objects to other cmdlets, such as the Import-Module and Remove-Module cmdlets. Get-Module lists modules, but it does not import them. Starting in Windows PowerShell 3.0, modules are automatically imported when you use a command in the module, but a Get-Module command does not trigger an automatic import. You can also import the modules into your session using the Import-Module cmdlet. Starting in Windows PowerShell 3.0, you can get and then, import modules from remote sessions into the local session. This strategy uses the Implicit Remoting feature of PowerShell and is equivalent to using the Import-PSSession cmdlet. When you use commands in modules imported from another session, the commands run implicitly in the remote session. This feature lets you manage the remote computer from the local session. Also, starting in Windows PowerShell 3.0, you can use Get-Module and Import-Module to get and import Common Information Model (CIM) modules. CIM modules define cmdlets in Cmdlet Definition XML (CDXML) files. This feature lets you use cmdlets that are implemented in non-managed code assemblies, such as those written in C++. Implicit remoting can be used to manage remote computers that have PowerShell remoting enabled. Create a PSSession on the remote computer and then use the PSSession parameter of Get-Module to get the PowerShell modules in the remote session. When you import a module from the remote session the imported commands run in the session on the remote computer. You can use a similar strategy to manage computers that do not have PowerShell remoting enabled. These include computers that are not running the Windows operating system, and computers that have PowerShell but do not have PowerShell remoting enabled. Start by creating a CIM session on the remote computer. A CIM session is a connection to Windows Management Instrumentation (WMI) on the remote computer. Then use the CimSession parameter of Get-Module to get CIM modules from the CIM session. When you import a CIM module by using the Import-Module cmdlet and then run the imported commands, the commands run implicitly on the remote computer. You can use this WMI and CIM strategy to manage the remote computer.
General Meta Tags
59- titleGet-Module (Microsoft.PowerShell.Core) - PowerShell | Microsoft Learn
- charsetutf-8
- viewportwidth=device-width, initial-scale=1.0
- color-schemelight dark
- descriptionThe Get-Module cmdlet lists the PowerShell modules that have been imported, or that can be imported, into a PowerShell session. Without parameters, Get-Module gets modules that have been imported into the current session. The ListAvailable parameter is used to list the modules that are available to be imported from the paths specified in the PSModulePath environment variable ($Env:PSModulePath). The module object that Get-Module returns contains valuable information about the module. You can also pipe the module objects to other cmdlets, such as the Import-Module and Remove-Module cmdlets. Get-Module lists modules, but it does not import them. Starting in Windows PowerShell 3.0, modules are automatically imported when you use a command in the module, but a Get-Module command does not trigger an automatic import. You can also import the modules into your session using the Import-Module cmdlet. Starting in Windows PowerShell 3.0, you can get and then, import modules from remote sessions into the local session. This strategy uses the Implicit Remoting feature of PowerShell and is equivalent to using the Import-PSSession cmdlet. When you use commands in modules imported from another session, the commands run implicitly in the remote session. This feature lets you manage the remote computer from the local session. Also, starting in Windows PowerShell 3.0, you can use Get-Module and Import-Module to get and import Common Information Model (CIM) modules. CIM modules define cmdlets in Cmdlet Definition XML (CDXML) files. This feature lets you use cmdlets that are implemented in non-managed code assemblies, such as those written in C++. Implicit remoting can be used to manage remote computers that have PowerShell remoting enabled. Create a PSSession on the remote computer and then use the PSSession parameter of Get-Module to get the PowerShell modules in the remote session. When you import a module from the remote session the imported commands run in the session on the remote computer. You can use a similar strategy to manage computers that do not have PowerShell remoting enabled. These include computers that are not running the Windows operating system, and computers that have PowerShell but do not have PowerShell remoting enabled. Start by creating a CIM session on the remote computer. A CIM session is a connection to Windows Management Instrumentation (WMI) on the remote computer. Then use the CimSession parameter of Get-Module to get CIM modules from the CIM session. When you import a CIM module by using the Import-Module cmdlet and then run the imported commands, the commands run implicitly on the remote computer. You can use this WMI and CIM strategy to manage the remote computer.
Open Graph Meta Tags
6- og:typewebsite
- og:image:altGet-Module (Microsoft.PowerShell.Core) - PowerShell | Microsoft Learn
- og:imagehttps://learn.microsoft.com/media/logos/logo-powershell-social.png
- og:titleGet-Module (Microsoft.PowerShell.Core) - PowerShell
- og:urlhttps://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/get-module?view=powershell-7.5
Twitter Meta Tags
2- twitter:cardsummary
- twitter:site@MicrosoftLearn
Link Tags
6- canonicalhttps://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/get-module?view=powershell-7.5
- dns-prefetch//target.microsoft.com
- dns-prefetch//microsoftmscompoc.tt.omtrdc.net
- preconnect//mscom.demdex.net
- preload/static/third-party/adobe-target/at-js/2.9.0/at.js
Links
23- https://aka.ms/yourcaliforniaprivacychoices
- https://docs.microsoft.com/en-us/dotnet/api/microsoft.management.infrastructure.cimsession
- https://docs.microsoft.com/en-us/dotnet/api/microsoft.powershell.commands.modulespecification
- https://docs.microsoft.com/en-us/dotnet/api/system.management.automation.psmoduleinfo
- https://docs.microsoft.com/en-us/dotnet/api/system.management.automation.runspaces.initialsessionstate.createdefault2