jasbowl.blogg.se

I’m not sure how they got on there, but assume that it was a Dell image load or something. I assume that this error was caused by an aborted uninstallation of one of the language packs. After running this script I was able to remove the Windows Hyper-V feature with no problems. Hopefully this helps someone else avoid a reinstallation. I went through a lot of iterative testing to make sure that I targeted the proper values. It’s pretty simple, but was frustrating because of the need to get the. (Get-ItemProperty -Path $key.PSPath).psobject.properties |where-object | Remove-ItemProperty -path $key.PSPath $keys = Get-ChildItem -Path "hklm:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect" In my case it was a German edition, so we’re searching for the string ‘~de-DE~’ below: $string = "*~de-DE~*" I really needed to resolve this, so I spent an hour writing a PowerShell script to run through each subkey value and remove the one’s that referenced a missing language pack. Just one of the 7600 registry values that need to be filtered. There are lots of them, literally thousands. The long fix starts with uninstalling language packs using the lpksetup tool and then manually removing references to any missing packs under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetectregistry subkeys. Now the original post recommends reinstalling the OS, which is a huge non-starter for me in an environment with a single file/AD server. This post gave me hint I needed to figure out the root cause, some missing language packs. I ran into the above error on a Dell Server 2016 machine when trying to uninstall Windows components (Hyper-V in this case). My day to day involves a good deal of sysadmin work, mostly Windows networks for small business customers.