How to use the windows powershell

NET Core. Supported versions are available on Windows, macOS, and Linux. Beginning in PowerShell 6, the PowerShell binary was renamed pwsh. You can start PowerShell preview versions using pwsh-preview. For more information, see About pwsh. To find cmdlet reference and installation documentation for PowerShell 7, use the following links:.

Use any of the following methods to start the installed version of Windows PowerShell 3. In cmd. You can also use the parameters of the powershell. For more information, see PowerShell. In Windows PowerShell 4. Example 1 Open a notepad file and write the script directly to Then save this file with a filename with the extension. The benefit of using ISE is that it provides an environment to run, test as well as debug the scripts easily. In this article, we tried to cover almost all the basic ideas on it and hopefully, this will give a clear picture of how to use it.

There are numerous tasks one can perform with the help of ps, even those of which you might not be aware. The more you start using it, the more you will start learning the capabilities of this powerful tool.

This is a guide to How to Use PowerShell?. You can also go through our other related articles to learn more —. Submit Next Question. By signing up, you agree to our Terms of Use and Privacy Policy. Forgot Password? This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the cookie policy.

I often find that presenters at conferences and user group meetings already have PowerShell running when they start entry-level presentations. This book begins by answering the questions I've heard attendees who haven't previously used PowerShell ask in those sessions. Specifically, this chapter focuses on finding and launching PowerShell, and solving some of the initial pain points that new users experience with PowerShell.

Be sure to follow along and walk through the examples shown in this chapter on your Windows 10 lab environment computer. All modern versions of Windows operating systems ship with PowerShell installed. If you're running a version older than 5. Notice that four different shortcuts for PowerShell are shown in Figure The computer used for demonstration purposes in this book is running the bit version of Windows 10 so there's a bit version of the PowerShell console and the PowerShell ISE Integrated Scripting Environment , and a bit version of each one as denoted by the x86 suffix on the shortcuts.

If you happen to be running a bit version of Windows 10, you'll only have two shortcuts. Those items don't have the x86 suffix, but are bit versions. If you have a bit operating system, my recommendation is to run the bit version of PowerShell unless you have a specific reason for running the bit version. In the production enterprise environments that I support, I use three different Active Directory user accounts.

I've mirrored those accounts in the lab environment used in this book. I log into the Windows 10 computer as a domain user who is not a domain or local administrator. That means it's unable to prompt for elevation for tasks that require the approval of an administrator. The following error message is generated:. The solution to this problem is to run PowerShell as a domain user who is a local administrator. This is how my second domain user account is configured.

Using the principle of least privilege, this account should NOT be a domain administrator, or have any elevated privileges in the domain. Close PowerShell. Relaunch the PowerShell console, except this time right-click on the Windows PowerShell shortcut and select Run as administrator as shown in Figure If you're logged into Windows as a normal user, you'll be prompted for credentials. I'll enter the credentials for my user account who is a domain user and local admin as shown in Figure