All the updates went fine until ........ SP1 wouldn't update kept on getting an error "800F0818"
so followed the usual went to google etc and downloaded the "System Update Readiness Tool" ran that and that tried to install a hotfix did that successfully and retried to install SP1 got the same error "800F0818"
so I went to Advanced guidelines for diagnosing and fixing servicing corruption and got the log
by running
%windir%\logs\cbs\checksur.log
it returned
Now following what it says on the technet article its a simple case of getting the same OS with the same update, however this is SBS2011 and I know of only 2 people who have this installed that are maybe accessible to get the mum and cat files.
However my question is since SBS2011 is based on 2008R2 would that be "good enough" if those files are there ? or is SBS2011 tweaked that much that this wouldnt work ?and Id screw it all up ?
There is this option LINK which involves
however Im unsure which is the safest route to pursue
any suggestions please
EDIT:
Continuing on it looks like an IE 6,7,8 or 9 Issue (IE8 in this case as thats whats installed and SP1 doesn't force or come with IE9) following this guide
as this package "KB2530548" is the issue Link The only Issue I have here is that its an RTM on the server whereby any update should do?
UPDATE:
Currently having an Issue with extracting the file using
getting this error back when the above code is ran in an admin state cmd prompt
+++FIXED+++
Issue Resolved by downloading the MRU file for the affected download then extracting the cab file then extracting the particular package and copying it into the mum and cat file location (as mentioned at the start) then re running windows ready update tool and restarting followed by upgraded to sp1 it does take ages though roughly 1-2 hour(s)
so followed the usual went to google etc and downloaded the "System Update Readiness Tool" ran that and that tried to install a hotfix did that successfully and retried to install SP1 got the same error "800F0818"
so I went to Advanced guidelines for diagnosing and fixing servicing corruption and got the log
by running
%windir%\logs\cbs\checksur.log
it returned
Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 12.0
2011-06-27 19:14
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB2530548_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum
does not match the actual file name
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 324
Found 1 errors
CBS MUM Corrupt Total count: 1
Unavailable repair files:
servicing\packages\Package_for_KB2530548_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_for_KB2530548_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat
Customer Experience report successfully uploaded. Thank you for participating.
For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.Now following what it says on the technet article its a simple case of getting the same OS with the same update, however this is SBS2011 and I know of only 2 people who have this installed that are maybe accessible to get the mum and cat files.
However my question is since SBS2011 is based on 2008R2 would that be "good enough" if those files are there ? or is SBS2011 tweaked that much that this wouldnt work ?and Id screw it all up ?
There is this option LINK which involves
however Im unsure which is the safest route to pursue
any suggestions please
EDIT:
Continuing on it looks like an IE 6,7,8 or 9 Issue (IE8 in this case as thats whats installed and SP1 doesn't force or come with IE9) following this guide
Code:
Obtain files from the update package
Identify which update package you need to download.
Important
You can only use this option if the file requested has a KB number associated with it. For Package_for_KB958690_sc_0~31bf3856ad364e35~amd64~~6.0.1.6.mum, the KB number is KB958690, the architecture version is amd64 (which is the same as x64) and the package version is 6.0.1.6.
Download the KB from Microsoft Help and Support.
Expand the package.
Assuming you downloaded the msu package to the %temp% directory and you want to expand the package to c:\targetDir: expand %temp%\Windows6.0-KB958690-x64.msu /f:* c:\targetDir
Expand the cab files to the same location: expand Windows6.0-KB938979-x64.cab /f:* c:\targetDir
All the files will be located in the above directory as only payload files are located in specific subdirectories.
Occasionally, the required file may be a root package. These packages have no SKU information and follow a set prefix: Package_for_KB958690~31bf3856ad364e35~amd64~~6.0.1.6.mum. The root package extracted from the cab file will be named update.mum.
To verify that the newly created update.mum is in fact the correct file, open the file with notepad.exe and ensure the following attributes are present in <assemble>\<assemblyIdentity>
name=”KB958690”
processorArchitecture=”amd64"
version="6.0.1.6"
If the update.mum is correct, rename it to Package_for_KB958690~31bf3856ad364e35~amd64~~6.0.1.6.mum before copying it to the checkSUR temporary directory.as this package "KB2530548" is the issue Link The only Issue I have here is that its an RTM on the server whereby any update should do?
UPDATE:
Currently having an Issue with extracting the file using
Code:
expand C:\Users\USERADMIN\Desktop\ie8\Windows6.1-KB2530548-x644.msu /f:* c:\testgetting this error back when the above code is ran in an admin state cmd prompt
Code:
C:\Windows\system32>expand C:\Users\USERADMIN\Desktop\ie8\Windows6.1-KB2530548-x6
44.msu /f:* c:\test
Microsoft (R) File Expansion Utility Version 6.1.7600.16385
Copyright (c) Microsoft Corporation. All rights reserved.
Can't open input file: c:\users\USERADMIN\desktop\ie8\windows6.1-kb2530548-x644.m
su.+++FIXED+++
Issue Resolved by downloading the MRU file for the affected download then extracting the cab file then extracting the particular package and copying it into the mum and cat file location (as mentioned at the start) then re running windows ready update tool and restarting followed by upgraded to sp1 it does take ages though roughly 1-2 hour(s)
Last edited: