DISM error 87 the add-package option is unknown
Solution 1
Check "Windows Modules Installer" Service (TrustedInstaller.exe) is not disabled. It solves my similar problem
Solution 2
DISM global options are NOT case sensitive.
DISM feature names ARE case sensitive.
I noticed you're doing this online. Is there a particular reason you're using DISM instead of WUSA?
wusa path\to\file.msu /quiet /norestart
Error 87 is indeed a parameter problem (verified by net helpmsg 87
and confirmed here) but I'm not seeing specifically what's wrong with the syntax.
Did you copy/paste from the web or manually type it? If the former, try the latter just to be sure it didn't use some strange em-dash type character.
I've never run into a case issue, except when dealing with FeatureNames, so this would be a first. So to appease those who obsess over case (they likely come from a *n?x background ^_^) you could try doing it exactly as Microsoft has it documented and surround it on double quotes just to be sure:
DISM.exe /Online /Add-Package /PackagePath:"C:\tmp\tmp\Windows8.1-kb2999226-x64.cab"
Also, just to save us a bit of headache: You sure that's the proper path?
I'm on Windows 10 so the package doesn't apply to me but after pulling the .CAB from the .MSU, the command works just fine:
Try WUSA with the .MSU - you're making more work for yourself.
Related videos on Youtube
Plof27
Updated on September 18, 2022Comments
-
Plof27 almost 2 years
I am attempting to manually install Windows update KB2999226. I have extracted the msu file, but when attempting to install the .cab file through dism, I get the following error.
-
Ramhound over 8 yearsScreenshot does not work. Which is the reason your encourage to upload images to our imgur instead.
-
Plof27 over 8 yearsScreenshot should be working now.
-
Ramhound over 8 years[Your syntax is incorrect it is
Add-Package
notadd-package
...])technet.microsoft.com/en-us/library/dd744559%28v=ws.10%29.aspx). Determined this by doing a google search by the way. -
Plof27 over 8 years@Ramhound Makes no difference. Cmd is not case sensitive.
-
Ramhound over 8 yearsHave you tried? Those applets in my experience are case sensitive. What version of Windows?
-
Plof27 over 8 yearsYes I have tried. I'm on Windows 8.1
-
Ramhound over 8 years
-
-
Excellll about 8 yearsWelcome to Super User! Could you improve your answer by explaining how/where to check if the service is disabled?
-
himself over 7 yearsBurgi, how does it not? It just worked for me. DISM indeed shows this unrelated error when TrustedInstaller is disabled.
-
taz about 7 yearsRun (win+r) services.msc and on my Windows 7 enabling "Windows Modules Installer" fixed this issue.
-
not2qubit over 3 yearsthx for very cool trick with:
net helpmsg 87
. -
JW0914 over 2 yearsNo Windows commands are case-sensitive, as Windows is a case-insensitive OS. Windows commands and parameters are often presented with the first letter of each word capitalized since it makes it easier for readers, similar to how the first character words within a hashtag is capitalized.
-
JW0914 over 2 years
Dism
in Windows ≥8 isn't the same asDism
in Windows ≤7 - have you verified if you can useDism
from Windows ≥8 in Windows 7 (I'm assuming you're not using Windows 7 since it's EoL)?