
docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/import-module
Preview meta tags from the docs.microsoft.com website.
Linked Hostnames
7- 12 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
Import-Module (Microsoft.PowerShell.Core) - PowerShell
The Import-Module cmdlet adds one or more modules to the current session. Starting in PowerShell 3.0, installed modules are automatically imported to the session when you use any commands or providers in the module. However, you can still use the Import-Module command to import a module. You can disable automatic module importing using the $PSModuleAutoLoadingPreference preference variable. For more information about the $PSModuleAutoLoadingPreference variable, see about_Preference_Variables. A module is a package that contains members that can be used in PowerShell. Members include cmdlets, providers, scripts, functions, variables, and other tools and files. After a module is imported, you can use the module members in your session. For more information about modules, see about_Modules. By default, Import-Module imports all members that the module exports, but you can use the Alias, Function, Cmdlet, and Variable parameters to restrict which members are imported. The NoClobber parameter prevents Import-Module from importing members that have the same names as members in the current session. Import-Module imports a module only into the current session. To import the module into every new session, add an Import-Module command to your PowerShell profile. For more information about profiles, see about_Profiles. You can manage remote Windows computers that have PowerShell remoting enabled by creating a PSSession on the remote computer. Then use the PSSession parameter of Import-Module to import the modules that are installed on the remote computer. When you use the imported commands in the current session the commands implicitly run on the remote computer. Starting in Windows PowerShell 3.0, you can use Import-Module to 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++. For remote computers that don't have PowerShell remoting enabled, including computers that aren't running the Windows operating system, you can use the CimSession parameter of Import-Module to import CIM modules from the remote computer. The imported commands run implicitly on the remote computer. A CIMSession is a connection to Windows Management Instrumentation (WMI) on the remote computer.
Bing
Import-Module (Microsoft.PowerShell.Core) - PowerShell
The Import-Module cmdlet adds one or more modules to the current session. Starting in PowerShell 3.0, installed modules are automatically imported to the session when you use any commands or providers in the module. However, you can still use the Import-Module command to import a module. You can disable automatic module importing using the $PSModuleAutoLoadingPreference preference variable. For more information about the $PSModuleAutoLoadingPreference variable, see about_Preference_Variables. A module is a package that contains members that can be used in PowerShell. Members include cmdlets, providers, scripts, functions, variables, and other tools and files. After a module is imported, you can use the module members in your session. For more information about modules, see about_Modules. By default, Import-Module imports all members that the module exports, but you can use the Alias, Function, Cmdlet, and Variable parameters to restrict which members are imported. The NoClobber parameter prevents Import-Module from importing members that have the same names as members in the current session. Import-Module imports a module only into the current session. To import the module into every new session, add an Import-Module command to your PowerShell profile. For more information about profiles, see about_Profiles. You can manage remote Windows computers that have PowerShell remoting enabled by creating a PSSession on the remote computer. Then use the PSSession parameter of Import-Module to import the modules that are installed on the remote computer. When you use the imported commands in the current session the commands implicitly run on the remote computer. Starting in Windows PowerShell 3.0, you can use Import-Module to 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++. For remote computers that don't have PowerShell remoting enabled, including computers that aren't running the Windows operating system, you can use the CimSession parameter of Import-Module to import CIM modules from the remote computer. The imported commands run implicitly on the remote computer. A CIMSession is a connection to Windows Management Instrumentation (WMI) on the remote computer.
DuckDuckGo
Import-Module (Microsoft.PowerShell.Core) - PowerShell
The Import-Module cmdlet adds one or more modules to the current session. Starting in PowerShell 3.0, installed modules are automatically imported to the session when you use any commands or providers in the module. However, you can still use the Import-Module command to import a module. You can disable automatic module importing using the $PSModuleAutoLoadingPreference preference variable. For more information about the $PSModuleAutoLoadingPreference variable, see about_Preference_Variables. A module is a package that contains members that can be used in PowerShell. Members include cmdlets, providers, scripts, functions, variables, and other tools and files. After a module is imported, you can use the module members in your session. For more information about modules, see about_Modules. By default, Import-Module imports all members that the module exports, but you can use the Alias, Function, Cmdlet, and Variable parameters to restrict which members are imported. The NoClobber parameter prevents Import-Module from importing members that have the same names as members in the current session. Import-Module imports a module only into the current session. To import the module into every new session, add an Import-Module command to your PowerShell profile. For more information about profiles, see about_Profiles. You can manage remote Windows computers that have PowerShell remoting enabled by creating a PSSession on the remote computer. Then use the PSSession parameter of Import-Module to import the modules that are installed on the remote computer. When you use the imported commands in the current session the commands implicitly run on the remote computer. Starting in Windows PowerShell 3.0, you can use Import-Module to 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++. For remote computers that don't have PowerShell remoting enabled, including computers that aren't running the Windows operating system, you can use the CimSession parameter of Import-Module to import CIM modules from the remote computer. The imported commands run implicitly on the remote computer. A CIMSession is a connection to Windows Management Instrumentation (WMI) on the remote computer.
General Meta Tags
59- titleImport-Module (Microsoft.PowerShell.Core) - PowerShell | Microsoft Learn
- charsetutf-8
- viewportwidth=device-width, initial-scale=1.0
- color-schemelight dark
- descriptionThe Import-Module cmdlet adds one or more modules to the current session. Starting in PowerShell 3.0, installed modules are automatically imported to the session when you use any commands or providers in the module. However, you can still use the Import-Module command to import a module. You can disable automatic module importing using the $PSModuleAutoLoadingPreference preference variable. For more information about the $PSModuleAutoLoadingPreference variable, see about_Preference_Variables. A module is a package that contains members that can be used in PowerShell. Members include cmdlets, providers, scripts, functions, variables, and other tools and files. After a module is imported, you can use the module members in your session. For more information about modules, see about_Modules. By default, Import-Module imports all members that the module exports, but you can use the Alias, Function, Cmdlet, and Variable parameters to restrict which members are imported. The NoClobber parameter prevents Import-Module from importing members that have the same names as members in the current session. Import-Module imports a module only into the current session. To import the module into every new session, add an Import-Module command to your PowerShell profile. For more information about profiles, see about_Profiles. You can manage remote Windows computers that have PowerShell remoting enabled by creating a PSSession on the remote computer. Then use the PSSession parameter of Import-Module to import the modules that are installed on the remote computer. When you use the imported commands in the current session the commands implicitly run on the remote computer. Starting in Windows PowerShell 3.0, you can use Import-Module to 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++. For remote computers that don't have PowerShell remoting enabled, including computers that aren't running the Windows operating system, you can use the CimSession parameter of Import-Module to import CIM modules from the remote computer. The imported commands run implicitly on the remote computer. A CIMSession is a connection to Windows Management Instrumentation (WMI) on the remote computer.
Open Graph Meta Tags
6- og:typewebsite
- og:image:altImport-Module (Microsoft.PowerShell.Core) - PowerShell | Microsoft Learn
- og:imagehttps://learn.microsoft.com/media/logos/logo-powershell-social.png
- og:titleImport-Module (Microsoft.PowerShell.Core) - PowerShell
- og:urlhttps://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/import-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/import-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
26- 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.pscustomobject
- https://docs.microsoft.com/en-us/dotnet/api/system.management.automation.psmoduleinfo