Answered by:
Missing / Corrupt MUM file

Question
-
Here is the result from the CheckSUR log
CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-ApplicationServer-BPA-Package-MiniLP~31bf3856ad364e35~amd64~fr-FR~7.1.7600.16400.mum Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file name
I have looked at all my machines and cannot find it. Where can I get version 16385 of this file(s)?
Tuesday, September 24, 2013 9:50 PM
Answers
-
Advanced guidelines for diagnosing and fixing servicing corruption
http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx
Note: Refer to the “Options for obtaining files” section to get the files required.
For detailed steps, refer to the following steps:
1. Download the KB from Microsoft Download Center. Go to: http://www.microsoft.com/en-us/download/details.aspx?id=3941 This link is for Update for Best Practices Analyzer for Application Server for Windows Server 2008 R2 x64 Edition (KB981392)
2. Expand the package.
Assuming you downloaded the msu package to the C:\Windows\Temp directory and you want to expand the package to c:\targetDir, for example, run the following command:
expand C:\Windows\Temp\Windows6.1-KB981392-x64.msu /f:* c:\targetDir
3. Expand the cab files to the same location.
expand C:\targetDir\Windows6.1-KB981392-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. Check the above link for detailed instructions.
Then, move to the following steps to fix the error:
4. 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
For Example:
copy C:\targetDir\microsoft-windows-applicationserver-bpa-package-minilp~31bf3856ad364e35~amd64~fr-fr~7.1.7600.16400.mum to %Windir%\Temp\CheckSUR\servicing\packages\copy C:\targetDir\microsoft-windows-applicationserver-bpa-package-minilp~31bf3856ad364e35~amd64~fr-fr~7.1.7600.16400.cat to %Windir%\Temp\CheckSUR\servicing\packages\
5. Rerun the System Update Readiness tool.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.- Marked as answer by Andy Qi Wednesday, October 9, 2013 5:30 PM
Thursday, September 26, 2013 1:36 AM
All replies
-
Need to know operating system and service pack installed. Please run the system update readiness tool.
http://windows.microsoft.com/en-us/windows7/What-is-the-System-Update-Readiness-Tool?SignedIn=1
Then post the complete contents of;
%SYSTEMROOT%\Logs\CBS\CheckSUR.logRegards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.Wednesday, September 25, 2013 2:11 AM -
Windows 2008 Server R2 Standard - No service pack. Trying to install
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 20.0
2013-09-20 13:53
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-ApplicationServer-BPA-Package-MiniLP~31bf3856ad364e35~amd64~fr-FR~7.1.7600.16400.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: 2524
Found 1 errors
CBS MUM Corrupt Total count: 1
Unavailable repair files:
servicing\packages\Microsoft-Windows-ApplicationServer-BPA-Package-MiniLP~31bf3856ad364e35~amd64~fr-FR~7.1.7600.16400.mum
servicing\packages\Microsoft-Windows-ApplicationServer-BPA-Package-MiniLP~31bf3856ad364e35~amd64~fr-FR~7.1.7600.16400.cat
Wednesday, September 25, 2013 5:23 AM -
Advanced guidelines for diagnosing and fixing servicing corruption
http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx
Note: Refer to the “Options for obtaining files” section to get the files required.
For detailed steps, refer to the following steps:
1. Download the KB from Microsoft Download Center. Go to: http://www.microsoft.com/en-us/download/details.aspx?id=3941 This link is for Update for Best Practices Analyzer for Application Server for Windows Server 2008 R2 x64 Edition (KB981392)
2. Expand the package.
Assuming you downloaded the msu package to the C:\Windows\Temp directory and you want to expand the package to c:\targetDir, for example, run the following command:
expand C:\Windows\Temp\Windows6.1-KB981392-x64.msu /f:* c:\targetDir
3. Expand the cab files to the same location.
expand C:\targetDir\Windows6.1-KB981392-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. Check the above link for detailed instructions.
Then, move to the following steps to fix the error:
4. 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
For Example:
copy C:\targetDir\microsoft-windows-applicationserver-bpa-package-minilp~31bf3856ad364e35~amd64~fr-fr~7.1.7600.16400.mum to %Windir%\Temp\CheckSUR\servicing\packages\copy C:\targetDir\microsoft-windows-applicationserver-bpa-package-minilp~31bf3856ad364e35~amd64~fr-fr~7.1.7600.16400.cat to %Windir%\Temp\CheckSUR\servicing\packages\
5. Rerun the System Update Readiness tool.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.- Marked as answer by Andy Qi Wednesday, October 9, 2013 5:30 PM
Thursday, September 26, 2013 1:36 AM -
I understand that, but I have no idea what update this came from. There is no KB in the file name, and I searched on everything related to the rest of the name. Any ideas?
Once I know the update it came from I can figure it out from there.
Thanks again,
Thursday, September 26, 2013 5:15 AM -
Its mentioned in step one above, follow the steps for extraction from package and copy the files mentioned as in step four, rerun tool.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.Thursday, September 26, 2013 9:17 AM