cannot install feature in windows 2008 powershell 2.0

#Cannot install feature in windows 2008 powershell 2.0 how to#
#Cannot install feature in windows 2008 powershell 2.0 windows 10#
#Cannot install feature in windows 2008 powershell 2.0 free#

Using PowerShell to Install the Hyper-V PowerShell Module in Windows Server or Hyper-V Server 2012, 2016 & 2019 The Enable-WindowsOptionalFeature cmdlet does not have a ComputerName parameter, but it can be used in explicit PowerShell Remoting. For example, if you enabled the Hyper-V platform but not the tools, you can enable Microsoft-Hyper-V-All and it will not hurt anything. It’s fine to install a higher-level item even if some of its subcomponents are already installed. You can use the output from Get-WindowsOptionalFeature so that you don’t need to type any feature names. But, don’t forget that copy/paste works perfectly well in a PowerShell window (click/drag to highlight, to copy, right-click to paste). Tab completion will work for everything except the specific feature name. # Install the entire Hyper-V stack (hypervisor, services, and tools)Įnable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All # Install the Hyper-V management tool pack (Hyper-V Manager and the Hyper-V PowerShell module)Įnable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Tools-All I trimmed off the feature name in the images above, so all three possibilities are shown below: # Install only the PowerShell moduleĮnable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Management-PowerShell Installing either of the two options above it (Hyper-V Management Tools or the entire Hyper-V section) will include the module. The simplest is to install only the module by using its feature name. You have three options if you want to install the PowerShell Module on Windows 10. Compare the output of the cmdlet to the Windows Features screen: Unfortunately, this cmdlet does not have a nicely formatted display (even if you don’t pare it down with any filters), so it might not be obvious.

The reason that you see so many different objects is that it’s showing a flat display of the hierarchical tree that you’d get if you opened the Windows Features window instead. You can see all of the available options like this: Get-WindowsOptionalFeature -Online -FeatureName *hyper-v* | select DisplayName, FeatureName However, the module appears in a few different features, so you’ll need to pick the one that is most appropriate to you. There is only a single cmdlet, and you will only need to use it to enable a single feature. All cmdlets must be run from an elevated PowerShell prompt.Īs I mentioned in the preamble to this section, there a few different ways that you can enable the Hyper-V PowerShell module. The cmdlets that I’m about to show you will work just as well on a server operating system as on Windows 10, although the exact names of the features that you’ll use might be somewhat different.

#Cannot install feature in windows 2008 powershell 2.0 windows 10#

The server module’s cmdlets are simpler, so I’m going to separate out the more involved cmdlets into the Windows 10 section.

Windows 10 does include a PowerShell module for DISM, but it uses a smaller cmdlet set than what you’ll find on your servers. Using PowerShell to Install the Hyper-V PowerShell Module in Windows 10Īll of the PowerShell cmdlets for turning off and on Windows features and roles are overlays for the Deployment Image Servicing and Management (DISM) subsystem. There are several ways to do that, depending on your operating system and your goal. The quickest way to install the module is through PowerShell.

#Cannot install feature in windows 2008 powershell 2.0 how to#

How to Install the Hyper-V PowerShell Module with PowerShell If you need to use directly control Windows Server 2012/R2 or Hyper-V Server 2012/R2 using the PowerShell module as it ships in Windows 10/Windows Server 2016 or 2019, instructions are at the very end of this post. This short guide will explain how to install that module and understand its basic structure.

#Cannot install feature in windows 2008 powershell 2.0 free#

Even if you have installed the free Hyper-V Server product that ships with the Hyper-V role already enabled, you’ll still need to install the PowerShell module separately. The module’s installable component is distinct from the Hyper-V role, and the two are not automatically installed together. The best combination of power and simplicity for controlling Hyper-V is its PowerShell module.