locked
Error 800F0818 - SP1 Installation on Server 2008 R2 RRS feed

  • Question

  • =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 11.0
    2011-03-16 13:04

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.mum  Expected file name Microsoft-Windows-WSUS-BPA-Package~31bf3856ad364e35~amd64~~7.1.7600.16399.mum does not match the actual file name

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 253
     Found 1 errors
      CBS MUM Corrupt Total count: 1

    Unavailable repair files:
     servicing\packages\Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.mum
     servicing\packages\Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.cat

    --

    From what I've gathered, I need to copy these two files from another 2008 R2 Server. My other 2008 R2 Server (with SP1 installed) does not have these files in the Packages folder, even though it has FileServices installed. Is there anything else that I can do to resolve this error?

    Thank you,

    John


    Saturday, March 19, 2011 5:04 AM

Answers

All replies

  • PLEASE COPY AND REPLACE THE BELOW FILES FROM RUNNING WINDOWS 2008 SP1 MACHINE TO THE PROBLEMATIC SERVER ON GIVEN PATH

     Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.mum


    Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.cat


    http://www.virmansec.com/blogs/skhairuddin

    Saturday, March 19, 2011 10:49 AM
  • Are these the files that you're talking about? I found them on the 2008 R2 SP1 machine that I can copy from:

    Package_for_KB979916_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    Package_for_KB979916_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat

    The System Update Readiness Tool is saying the following files are corrupt:

    Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.mum
    Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.cat

    Saturday, March 19, 2011 3:51 PM
  • I have the exact same problem with the exact same files.  Your link above was exactly zero help as it doesn't answer his question, which is mine - Why are you saying to copy:

    Package_for_KB979916_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    Package_for_KB979916_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat

    When the files listed as corrupt are:

    Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.mum
    Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.cat

    ??Where did you get that KB number from??  The cab file contained in that KB doesn't contain the file names we have...

    johnw02 - Did you go ahead and copy the files anyway?  Did it work for you?  Or did you find another solution?

    Sunday, March 20, 2011 10:18 PM
  • Hi,

     

    Please copy the following two files from another working machine:

     

    Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.mum

    Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.cat

     

    Tim Quan

    Monday, March 21, 2011 4:13 AM
  • sorry you need to copy those 2 above files I posted by mistake
    http://www.virmansec.com/blogs/skhairuddin
    Monday, March 21, 2011 6:27 AM
  • Syed, NP.  Just wondering where that came from.  Ironically, I can find those files you incorrectly told us to get, but I've tried searching for:

    Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.mum
    Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.cat

    On 6 different servers, 3 running R2 Pre-SP1 and 3 with SP1.  No luck. Two of each run the same server roles as the problematic server.

    Any idea what patch or KB would contain those files?  Searching online hasn't resulted in any ideas...

    Thanks!

    Monday, March 21, 2011 6:47 AM
  • have you tried the above link provided ?

     


    http://www.virmansec.com/blogs/skhairuddin
    Monday, March 21, 2011 8:20 AM
  • Hi,

     

    Please download the files from the following site and then copy them to C:\Windows\servicing\Packages to replace the old files.

     

    https://sftus.one.microsoft.com/choosetransfer.aspx?key=b0882070-dd83-4636-9d33-a4b854822e8f

     

    Password: usulY)^WaN#

     

    Tim Quan

     

    • Marked as answer by Tim Quan Monday, March 28, 2011 3:04 AM
    Monday, March 21, 2011 8:36 AM
  • Thank you, I'll try that tonight.  It's a production server that can't go offline until then.
    Monday, March 21, 2011 6:03 PM
  • Hello I'm having a similar problem with error code 0x800f0818 when I try to run sp1 on a server with 2008 r2. Instead of the above error when I look at the Readiness tool it that compains about Microsoft-Windows-WSUS-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16399.mum

    I've spent most of the day looking for another server with this file but I can't find it. Any help would be appreciated.

     

    Jeff Meyers

     

    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 11.0
    2011-03-21 14:08

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f)    CBS MUM Corrupt    0x00000000    servicing\Packages\Microsoft-Windows-WSUS-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16399.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: 85
     Found 1 errors
      CBS MUM Corrupt Total count: 1

    Unavailable repair files:
        servicing\packages\Microsoft-Windows-WSUS-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16399.mum
        servicing\packages\Microsoft-Windows-WSUS-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16399.cat

    Monday, March 21, 2011 8:10 PM
  • Tim:  Lol, that MS site is apparently incompatible with IE9, even in compatibility mode.  I tried it on three machines before I gave up and installed Firefox, which downloaded it just fine. :)  I'll be installing it in a little bit, I'll post back the results.
    Tuesday, March 22, 2011 4:25 AM
  • Argh.  Installation went fine, I verified the files got updated - but the system readiness tool still returns errors on them:

     


    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 11.0
    2011-03-21 22:34

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f)    CBS MUM Corrupt    0x00000000    servicing\Packages\Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.mum        Expected file name Microsoft-Windows-NFS-Full-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: 473
     Found 1 errors
      CBS MUM Corrupt Total count: 1

    Unavailable repair files:
        servicing\packages\Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.mum
        servicing\packages\Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.cat

    (w)    Unable to get system disk properties    0x0000045D    IOCTL_STORAGE_QUERY_PROPERTY    Disk Cache   

    ----------------------------------------------------------------------------------------------------------------------------------

     

    Any other thoughts? thanks!

    Tuesday, March 22, 2011 5:18 AM
  • This is the error message i get when I try a powershell copy command on the files in question. I'm logged in as a domain admin.

    Any more thoughts on this problem.

     

    PS C:\Users> copy-item c:\windows\servicing\packages\sp1fix\* c:\windows\servicing\packages
    Copy-Item : Access to the path 'C:\windows\servicing\packages\Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf
    6ad364e35~amd64~en-US~7.1.7600.16422.cat' is denied.
    At line:1 char:10
    + copy-item <<<<  c:\windows\servicing\packages\sp1fix\* c:\windows\servicing\packages
        + CategoryInfo          : PermissionDenied: (C:\windows\serv....7600.16422.cat:FileInfo) [Copy-Item], Unauthoriz
       AccessException
        + FullyQualifiedErrorId : CopyFileInfoItemUnauthorizedAccessError,Microsoft.PowerShell.Commands.CopyItemCommand

    Copy-Item : Access to the path 'C:\windows\servicing\packages\Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf
    6ad364e35~amd64~en-US~7.1.7600.16422.mum' is denied.
    At line:1 char:10
    + copy-item <<<<  c:\windows\servicing\packages\sp1fix\* c:\windows\servicing\packages
        + CategoryInfo          : PermissionDenied: (C:\windows\serv....7600.16422.mum:FileInfo) [Copy-Item], Unauthoriz
       AccessException
        + FullyQualifiedErrorId : CopyFileInfoItemUnauthorizedAccessError,Microsoft.PowerShell.Commands.CopyItemCommand

    Wednesday, March 23, 2011 9:16 PM
  • Thanks, Tim.

    I'm receiving the message "There are no files available for download" when clicking the link that you provided.

    Are the files still available for download?

    Thank you,

    John

    Friday, March 25, 2011 4:42 AM
  • Charles - Did you figure out why the System Update Readiness Tool still reports the files as corrupt? Also, has everything been running OK after replacing the corrupt files and installing SP1?

    Thank you,

    John

    Friday, March 25, 2011 4:45 AM
  • Hi John,

    Please try again now.

    Regards,

    Tim

     

     

    Friday, March 25, 2011 7:31 AM
  • Thanks, Tim. It worked that time.

    Friday, March 25, 2011 2:43 PM
  • Success!  Thanks to (additional!) help on Experts-Exchange, I extracted:

    Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.mum
    Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.cat

    From Windows6.1-KB981111-x64.msu

    Followed this advice from the link http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx:

    "Steps to resolve this issue

        Get the files required from other sources. The options available can be found in the “Options for obtaining files” section below.

        Copy the files to %Windir%\Temp\CheckSUR directory of the corrupted computer following the subdirectory format as follows:
            All files of type *.mum and *.cat should be placed in the %windir%\Temp\CheckSUR\servicing packages directory

            All files of type *.manifest should be placed in the %windir%\Temp\CheckSUR\manifests\ directory

            For example:

            Copy Package_for_KB958690_sc_0~31bf3856ad364e35~amd64~~6.0.1.6.mum to %Windir%\Temp\CheckSUR \servicing\packages\

            Copy x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0.manifestto %Windir%\Temp\CheckSUR \winsxs\manifests\


            ImportantImportant
            Whenever you copy a .mum file, you must also copy the corresponding .cat file of the same name.

            Rerun the System Update Readiness tool."

    And got:


    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 11.0
    2011-03-26 19:06

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f)      CBS MUM Corrupt      0x00000000      servicing\Packages\Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.mum            Expected file name Microsoft-Windows-NFS-Full-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file name
    (fix)      CBS MUM Corrupt      CBS File Replaced      Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-neutralcab.cab.
    (fix)      CBS Paired File      CBS File also Replaced      Microsoft-Windows-FileServices-BPA-Package-MiniLP~31bf3856ad364e35~amd64~en-US~7.1.7600.16422.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-neutralcab.cab.

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 482
     Found 1 errors
     Fixed 1 errors
      CBS MUM Corrupt Total count: 1
      Fixed: CBS MUM Corrupt.  Total count: 1
      Fixed: CBS Paired File.  Total count: 1

    ---------------------------------------------------------------------------------------------------------------------------


    SP1 is installing now. Thanks to all that helped!


    For all of those looking into this note that the solution is *not* to replace the corrupt *.cat, *.mum or *.manifest files in their 'final resting place' folder, but instead to place them where the system readiness tool could pick them up (in the 'CheckSUR' temp directory) and place them nicely for you.
    Sunday, March 27, 2011 1:28 AM
  • Thx Charles, you find solution! It works for me
    Tuesday, June 14, 2011 9:36 AM
  • I know this was resolved quite a while ago, but I ran the system update readiness tool, then installed the standalone version of SP1, instead of the Windows Update version. This worked for me.
    Tuesday, October 15, 2013 10:34 PM