# PowerShell

> Mediated Wiki article. Canonical URL: https://mediated.wiki/source/PowerShell
> Markdown URL: https://mediated.wiki/source/PowerShell.md
> Source: https://en.wikipedia.org/wiki/PowerShell
> Source revision: 1357011183
> License: Creative Commons Attribution-ShareAlike 4.0 International (https://creativecommons.org/licenses/by-sa/4.0/)

Cross-platform shell based on .NET technology

PowerShell Screenshot of a PowerShell 7.5.0 session in Windows Terminal Paradigm Imperative, pipeline, object-oriented, functional and reflective Designed by Jeffrey Snover, Bruce Payette, James Truher (et al.) Developer Microsoft First appeared November 14, 2006; 19 years ago (2006-11-14) Stable release 7.6.3[1] / 16 June 2026; 10 days ago (16 June 2026) Preview release 7.7.0-preview.2 / 27 May 2026; 30 days ago (2026-05-27)[2] Typing discipline Strong, safe, implicit and dynamic Implementation language C# Platform PowerShell: .NET Windows PowerShell: .NET Framework OS Windows 11 2024 Update and later Windows Server 2025 and later macOS 14 and later Ubuntu since 22.04 Debian 12 and 13 Red Hat Enterprise Linux 8, 9 and 10 openSUSE 15.6 and 16.0 Fedora 42, 43 and 44 License MIT License[3] (but the Windows component remains proprietary) Filename extensions .ps1 (Script) .ps1xml (XML Document) .psc1 (Console File) .psd1 (Data File) .psm1 (Script Module) .pssc (Session Configuration File) .psrc (Role Capability File) .cdxml (Cmdlet Definition XML Document) Website microsoft.com/powershell Influenced by Python, Shell script, Perl, C#, CL, DCL, SQL, Tcl, Tk,[4] Chef, Puppet

**PowerShell** is a [shell](/source/Shell_(computing)) [program](/source/Computer_program) developed by [Microsoft](/source/Microsoft) for task automation and [configuration management](/source/Configuration_management). As is typical for a shell, it provides a [command-line](/source/Command-line_interface) [interpreter](/source/Interpreter) for interactive use and a [script](/source/Scripting_language) interpreter for automation via a [language](/source/Programming_language) defined for it. Originally only for Windows, known as **Windows PowerShell**, it was made [open-source](/source/Open-source_software) and [cross-platform](/source/Cross-platform) on August 18, 2016, with the introduction of **PowerShell Core**.[5] The former is built on the [.NET Framework](/source/.NET_Framework) and the latter on [.NET](/source/.NET) (previously .NET Core).

PowerShell is bundled with current [versions of Windows](/source/List_of_Microsoft_Windows_versions) and can be installed on [macOS](/source/MacOS) and [Linux](/source/Linux).[5] Since [Windows 10](/source/Windows_10) build 14971, PowerShell replaced [Command Prompt](/source/Cmd.exe) as the default [command shell](/source/Command_shell) exposed by [File Explorer](/source/File_Explorer).[6][7]

In PowerShell, administrative tasks are generally performed via *cmdlets* (pronounced *command-lets*), which are specialized .NET [classes](/source/Class_(computer_programming)) implementing a particular operation. These work by accessing data in different data stores, like the [file system](/source/File_system) or [Windows Registry](/source/Windows_Registry), which are made available to PowerShell via *providers*. Third-party developers can add cmdlets and providers to PowerShell.[8][9] Cmdlets may be used by scripts, which may in turn be packaged into modules. Cmdlets work in tandem with the .NET [API](/source/Application_programming_interface).

PowerShell's support for [.NET Remoting](/source/.NET_Remoting), [WS-Management](/source/WS-Management), [CIM](/source/Common_Information_Model_(computing)), and [SSH](/source/SSH) enables administrators to perform administrative tasks on both local and remote Windows systems. PowerShell also provides a hosting [API](/source/API) with which the PowerShell runtime can be embedded inside other applications. These applications can then use PowerShell functionality to implement certain operations, including those exposed via the [graphical interface](/source/Graphical_user_interface). This capability has been used by [Microsoft Exchange Server](/source/Microsoft_Exchange_Server) 2007 to expose its management functionality as PowerShell cmdlets and providers and implement the graphical management tools as PowerShell hosts which invoke the necessary cmdlets.[8][10] Other Microsoft applications including [Microsoft SQL Server 2008](/source/Microsoft_SQL_Server_2008) also expose their management interface via PowerShell cmdlets.[11]

PowerShell includes its own extensive, [console-based](/source/Command-line_interface) help (similar to [man pages](/source/Man_page) in [Unix shells](/source/Unix_shell)) accessible via the Get-Help cmdlet. Updated local help contents can be retrieved from the Internet via the Update-Help cmdlet. Alternatively, help from the web can be acquired on a case-by-case basis via the -online switch to Get-Help.

## Background

Shell programs, including PowerShell, trace lineage to shells in older [operating systems](/source/Operating_system) such as [MS-DOS](/source/MS-DOS) and [Xenix](/source/Xenix) which exposed system functionality to the user almost exclusively via a [command-line interface](/source/Command-line_interface) (CLI) – although MS-DOS 5 also came with a complementary graphical [DOS Shell](/source/DOS_Shell). The [Windows 9x](/source/Windows_9x) family came bundled with [COMMAND.COM](/source/COMMAND.COM), the command-line environment of MS-DOS. The [Windows NT](/source/Windows_NT) and [Windows CE](/source/Windows_Embedded_Compact) families, however, came with the newer [cmd.exe](/source/Cmd.exe) – a significant upgrade from COMMAND.COM. Both environments provide CLI for both internal and external commands and automation via [batch files](/source/Batch_file) – a relatively primitive language for scripting.

To address limitations of these shells – including the inability to directly use a [software component](/source/Software_component) exposed via [COM](/source/Component_Object_Model) – Microsoft introduced the [Windows Script Host](/source/Windows_Script_Host) in 1998 with [Windows 98](/source/Windows_98), and its command-line based host, cscript.exe. It integrates with the [Active Script](/source/Active_Scripting) engine and allows scripts to be written in compatible languages, such as [JScript](/source/JScript) and [VBScript](/source/VBScript). These scripts can use COM components directly, but it has relatively inaccessible documentation and gained a reputation as a system [vulnerability vector](/source/Vulnerability_(computer_security)) after several high-profile [computer viruses](/source/Computer_virus) exploited weaknesses in its security provisions.

Different versions of Windows provided various special-purpose command-line interpreters (such as [netsh](/source/Netsh) and [WMIC](/source/Windows_Management_Instrumentation_Command-line)) with their own command sets but they were not interoperable. [Windows Server 2003](/source/Windows_Server_2003) further attempted to improve the command-line experience but scripting support was still unsatisfactory.[12]

### Kermit

Microsoft program manager and PowerShell Chief Architect [Jeffrey Snover](/source/Jeffrey_Snover)

By the late 1990s, [Intel](/source/Intel) had come to Microsoft asking for help in making Windows, which ran on Intel CPUs, a more appropriate platform to support the development of future Intel CPUs. At the time, Intel CPU development was accomplished on [Sun Microsystems](/source/Sun_Microsystems) computers which ran [Solaris](/source/Oracle_Solaris) (a [Unix](/source/Unix) variant) on [RISC](/source/RISC)-architecture CPUs. The ability to run Intel's many [KornShell](/source/KornShell) automation scripts on Windows was identified as a key capability. Internally, Microsoft began an effort to create a Windows port of Korn Shell, which was code-named Kermit.[13] Intel ultimately pivoted to a [Linux](/source/Linux)-based development platform that could run on Intel CPUs, rendering the Kermit project redundant. However, with a fully funded team, Microsoft program manager [Jeffrey Snover](/source/Jeffrey_Snover) realized there was an opportunity to create a more general-purpose solution to Microsoft's problem of administrative automation.

### Monad

By 2002, Microsoft had started to develop a new approach to command-line management, including a CLI called Monad (also known as Microsoft Shell or MSH). The ideas behind it were published in August 2002 in a white paper called the "Monad Manifesto" by its chief architect, [Jeffrey Snover](/source/Jeffrey_Snover).[14] In a 2017 interview, Snover explains the genesis of PowerShell, saying that he had been trying to make [Unix](/source/Unix) tools available on Windows, which didn't work due to "[core architectural difference\[s\] between Windows and Linux](/source/Unix_philosophy)". Specifically, he noted that [Linux](/source/Linux) considers everything a [text file](/source/Text_file), whereas Windows considers everything an "[API](/source/Application_programming_interface) that returns structured data". They were fundamentally incompatible, which led him to take a different approach.[15]

Monad was to be a new extensible CLI with a fresh design capable of automating a range of core administrative tasks. Microsoft first demonstrated Monad publicly at the Professional Development Conference in Los Angeles in October 2003. A few months later, they opened up private beta, which eventually led to a public beta. Microsoft published the first Monad public [beta release](/source/Development_stage#Beta) on June 17, 2005, and the Beta 2 on September 11, 2005, and Beta 3 on January 10, 2006.

### PowerShell

The first version of PowerShell

On April 25, 2006, two and a half years after the initial Monad announcement, Microsoft announced that Monad had been renamed **Windows PowerShell**, positioning it as a significant part of its management technology offerings.[16] Release Candidate (RC) 1 of PowerShell was released at the same time. A significant aspect of both the name change and the RC was that this was now a component of Windows, rather than a mere add-on.

Release Candidate 2 of PowerShell version 1 was released on September 26, 2006, with final [release to the web](/source/Software_release_life_cycle#Release_to_the_Web_(RTW)) on November 14, 2006. PowerShell for earlier versions of Windows was released on January 30, 2007.[17] PowerShell v2.0 development began before PowerShell v1.0 shipped. During the development, Microsoft shipped three [community technology previews (CTP)](/source/Community_Technology_Preview). Microsoft made these releases available to the public. The last CTP release of Windows PowerShell v2.0 was made available in December 2008.

PowerShell v2.0 was completed and released to manufacturing in August 2009, as an integral part of Windows 7 and Windows Server 2008 R2. Versions of PowerShell for Windows XP, Windows Server 2003, Windows Vista and Windows Server 2008 were released in October 2009 and are available for download for both 32-bit and 64-bit platforms.[18] In an October 2009 issue of *[TechNet Magazine](/source/Microsoft_TechNet)*, Microsoft called proficiency with PowerShell "the single most important skill a Windows [administrator](/source/System_administrator) will need in the coming years".[19]

Windows 10 shipped with Pester, a script validation suite for PowerShell.[20]

PowerShell for Linux 7.3.1 on [Ubuntu](/source/Ubuntu_(operating_system)) 22.10

On August 18, 2016, Microsoft announced[21] that they had made PowerShell open-source and cross-platform with support for Windows, [macOS](/source/MacOS), [CentOS](/source/CentOS) and [Ubuntu](/source/Ubuntu_(operating_system)).[5] The source code was published on [GitHub](/source/GitHub).[22] The move to open source created a second incarnation of PowerShell called "PowerShell Core", which runs on [.NET Core](/source/.NET_Core). It is distinct from "Windows PowerShell", which runs on the full [.NET Framework](/source/.NET_Framework).[23] Starting with version 5.1, PowerShell Core is bundled with [Windows Server 2016 Nano Server](/source/Windows_Server_2016#Nano_Server).[24][25]

### Pash

A project named *Pash*, a [pun](/source/Pun) on the widely known "[bash](/source/Bash_(Unix_shell))" Unix shell, has been an [open-source](/source/Open-source_software) and [cross-platform](/source/Cross-platform) reimplementation of PowerShell via the [Mono framework](/source/Mono_(software)).[26] Pash was created by Igor Moochnick, written in [C#](/source/C_Sharp_(programming_language)) and was released under the [GNU General Public License](/source/GNU_General_Public_License). Pash development stalled in 2008, was restarted on [GitHub](/source/GitHub) in 2012,[27] and finally ceased in 2016 when PowerShell was officially made open-source and cross-platform.[28]

## Design

### Philosophy

A key design goal for PowerShell was to leverage the large number of [APIs](/source/API) that already existed in Windows, Windows Management Instrumentation, .NET Framework, and other software. PowerShell cmdlets generally wrap and expose existing functionality instead of implementing new functionality. The intent was to provide an administrator-friendly, more-consistent interface between administrators and a wide range of underlying functionality. With PowerShell, an administrator doesn't need to know .NET, WMI, or low-level API coding, and can instead focus on using the cmdlets exposed by PowerShell. In this regard, PowerShell creates little new functionality, instead focusing on making existing functionality more accessible to a particular audience.[29]

### Grammar

PowerShell's developers based the core grammar of the tool on that of the [POSIX 1003.2](/source/POSIX) [KornShell](/source/KornShell).[30]

However, PowerShell's language was also influenced by [PHP](/source/PHP), [Perl](/source/Perl), and many other existing languages.[31]

### Named commands

PowerShell can execute four kinds of named commands:[32]

- *cmdlets* ([.NET Framework](/source/.NET_Framework) programs designed to interact with PowerShell)

- PowerShell scripts (files suffixed by .ps1)

- PowerShell functions

- Standalone [executable](/source/Executable) programs

If a command is a standalone executable program, PowerShell launches it in a separate [process](/source/Process_(computing)); if it is a cmdlet, it executes in the PowerShell process. PowerShell provides an interactive [command-line interface](/source/Command-line_interface), where the commands can be entered and their output displayed. The user interface offers customizable [tab completion](/source/Command-line_completion). PowerShell enables the creation of *[aliases](/source/Alias_(command))* for cmdlets, which PowerShell textually translates into invocations of the original commands. PowerShell supports both [named](/source/Named_parameter) and positional [parameters](/source/Parameter_(computer_science)) for commands. In executing a cmdlet, the job of binding the argument value to the parameter is done by PowerShell itself, but for external executables, arguments are parsed by the external executable independently of PowerShell interpretation.[33]

### Extended Type System

The PowerShell *Extended Type System* (*ETS*) is based on the .NET type system, but with extended semantics (for example, propertySets and third-party extensibility). For example, it enables the creation of different views of objects by exposing only a subset of the data fields, properties, and methods, as well as specifying custom formatting and sorting behavior. These views are mapped to the original object using [XML](/source/XML)-based configuration files.[34]

### Cmdlets

A cmdlet is a .NET [class](/source/Class_(programming)) that derives either from Cmdlet or from PSCmdlet; the latter is used when it needs to interact with the PowerShell runtime.[35] The base classes specify methods – BeginProcessing(), ProcessRecord() and EndProcessing() – which a cmdlet overrides to provide functionality based on the events that these functions represent. ProcessRecord() is called if the object receives pipeline input.[36] If a collection of objects is piped, the method is invoked for each object in the collection. The cmdlet class must have the [attribute](/source/Attribute_(computing)) CmdletAttribute which specifies the verb and the noun that make up the name of the cmdlet.

A cmdlet name follows a *Verb-Noun* naming pattern, such as *Get-ChildItem*, which tends to make it [self-documented](/source/Self-documenting_code).[35] Common verbs are provided as an [enum](/source/Enumerated_type).[37][38]

If a cmdlet receives either pipeline input or command-line parameter input, there must be a corresponding [property](/source/Property_(programming)) in the class, with a [mutator](/source/Mutator_method) implementation. PowerShell invokes the mutator with the parameter value or pipeline input, which is saved by the mutator implementation in class variables. These values are then referred to by the methods which implement the functionality. Properties that map to command-line parameters are marked by ParameterAttribute[39] and are set before the call to BeginProcessing(). Those which map to pipeline input are also flanked by ParameterAttribute, but with the ValueFromPipeline attribute parameter set.[40]

A cmdlet can use any [.NET](/source/.NET_Framework) [API](/source/API) and may be written in any [.NET language](/source/List_of_CLI_languages). In addition, PowerShell makes certain APIs available, such as WriteObject(), which is used to access PowerShell-specific functionality, such as writing objects to the pipeline. A cmdlet can use .NET a data access [API](/source/API) directly or use the PowerShell infrastructure of *Providers*, which make data stores addressable using unique [paths](/source/Path_(computing)). Data stores are exposed using [drive letters](/source/Drive_letter_assignment), and hierarchies within them, addressed as directories. PowerShell ships with providers for the [file system](/source/File_system), [registry](/source/Windows_Registry), the [certificate](/source/Public_key_certificate) store, as well as the [namespaces](/source/Namespace) for command aliases, variables, and functions.[41] PowerShell also includes various cmdlets for managing various [Windows](/source/Microsoft_Windows) systems, including the file system, or using [Windows Management Instrumentation](/source/Windows_Management_Instrumentation) to control [Windows components](/source/List_of_Microsoft_Windows_components). Other applications can register cmdlets with PowerShell, thus allowing it to manage them, and, if they enclose any datastore (such as a database), they can add specific providers as well.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*]

A cmdlet can be added to the shell via modules or before v2 snap-ins. Users are not limited to the cmdlets included in the base PowerShell installation.

The number of cmdlets included in the base PowerShell install for various versions:

- Windows PowerShell 1.0: 129[42]

- Windows PowerShell 2.0: 632[43]

- Windows PowerShell 3.0: ≈1,000[44]

- Windows PowerShell 5.0: ≈1,300[45]

- Windows PowerShell 5.1: 1,586[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*]

- PowerShell 7.0: 1,507[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*]

- PowerShell 7.4: 1,656

### Pipeline

To enable [pipeline](/source/Pipeline_(computing)) [semantics](/source/Semantics_(computer_science)), similar to the [Unix pipeline](/source/Pipeline_(Unix)), a cmdlet receives input and outputs result as objects. If a cmdlet outputs multiple objects, each object of the collection is passed through the pipeline before the next object is processed.[35] A PowerShell pipeline enables complex logic using the pipe (|) operator to connect stages. However, the PowerShell pipeline differs from Unix pipelines in that stages execute *within* the PowerShell runtime rather than as a set of processes coordinated by the [operating system](/source/Operating_system). Additionally, structured .NET objects, rather than [byte streams](/source/Bitstream), are passed from one stage to the next. Using [objects](/source/Object_(computer_science)) and executing stages within the PowerShell runtime eliminates the need to [serialize](/source/Serialization_(computing)) data structures, or to extract them by explicitly [parsing](/source/Parser) text output.[46] An object can also [encapsulate](/source/Encapsulation_(computer_programming)) certain functions that work on the contained data, which become available to the recipient command for use.[47][48] For the last cmdlet in a pipeline, PowerShell automatically pipes its output object to the Out-Default cmdlet, which transforms the objects into a stream of format objects and then renders those to the screen.[49][50]

Because a PowerShell object is a .NET object, it has a .ToString() method which is used to serialize object state. In addition, PowerShell allows formatting definitions to be specified, so the text representation of objects can be customized by choosing which data elements to display, and in what manner. However, in order to maintain [backward compatibility](/source/Backward_compatibility), if an external executable is used in a pipeline, it receives a text stream representing the object, instead of directly integrating with the PowerShell type system.[51][52][53]

### Scripting

PowerShell includes a [dynamically typed](/source/Dynamically_typed) [language for scripting](/source/Scripting_language) which can implement complex operations using cmdlets [imperatively](/source/Imperative_programming). The language supports variables, functions, branching ([if-then-else](/source/Conditional_(programming))), loops ([while](/source/While_loop), [do](/source/Do_while_loop), [for](/source/For_loop), and [foreach](/source/Foreach)), structured error/exception handling and [closures](/source/Closure_(computer_science))/[lambda expressions](/source/Anonymous_function),[54] as well as integration with .NET. Variables in PowerShell scripts are prefixed with $. Variables can be assigned any value, including the output of cmdlets. Strings can be enclosed either in single quotes or in double quotes: when using double quotes, variables will be expanded even if they are inside the quotation marks. Enclosing the path to a file in braces preceded by a dollar sign (as in ${C:\foo.txt}), known as namespace variable notation, creates a reference to the contents of the file. If it is used as an [L-value](/source/Value_(computer_science)), anything assigned to it will be written to the file. When used as an [R-value](/source/Value_(computer_science)), the contents of the file will be read. If an object is assigned, it is serialized before being stored.[55]

Object members can be accessed using . notation, as in C# syntax. PowerShell provides special variables, such as $args, which is an array of all the command-line arguments passed to a function from the command line, and $_, which refers to the current object in the pipeline.[56] PowerShell also provides [arrays](/source/Array_data_type) and [associative arrays](/source/Associative_array). The PowerShell language also evaluates arithmetic expressions entered on the command line immediately, and it parses common abbreviations, such as GB, MB, and KB.[57][58]

Using the function keyword, PowerShell provides for the creation of functions. A simple function has the following general look:[59]

function name ([Type]$Param1, [Type]$Param2) {
    # Instructions
}

However, PowerShell allows for advanced functions that support named parameters, positional parameters, switch parameters and dynamic parameters.[59]

function Verb-Noun {
    param (
        # Definition of static parameters
    )
    dynamicparam {
        # Definition of dynamic parameters
    }
    begin {
        # Set of instruction to run at the start of the pipeline
    }
    process {
        # Main instruction sets, ran for each item in the pipeline
    }
    end {
        # Set of instruction to run at the end of the pipeline
    }
}

The defined function is invoked in either of the following forms:[59]

name value1 value2
Verb-Noun -Param1 value1 -Param2 value2

PowerShell allows any static .NET methods to be called by providing their namespaces enclosed in brackets ([]), and then using a pair of colons (::) to indicate the static method.[60] For example:

[Console]::WriteLine("PowerShell")

There are dozens of ways to create objects in PowerShell. Once created, one can access the properties and instance methods of an object using the . notation.[60]

PowerShell accepts [strings](/source/String_(computer_science)), both raw and [escaped](/source/Escape_character). A string enclosed between single [quotation marks](/source/Quotation_mark) is a raw string while a string enclosed between double quotation marks is an escaped string. PowerShell treats straight and curly quotes as equivalent.[61]

The following list of special characters is supported by PowerShell:[62]

PowerShell special characters Sequence Meaning `0 Null `a Alert `b Backspace `e Escape (since PowerShell 6) `f Form feed `n Newline `r Carriage return `t Horizontal tab `u{x} Unicode escape sequence (since PowerShell 6) `v Vertical tab --% Treat any character from this point forward literally

For error handling, PowerShell provides a .NET-based [exception-handling](/source/Exception_handling_syntax) mechanism. In case of errors, objects containing information about the error (Exception object) are thrown, which are caught using the try ... catch construct (although a trap construct is supported as well). PowerShell can be configured to silently resume execution, without actually throwing the exception; this can be done either on a single command, a single session or perpetually.[63]

Scripts written using PowerShell can be made to persist across sessions in either a .ps1 file or a .psm1 file (the latter is used to implement a module). Later, either the entire script or individual functions in the script can be used. Scripts and functions operate analogously with cmdlets, in that they can be used as commands in pipelines, and parameters can be bound to them. Pipeline objects can be passed between functions, scripts, and cmdlets seamlessly. To prevent unintentional running of scripts, script execution is disabled by default and must be enabled explicitly.[64] Enabling of scripts can be performed either at system, user or session level. PowerShell scripts can be [signed](/source/Code_signing) to verify their integrity, and are subject to [Code Access Security](/source/Code_Access_Security).[65]

The PowerShell language supports [binary prefix](/source/Binary_prefix) notation similar to the [scientific notation](/source/Scientific_notation) supported by many programming languages in the C-family.[66]

### Hosting

One can also use PowerShell embedded in a management application, which uses the PowerShell runtime to implement the management functionality. For this, PowerShell provides a [managed](/source/Managed_code) hosting [API](/source/API). Via the APIs, the application can instantiate a *runspace* (one instantiation of the PowerShell runtime), which runs in the application's [process](/source/Process_(computing)) and is exposed as a Runspace object.[8] The state of the runspace is encased in a SessionState object. When the runspace is created, the PowerShell runtime initializes the instantiation, including initializing the providers and enumerating the cmdlets, and updates the SessionState object accordingly. The Runspace then must be opened for either synchronous processing or asynchronous processing. After that it can be used to execute commands.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*]

To execute a command, a pipeline (represented by a Pipeline object) must be created and associated with the runspace. The pipeline object is then populated with the cmdlets that make up the pipeline. For sequential operations (as in a PowerShell script), a Pipeline object is created for each statement and nested inside another Pipeline object.[8] When a pipeline is created, PowerShell invokes the pipeline processor, which resolves the cmdlets into their respective [assemblies](/source/Assembly_(CLI)) (the *command processor*) and adds a reference to them to the pipeline, and associates them with InputPipe, OutputPipe and ErrorOutputPipe objects, to represent the connection with the pipeline. The types are verified and parameters bound using [reflection](/source/Reflection_(computer_science)).[8] Once the pipeline is set up, the host calls the Invoke() method to run the commands, or its asynchronous equivalent, InvokeAsync(). If the pipeline has the Write-Host cmdlet at the end of the pipeline, it writes the result onto the console screen. If not, the results are handed over to the host, which might either apply further processing or display the output itself.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*]

[Microsoft Exchange Server](/source/Microsoft_Exchange_Server) 2007 uses the hosting APIs to provide its management GUI. Each operation exposed in the GUI is mapped to a sequence of PowerShell commands (or pipelines). The host creates the pipeline and executes them. In fact, the interactive PowerShell console itself is a PowerShell host, which [interprets](/source/Interpreter) the scripts entered at command line and creates the necessary Pipeline objects and invokes them.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*]

### Desired State Configuration

DSC allows for declaratively specifying how a software environment should be configured.[67]

Upon running a *configuration*, DSC will ensure that the system gets the state described in the configuration. DSC configurations are idempotent. The *Local Configuration Manager* (LCM) periodically polls the system using the control flow described by *resources* (imperative pieces of DSC) to make sure that the state of a configuration is maintained.

## Versions

All major releases are still supported, and each major release has featured backwards compatibility with preceding versions.[*[dubious](https://en.wikipedia.org/wiki/Wikipedia:Accuracy_dispute#Disputed_statement) – [discuss](https://en.wikipedia.org/wiki/Talk:PowerShell#Dubious)*]

### Project Monad

Initially using the code name "Monad", PowerShell was first shown publicly at the Professional Developers Conference in October 2003 in Los Angeles.

### Windows PowerShell

#### 1.0

Named Windows PowerShell, version 1.0 was released in November 2006 for [Windows XP SP2](/source/Windows_XP_SP2), [Windows Server 2003 SP1](/source/Windows_Server_2003_SP1) and [Windows Vista](/source/Windows_Vista)[68] and as an optional component of [Windows Server 2008](/source/Windows_Server_2008).

#### 2.0

Windows PowerShell ISE v2.0 on [Windows 7](/source/Windows_7), an [integrated development environment](/source/Integrated_development_environment) for PowerShell scripts

Version 2.0 integrates with [Windows 7](/source/Windows_7) and [Windows Server 2008 R2](/source/Windows_Server_2008_R2)[69] and is released for [Windows XP](/source/Windows_XP) with Service Pack 3, [Windows Server 2003](/source/Windows_Server_2003) with Service Pack 2, and [Windows Vista](/source/Windows_Vista) with Service Pack 1.[70][71]

The version includes changes to the language and hosting API, in addition to including more than 240 new cmdlets.[72][73]

New features include:[74][75][76]

- **Remoting**: Using [WS-Management](/source/WS-Management), Allows scripts and cmdlets to be invoked on a remote machine or a large set of remote machines.

- **Background jobs**: Also called a *PSJob*, it allows a command sequence (script) or pipeline to be invoked asynchronously. Jobs can be run on the local machine or on multiple remote machines. An interactive cmdlet in a PSJob blocks the execution of the job until user input is provided.

- **Transactions**: Enable cmdlet and developers can perform [transactional operations](/source/Transaction_processing). Includes transaction cmdlets for starting, committing, and rolling back a *PSTransaction* as well as features to manage and direct the transaction to the participating cmdlet and provider operations. The PowerShell Registry provider supports transactions.

- **Advanced functions**: Initially called "script cmdlets", these bundled cmdlets was later renamed "advanced functions".[77]

- **SteppablePipelines**: This allows the user to control when the BeginProcessing(), ProcessRecord() and EndProcessing() functions of a cmdlet are called.

- **Modules**: Allows script developers and administrators to organize and partition scripts in self-contained, reusable units. Code from a [module](/source/Modular_programming) executes in its own self-contained context and does not affect the state outside the module. Modules can define a restricted runspace environment by using a script. They have a persistent state as well as public and private members.

- **Data language**: A domain-specific subset of the language that allows data definitions to be decoupled from the scripts and allows [localized](/source/Internationalization_and_localization) string resources to be imported into the script at runtime (*Script Internationalization*).

- **Script debugging**: Allows [breakpoints](/source/Breakpoint) to be set in a script or function. Breakpoints can be set on lines, line & columns, commands and read or write access of variables. It includes a set of cmdlets to control the breakpoints via script.

- **Eventing**: Allows listening, forwarding, and acting on management and system events. Eventing allows hosts to be notified about state changes to their managed entities. It also enables scripts to subscribe to *ObjectEvents*, *PSEvents*, and *WmiEvents* and process them synchronously and asynchronously.

- **Integrated Scripting Environment (ISE)**: GUI-based host that provides integrated debugger, [syntax highlighting](/source/Syntax_highlighting), tab completion and up to 8 Unicode-enabled consoles (Runspaces) in a tabbed UI, as well as the ability to run only the selected parts in a script.

- **Network file transfer**: Native support for prioritized, throttled, and asynchronous transfer of files between machines using the [Background Intelligent Transfer Service](/source/Background_Intelligent_Transfer_Service) (BITS).[78]

- **New cmdlets**: Including Out-GridView, which displays tabular data in the [WPF](/source/Windows_Presentation_Foundation) [GridView](/source/Grid_view) object, on systems that allow it, and if ISE is installed and enabled.

- **New operators**: -Split, -Join, and Splatting (@) operators.

- **Exception handling with Try-Catch-Finally**: Unlike other .NET languages, this allows multiple exception types for a single catch block.

- **Nestable Here-Strings**: [Here-Strings](/source/Here_document) have been improved and can now nest.[79]

- **Block comments**: Support for block comments using <# and #> as delimiters.[80]

- **New APIs**: The new APIs range from handing more control over the parser and runtime to the host, to creating and managing collection of Runspaces (RunspacePools) as well as the ability to create *Restricted Runspaces* which only allow a configured subset of PowerShell to be invoked. The new APIs also support participation in a transaction

#### 3.0

Version 3.0 integrates with [Windows 8](/source/Windows_8), [Windows Server 2012](/source/Windows_Server_2012), [Windows 7](/source/Windows_7) with Service Pack 1, [Windows Server 2008](/source/Windows_Server_2008) with Service Pack 1, and [Windows Server 2008 R2](/source/Windows_Server_2008_R2) with Service Pack 1.[81][82]

Version 3.0 is part of a larger package, Windows Management Framework 3.0 (WMF3), which also contains the [WinRM](/source/WinRM) service to support remoting.[82] Microsoft made several [Community Technology Preview](/source/Community_Technology_Preview) releases of WMF3. An early community technology preview 2 (CTP 2) version of Windows Management Framework 3.0 was released on December 2, 2011.[83] Windows Management Framework 3.0 was released for general availability in December 2012[84] and is included with Windows 8 and Windows Server 2012 by default.[85]

New features include:[82][86]: 33–34

- **Scheduled jobs**: Jobs can be scheduled to run on a preset time and date using the [Windows Task Scheduler](/source/Windows_Task_Scheduler) infrastructure.

- **Session connectivity**: Sessions can be disconnected and reconnected. Remote sessions have become more tolerant of temporary network failures.

- **Improved code writing**: [Code completion](/source/Code_completion) (IntelliSense) and [snippets](/source/Snippet_(programming)) are added. ISE allows users to use dialog boxes to fill in parameters for cmdlets.

- **Delegation support**: Administrative tasks can be delegated to users who do not have permissions for that type of task, without granting them perpetual additional permissions.

- **Help update**: Help documentations can be updated via Update-Help command.

- **Automatic module detection**: Modules are loaded implicitly whenever a command from that module is invoked. Code completion works for unloaded modules as well.

- **New commands**: Dozens of new modules were added, including functionality to manage disks get-WmiObject win32_logicaldisk, volumes, firewalls, network connections, and printers, which had previously been performed via WMI.[*[further explanation needed](https://en.wikipedia.org/wiki/Wikipedia:Please_clarify)*]

#### 4.0

Version 4.0 integrates with [Windows 8.1](/source/Windows_8.1), [Windows Server 2012 R2](/source/Windows_Server_2012_R2), [Windows 7 SP1](/source/Windows_7_SP1), [Windows Server 2008 R2](/source/Windows_Server_2008_R2) SP1 and [Windows Server 2012](/source/Windows_Server_2012).[87]

New features include:

- **Desired State Configuration**:[88][89][90] Declarative language extensions and tools that enable the deployment and management of configuration data for systems using the [DMTF](/source/DMTF) management standards and [WS-Management](/source/WS-Management) Protocol

- **New default execution policy**: On Windows Servers, the default execution policy is now RemoteSigned.

- **Save-Help**: Help can now be saved for modules that are installed on remote computers.

- **Enhanced debugging**: The [debugger](/source/Debugger) now supports debugging workflows, remote script execution and preserving debugging sessions across session reconnections.

- **-PipelineVariable switch**: A new ubiquitous parameter to expose the current pipeline object as a variable for programming purposes

- **Network diagnostics** to manage physical and [Hyper-V](/source/Hyper-V)'s virtualized [network switches](/source/Network_switch)

- **Where and ForEach** method syntax provides an alternate method of filtering and iterating over objects.

#### 5.0

Version 5.0 icon

Version 5.0 was re-released with Windows Management Framework (WMF) 5.0 on February 24, 2016, following an initial release with a severe bug.[91]

Key features included:

- The new class [keyword](/source/Reserved_word) that creates [classes](/source/Class_(computer_programming)) for [object-oriented programming](/source/Object-oriented_programming)

- The new enum keyword that creates [enums](/source/Enumeration)

- OneGet cmdlets to support the [Chocolatey](/source/Chocolatey) [package manager](/source/Package_management)[92]

- Extending support for switch management to [layer 2](/source/Data_link_layer) network switches.[93]

- Debugging for background jobs and instances hosted in other processes (each of which is called a "runspace")

- Desired State Configuration (DSC) Local Configuration Manager (LCM) version 2.0

- DSC partial configurations

- DSC Local Configuration Manager meta-configurations

- Authoring of DSC resources using classes

#### 5.1

Version 5.1 was released along with the [Windows 10 Anniversary Update](/source/Windows_10_Anniversary_Update)[94] on August 2, 2016, and in [Windows Server 2016](/source/Windows_Server_2016).[95] PackageManagement now supports proxies, PSReadLine now has ViMode support, and two new cmdlets were added: Get-TimeZone and Set-TimeZone. The LocalAccounts module allows for adding/removing local user accounts.[96] A preview for was released for Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 on July 16, 2016,[97] and was released on January 19, 2017.[98]

Version 5.1 is the first to come in two editions of "Desktop" and "Core". The "Desktop" edition is the continuation product line that uses the .NET Framework, and the "Core" edition runs on .NET Core and is bundled with Windows Server 2016 Nano Server. In exchange for smaller footprint, the latter lacks some features such as the cmdlets to manage clipboard or join a computer to a domain, WMI version 1 cmdlets, Event Log cmdlets and profiles.[25] This was the final version exclusively for Windows. Version 5.1 remains pre-installed on Windows 10, Windows 11 and Windows Server 2022, while the .NET version needs to be installed separately and can run side-by-side with the .NET Framework version.[99][100]

### PowerShell Core

#### 6.0

Renamed to PowerShell Core, version 6.0 was first announced on August 18, 2016, when Microsoft unveiled its decision to make the product [cross-platform](/source/Cross-platform_software), independent of Windows, free and open source.[5] It achieved [general availability](/source/General_availability) on January 10, 2018, for Windows, [macOS](/source/MacOS) and [Linux](/source/Linux).[101] It has its own support lifecycle and adheres to the Microsoft lifecycle policy that is introduced with Windows 10: Only the latest version of PowerShell Core is supported. Microsoft expects to release one minor version for PowerShell Core 6.0 every six months.[102]

The most significant change in this version is the expansion to the other platforms. For Windows administrators, this version did not include any major new features. In an interview with the community on January 11, 2018, the development team was asked to list the top 10 most exciting things that would happen for a Windows IT professional who would migrate from version 5.1 to version 6.0. In response, Angel Calvo of Microsoft could only name two: cross-platform and open-source.[103] PowerShell 6 changed to [UTF-8](/source/UTF-8) as default encoding, with some exceptions.[104] (version 7.4 changes more to UTF-8).[105]

#### 6.1

According to Microsoft, one of the new features of version 6.1 is "Compatibility with 1900+ existing cmdlets in Windows 10 and [Windows Server 2019](/source/Windows_Server_2019)."[106] Still, no details of these cmdlets can be found in the full version of the change log.[107] Microsoft later professes that this number was insufficient as PowerShell Core failed to replace Windows PowerShell 5.1 and gain traction on Windows.[108] It was, however, popular on Linux.[108]

#### 6.2

Version 6.2 is focused primarily on performance improvements, bug fixes, and smaller cmdlet and language enhancements that improved developer productivity.[109]

### PowerShell

#### 7.0

Renamed to simply PowerShell, version 7 replaces the previous product lines: PowerShell Core and Windows PowerShell.[110][108] The focus in development was to make version 7 a viable replacement for version 5.1, i.e. to have near parity with it in terms of compatibility with modules that ship with Windows.[111]

New features include:[112]

- The -Parallel switch for the ForEach-Object cmdlet to help handle parallel processing

- A new error view

- The Get-Error cmdlet

- Pipeline chaining operators (&& and ||) that allow conditional execution of the next cmdlet in the pipeline

- The [?:](/source/%3F%3A) operator for [ternary operation](/source/Ternary_operation)

- The ?? operator for [null coalescing](/source/Null_coalescing_operator)

- The ??= operator for null coalescing assignment

- Cross-platform Invoke-DscResource (experimental)

- Return of the Out-GridView cmdlet

- Return of the -ShowWindow switch for the Get-Help

#### 7.2

Version 7.2 is the next long-term support version, after version 7.0. It uses .NET 6.0 and features universal installer packages for Linux. On Windows, updates to version 7.2 and later come via the [Microsoft Update](/source/Microsoft_Update) service; this feature has been missing from versions 6.0 through 7.1.[113]

#### 7.3

Version 7.3 includes some general Cmdlet updates and fixes, testing for framework dependent package in release pipeline as well as build and packaging improvements.[114]

#### 7.4

Version 7.4 is based on .NET 8 and is considered the long term support (LTS) release.[115]

Changes include:[116]

- webcmdlets default to [UTF-8](/source/UTF-8) [encoding](/source/Character_encoding) (changing from [ASCII](/source/ASCII)-superset [ISO-8859-1](/source/ISO-8859-1), that does not support [Unicode](/source/Unicode)). Previously UTF-8 was default for other, but not all, things.

#### 7.5

Version 7.5 is the latest stable release, released January 2025; it was built on .NET 9.0.1. It includes enhancements for performance, usability, and security.[117] Key updates include improvements to tab completion, such as better type inference and new argument completers, as well as fixes for Invoke-WebRequest and Invoke-RestMethod. This release also adds the new ConvertTo-CliXml and ConvertFrom-CliXml cmdlets, and updates core modules like PSReadLine and Microsoft.PowerShell.PSResourceGet. Breaking changes include updates to Test-Path parameter handling, and default settings for New-FileCatalog.

Prior to GA Release there were 5 preview releases and 1 RC release of PowerShell v7.5.0,[118] with a full release blog post for this version expected soon.

#### 7.6

Version 7.6 is based on .NET 9 and is the latest release. It was released on March 17, 2026.[119]

Changes include:

- General cmdlet updates and fixes

- Update PowerShell Profile DSC resource manifests to allow null for content

- Add GitHub Actions annotations for Pester test failures

- Fix Import-Module.Tests.ps1 to handle Arm32 platform[120]

## Comparison of cmdlets with similar commands

The following table contains various cmdlets that ship with PowerShell that have notably similar functionality to commands in other shells. Many of these cmdlets are exposed to the user via predefined aliases to make their use familiar to users of the other shells.

Comparison of cmdlets with commands of other shells Cmdlet Predefined alias Command Prompt command Unix shell command Functionality Clear-Host[a] cls, clear cls clear Clears the screen Compare-Object compare, diff fc diff Compares the content of two files Copy-Item cpi, copy, cp copy cp Copies files and folders Get-ChildItem gci, dir, ls[b] dir ls Lists files and folders Get-Command gcm help, where type, which, compgen Lists available commands and gets command path Get-ComputerInfo gin systeminfo uname -a Retrieve system information Get-Content gc, type, cat type cat Reports the content of a file Get-Date {{{1}}} date + time date Reports date and time Get-Help help, man[c] help apropos, man Reports a command's documentation Get-History ghy, h, history DOSKEY /HISTORY fc -l, history[d] Lists previous commands Get-Location gl, pwd cd pwd Reports the working directory Get-Process gps, ps tlist,[e] tasklist[f] ps Reports running processes Invoke-WebRequest iwr, curl, wget[g] curl[121] wget, curl Downloads contents from the Internet Measure-Command —N/a —N/a time (Unix) Reports elapsed time in the real world to execute the command that follows. Measure-Object measure —N/a wc Counts characters, words and lines of text. Powershell adds summaries of numeric properties of objects Move-Item mi, move, mv move mv Moves files and folders Pop-Location popd popd popd Reverts the working directory to the path last pushed Push-Location pushd pushd pushd Pushes the working directory path and changes the working directory Read-Host {{{1}}} set /P read Reads input into a variable from the command line Remove-Item ri, del, erase, rmdir, rd, rm del, erase, rmdir, rd rm, rmdir Deletes files or folders Rename-Item rni, ren ren, rename mv Renames a file or folder Register-ScheduledJob —N/a at, schtasks[122] at, cron Schedule tasks to be run at a different time Select-String sls find, findstr grep Reports lines of a file that match a pattern Set-Date {{{1}}} date + time date -s Resets the date and time Set-Location sl, cd, chdir cd, chdir cd Changes the working path Set-Variable sv, set set env, export, set, setenv Creates or alters the contents of an environment variable Sort-Object sort sort sort Sorts lines of text; cmdlet also sorts objects Start-Sleep sleep sleep timeout[h] Pauses the current process for a specified amount of time. Stop-Process spps, kill kill,[e] taskkill[f] kill[i] Stops a running process Tee-Object tee —N/a tee Pipes input to a file or variable, passing the input along the pipeline Test-Connection ping ping ping Sends ICMP echo requests to a remote machine Write-Output echo, write echo echo Writes text to standard output

**Notes**

1. **[^](#cite_ref-121)** implemented as a predefined function

1. **[^](#cite_ref-122)** ls is absent from the Linux version of PowerShell Core

1. **[^](#cite_ref-123)** man is absent from the Linux version of PowerShell Core

1. '*[^](#cite_ref-124)**fc* is defined in the POSIX standard and **history** is not. However most Unix implementations also define **history**.

1. ^ [***a***](#cite_ref-Available_tlist_kill_125-0) [***b***](#cite_ref-Available_tlist_kill_125-1) Available in [Windows NT 4](/source/Windows_NT_4), [Windows 98 Resource Kit](/source/Resource_Kit#Windows_Resource_Kits), Windows 2000 Support Tools

1. ^ [***a***](#cite_ref-Available_tasklist_taskkill_126-0) [***b***](#cite_ref-Available_tasklist_taskkill_126-1) Introduced in Windows XP Professional Edition

1. **[^](#cite_ref-127)** curl and wget are absent from PowerShell Core, so as to not interfere with similarly named native commands

1. **[^](#cite_ref-130)** Windows cmd shell only

1. **[^](#cite_ref-UNIX_kill_misnomer_131-0)** Also used in UNIX to send a process any [signal](/source/Signal_(computing)), the "Terminate" signal is merely the default

## Filename extensions

Extension Description .ps1 Script file[123] .psd1 Module's manifest file; usually comes with a script module or binary module[124] .psm1 Script module file[125] .ps1xml Format and type definitions file[53][126] .psc1 Console file[127] .pssc Session configuration file[128] .psrc Role Capability file[129]

## Application support

Application Version Cmdlets Provider Management GUI Exchange Server 2007 402 Yes Yes Windows Server 2008 Yes Yes No Microsoft SQL Server 2008 Yes Yes No Microsoft SharePoint 2010 Yes Yes No System Center Configuration Manager 2012 R2 400+ Yes No System Center Operations Manager 2007 74 Yes No System Center Virtual Machine Manager 2007 Yes Yes Yes System Center Data Protection Manager 2007 Yes No No Windows Compute Cluster Server 2007 Yes Yes No Microsoft Transporter Suite for Lotus Domino[130] 08.02.0012 47 No No Microsoft PowerTools for Open XML[131] 1.0 33 No No IBM WebSphere MQ[132] 6.0.2.2 44 No No IoT Core Add-ons[133] 74 Unknown Unknown Quest Management Shell for Active Directory[134] 1.7 95 No No Special Operations Software Specops Command[135] 1.0 Yes No Yes VMware vSphere PowerCLI[136] 6.5 R1 500+ Yes Yes Internet Information Services[137] 7.0 54 Yes No Windows 7 Troubleshooting Center[138] 6.1 Yes No Yes Microsoft Deployment Toolkit[139] 2010 Yes Yes Yes NetApp PowerShell Toolkit[140][141] 4.2 2000+ Yes Yes JAMS Scheduler – Job Access & Management System[142] 5.0 52 Yes Yes UIAutomation[143] 0.8 432 No No Dell Equallogic[144] 3.5 55 No No LOGINventory[145] 5.8 Yes Yes Yes SePSX[146] 0.4.1 39 No No ScriptRunner 7.3 Yes Yes Yes

## See also

- [Common Information Model (computing)](/source/Common_Information_Model_(computing))

- [Comparison of command shells](/source/Comparison_of_command_shells)

- [Comparison of programming languages](/source/Comparison_of_programming_languages)

- [Web-Based Enterprise Management](/source/Web-Based_Enterprise_Management)

- [Windows Script Host](/source/Windows_Script_Host)

- [Windows Terminal](/source/Windows_Terminal)

## References

1. **[^](#cite_ref-wikidata-f537b8b935009ed76655962b9f36670bdb07a44d-v20_1-0)** ["Release 7.6.3"](https://github.com/PowerShell/PowerShell/releases/tag/v7.6.3). June 16, 2026. Retrieved June 17, 2026.

1. **[^](#cite_ref-2)** ["v7.7.0-preview.2 Release of PowerShell"](https://github.com/PowerShell/PowerShell/releases/tag/v7.7.0-preview.2). *GitHub*. May 27, 2026. Retrieved May 28, 2026.

1. **[^](#cite_ref-3)** ["PowerShell for every system!"](https://github.com/PowerShell/PowerShell). June 12, 2017 – via [GitHub.com](/source/GitHub.com).

1. **[^](#cite_ref-snover2008_4-0)** Snover, Jeffrey (May 25, 2008). ["PowerShell and WPF: WTF"](https://blogs.msdn.microsoft.com/powershell/2008/05/25/powershell-and-wpf-wtf/). *Windows PowerShell Blog*. Microsoft.

1. ^ [***a***](#cite_ref-ars-opensource_5-0) [***b***](#cite_ref-ars-opensource_5-1) [***c***](#cite_ref-ars-opensource_5-2) [***d***](#cite_ref-ars-opensource_5-3) Bright, Peter (August 18, 2016). ["PowerShell is Microsoft's latest open source release, coming to Linux, OS X"](https://arstechnica.com/information-technology/2016/08/powershell-is-microsofts-latest-open-source-release-coming-to-linux-os-x/). *[Ars Technica](/source/Ars_Technica)*. [Condé Nast](/source/Cond%C3%A9_Nast). [Archived](https://web.archive.org/web/20200409020253/https://arstechnica.com/information-technology/2016/08/powershell-is-microsofts-latest-open-source-release-coming-to-linux-os-x/) from the original on April 9, 2020. Retrieved May 12, 2020.

1. **[^](#cite_ref-6)** ["Announcing Windows 10 Insider Preview Build 14971 for PC"](https://blogs.windows.com/windows-insider/2016/11/17/announcing-windows-10-insider-preview-build-14971-for-pc/). November 17, 2016.

1. **[^](#cite_ref-7)** ["PowerShell is replacing Command Prompt"](https://support.microsoft.com/en-us/windows/powershell-is-replacing-command-prompt-fdb690cf-876c-d866-2124-21b6fb29a45f).

1. ^ [***a***](#cite_ref-how_8-0) [***b***](#cite_ref-how_8-1) [***c***](#cite_ref-how_8-2) [***d***](#cite_ref-how_8-3) [***e***](#cite_ref-how_8-4) ["powershell"](https://stackoverflow.com/questions/tagged/powershell). Retrieved March 13, 2023.

1. **[^](#cite_ref-MSDN_9-0)** Truher, Jim (December 2007). ["Extend Windows PowerShell With Custom Commands"](https://web.archive.org/web/20081006195551/http://msdn.microsoft.com/en-us/magazine/cc163293.aspx). *[MSDN Magazine](/source/MSDN_Magazine)*. Microsoft. Archived from [the original](https://msdn.microsoft.com/en-us/magazine/cc163293.aspx) on October 6, 2008.

1. **[^](#cite_ref-lowe2007_10-0)** Lowe, Scott (January 4, 2007). ["Exchange 2007: Get used to the command line"](https://www.techrepublic.com/article/exchange-2007-get-used-to-the-command-line/). *[TechRepublic](/source/TechRepublic)*. [CBS Interactive](/source/CBS_Interactive). [Archived](https://web.archive.org/web/20181116084157/https://www.techrepublic.com/article/exchange-2007-get-used-to-the-command-line/) from the original on November 16, 2018. Retrieved May 12, 2020.

1. **[^](#cite_ref-snover2007b_11-0)** Snover, Jeffrey (November 13, 2007). ["SQL Server Support for PowerShell!"](https://web.archive.org/web/20071115215316/http://blogs.msdn.com/powershell/archive/2007/11/13/sql-server-support-for-powershell.aspx). *Windows PowerShell Blog* (blog posting). Microsoft. Archived from [the original](http://blogs.msdn.com/powershell/archive/2007/11/13/sql-server-support-for-powershell.aspx) on November 15, 2007. Retrieved November 13, 2007.

1. **[^](#cite_ref-pcmag-server2003_12-0)** Dragan, Richard V. (April 23, 2003). ["Windows Server 2003 Delivers Improvements All Around"](https://www.pcmag.com/archive/windows-server-2003-delivers-improvements-all-around-40764). *[PCMag.com](/source/PCMag.com)*. [Ziff Davis](/source/Ziff_Davis). A standout feature here is that virtually all admin utilities now work from the command line (and most are available through telnet).

1. **[^](#cite_ref-13)** Jones, Don (2020). *Shell of an Idea: The Untold History of PowerShell*. Don Gannon-Jones. p. 25. [ISBN](/source/ISBN_(identifier)) [978-1-9536450-3-6](https://en.wikipedia.org/wiki/Special:BookSources/978-1-9536450-3-6).

1. **[^](#cite_ref-MonadManifesto_14-0)** Jeffrey P. Snover (August 8, 2002). ["Monad Manifesto"](https://www.jsnover.com/Docs/MonadManifesto.pdf) (PDF). *Windows PowerShell Blog*. Microsoft. Retrieved April 2, 2021.

1. **[^](#cite_ref-15)** Biggar and Harbaugh (September 14, 2017). ["The Man Behind Windows PowerShell"](https://www.heavybit.com/library/podcasts/to-be-continuous/ep-37-the-man-behind-windows-powershell/). *To Be Continuous* (Podcast). Heavybit. Retrieved September 14, 2017.

1. **[^](#cite_ref-monad-renamed_16-0)** ["Windows PowerShell (Monad) Has Arrived"](https://blogs.msdn.microsoft.com/powershell/2006/04/25/windows-powershell-monad-has-arrived/). *Windows PowerShell Blog*. [Microsoft](/source/Microsoft). April 25, 2006.

1. **[^](#cite_ref-powershell-vista_17-0)** Snover, Jeffrey (November 15, 2006). ["Windows PowerShell & Windows Vista"](http://blogs.msdn.com/powershell/archive/2006/11/15/windows-powershell-windows-vista.aspx). *Windows PowerShell Blog* (blog posting). [Microsoft](/source/Microsoft).

1. **[^](#cite_ref-PowerShell-V2-RTM_18-0)** ["Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0)"](https://web.archive.org/web/20131013100052/http://support.microsoft.com/kb/968929). *Support*. [Microsoft](/source/Microsoft). September 30, 2013. Archived from [the original](http://support.microsoft.com/kb/968929) on October 13, 2013.

1. **[^](#cite_ref-posey_19-0)** Posey, Brien (October 6, 2009). ["10 reasons why you should learn to use PowerShell"](https://www.techrepublic.com/blog/10-things/10-reasons-why-you-should-learn-to-use-powershell/). *TechRepublic*. Retrieved April 2, 2021.

1. **[^](#cite_ref-20)** ["What is Pester and Why Should I Care?"](https://blogs.technet.microsoft.com/heyscriptingguy/2015/12/14/what-is-pester-and-why-should-i-care/). December 14, 2015.

1. **[^](#cite_ref-21)** Snover, Jeffrey (August 18, 2016). ["PowerShell is open sourced and is available on Linux"](https://azure.microsoft.com/en-us/blog/powershell-is-open-sourced-and-is-available-on-linux/). *Microsoft Azure Blog*. [Microsoft](/source/Microsoft).

1. **[^](#cite_ref-22)** ["PowerShell/PowerShell"](https://github.com/PowerShell/PowerShell). *GitHub*. Retrieved August 18, 2016.

1. **[^](#cite_ref-23)** Hansen, Kenneth; Calvo, Angel (August 18, 2016). ["PowerShell on Linux and Open Source!"](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/). *Windows PowerShell Blog*. [Microsoft](/source/Microsoft).

1. **[^](#cite_ref-24)** [Foley, Mary Jo](/source/Mary_Jo_Foley) (August 18, 2016). ["Microsoft open sources PowerShell; brings it to Linux and Mac OS X"](https://www.zdnet.com/article/microsoft-open-sources-powershell-brings-it-to-linux-and-mac-os-x/). *[ZDNet](/source/ZDNet)*. [CBS Interactive](/source/CBS_Interactive).

1. ^ [***a***](#cite_ref-:0_25-0) [***b***](#cite_ref-:0_25-1) ["PowerShell on Nano Server"](https://technet.microsoft.com/en-us/windows-server-docs/get-started/powershell-on-nano-server). *[TechNet](/source/Microsoft_TechNet)*. [Microsoft](/source/Microsoft). October 20, 2016.

1. **[^](#cite_ref-pash_26-0)** ["Pash"](https://pash.sourceforge.net/). *[SourceForge](/source/SourceForge)*. [Dice Holdings, Inc.](/source/Dice_Holdings%2C_Inc.) Retrieved September 27, 2011.

1. **[^](#cite_ref-pash_project_27-0)** ["Pash Project"](https://github.com/Pash-Project/Pash/). *[GitHub](/source/GitHub)*. Retrieved April 10, 2013.

1. **[^](#cite_ref-28)** ["Pash is now obsolete · Issue #429 · Pash-Project/Pash"](https://github.com/Pash-Project/Pash/issues/429). *GitHub*. Retrieved November 26, 2019.

1. **[^](#cite_ref-29)** Jones, Don (2020). *Shell of an Idea: The Untold History of PowerShell*. Don Gannon-Jones. p. 45. [ISBN](/source/ISBN_(identifier)) [978-1-9536450-3-6](https://en.wikipedia.org/wiki/Special:BookSources/978-1-9536450-3-6).

1. **[^](#cite_ref-30)** Payette, Bruce (2008). [*Windows PowerShell in Action*](https://books.google.com/books?id=MYZQAAAAMAAJ). Manning Pubs Co Series. Manning. p. 27. [ISBN](/source/ISBN_(identifier)) [9781932394900](https://en.wikipedia.org/wiki/Special:BookSources/9781932394900). Retrieved July 22, 2016. The core PowerShell language is based on the POSIX 1003.2 grammar for the [Korn shell](/source/KornShell).

1. **[^](#cite_ref-31)** Jones, Don (2020). *Shell of an Idea: The Untold History of PowerShell*. Don Gannon-Jones. p. 109. [ISBN](/source/ISBN_(identifier)) [978-1-9536450-3-6](https://en.wikipedia.org/wiki/Special:BookSources/978-1-9536450-3-6).

1. **[^](#cite_ref-32)** ["about_Command_Precedence"](https://technet.microsoft.com/en-us/library/hh848304.aspx). *[TechNet](/source/Microsoft_TechNet)*. [Microsoft](/source/Microsoft). May 8, 2014.

1. **[^](#cite_ref-33)** Wheeler, Sean (September 7, 2021). ["about Parsing - PowerShell"](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_parsing?view=powershell-7.2#passing-arguments-to-native-commands). *Microsoft Docs*. Retrieved December 5, 2021.

1. **[^](#cite_ref-34)** ["Windows PowerShell Extended Type System"](http://msdn2.microsoft.com/en-us/library/ms714419.aspx). Retrieved November 28, 2007.

1. ^ [***a***](#cite_ref-cmdlets_35-0) [***b***](#cite_ref-cmdlets_35-1) [***c***](#cite_ref-cmdlets_35-2) ["Windows PowerShell Cmdlets"](http://msdn2.microsoft.com/en-us/library/ms714395.aspx). Retrieved November 28, 2007.

1. **[^](#cite_ref-firstcmdlet_36-0)** ["Creating Your First Cmdlet"](http://msdn2.microsoft.com/en-us/library/ms714622.aspx). Retrieved November 28, 2007.

1. **[^](#cite_ref-37)** ["Get-Verb"](https://technet.microsoft.com/en-us/library/hh852690.aspx). *[TechNet](/source/Microsoft_TechNet)*. [Microsoft](/source/Microsoft). May 8, 2014.

1. **[^](#cite_ref-38)** ["Cmdlet Overview"](https://msdn.microsoft.com/en-us/library/ms714395%28v=vs.85%29.aspx). *[MSDN](/source/MSDN)*. [Microsoft](/source/Microsoft). May 8, 2014.

1. **[^](#cite_ref-39)** ["Adding parameters That Process Command Line Input"](http://msdn2.microsoft.com/en-us/library/ms714663.aspx). Retrieved November 28, 2007.

1. **[^](#cite_ref-40)** ["Adding parameters That Process Pipeline Input"](http://msdn2.microsoft.com/en-us/library/ms714597.aspx). Retrieved November 28, 2007.

1. **[^](#cite_ref-41)** ["Windows PowerShell Providers"](https://technet.microsoft.com/en-us/library/dd347723.aspx). Retrieved October 14, 2010.

1. **[^](#cite_ref-42)** Yoshizawa, Tomoaki; Ramos, Durval (September 29, 2012). ["PowerShell 1.0 Cmdlets"](https://social.technet.microsoft.com/wiki/contents/articles/13769.powershell-1-0-cmdlets.aspx). *TechNet Articles*. Microsoft.

1. **[^](#cite_ref-43)** Yoshizawa, Tomoaki (July 10, 2012). ["PowerShell 2.0 Cmdlets"](https://social.technet.microsoft.com/wiki/contents/articles/13876.powershell-2-0-cmdlets.aspx). *TechNet Articles*. Microsoft.

1. **[^](#cite_ref-44)** Wilson, Ed (2013). ["1: Overview of Windows PowerShell 3.0"](https://www.microsoftpressstore.com/articles/article.aspx?p=2201304). *Windows Powershell 3.0 Step by Step*. Sebastopol, California: [Microsoft Press](/source/Microsoft_Press). [ISBN](/source/ISBN_(identifier)) [978-0-7356-7000-6](https://en.wikipedia.org/wiki/Special:BookSources/978-0-7356-7000-6). [OCLC](/source/OCLC_(identifier)) [829236530](https://search.worldcat.org/oclc/829236530). Windows PowerShell 3.0 comes with about 1,000 cmdlets on Windows 8

1. **[^](#cite_ref-45)** Wilson, Ed (2015). ["1: Overview of Windows PowerShell 5.0"](https://www.microsoftpressstore.com/articles/article.aspx?p=2449029). *Windows PowerShell Step by Step* (Third ed.). Redmond, Washington: [Microsoft Press](/source/Microsoft_Press). [ISBN](/source/ISBN_(identifier)) [978-1-5093-0043-3](https://en.wikipedia.org/wiki/Special:BookSources/978-1-5093-0043-3). [OCLC](/source/OCLC_(identifier)) [927112976](https://search.worldcat.org/oclc/927112976). Windows PowerShell 5.0 comes with about 1,300 cmdlets on Windows 10

1. **[^](#cite_ref-46)** ["Windows PowerShell Owner's Manual: Piping and the Pipeline in Windows PowerShell"](https://technet.microsoft.com/en-us/library/ee176927.aspx). *[TechNet](/source/Microsoft_TechNet)*. [Microsoft](/source/Microsoft). Retrieved September 27, 2011.

1. **[^](#cite_ref-47)** Jones, Don (2008). ["Windows PowerShell – Rethinking the Pipeline"](http://www.microsoft.com/technet/technetmag/issues/2007/07/PowerShell/default.aspx). *[Microsoft TechNet](/source/Microsoft_TechNet)*. [Microsoft](/source/Microsoft). Retrieved November 28, 2007.

1. **[^](#cite_ref-48)** ["Windows PowerShell Object Concepts"](https://web.archive.org/web/20070819233213/http://msdn2.microsoft.com/en-us/library/aa347685.aspx). Archived from [the original](http://msdn2.microsoft.com/en-us/library/aa347685.aspx) on August 19, 2007. Retrieved November 28, 2007.

1. **[^](#cite_ref-49)** ["How PowerShell Formatting and Outputting REALLY works"](http://blogs.msdn.com/powershell/archive/2006/04/30/586973.aspx). Retrieved November 28, 2007.

1. **[^](#cite_ref-50)** ["More – How does PowerShell formatting really work?"](http://blogs.msdn.com/powershell/archive/2006/06/21/641738.aspx). Retrieved November 28, 2007.

1. **[^](#cite_ref-51)** ["about_Pipelines"](https://technet.microsoft.com/en-us/library/hh847902.aspx). *[TechNet](/source/Microsoft_TechNet)*. [Microsoft](/source/Microsoft). May 8, 2014.

1. **[^](#cite_ref-52)** ["about_Objects"](https://technet.microsoft.com/en-us/library/hh847810.aspx). *[TechNet](/source/Microsoft_TechNet)*. [Microsoft](/source/Microsoft). May 8, 2014.

1. ^ [***a***](#cite_ref-about_Format.ps1xml_53-0) [***b***](#cite_ref-about_Format.ps1xml_53-1) ["about_Format.ps1xml"](https://technet.microsoft.com/en-us/library/hh847831.aspx). *[TechNet](/source/Microsoft_TechNet)*. [Microsoft](/source/Microsoft). May 8, 2014.

1. **[^](#cite_ref-lambda1_54-0)** ["Anonymous Functions and Code Blocks in PowerShell"](http://defndo.com/powershell-code-blocks-and-anonymous-functions/). Retrieved January 21, 2012.

1. **[^](#cite_ref-55)** Payette, Bruce (2007). [*Windows PowerShell in Action*](https://books.google.com/books?id=MYZQAAAAMAAJ). Manning. p. 144. [ISBN](/source/ISBN_(identifier)) [978-1-932394-90-0](https://en.wikipedia.org/wiki/Special:BookSources/978-1-932394-90-0).

1. **[^](#cite_ref-56)** ["Introduction to Windows PowerShell's Variables"](https://web.archive.org/web/20180527163406/http://www.computerperformance.co.uk/powershell/powershell_variables.htm). Archived from [the original](http://www.computerperformance.co.uk/powershell/powershell_variables.htm) on May 27, 2018. Retrieved November 28, 2007.

1. **[^](#cite_ref-57)** ["Byte Conversion"](https://technet.microsoft.com/en-us/library/ee692684.aspx). *Windows PowerShell Tip of the Week*. October 22, 2009. Retrieved November 15, 2013.

1. **[^](#cite_ref-58)** Ravikanth (May 20, 2013). ["Converting to size units (KB, MB, GB, TB, and PB) without using PowerShell multipliers"](http://www.powershellmagazine.com/2013/05/20/converting-to-size-units-kb-mbgbtb-and-pb-without-using-powershell-multipliers/). *PowerShell Magazine*.

1. ^ [***a***](#cite_ref-about_Functions_59-0) [***b***](#cite_ref-about_Functions_59-1) [***c***](#cite_ref-about_Functions_59-2) ["about_Functions"](https://technet.microsoft.com/en-us/library/hh847829.aspx). *[Microsoft TechNet](/source/Microsoft_TechNet)*. [Microsoft](/source/Microsoft). October 17, 2013. Retrieved November 15, 2013.

1. ^ [***a***](#cite_ref-dotnet_60-0) [***b***](#cite_ref-dotnet_60-1) ["Lightweight Testing with Windows PowerShell"](http://msdn.microsoft.com/msdnmag/issues/07/05/TestRun/default.aspx). Retrieved November 28, 2007.

1. **[^](#cite_ref-61)** Angelopoulos, Alex; Karen, Bemowski (December 4, 2007). ["PowerShell Got Smart About Smart Quotes"](http://windowsitpro.com/powershell/powershell-got-smart-about-smart-quotes). *Windows IT Pro*. [Penton Media](/source/Penton_Media). Retrieved November 15, 2013.

1. **[^](#cite_ref-62)** ["About Special Characters"](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_special_characters?view=powershell-6). Powershell / Scripting. *Microsoft*. June 8, 2017. Retrieved June 20, 2019.

1. **[^](#cite_ref-63)** ["Trap \[Exception\] { "In PowerShell" }"](http://huddledmasses.org/trap-exception-in-powershell). Retrieved November 28, 2007.

1. **[^](#cite_ref-64)** ["Running Windows PowerShell Scripts"](http://www.microsoft.com/technet/scriptcenter/topics/winpsh/manual/run.mspx). *[Microsoft](/source/Microsoft)*. Retrieved November 28, 2007.

1. **[^](#cite_ref-65)** ["about_Signing"](https://technet.microsoft.com/en-us/library/hh847874.aspx). *[Microsoft TechNet](/source/Microsoft_TechNet)*. [Microsoft](/source/Microsoft). October 17, 2013. Retrieved November 15, 2013.

1. **[^](#cite_ref-66)** Lee Holmes (September 2006). *Windows PowerShell Quick Reference*. O'Reilly Media.

1. **[^](#cite_ref-67)** eslesar (May 23, 2023). ["Windows PowerShell Desired State Configuration Overview"](https://msdn.microsoft.com/en-us/powershell/dsc/overview). *msdn.microsoft.com*.

1. **[^](#cite_ref-68)** Chung, Leonard; Snover, Jeffrey; Kumaravel, Arul (November 14, 2006). ["It's a Wrap! Windows PowerShell 1.0 Released!"](https://devblogs.microsoft.com/powershell/its-a-wrap-windows-powershell-1-0-released). *Windows PowerShell Blog*. [Microsoft](/source/Microsoft).

1. **[^](#cite_ref-69)** ["PowerShell will be installed by default on Windows Server 08 R2 (WS08R2) and Windows 7 (W7)!"](http://blogs.msdn.com/powershell/archive/2008/10/28/powershell-will-be-installed-by-default-on-windows-server-08-r2-ws08r2-and-windows-7-w7.aspx). *Windows PowerShell Blog*. [Microsoft](/source/Microsoft). October 28, 2008. Retrieved September 27, 2011.

1. **[^](#cite_ref-70)** ["Windows Management Framework is here!"](http://blogs.msdn.com/powershell/archive/2009/10/27/windows-management-framework-is-here.aspx). October 27, 2009. Retrieved October 30, 2009.

1. **[^](#cite_ref-71)** ["Microsoft Support Knowledge Base: Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0)"](http://support.microsoft.com/kb/968929). Support.microsoft.com. September 23, 2011. Retrieved September 27, 2011.

1. **[^](#cite_ref-72)** ["574 Reasons Why We Are So Proud and Optimistic About W7 and WS08R2"](http://blogs.msdn.com/powershell/archive/2008/10/29/574-reasons-why-we-are-so-proud-and-optimistic-about-w7-and-ws08r2.aspx). *Windows PowerShell Blog*. [Microsoft](/source/Microsoft). October 29, 2008. Retrieved September 27, 2011.

1. **[^](#cite_ref-73)** Snover, Jeffrey (2008). ["PowerShell: Creating Manageable Web Services"](https://web.archive.org/web/20081013065033/http://channel9.msdn.com/pdc2008/ES24/). Archived from [the original](http://channel9.msdn.com/pdc2008/ES24/) on October 13, 2008. Retrieved July 19, 2015.

1. **[^](#cite_ref-74)** ["What's New in CTP of PowerShell 2.0"](http://blogs.msdn.com/powershell/archive/2007/11/06/what-s-new-in-ctp-of-powershell-2-0.aspx). Retrieved November 28, 2007.

1. **[^](#cite_ref-75)** ["Windows PowerShell V2 Community Technology Preview 2 (CTP2) – releaseNotes"](https://web.archive.org/web/20080506150324/http://www.microsoft.com/downloads/details.aspx?FamilyID=7c8051c2-9bfc-4c81-859d-0864979fa403&DisplayLang=en). *[Microsoft](/source/Microsoft)*. Archived from [the original](http://www.microsoft.com/downloads/details.aspx?FamilyId=7C8051C2-9BFC-4C81-859D-0864979FA403&displaylang=en) on May 6, 2008. Retrieved May 5, 2008.

1. **[^](#cite_ref-76)** ["Differences between PowerShell 1.0 and PowerShell 2.0"](https://web.archive.org/web/20100917075605/http://activexperts.com/admin/powershell/ps1vs2/). Archived from [the original](https://activexperts.com/admin/powershell/ps1vs2/) on September 17, 2010. Retrieved June 26, 2010.

1. **[^](#cite_ref-77)** Jones, Don (May 2010). ["Windows PowerShell: Writing Cmdlets in Script"](https://technet.microsoft.com/en-us/library/ff677563.aspx). *[TechNet Magazine](/source/TechNet_Magazine)*. Microsoft.

1. **[^](#cite_ref-78)** ["GoGrid Snap-in – Managing Cloud Services with PowerShell"](http://blogs.msdn.com/powershell/archive/2008/10/14/gogrid-snap-in-managing-cloud-services-with-powershell.aspx). *Windows PowerShell Blog*. [Microsoft](/source/Microsoft). October 14, 2008. Retrieved September 27, 2011.

1. **[^](#cite_ref-79)** ["Emit-XML"](http://blogs.msdn.com/powershell/archive/2008/10/18/emit-xml.aspx). *Windows PowerShell Blog*. [Microsoft](/source/Microsoft). October 17, 2008. Retrieved September 27, 2011.

1. **[^](#cite_ref-80)** ["Block Comments in V2"](http://blogs.msdn.com/powershell/archive/2008/06/14/block-comments-in-v2.aspx). *Windows PowerShell Blog*. [Microsoft](/source/Microsoft). June 14, 2008. Retrieved September 27, 2011.

1. **[^](#cite_ref-81)** Lee, Thomas (August 13, 2012). ["PowerShell Version 3 is RTM!"](http://tfl09.blogspot.co.uk/2012/08/powershell-version-3-is-rtm.html). *Under The Stairs*. Retrieved August 13, 2012.

1. ^ [***a***](#cite_ref-WMF3_82-0) [***b***](#cite_ref-WMF3_82-1) [***c***](#cite_ref-WMF3_82-2) ["Windows Management Framework 3.0"](http://www.microsoft.com/en-us/download/details.aspx?id=34595). *Download Center*. [Microsoft](/source/Microsoft). September 4, 2012. Retrieved November 8, 2012.

1. **[^](#cite_ref-83)** ["Windows Management Framework 3.0 Community Technology Preview (CTP) #2 Available for Download"](http://blogs.msdn.com/b/powershell/archive/2011/12/02/windows-management-framework-3-0-community-technology-preview-ctp-2-available-for-download.aspx). *Windows PowerShell Blog*. [Microsoft](/source/Microsoft). December 2, 2011.

1. **[^](#cite_ref-84)** ["Windows Management Framework 3.0"](https://www.microsoft.com/en-us/download/details.aspx?id=34595). *Download Center*. [Microsoft](/source/Microsoft). December 3, 2012.

1. **[^](#cite_ref-85)** Jofre, JuanPablo (December 14, 2016). ["Windows PowerShell System Requirements"](https://msdn.microsoft.com/en-us/powershell/scripting/setup/windows-powershell-system-requirements). *Microsoft Developer Network*. Microsoft. Retrieved April 20, 2017.

1. **[^](#cite_ref-86)** Honeycutt, Jerry (2012). Woolley, Valerie (ed.). [*Introducing Windows 8: An Overview for IT Professionals*](http://blogs.msdn.com/b/microsoft_press/archive/2012/11/13/free-ebook-introducing-windows-8-an-overview-for-it-professionals-final-edition.aspx). Redmond, WA: [Microsoft Press](/source/Microsoft_Press). [ISBN](/source/ISBN_(identifier)) [978-0-7356-7050-1](https://en.wikipedia.org/wiki/Special:BookSources/978-0-7356-7050-1).

1. **[^](#cite_ref-87)** ["Windows Management Framework 4.0 is now available"](http://blogs.msdn.com/b/powershell/archive/2013/10/25/windows-management-framework-4-0-is-now-available.aspx). [Microsoft](/source/Microsoft). October 24, 2013. Retrieved November 4, 2013.

1. **[^](#cite_ref-88)** Levy, Shay (June 25, 2013). ["New Features in Windows PowerShell 4.0"](http://www.powershellmagazine.com/2013/06/25/new-features-in-windows-powershell-4-0/). *PowerShell Magazine*. Retrieved June 26, 2013.

1. **[^](#cite_ref-89)** ["Desired State Configuration in Windows Server 2012 R2 PowerShell"](https://web.archive.org/web/20131226224907/http://channel9.msdn.com/Events/TechEd/NorthAmerica/2013/MDC-B302#fbid=sBK5uHH2bcL). *[Channel 9](/source/Channel_9_(Microsoft))*. [Microsoft](/source/Microsoft). June 3, 2013. Archived from [the original](http://channel9.msdn.com/Events/TechEd/NorthAmerica/2013/MDC-B302#fbid=sBK5uHH2bcL) on December 26, 2013. Retrieved June 26, 2013.

1. **[^](#cite_ref-90)** Hall, Adrian (June 7, 2013). ["Thoughts from Microsoft TechEd North America"](http://blogs.splunk.com/2013/06/07/thoughts-from-microsoft-teched-north-america/). *Blogs: Tips & Tricks*. [Splunk](/source/Splunk). Retrieved June 26, 2013.

1. **[^](#cite_ref-91)** ["Windows Management Framework (WMF) 5.0 RTM packages has been republished"](https://blogs.msdn.microsoft.com/powershell/2016/02/24/windows-management-framework-wmf-5-0-rtm-packages-has-been-republished/). *Windows PowerShell Blog*. [Microsoft](/source/Microsoft). February 24, 2016.

1. **[^](#cite_ref-92)** ["Q and A"](https://github.com/OneGet/oneget/wiki/Q-and-A). *GitHub*. Retrieved April 21, 2015.

1. **[^](#cite_ref-Snover_2014-04-03_93-0)** Snover, Jeffrey (April 3, 2014). ["Windows Management Framework V5 Preview"](https://web.archive.org/web/20140630174828/http://blogs.technet.com/b/windowsserver/archive/2014/04/03/windows-management-framework-v5-preview.aspx). *blogs.technet.com*. [Microsoft](/source/Microsoft). Archived from [the original](http://blogs.technet.com/b/windowsserver/archive/2014/04/03/windows-management-framework-v5-preview.aspx) on June 30, 2014. Retrieved April 21, 2015.

1. **[^](#cite_ref-94)** says, Jaap Brasser (August 2, 2016). ["#PSTip New PowerShell Commands in Windows 10 Anniversary Update"](http://www.powershellmagazine.com/2016/08/02/pstip-new-powershell-commands-in-windows-10-anniversary-update/).

1. **[^](#cite_ref-95)** ["What's New In Windows Server 2016 Standard Edition Part 9 – Management And Automation"](https://blogs.technet.microsoft.com/ausoemteam/2016/09/04/whats-new-in-windows-server-2016-standard-edition-part-9-management-and-automation/). September 4, 2016.

1. **[^](#cite_ref-96)** ["Microsoft.PowerShell.LocalAccounts Module"](https://technet.microsoft.com/en-us/library/mt651681.aspx). *technet.microsoft.com*. June 16, 2016.

1. **[^](#cite_ref-97)** ["Announcing Windows Management Framework (WMF) 5.1 Preview"](https://blogs.msdn.microsoft.com/powershell/2016/07/16/announcing-windows-management-framework-wmf-5-1-preview/). July 16, 2016.

1. **[^](#cite_ref-98)** ["WMF 5.1"](https://www.microsoft.com/en-us/download/details.aspx?id=54616). *Microsoft Download Center*.

1. **[^](#cite_ref-99)** ["What is Windows PowerShell? - PowerShell"](https://learn.microsoft.com/en-us/powershell/scripting/what-is-windows-powershell?view=powershell-7.4). *Microsoft Learn*. March 7, 2024. Retrieved August 19, 2024.

1. **[^](#cite_ref-100)** ["Migrating from Windows PowerShell 5.1 to PowerShell 7 - PowerShell"](https://learn.microsoft.com/en-us/powershell/scripting/whats-new/migrating-from-windows-powershell-51-to-powershell-7?view=powershell-7.4#using-powershell-7-side-by-side-with-windows-powershell-51). *Microsoft Learn*. April 2, 2024. Retrieved August 19, 2024.

1. **[^](#cite_ref-101)** Aiello, Joey (January 11, 2018). ["PowerShell Core 6.0: Generally Available (GA) and Supported!"](https://blogs.msdn.microsoft.com/powershell/2018/01/10/powershell-core-6-0-generally-available-ga-and-supported/). *PowerShell Team Blog*. Microsoft. [Archived](http://web.archive.org/web/20190716011707/https://blogs.msdn.microsoft.com/powershell/2018/01/10/powershell-core-6-0-generally-available-ga-and-supported/) from the original on July 16, 2019. Retrieved June 11, 2018.

1. **[^](#cite_ref-102)** Aiello, Joey; Wheeler, Sean (January 10, 2018). ["PowerShell Core Support Lifecycle"](https://web.archive.org/web/20181116013534/https://docs.microsoft.com/en-us/powershell/scripting/powershell-core-support?view=powershell-6). *Microsoft Docs*. [Microsoft](/source/Microsoft). Archived from [the original](https://docs.microsoft.com/en-us/powershell/scripting/PowerShell-Core-Support?view=powershell-6) on November 16, 2018. Retrieved January 11, 2018.

1. **[^](#cite_ref-103)** Calvo, Angel (January 11, 2018). ["Top 10 most exciting reasons to migrate"](https://techcommunity.microsoft.com/t5/PowerShell-AMA/Top-10-most-exciting-reasons-to-migrate/m-p/143960#M25). *PowerShell AMA*. [Microsoft](/source/Microsoft).

1. **[^](#cite_ref-104)** sdwheeler (August 3, 2023). ["What's New in PowerShell Core 6.0"](https://learn.microsoft.com/en-us/previous-versions/powershell/scripting/whats-new/what-s-new-in-powershell-core-60?view=powershell-7.1). *learn.microsoft.com*. Retrieved December 11, 2023. Default encoding is UTF-8 without a BOM except for New-ModuleManifest

1. **[^](#cite_ref-Windows-1252_105-0)** ["Understanding file encoding in VS Code and PowerShell - PowerShell"](https://learn.microsoft.com/en-us/powershell/scripting/dev-cross-plat/vscode/understanding-file-encoding?view=powershell-7.4). *learn.microsoft.com*. November 29, 2023. Retrieved December 11, 2023.

1. **[^](#cite_ref-106)** Aiello, Joey (September 13, 2018). ["Announcing PowerShell Core 6.1"](https://devblogs.microsoft.com/powershell/announcing-powershell-core-6-1/). *devblogs.microsoft.com*. [Microsoft](/source/Microsoft). Retrieved June 1, 2019.

1. **[^](#cite_ref-107)** ["PowerShell/PowerShell"](https://github.com/PowerShell/PowerShell). *GitHub*. Retrieved June 22, 2020.

1. ^ [***a***](#cite_ref-:1_108-0) [***b***](#cite_ref-:1_108-1) [***c***](#cite_ref-:1_108-2) Lee, Steve (April 5, 2019). ["The Next Release of PowerShell – PowerShell 7"](https://devblogs.microsoft.com/powershell/the-next-release-of-powershell-powershell-7/). [Microsoft](/source/Microsoft). Retrieved June 1, 2019.

1. **[^](#cite_ref-109)** Lee, Steve (March 28, 2019). ["General Availability of PowerShell Core 6.2"](https://devblogs.microsoft.com/powershell/general-availability-of-powershell-core-6-2/). *devblogs.microsoft.com*. [Microsoft](/source/Microsoft). Retrieved June 1, 2019.

1. **[^](#cite_ref-110)** Mackie, Kurt (May 30, 2019). ["Microsoft Releases PowerShell 7 Preview"](https://redmondmag.com/articles/2019/05/30/powershell-7-preview-released.aspx). [1105 Media Inc](https://en.wikipedia.org/w/index.php?title=1105_Media_Inc&action=edit&redlink=1). Retrieved June 1, 2019.

1. **[^](#cite_ref-111)** Lee, Steve (May 30, 2019). ["PowerShell 7 Road Map"](https://devblogs.microsoft.com/powershell/powershell-7-road-map/). *devblogs.microsoft.com*. [Microsoft](/source/Microsoft). Retrieved August 12, 2020.

1. **[^](#cite_ref-ps7p5_112-0)** ["PowerShell 7 Preview 5 | PowerShell"](https://devblogs.microsoft.com/powershell/powershell-7-preview-5/). October 23, 2019. [Archived](https://web.archive.org/web/20200215113601/https://devblogs.microsoft.com/powershell/powershell-7-preview-5/) from the original on February 15, 2020. Retrieved March 5, 2020.

1. **[^](#cite_ref-113)** ["PowerShell 7.2 is the new version of Microsoft's next-generation shell"](https://www.itsfoss.net/powershell-7-2/). *itsfoss.net*. November 12, 2021.

1. **[^](#cite_ref-114)** ["Release v7.3.0 Release of PowerShell · PowerShell/PowerShell"](https://github.com/PowerShell/PowerShell/releases/tag/v7.3.0). *[GitHub](/source/GitHub)*. [Archived](https://web.archive.org/web/20221109021444/https://github.com/PowerShell/PowerShell/releases/tag/v7.3.0) from the original on November 9, 2022. Retrieved March 7, 2022.

1. **[^](#cite_ref-115)** ["Release v7.4.7 Release of PowerShell · PowerShell/PowerShell"](https://github.com/PowerShell/PowerShell/releases/tag/v7.4.7). *GitHub*. Retrieved January 27, 2025.

1. **[^](#cite_ref-116)** sdwheeler (January 23, 2025). ["What's New in PowerShell 7.4 - PowerShell"](https://learn.microsoft.com/en-us/powershell/scripting/whats-new/what-s-new-in-powershell-74?view=powershell-7.4). *learn.microsoft.com*. Retrieved January 27, 2025.

1. **[^](#cite_ref-117)** sdwheeler (January 23, 2025). ["What's New in PowerShell 7.5 - PowerShell"](https://learn.microsoft.com/en-us/powershell/scripting/whats-new/what-s-new-in-powershell-75?view=powershell-7.5). *learn.microsoft.com*. Retrieved January 27, 2025.

1. **[^](#cite_ref-118)** ["Release v7.5.0 Release of PowerShell · PowerShell/PowerShell"](https://github.com/PowerShell/PowerShell/releases/tag/v7.5.0). *GitHub*. Retrieved January 27, 2025.

1. **[^](#cite_ref-119)** ["Release v7.6.0 of PowerShell · PowerShell/PowerShell"](https://github.com/PowerShell/PowerShell/releases/tag/v7.6.0). *GitHub*. Retrieved January 27, 2025.

1. **[^](#cite_ref-120)** sdwheeler (January 17, 2025). ["What's New in PowerShell 7.6 - PowerShell"](https://learn.microsoft.com/en-us/powershell/scripting/whats-new/what-s-new-in-powershell-76?view=powershell-7.6). *learn.microsoft.com*. Retrieved January 27, 2025.

1. **[^](#cite_ref-128)** ["Tar and Curl Come to Windows! - Microsoft Tech Community - 382409"](https://techcommunity.microsoft.com/t5/Containers/Tar-and-Curl-Come-to-Windows/ba-p/382409). March 22, 2019. [Archived](https://web.archive.org/web/20200911181923/https://techcommunity.microsoft.com/t5/containers/tar-and-curl-come-to-windows/ba-p/382409) from the original on September 11, 2020. Retrieved May 17, 2020.

1. **[^](#cite_ref-129)** ["Schtasks.exe"](https://learn.microsoft.com/en-us/windows/win32/taskschd/schtasks). March 12, 2023. Retrieved May 25, 2025.

1. **[^](#cite_ref-132)** Wheeler, Sean (June 2, 2020). ["About Scripts"](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_scripts?view=powershell-7.1). *Microsoft Docs*. Microsoft.

1. **[^](#cite_ref-133)** Wheeler, Sean; Smatlak, David; Wilson, Chase (October 16, 2019). ["How to write a PowerShell module manifest"](https://docs.microsoft.com/en-us/powershell/scripting/developer/module/how-to-write-a-powershell-module-manifest?view=powershell-7). *Docs*. Microsoft.

1. **[^](#cite_ref-134)** Wheeler, Sean; Smatlak, David (November 22, 2019). ["How to Write a PowerShell Script Module"](https://docs.microsoft.com/en-us/powershell/scripting/developer/module/how-to-write-a-powershell-script-module?view=powershell-7). *Microsoft Docs*. Microsoft.

1. **[^](#cite_ref-135)** Wheeler, Sean; Jofre, Juan Pablo; Vorobev, Sergei; Nikolaev, Kirill; Coulter, David (June 2, 2020). ["About Types.ps1xml"](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_types.ps1xml?view=powershell-7). *Microsoft Docs*. Microsoft.

1. **[^](#cite_ref-136)** Wheeler, Sean; Jofre, Juan Pablo; Vorobev, Sergei; Nikolaev, Kirill; Coulter, David. ["Export-Console"](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/export-console?view=powershell-5.1). *Microsoft Docs*. Microsoft.

1. **[^](#cite_ref-137)** Wheeler, Sean (June 2, 2020). ["About Session Configuration Files"](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_session_configuration_files?view=powershell-7). *Microsoft Docs*. Microsoft.

1. **[^](#cite_ref-138)** Wheeler, Sean (June 2, 2020). ["New-PSRoleCapabilityFile"](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/new-psrolecapabilityfile?view=powershell-7). *Microsoft Docs*. Microsoft.

1. **[^](#cite_ref-139)** ["Microsoft Transporter Suite for Lotus Domino"](http://www.microsoft.com/downloads/details.aspx?familyid=35fc4205-792b-4306-8e4b-0de9cce72172&displaylang=en). *[Microsoft](/source/Microsoft)*. Retrieved March 7, 2008.

1. **[^](#cite_ref-140)** ["PowerTools for Open XML"](http://www.codeplex.com/PowerTools). Retrieved June 20, 2008.

1. **[^](#cite_ref-141)** ["MO74: WebSphere MQ – Windows PowerShell Library"](http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg24017698). Retrieved December 5, 2007.

1. **[^](#cite_ref-142)** ["IoT Core Add-ons command-line options"](https://docs.microsoft.com/en-us/windows-hardware/manufacture/iot/iot-core-adk-addons-command-line-options). October 15, 2018. Retrieved June 13, 2020.

1. **[^](#cite_ref-143)** ["PowerShell Commands for Active Directory by Quest Software"](http://www.quest.com/powershell/activeroles-server.aspx). Retrieved July 2, 2008.

1. **[^](#cite_ref-144)** ["PowerShell Remoting through Group Policy"](http://www.specopssoft.com/powershell/). Retrieved December 7, 2007.

1. **[^](#cite_ref-145)** ["VMware vSphere PowerCLI"](https://www.vmware.com/go/PowerCLI). Retrieved September 9, 2014.{{[cite web](https://en.wikipedia.org/wiki/Template:Cite_web)}}: CS1 maint: deprecated archival service ([link](https://en.wikipedia.org/wiki/Category:CS1_maint:_deprecated_archival_service))

1. **[^](#cite_ref-146)** ["IIS7 PowerShell Provider Tech Preview 2"](https://web.archive.org/web/20100204104602/https://blogs.msdn.com/powershell/archive/2008/07/03/iis7-powershell-provider-tech-preview-2.aspx). *Windows PowerShell blog*. Archived from [the original](https://blogs.msdn.com/powershell/archive/2008/07/03/iis7-powershell-provider-tech-preview-2.aspx) on February 4, 2010. Retrieved July 3, 2008.

1. **[^](#cite_ref-147)** ["Kudos to the Win7 Diagnostics Team"](http://blogs.msdn.com/powershell/archive/2009/06/14/kudos-to-the-win7-diagnostics-team.aspx). Retrieved June 15, 2009.

1. **[^](#cite_ref-148)** Michael, Niehaus (July 10, 2009). ["MDT 2010 New Feature #16: PowerShell support"](http://blogs.technet.com/b/mniehaus/archive/2009/07/10/mdt-2010-new-feature-16-powershell-support.aspx). Retrieved October 27, 2014.

1. **[^](#cite_ref-149)** ["Kudos to NetApp for Data ONTAP PowerShell ToolKit"](http://blogs.msdn.com/b/powershell/archive/2010/06/16/kudos-to-netapp-for-data-ontap-powershell-toolkit.aspx). Retrieved June 15, 2010.

1. **[^](#cite_ref-150)** ["PowerShell Toolkit 4.2 Announcement"](http://community.netapp.com/t5/Microsoft-Cloud-and-Virtualization-Discussions/NetApp-PowerShell-Toolkit-4-2-released/m-p/120539). June 23, 2016. Retrieved September 7, 2016.

1. **[^](#cite_ref-151)** ["Heterogeneous Job Scheduling With PowerShell"](http://blogs.msdn.com/b/powershell/archive/2007/06/28/heterogeneous-job-scheduling-with-powershell.aspx). Retrieved September 15, 2010.

1. **[^](#cite_ref-152)** ["UIAutomation PowerShell Extensions"](https://web.archive.org/web/20160817204820/http://uiautomation.codeplex.com/). Archived from [the original](http://uiautomation.codeplex.com/) on August 17, 2016. Retrieved February 16, 2012.

1. **[^](#cite_ref-153)** ["EqualLogic HIT-ME with PowerShell"](http://en.community.dell.com/techcenter/storage/w/wiki/2688.aspx). Retrieved March 9, 2012.

1. **[^](#cite_ref-154)** [de:LOGINventory](https://de.wikipedia.org/wiki/LOGINventory)

1. **[^](#cite_ref-155)** ["Selenium PowerShell eXtensions"](http://sepsx.codeplex.com). Retrieved August 20, 2012.{{[cite web](https://en.wikipedia.org/wiki/Template:Cite_web)}}: CS1 maint: deprecated archival service ([link](https://en.wikipedia.org/wiki/Category:CS1_maint:_deprecated_archival_service))

## Further reading

- Finke, Douglas (2012). *Windows PowerShell for Developers*. [O'Reilly Media](/source/O'Reilly_Media). [ISBN](/source/ISBN_(identifier)) [978-1-4493-2270-0](https://en.wikipedia.org/wiki/Special:BookSources/978-1-4493-2270-0).

- Holmes, Lee (2006). *Windows PowerShell Quick Reference*. [O'Reilly Media](/source/O'Reilly_Media). [ISBN](/source/ISBN_(identifier)) [0-596-52813-2](https://en.wikipedia.org/wiki/Special:BookSources/0-596-52813-2).

- Holmes, Lee (2007). *Windows PowerShell Cookbook*. [O'Reilly Media](/source/O'Reilly_Media). [ISBN](/source/ISBN_(identifier)) [978-0-596-52849-2](https://en.wikipedia.org/wiki/Special:BookSources/978-0-596-52849-2).

- Jones, Don; Hicks, Jeffery (2010). *Windows PowerShell 2.0: TFM* (3rd ed.). Sapien Technologies. [ISBN](/source/ISBN_(identifier)) [978-0-9821314-2-8](https://en.wikipedia.org/wiki/Special:BookSources/978-0-9821314-2-8).

- Jones, Don (2020). *Shell of an Idea: The Untold History of PowerShell*. Self-published. [ISBN](/source/ISBN_(identifier)) [978-1-9536450-3-6](https://en.wikipedia.org/wiki/Special:BookSources/978-1-9536450-3-6).

- Kopczynski, Tyson; Handley, Pete; Shaw, Marco (2009). *Windows PowerShell Unleashed* (2nd ed.). [Pearson Education](/source/Pearson_Education). [ISBN](/source/ISBN_(identifier)) [978-0-672-32988-3](https://en.wikipedia.org/wiki/Special:BookSources/978-0-672-32988-3).

- Kumaravel, Arul; White, Jon; Naixin Li, Michael; Happell, Scott; Xie, Guohui; Vutukuri, Krishna C. (2008). *Professional Windows PowerShell Programming: Snapins, Cmdlets, Hosts and Providers*. [Wrox Press](/source/Wrox_Press). [ISBN](/source/ISBN_(identifier)) [978-0-470-17393-0](https://en.wikipedia.org/wiki/Special:BookSources/978-0-470-17393-0).

- Oakley, Andy (2005). *Monad (AKA PowerShell)*. [O'Reilly Media](/source/O'Reilly_Media). [ISBN](/source/ISBN_(identifier)) [0-596-10009-4](https://en.wikipedia.org/wiki/Special:BookSources/0-596-10009-4).

- Watt, Andrew (2007). *Professional Windows PowerShell*. [Wrox Press](/source/Wrox_Press). [ISBN](/source/ISBN_(identifier)) [978-0-471-94693-9](https://en.wikipedia.org/wiki/Special:BookSources/978-0-471-94693-9).

- Wilson, Ed (2013). *Windows PowerShell 3.0 Step by Step*. [Microsoft Press](/source/Microsoft_Press). [ISBN](/source/ISBN_(identifier)) [978-0-7356-6339-8](https://en.wikipedia.org/wiki/Special:BookSources/978-0-7356-6339-8).

- Wilson, Ed (2014). *Windows PowerShell Best Practices*. [Microsoft Press](/source/Microsoft_Press). [ISBN](/source/ISBN_(identifier)) [978-0-7356-6649-8](https://en.wikipedia.org/wiki/Special:BookSources/978-0-7356-6649-8).

## External links

Wikiversity has learning resources about ***[PowerShell](https://en.wikiversity.org/wiki/PowerShell)***

- [Official website](https://microsoft.com/powershell)

- [PowerShell](https://github.com/PowerShell/PowerShell) on [GitHub](/source/GitHub)

- [*Windows PowerShell Survival Guide*](http://social.technet.microsoft.com/wiki/contents/articles/183.windows-powershell-survival-guide-en-us.aspx) [Archived](https://web.archive.org/web/20120915113215/http://social.technet.microsoft.com/wiki/contents/articles/183.windows-powershell-survival-guide-en-us.aspx) September 15, 2012, at the [Wayback Machine](/source/Wayback_Machine) on [TechNet](/source/Microsoft_TechNet) Wiki

- [Windows Management Framework](https://www.microsoft.com/en-in/download/details.aspx?id=34595)[Archived](https://web.archive.org/web/20260308013456/https://www.microsoft.com/en-in/download/details.aspx?id=34595) March 8, 2026, at the [Wayback Machine](/source/Wayback_Machine)

v t e Microsoft Windows components APIs Architecture 9x NT Booting process Games Management tools App Installer Command Prompt Control Panel Device Manager DirectX Diagnostic Tool Disk Cleanup Drive Optimizer Driver Verifier Event Viewer IExpress Management Console Netsh Performance Monitor PowerShell Recovery Console Resource Monitor Settings Sysprep System Configuration System File Checker System Information System Policy Editor System Restore Task Manager Windows Backup Windows Error Reporting Windows Ink Windows Installer Windows Update Windows Insider WinRE WMI Apps 3D Viewer Calculator Calendar Camera Character Map City Art Search Clipchamp Clock Company Portal Copilot Edge Fax and Scan Feedback Hub Get Help Magnifier Mail Media Player 2022 Mesh Messaging Mobility Center Money Movies & TV Narrator News Notepad OneDrive OneNote Paint PC Manager People Phone Link Photos Quick Assist Remote Desktop Connection Snipping Tool Sound Recorder Speech Recognition Sticky Notes Store Terminal To Do Weather Whiteboard Windows App Xbox Shell Action Center Aero AutoPlay AutoRun ClearType Explorer Search IFilter Indexing Service Namespace Saved search Special folder Start menu Task View Taskbar Windows Spotlight Windows XP visual styles Services BITS CLFS Error Reporting Multimedia Class Scheduler Service Control Manager Shadow Copy Task Scheduler Wireless Zero Configuration File systems CDFS DFS exFAT FAT IFS NTFS EFS Hard link links Mount Point Reparse point TxF ReFS UDF Server Active Directory Active DRM Services DFS Replication Distributed Transaction Coordinator DNS Domains Folder redirection Group Policy Hyper-V IIS MSMQ Network Access Protection Print Services for UNIX PWS Remote Desktop Services Remote Differential Compression Remote Installation Services Roaming user profiles Server Core SharePoint System Resource Manager Windows Deployment Services Windows Media Services WSUS Architecture Boot Manager Console CSRSS Desktop Window Manager Enhanced Write Filter Graphics Device Interface Hardware Abstraction Layer I/O request packet Imaging Format Kernel Transaction Manager Library files Logical Disk Manager LSASS MinWin NTLDR Ntoskrnl.exe Object Manager Open XML Paper Specification Portable Executable DLL EXE Registry Resource Protection Security Account Manager Server Message Block Shadow Copy SMSS System Idle Process USER WHEA Winlogon WinUSB Security Security and Maintenance AppLocker BitLocker Credential Guard Data Execution Prevention Defender Family features Kernel Patch Protection Mandatory Integrity Control Protected Media Path User Account Control User Interface Privilege Isolation Windows Firewall Compatibility COMMAND.COM Windows Subsystem for Linux WoW64 API Active Scripting JScript VBScript WSH COM ActiveX ActiveX Document COM Structured storage DCOM OLE OLE Automation Transaction Server DirectX Native .NET Universal Windows Platform WinAPI Windows Mixed Reality Windows Runtime WinUSB Games Solitaire Collection Surf Discontinued Games 3D Pinball Chess Titans FreeCell Hearts Hold 'Em InkBall Purble Place Solitaire Spider Solitaire Tinker Apps ActiveMovie Address Book Anytime Upgrade Backup and Restore Cardfile CardSpace CD Player Chat Contacts Cortana Desktop Gadgets Diagnostics DriveSpace DVD Maker Easy Transfer Edge Legacy Fax Food & Drink Groove Music Health & Fitness Help and Support Center HyperTerminal Imaging Internet Explorer Journal Make Compatible Maps Media Center Meeting Space Messaging Messenger Mobile Device Center Movie Maker MSN Dial-Up NetMeeting NTBackup Outlook Express Paint 3D Pay Phone Companion Photo Gallery Photo Viewer Program Manager Skype Sports Start Steps Recorder Sysedit Syskey Tips Travel WinHelp WordPad Write Others Desktop Cleanup Wizard File Protection Games for Windows HPFS Interix Media Control Interface MS-DOS 7 Next-Generation Secure Computing Base POSIX subsystem ScanDisk Video for Windows Virtual DOS machine Windows on Windows Windows Services for UNIX Windows SideShow Windows System Assessment Tool Windows To Go WinFS Spun off to Microsoft Store DVD Player File Manager Hover! Mahjong Minesweeper Category List

v t e Windows command-line programs and shell builtins Ecosystem Interpreters COMMAND.COM Command Prompt PowerShell Recovery Console Terminals Windows Console Windows Terminal File system navigation cd (chdir) dir popd pushd tree File management attrib cacls cipher compact copy del (erase) deltree icacls mkdir (md) mklink move openfiles recover ren (rename) replace rmdir (rd) robocopy takeown xcopy Archiving expand extrac32 extract makecab pax tar Disk management chkdsk convert defrag diskcomp diskcopy diskpart diskraid diskshadow drvspace fdisk format fsutil label manage-bde MSCDEX refsutil subst scandisk sys vol vssadmin Processes at exit kill runas sc schtasks shutdown start taskkill tasklist Registry assoc ftype reg regini regsvr32 User environment chcp cmdkey date graftabl mode path set setver setx time title ver where whoami File contents comp edit edlin fc find findstr print type Scripting choice clip cscript doskey echo for forfiles goto if more pause prompt rem timeout Networking arp bitsadmin curl getmac hostname ipconfig nbtstat net netsh netstat nslookup PathPing ping rpcping route scp setspn sftp ssh ssh-add ssh-agent ssh-keygen ssh-keyscan tracert winrm winrs Maintenance and care auditpol dism dispdiag driverquery eventcreate eventtriggers gpresult gpupdate logman mofcomp msiexec ntbackup pentnt pnpunattend pnputil REAgentC relog sfc sxstrace systeminfo tpmtool tpmvscmgr tracerpt typeperf w32tm WBAdmin wecutil wevtutil winmgmt winsat wmic Boot management bcdedit bootcfg bootsect fixboot fixmbr Software development break debug exe2bin QBasic wsl Miscellaneous cls dpath help List of DOS commands Environment variables Windows Support Tools

v t e Common Language Infrastructure Architecture Application domain Code Access Security Common Intermediate Language instructions Common Type System Platform Invocation Services Virtual Execution System Components Assembly Delegate Global Assembly Cache Manifest Metadata Standard Libraries Implementations Microsoft .NET .NET Framework .NET Compact Framework .NET Micro Framework Other Mono DotGNU Languages Major C# Visual Basic F# PowerShell Other Axum A# Boo Clojure Cobra C++/CLI IronScheme IronPython IronRuby JScript .NET J# Nemerle Oxygene Phalanger Q# Scala Small Basic Comparison C# and Java C# and Visual Basic .NET Visual Basic and Visual Basic .NET

v t e Microsoft APIs and frameworks Graphics and UI Desktop Window Manager Direct2D Direct3D D3D (extensions) GDI / GDI+ WPF Silverlight WinUI Windows Color System Windows Image Acquisition Windows Imaging Component DirectX Graphics Infrastructure (DXGI) Windows Advanced Rasterization Platform WinG Audio DirectMusic DirectSound XACT Speech API XAudio2 Multimedia DirectX Media Objects Video Acceleration Xinput DirectInput DirectShow Managed DirectX Media Foundation XNA Windows Media Video for Windows Web MSHTML JScript VBScript BHO XDR SideBar Gadgets TypeScript Data access Data Access Components (MDAC) ADO ADO.NET ODBC OLE DB Extensible Storage Engine Entity Framework Sync Framework Access Database Engine MSXML OPC Networking Winsock LSP Winsock Kernel Filtering Platform NDIS Windows Rally BITS P2P API MSMQ DirectPlay Communication Messaging API Telephony API WCF Administration and management Win32 console Windows Script Host WMI (extensions) PowerShell Task Scheduler Offline Files Shadow Copy Windows Installer Error Reporting Event Log Common Log File System Component model COM COM+ ActiveX Distributed Component Object Model .NET Framework Libraries Framework Class Library Microsoft Foundation Classes (MFC) Active Template Library (ATL) Windows Template Library (WTL) Device drivers WDM WDF KMDF UMDF WDDM NDIS UAA VxD Security Crypto API CAPICOM Windows CardSpace Data Protection API Security Support Provider Interface (SSPI) .NET ASP.NET ADO.NET Remoting Silverlight TPL WCF WCS WPF WF Software factories Enterprise Library CCF IPC MSRPC Dynamic Data Exchange (DDE) Remoting WCF Accessibility Active Accessibility UI Automation Text and multilingual support DirectWrite Text Services Framework Text Object Model Input method editor Language Interface Pack Multilingual User Interface Uniscribe

v t e Microsoft free and open-source software (FOSS) Overview Microsoft and open source Shared Source Initiative Software Applications 3D Movie Maker Atom Conference XP Family.Show File Manager Open Live Writer Microsoft Edit Microsoft PowerToys Terminal Windows Calculator Windows Console Windows Package Manager WorldWide Telescope XML Notepad Video games Allegiance Zork Programming languages Bosque C# Dafny F# F* GW-BASIC IronPython IronRuby Lean P Power Fx PowerShell Project Verona Q# Small Basic Online TypeScript Visual Basic Frameworks, development tools .NET .NET Framework .NET Gadgeteer .NET MAUI .NET Micro Framework AirSim ASP.NET ASP.NET AJAX ASP.NET Core ASP.NET MVC ASP.NET Razor ASP.NET Web Forms Avalonia Babylon.js BitFunnel Blazor C++/WinRT CCF ChakraCore CLR Profiler Dapr DeepSpeed DiskSpd Dryad Dynamic Language Runtime eBPF on Windows Electron Entity Framework Fluent Design System Fluid Framework Infer.NET LightGBM Managed Extensibility Framework Microsoft Automatic Graph Layout Microsoft C++ Standard Library Microsoft Cognitive Toolkit Microsoft Design Language Microsoft Detours Microsoft Enterprise Library Microsoft SEAL mimalloc Mixed Reality Toolkit ML.NET mod_mono Mono MonoDevelop MSBuild MsQuic Neural Network Intelligence npm NuGet OneFuzz Open Management Infrastructure Open Neural Network Exchange Open Service Mesh Open XML SDK Orleans Playwright ProcDump ProcMon Python Tools for Visual Studio R Tools for Visual Studio RecursiveExtractor Roslyn Sandcastle SignalR StyleCop SVNBridge T2 Temporal Prover Text Template Transformation Toolkit TLA+ Toolbox U-Prove vcpkg Virtual File System for Git Voldemort VoTT Vowpal Wabbit Windows App SDK Windows Communication Foundation Windows Driver Frameworks KMDF UMDF Windows Forms Windows Presentation Foundation Windows Template Library Windows UI Library WinJS WinObjC WiX XDP for Windows XSP xUnit.net Z3 Theorem Prover Operating systems MS-DOS (v1.25, v2.0 & v4.0) Barrelfish SONiC Azure Linux Other ChronoZoom Extensible Storage Engine FlexWiki FourQ Gollum Project Mu ReactiveX SILK TLAPS TPM 2.0 Reference Implementation Windows Subsystem for Linux Licenses Microsoft Public License Microsoft Reciprocal License Forges CodePlex GitHub Related .NET Foundation F# Software Foundation Microsoft Open Specification Promise Open Letter to Hobbyists Open Source Security Foundation Outercurve Foundation Category

---
Adapted from the Wikipedia article [PowerShell](https://en.wikipedia.org/wiki/PowerShell) by Wikipedia contributors ([contributor history](https://en.wikipedia.org/wiki/PowerShell?action=history)). Available under [Creative Commons Attribution-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/). Changes may have been made.