What is Windows PowerShell?

All we need is an easy explanation of the problem, so here it is.

  • What is it for?
  • How do I use it?
  • How is it different from the regular Command Prompt?
  • Is there anything I should know before starting to use it?
  • Any awesome things you can do with it that a super user should know about?

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

Taken from Wikipedia http://en.wikipedia.org/wiki/Windows_PowerShell

Windows PowerShell is an extensible
command-line shell and associated
scripting language from Microsoft. It
was released in 2006 and is currently
available for Windows XP SP2/SP3,
Windows Server 2003, Windows Vista,
and is included in Windows Server 2008
as an optional feature. Windows
PowerShell 2.0 was released with
Windows 7 and Windows Server 2008 R2.
It is going to be backported to
previous supported platforms Windows
XP SP3, Windows Server 2003 SP2,
Windows Vista SP1 and Windows Server

Windows PowerShell integrates with the
Microsoft .NET Framework and provides
an environment to perform
administrative tasks by execution of
cmdlets (pronounced commandlets),
which are specialized .NET classes
implementing a particular operation;
scripts, which are compositions of
cmdlets along with imperative logic;
executables, which are standalone
applications; or by instantiating
regular .NET classes.5 These work
by accessing data in different data
stores, like the filesystem or
registry, which are made available to
the PowerShell runtime via Windows
PowerShell providers.

Windows PowerShell also provides a
hosting mechanism with which the
Windows PowerShell runtime can be
embedded inside other applications,
which can then leverage Windows
PowerShell functionality to implement
certain operations, including those
exposed via the graphical interface.
This capability has been utilized by
Microsoft Exchange Server 20075
to expose its management functionality
as PowerShell cmdlets and providers
and implement the graphical management
tools as PowerShell hosts which invoke
the necessary cmdlets. Other Microsoft
applications including Microsoft SQL
Server 20088 also expose their
management interface via PowerShell
cmdlets. In the future, graphical
interface-based management
applications on Windows will be
layered on top of Windows PowerShell.

Windows PowerShell includes its own
extensive, console-based help,
reminiscent of man pages in Unix
shells via the Get-Help cmdlet.

Searching Stackoverflow using this search I’ve found the following:

Again on serverfault using this search I’ve found the following:

Method 2

The “Great Powershell Heresy”, a.k.a. greatest innovation of PS over the UNIX-style shells you may be familiar with (tcsh, bash, etc.) is this:

Pipelines in “all those other shells” pass strings around.
Pipelines in PowerShell pass objects around.

Because of this, PowerShell might be “harder” to learn, i.e. it requires learning new technology, and doing detailed stuff requires more knowledge of what’s going on… but, once learned, it is VASTLY simpler to write shell scripts that can actually be read by other people (or you, 5 years later)… and those scripts are far less likely to “break” when something else on the system is changed.

Method 3

Quick and simple for the non power-user reading this:

Unless you are a system administrator you will not need Powershell. All it is is a collection of powerful shell commands for an administrator to use in the administration of Windows Server and client computers and the creation of scripts.

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply