Jump to content

Welcome to MSFN Forum
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 Account Create an Account


Photo

Can no longer slipstream vista updates

- - - - -

  • Please log in to reply
5 replies to this topic

#1
gotenks98

gotenks98

    Member

  • Member
  • PipPip
  • 162 posts
I am not sure whats going on with my machine. I keep getting an error 5 everytime I try to slipstream updates. Googling this it seems like an access denied error. But I have full control over the folder and I am running the command prompt as administrator. The machine I am on is on a domain, I am not sure if thats relevant or not because our IS department is constantly changing security policies and such. I am using a batch file that used to work sometime last week but now it just does not for some reason. I did a file system check to see if my hard drive where I work on this is corrupt but everything checked out fine. Here is the code. I cant make heads or tails out of the log file in terms of what the error actually is from.

for %g in (c:\cabs\*.cab) do dism /image:c:\mount /add-package /packagepath:%g /logpath:c:\wim2\slipstream.log


How to remove advertisement from MSFN

#2
Tripredacus

Tripredacus

    K-Mart-ian Legend

  • Super Moderator
  • 9,696 posts
  • OS:Server 2012
  • Country: Country Flag

Donator

Can you share the log file?
MSFN RULES | GimageX HTA for PE 3.x | lol probloms
msfn2_zpsc37c7153.jpg

#3
gotenks98

gotenks98

    Member

  • Member
  • PipPip
  • 162 posts
Ok let me know if you cant read it.

Attached Files



#4
Tripredacus

Tripredacus

    K-Mart-ian Legend

  • Super Moderator
  • 9,696 posts
  • OS:Server 2012
  • Country: Country Flag

Donator

The only error I am seeing is on KB2079403:

2011-10-26 14:58:32, Info                  DISM   Compatibility Manager: PID=3260 Processing the top level command token(add-package). - CCbsCliParser::Private_ValidateCmdLine
2011-10-26 14:58:32, Info                  DISM   Compatibility Manager: PID=3260 PackageManager command is being executed: c:\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6\pkgmgr.exe /l:"c:\wim2\slipstream.log.pkgmgr" /o:"c:\mount;c:\mount\Windows" /ip /m:"c:\cabs\Windows6.0-KB2079403-x64.cab" /s:"C:\Users\LPATTE~1\AppData\Local\Temp\92859898-98F2-4D36-9316-3678DE9FB403" - CCompatManager::InternalExecuteCommand
2011-10-26 14:59:29, Info                  DISM   Compatibility Manager: PID=3260 PackageManager return code = 0x5 - CCompatManager::InternalExecuteCommand
2011-10-26 14:59:29, Error                 DISM   Compatibility Manager: PID=3260 d:\w7rtm\base\ntsetup\opktools\dism\providers\compatprovider\dll\compatmanager.cpp:970 - CCompatManager::ProcessPackageList(hr:0x80070005)
2011-10-26 14:59:29, Error                 DISM   Compatibility Manager: PID=3260 d:\w7rtm\base\ntsetup\opktools\dism\providers\compatprovider\dll\compatmanager.cpp:589 - CCompatManager::CompatExecuteCmdLine(hr:0x80070005)

The previous update to this, KB2505189, is successful. On additional runs of your script, it only tries KB2079403.
KB: http://support.micro....com/kb/2079403

Its typical to not use hotfixes unless it will fix something that you actually use.

Have you tried deploying your existing image and see if you can install this hotfix manually?
Do you have MSXML Core Services 3.0 installed in your image? Here is the security bulletin, check with the Non-Affected Software too.
http://technet.micro...lletin/MS10-051
You can check your MSXML file version to see which you actually have:
http://support.microsoft.com/kb/269238
MSFN RULES | GimageX HTA for PE 3.x | lol probloms
msfn2_zpsc37c7153.jpg

#5
gotenks98

gotenks98

    Member

  • Member
  • PipPip
  • 162 posts
Well thats because I am getting the error 5, I usually just cancel the slipstream and discard the changes. Thats why you might see repeated entries of that specific kb number because I am trying different things but its using the same log file name. I am not sure if it was a hotfix or not. All I know is I wrote down all the needed patches from a sp2 install after running windows update several times and thats how I get which ones to install.

#6
gotenks98

gotenks98

    Member

  • Member
  • PipPip
  • 162 posts
Just a follow and resolution to this thread. My problem grew to not being able to slipstream all updates. This was due to changes in the companies anti-virus settings. It was blocking me from integrating any kind of update no matter what OS. So basically I just need a way around this now. I started a new thread since its a new problem.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN