Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.Login to AccountCreate an Account

Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

then I tried to apply my folder of updates:dism /Image:c:\wim /Add-Package /PackagePath:C:\updates

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Error: 2
An error occurred while processing the command.
For more information, review the log files.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

leen2

Posted 30 March 2012 - 11:33 AM

leen2

Member

Member

44 posts

Joined 17-June 08

OS:Windows 7 x64

Country:

The original error you were getting was "0x80070002" = ERROR_FILE_NOT_FOUND. This is usually caused by a little known feature of DISM, that it is horribly case sensitive and treats C:\path... as different from c:\Path... even though Windows explorer and the command line see them as the same. Note, if copying and pasting text from a text editor, smart quotes are different characters than regular quotes, etc... and will generate the same error.

So best advice is to locate the correct path in windows explorer and copy the entire path from the explorer bar as it is actually displayed. You can also copy it from the command line. This will copy the correct capitalization into the command.

In the second post, error code "0x80070057" = "The parameter is incorrect", so something is incorrect in the command you are trying to execute.

pacardon

Posted 30 March 2012 - 12:12 PM

Yikes. Reminds me of Linux where cd Home and cd home are two different directories. I'll give it a try and report my results. Thanks leen2!

Interesting results:

1. I can't seem to point DISM to a directory of cabs or msu files2. DISM refuses to accept an MSU file as a package using the /PackagePath command.3. I specifically have to tell it the cab to install. with /Add-Package /PackagePath:"C:\path\update.cab"

On the bright side, at least it isn't imagex and pkgmgr... I was trying that as well and I do not like it at all.

So I guess I have my answer. Just needed a nudge in the right direction. Thank you all!

cluberti

Posted 30 March 2012 - 02:59 PM

I've come across some other issues that the Win7 version of DISM has against a Vista or 2008 source - it's worth noting though, that DISM is just acting as a frontend for pkgmgr in this instance (you can see it in the logs), whereas on Win7 DISM does what pkgmgr did on Vista/2008. You'll notice in the log that the pkgmgr command line that is being passed contains /ip and /m, which means servicing a Vista or 2008 image via Win7's DISM cannot be pointed to a directory that doesn't already contain the requisite CAB and catalog files - ergo, the package you're trying to pass in cannot be an MSU package . That's the issue - you must manually expand the MSU file into it's CAB format before DISM on Win7 will be able to use those packages to service 2008 or Vista images (because of the options it chooses to pass to pkgmgr, which is actually doing the work).

Your script handles this already, so it's probably a better option in the meantime .