[SOLVED] 2008 R2 SP1 0x80240022 installing any CU

adamcook · Apr 23, 2019

Hello

Yet another 2008 R2 server that isn't installing any monthly rollups for a while but is installing other updates just fine.

WindowsUpdate.log errors out with 0x80070002 and so does CBS.log.

WindowsUpdate.log exerpt:

Code:

2019-04-23    10:51:26:567    11128    15b8    Handler    :::::::::::::
2019-04-23    10:51:26:569    11128    15b8    Handler    :: START ::  Handler: CBS Install
2019-04-23    10:51:26:569    11128    15b8    Handler    :::::::::
2019-04-23    10:51:26:575    11128    15b8    Handler    Starting install of CBS update 87A05CC7-9216-4F54-8A7C-B732888AA710
2019-04-23    10:51:27:233    11128    15b8    Handler    CBS package identity: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24411.1.8
2019-04-23    10:51:27:237    11128    15b8    Handler    Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\90d52dbca18d2b0ebfff8b98c0eaab35\Windows6.1-KB4493472-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\90d52dbca18d2b0ebfff8b98c0eaab35\inst
2019-04-23    10:51:31:466     156    2f08    Report    REPORT EVENT: {7E6DAC5E-E2A5-471E-98CE-4D2199E78F4A}    2019-04-23 10:51:26:438+0100    1    181    101    {C8630C56-66BA-4F5F-8564-30D73F25BEB8}    201    0    CcmExec    Success    Content Install    Installation Started: Windows successfully started the following update: 2019-04 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4493472)
2019-04-23    10:53:43:464     156    2f08    PT    WARNING: Cached cookie has expired or new PID is available
2019-04-23    10:53:43:465     156    2f08    PT    Initializing simple targeting cookie, clientId = 46c4d3ea-6d07-4623-8dc3-df69a5cf9f77, target group = , DNS name = struggling2008r2sp1server.example.com
2019-04-23    10:53:43:466     156    2f08    PT      Server URL = https://wsusserver.example.com:8531/SimpleAuthWebService/SimpleAuth.asmx
2019-04-23    10:53:49:901     156    2f08    Report    Uploading 1 events using cached cookie, reporting URL = https://wsusserver.example.com:8531/ReportingWebService/ReportingWebService.asmx
2019-04-23    10:53:50:015     156    2f08    Report    Reporter successfully uploaded 1 events.
2019-04-23    10:54:38:427    11128    25e0    Handler    FATAL: CBS called Error with 0x80070002,
2019-04-23    10:54:49:070    11128    15b8    Handler    FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x80070002
2019-04-23    10:54:49:232    11128    15b8    Handler    :::::::::
2019-04-23    10:54:49:232    11128    15b8    Handler    ::  END  ::  Handler: CBS Install
2019-04-23    10:54:49:232    11128    15b8    Handler    :::::::::::::

SFC /scannow: no problems found
KB947821 / SURT: after installing this, retrying the current monthly rollup update (KB4493472) failed to install with same reasons as per the exerpt above and CBS.log attached, and CheckSUR.log also reports "No errors detected"
SFCFix: no corruptions were detected

Attached is CBS.log! Something about "Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24411.1.8" it can't find. I do see Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24411.1.8.mum and Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24411.1.8.cat in C:\Windows\Servicing\Packages.

SleepyDude · Apr 25, 2019

Hi,

Lets try this:

Install Update using Dism

Please download KB4467107 http://download.windowsupdate.com/c..._1b77580629590e3fab05e08710e04be358a1f765.msu save the file to c:\windows\temp
change the name of the update file to a smaller name windows6.1-KB4467107-x64.msu
(keep the extension .msu in the end of the file name in case its visible if not ignore that)
open the Command Prompt as Administrator (Tutorial)
type or Copy & Paste the following commands line by line:

cd /d c:\windows\temp
expand windows6.1-KB4467107-x64.msu -f:* C:\windows\temp
DISM.exe /Online /Add-Package /PackagePath:C:\windows\temp\windows6.1-KB4467107-x64.cab
You should receive the message:
The operation completed successfully.
Restart Windows to complete this operation.
Do you want to restart the computer now (Y/N)?
Make sure to allow the computer to restart if prompted.

If you receive any other message:
Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
Paste (Ctrl+V) it into your next post please.

adamcook · Apr 26, 2019

Code:

C:\Users\x\Desktop\windows6.1-KB4467107-x64>dism /online /add-package
 /packagepath:C:\Users\x\Desktop\windows6.1-KB4467107-x64\windows6.1-
KB4467107-x64.cab

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7601.18489

Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~
~7601.24289.1.11
[==========================100.0%========================= ]
The operation completed successfully.

Thank you for your reply!

I was not prompted for reboot.

What specifically in CBS.log made you attempt dism installing KB4467107? I can see it referenced thousands of times but can't quite see the wood through the trees to understand why it's an update for interest.

SleepyDude · Apr 26, 2019

Hi,

This is the secret of the business :)

More seriously around the error 0x80070002 there is a "Failed to find file" and the file in question can be found on the KB4467107, reinstalling any missing part of this update may help...

Try to install the KB4493472 again if it fails collect the new CBS.log.

adamcook · Apr 26, 2019

SleepyDude said:
Hi,

This is the secret of the business :)

More seriously around the error 0x80070002 there is a "Failed to find file" and the file in question can be found on the KB4467107, reinstalling any missing part of this update may help...

Try to install the KB4493472 again if it fails collect the new CBS.log.

Useful insight, thank you again.

Looks like it failed in CBS.log on failing to find same file. Using PendingReboot module it suggests no file rename operations are causing a pending a reboot:

Code:

PS C:\Users\x> Test-PendingReboot -ComputerName x -Detailed

ComputerName                     : x
ComponentBasedServicing          : False
PendingComputerRenameDomainJoin  : False
PendingFileRenameOperations      : False
PendingFileRenameOperationsValue :
SystemCenterConfigManager        : False
WindowsUpdateAutoUpdate          : False
IsRebootPending                  : False

sfc /scannow still suggests no issues.

SleepyDude · Apr 26, 2019

Hi,

Lets collect more info...

SFCFix Script

!!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems...

Download SFCFix.exe (by Niemiro) and save it to the Desktop
Download the file SFCScript.txt, attached below, and save this to your Desktop
On your Desktop, make sure you have the two files:

SFCFix.exe and

SFCScript.txt
Drag the file SFCScript.txt onto the file SFCFix.exe and release it
The SFCFix tool will process the script
Upon completion, a log file SFCFix.txt should be created on your Desktop
Open the SFCFix.txt log and copy & paste the contents to your post

adamcook · Apr 26, 2019

SleepyDude said:
Hi,

Lets collect more info...

SFCFix Script

!!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems...

Download SFCFix.exe (by Niemiro) and save it to the Desktop

Download the file SFCScript.txt, attached below, and save this to your Desktop

On your Desktop, make sure you have the two files:

SFCFix.exe and

SFCScript.txt

Drag the file SFCScript.txt onto the file SFCFix.exe and release it

The SFCFix tool will process the script

Upon completion, a log file SFCFix.txt should be created on your Desktop

Open the SFCFix.txt log and copy & paste the contents to your post

Thank you!

Code:

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-04-26 14:51:11.487
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at C:\Users\x\Desktop\SFCScript.txt [0]




FileScan::
[0: 1] C:\Windows\winsxs\amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.2.9200.16521_none_c7b3cfc0b510e119\MsSpellCheckingFacility.exe
Expected: A38PfU4/3tbnN+ViF5JkxFLLUx1f1N57COw22+BNroM=
Expected: 6.2.9200.16521
Successfully traced component amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.2.9200.16521_none_c7b3cfc0b510e119.
Microsoft-Windows-ImageBasedSetup-IE-Package-Base-Downlevel~31bf3856ad364e35~amd64~~6.2.9200.16521.Microsoft-Windows-ImageBasedSetup-IE-Base-Downlevel-Deployment



[1: 1] C:\Windows\winsxs\amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.16428_none_5faf8886ff3d65d0\MsSpellCheckingFacility.exe
Expected: LZ1d1Vwhrhymd5KkcoHzzjT7Rgxow9PP0RSAwE9Pr3E=
Expected: 6.3.9600.16428
Successfully traced component amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.16428_none_5faf8886ff3d65d0.
Microsoft-Windows-ImageBasedSetup-IE-Package-Base-Downlevel~31bf3856ad364e35~amd64~~6.3.9600.16428.Microsoft-Windows-ImageBasedSetup-IE-Base-Downlevel-Deployment



[2: 2] C:\Windows\winsxs\amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.19230_none_5f9c6e26ff4d099e\MsSpellCheckingFacility.exe
Expected: u+tgzssxW4HXf1N5Us4O913B5TUTRLn4F0EHfXifdiQ=
Expected: 6.3.9600.19230
Successfully traced component amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.19230_none_5f9c6e26ff4d099e.
Package_1_for_KB4483187~31bf3856ad364e35~amd64~~11.2.1.0.4483187-1_neutral_GDR5

[C:\Windows\System32\MsSpellCheckingFacility.exe]


[3: 1] C:\Windows\winsxs\amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.19180_none_5f665ca4ff75982c\MsSpellCheckingFacility.exe
Expected: 4yk4k/EKlJ2otAJji6yX0G7A21Njq8CC+2cTLvave9E=
Expected: 6.3.9600.19180 Found: 6.3.9600.19178
Failed to trace component amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.19180_none_5f665ca4ff75982c with return code -3.
FileScan:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2019-04-26 14:51:15.134
Script hash: ylTSKS7GShP3vTcQhH605qJesy6hNcZbbN5AK9u4ick=
----------------------EOF-----------------------

SleepyDude · Apr 26, 2019

Retrieve the Components Hive

Navigate to C:\Windows\System32\Config and locate the COMPONENTS file
Please copy the COMPONENTS file to your desktop
Note: If you receive an error that this file is in-use, simply reboot your computer and try again
Right-click on this file on your Desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your Desktop
If file will is too large to upload to the forum please share the file using a service like Dropbox, OneDrive, Google Drive, or upload to www.sendspace.com and just provide the link for the file here

SleepyDude · May 2, 2019

Hi,

Any problem following my last instructions?

adamcook · May 3, 2019

SleepyDude said:
Hi,

Any problem following my last instructions?

Hey

Unfortunately trying to negotiate a reasonable period of time for reboot has been the biggest hurdle here. And I'm unable to achieve this next week either, I hope this is OK. I really appreciate your help.

SleepyDude · May 3, 2019

Hi,

Thanks for the update.

Lets try another option! Please apply the attached SFCFix script to see if we get the needed information...

adamcook · May 13, 2019

SleepyDude said:
Hi,

Thanks for the update.

Lets try another option! Please apply the attached SFCFix script to see if we get the needed information...

Hello!

Thanks again for your help. I managed to get the "COMPONENTS hive" as well as apply the SFCScript to SFCFix.

Meet Google Drive – One place for all your files

SleepyDude · May 13, 2019

Hi,

Thanks for the information.

Install Update using Dism

Please download KB4480970 http://download.windowsupdate.com/c..._a97919028931dcf220036af7c582a37f83f0d819.msu save the file to c:\windows\temp
change the name of the update file to a smaller name windows6.1-KB4480970-x64.msu
(keep the extension .msu in the end of the file name in case its visible if not ignore that)
open the Command Prompt as Administrator (Tutorial)
type or Copy & Paste the following commands line by line:

cd /d c:\windows\temp
expand windows6.1-KB4480970-x64.msu -f:* C:\windows\temp
DISM.exe /Online /Add-Package /PackagePath:C:\windows\temp\windows6.1-KB4480970-x64.cab
You should receive the message:
The operation completed successfully.
Restart Windows to complete this operation.
Do you want to restart the computer now (Y/N)?
Make sure to allow the computer to restart if prompted.

If you receive any other message:
Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
Paste (Ctrl+V) it into your next post please.

After this try to install the update and if it fails collect the new CBS.log

adamcook · May 13, 2019

SleepyDude said:
Hi,

Thanks for the information.

Install Update using Dism

Please download KB4480970 http://download.windowsupdate.com/c..._a97919028931dcf220036af7c582a37f83f0d819.msu save the file to c:\windows\temp

change the name of the update file to a smaller name windows6.1-KB4480970-x64.msu
(keep the extension .msu in the end of the file name in case its visible if not ignore that)

open the Command Prompt as Administrator (Tutorial)

type or Copy & Paste the following commands line by line:

cd /d c:\windows\temp
expand windows6.1-KB4480970-x64.msu -f:* C:\windows\temp
DISM.exe /Online /Add-Package /PackagePath:C:\windows\temp\windows6.1-KB4480970-x64.cab

You should receive the message:
The operation completed successfully.
Restart Windows to complete this operation.
Do you want to restart the computer now (Y/N)?

Make sure to allow the computer to restart if prompted.

If you receive any other message:

Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.

Paste (Ctrl+V) it into your next post please.

After this try to install the update and if it fails collect the new CBS.log

So the install for KB4480970 was successful. I was cheeky and retried the original offending update without a reboot but it had failed. Interestingly WindowsUpdate.log says success but it's not detected, as confirmed by looking in Get-Hotfix.

I'll reboot and retry, see what's going on after that. I'll let you know result and share CBS.log if still no good!

SleepyDude · May 13, 2019

Ok, I need to see the CBS.log created after the update failed to install.

adamcook · May 14, 2019

SleepyDude said:
Ok, I need to see the CBS.log created after the update failed to install.

Awesome, the latest monthly rollup now installs after a reboot!

So from my understanding of what you guided me through, you identified a componoent in the store that was partially installed. By reinstalling the update that was associated with the partially installed package/component, that essentially resolved the "file not found" issue. Sound about right? Please condition me if I'm wrong, I'm extremely interested in how you guys work.

Thanks
Adam

SleepyDude · May 14, 2019

Good.

Yes your description sounds good. So far I had success using Dism to restore the missing files on this cases.

adamcook said:
...I'm extremely interested in how you guys work.

Maybe you want to check our Windows Update Academy...
Learn How to Fix Windows Update: The Sysnative Windows Update Academy

You are welcome.

[SOLVED] 2008 R2 SP1 0x80240022 installing any CU

Member

Attachments

Windows Update Moderator, Security Analyst

Member

Windows Update Moderator, Security Analyst

Member

Attachments

Windows Update Moderator, Security Analyst

Attachments

Member

Windows Update Moderator, Security Analyst

Windows Update Moderator, Security Analyst

Member

Windows Update Moderator, Security Analyst

Attachments

Member

Attachments

Windows Update Moderator, Security Analyst

Member

Windows Update Moderator, Security Analyst

Member

Windows Update Moderator, Security Analyst