Posts Tagged ‘dism’

Recently I was trying to add a Windows Feature into a Windows.wim file. 

After mounting the Wim I ran the below on a server 2012 machine

Dism /Image:”c:\temp” /Enable-Feature /FeatureName:NetFx3 /all

However I got 

Error 87 : “enable-feature is unknown”

I had to run the Dism /Image:”c:\temp” /Enable-Feature /FeatureName:NetFx3 /all command on a Windows 10 Box

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently trying to install VDA on a server 2016 server and it comes up with the below error trying to install Remote Desktop Session Host

Error Id: XDMI:334CF235

Citrix.MetaInstaller.MetaInstallerException ‘dism’ component failed to install with error 0x800f080c.
at Citrix.MetaInstaller.Prerequisite.RdsComponents.Install(InstallationContext context)

at Citrix.MetaInstaller.InstallationManager.InstallComponent(InstallableComponent component, InstallationContext installContext)


Looking in the logs it’s failing when running this :

dism /quiet /norestart /english /online /enable-feature /featurename:Remote-Desktop-Services /featurename:ServerMediaFoundation /featurename:AppServer /featurename:InkAndHandwritingServices /featurename:DesktopExperience

When I run this manually I get  : 

Feature name DesktopExperience is unknown. 
Feature name InkAndHandwritingServices is unknown.

This is actually already bundled in 2016 , you will need to install VDA 7.11 ( the minimum version that supports Server 2016 ) 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

For Server 2008 r2 and High


DISM /online /Cleanup-Image /StartComponentCleanup

You may need to start trusted installer before hand

net start TrustedInstaller


Server 2008



Task Scheduler (Local) –> Task Scheduler Library –> Microsoft –> Windows –> Servicing –> StartComponentCleanup


  • dism.exe /Online /Cleanup-Image /RestoreHealth

  • sfc /scannow


In an elevated command prompt, exec these 2 commands

copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7da\cleanmgr.exe %systemroot%\System32

copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b9cb6194b257cc63\cleanmgr.exe.mui %systemroot%\System32\en-US

You can then invoke disk cleanup the normal way – type cleanmgr and hit enter.


Dism.exe /online /Cleanup-Image /StartComponentCleanup then: Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

MacRDPClient[1]Recently upgraded a 2008 R2 Server to Enterprise from Standard using

 Dism /online /Set-Edition:ServerEnterprise /ProductKey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Wouldn’t work with the customers Volume License Enterprise Key. I used the KMS key which did work and activated using the Volume license key again , however on restart the server could not be remote desktoped in.

I had to run a 


Restart the server and reactivate it using the proper Volume license key. After this , restarting the Remote Desktop Service enabled RDP to work again


You should check in the Computer settings , that the memory is not set to 4GB Usable out of the new memory allowance. If this is the case you will need to do the following

  1. Open the command prompt and change working directory to System32 directory
  2. Type in slmgr.vbs -ckms (this clears and KMS entry you may have)
  3. Type slmgr.vbs -upk (this removes any product key installed)
  4. Type slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx (where the x’s is the new product key you want to use )
  5. Type slmgr.vbs -ato (this activates the server)
  6. Restart Server


VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)