[SOLVED] Problems updating Windows 7 - KB3060716, KB3071756, KB3101746 & KB3080149

sofaMonster

Member
Joined
Jan 10, 2016
Posts
14
Hi!

Hope someone on this forum can help me with the problem I am having.
Was on a 5 month trip away from my computer. Came back and it had trouble installing these 4 updates. I've tried some of the other fixes found around on the internet, such as removing the KB29222something update, but I did not find the other file mentioned. This did sadly not work.
Posting here as my last attempt before simply hiding these updates.
View attachment CBS.rar
I've attached the CBS file, which I've seen mentioned several times in other threads.

Please, someone help me update :S

SFCFIX:
SFCFix version 2.4.5.0 by niemiro.
Start time: 2016-01-11 00:05:14.574
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.

AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-01-11 00:07:21.760
----------------------EOF-----------------------

EDIT: Forgot to mention, I also attempted to manually download the updates and install. This did not work.
 
Hello and welcome!

Code:
2016-01-10 23:57:12, Info                  CBS    Failed to open package file: \\?\C:\Windows\Servicing\Packages\Package_2_for_KB2922229~31bf3856ad364e35~amd64~~6.1.1.2.mum [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Please follow these instructions to replace the missing file:

View attachment Packs.zip

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing Packages
  5. Open the Packages folder and copy the files into the following folder

    C:\Windows\Temp\CheckSur\Servicing\Packages

  6. Run the System Update Readiness Tool (SURT) again.
  7. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.log
 
Hey Computerwiz, thanks for your reply.

I attemped to do what you asked. Was easily done and I ran the SURT.
But eh.. It kind of froze and I might have ended it prematurely after it not moving for 30 minutes..
Anyways, I attached the log that was made during the 45 minutes of runtime.
View attachment CheckSUR.rar
I chose to attach the file instead as it is pretty long.

Hopefully it got all the data you are looking for!
 
Looks like there's a lot more than one missing file.
Let's replace them with SURT. Let it run to completion, it may take a very long time.

View attachment Packs.zip

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing the Packages folder.
  5. Open the Packages folder and copy the files into the following folder

    C:\Windows\Temp\CheckSur\Servicing\Packages

  6. Run the System Update Readiness Tool (SURT) again.
  7. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.log
 
Do you know why this has happened in the first place?
Was it because I didn't turn on the computer for 5 months and it missed updates?
How can I avoid this in the future?
 
Check for updates and try to install any that are offered.

If the installation fails, zip and attach C:\Windows\Logs\CBS\CBS.log with your reply.
If the zip file is larger than 8MB, it will not upload. Please use a file sharing service such as OneDrive, DropBox, SendSpace, etc. and include the link with your reply.
 
Code:
2016-01-20 18:45:36, Info                  CBS    Exec: Installing Package: Package_4_for_KB2922229~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2922229-11_neutral_GDR, InstallDeployment: amd64_2a76a4ed4b5d53d8c2d3264cdc842936_31bf3856ad364e35_6.1.7601.18229_none_6c86676ab6f889d1
2016-01-20 18:45:36, Error                 CSI    0000020d@2016/1/20:17:45:36.982 (F) d:\win7sp1_gdr\base\wcp\componentstore\csd_locking.cpp(324): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)
[gle=0x80004005]
2016-01-20 18:45:39, Error                 CSI    0000020e (F) STATUS_SXS_ASSEMBLY_MISSING #6850667# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2016-01-20 18:45:39, Error                 CSI    0000020f (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #6850552# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_InstallDeployment(Flags = 0, a = 2a76a4ed4b5d53d8c2d3264cdc842936, Version = 6.1.7601.18229, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, cb = (null), s = (null), rid = [78]"Package_4_for_KB2922229~31bf3856ad364e35~amd64~~6.1.1.2.2922229-11_neutral_GDR", rah = [1]"3", manpath = (null), catpath = (null), disp = 0)[gle=0x80073701]

Let's try this:

Install Update with DISM

  1. Download the KB2922229 MSU here: https://www.microsoft.com/en-us/download/details.aspx?id=42346
  2. Copy the MSU file to a convenient location (such as C:\temp).
  3. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  4. When you see Command Prompt on the list, right-click on it and select Run as administrator
  5. When command prompt opens, copy and paste the following commands into it, press enter after each

    expand {update name}.msu -f:* C:\temp

    replace {update name} with the name of the MSU file downloaded in step 1

    DISM.exe /Online /Add-Package /PackagePath:C:\temp\{update name}.cab

  6. 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)?

  7. Make sure to allow the computer to restart if prompted.

    If you receive any other message:
  8. 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.
  9. Paste (Ctrl+V) it into your next post please.
 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>expand Windows6.1-KB2922229-x64.msu -f:* H:\WinUp
Microsoft (R) File Expansion Utility Version 6.1.7600.16385
Copyright (c) Microsoft Corporation. All rights reserved.

Can't open input file: windows6.1-kb2922229-x64.msu.


C:\Windows\system32>DISM.exe /Online /Add-Package /PackagePath:H:\WinUp\Windows6
.1-KB2922229-x64\Windows6.1-KB2922229-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_KB2922229~31bf3856ad364e35~amd64~
~6.1.1.2
[==========================100.0%==========================]
The operation completed successfully.

C:\Windows\system32>


So. Instead of using the cmd to open the update I managed to use WinRar. But I don't suppose this is the normal approach for Windows to handle updates.
Could this be one of the reason for the failed updates?
By the way, thanks for taking the time to help me out. I really appreciate it :)
 
So. Instead of using the cmd to open the update I managed to use WinRar. But I don't suppose this is the normal approach for Windows to handle updates.
Could this be one of the reason for the failed updates?
By the way, thanks for taking the time to help me out. I really appreciate it :)


This update is the one that I've been seeing in the logs so far, hopefully since it installed this should take care of the problem.
Glad to help!

Check for updates and install any that are offered. If the installation fails, zip and attach C:\windows\logs\cbs\cbs.log with your reply.
 
It.. It might just have worked!
I think you solved the problem with the updates :O
Finally I got 4 succesful updates instead of 4 failed ones!
As you can see in the image, it succesfully updated. 20% of my update log is filled with the failed ones.

Guess that solves the thread. Many thanks for your help!
 
Excellent!

Let's perform a final check with System File Checker to make sure everything is in order.


SFC Scan

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  4. This will create a file, cbs.txt on your Desktop. Please zip and attach this to your next post.

If SFC reports that no integrity violations were detected, you should be good to go :)
 
Looks like there were a couple successful fixes.

There's a few more files to replace, then everything should be wrapped up.

View attachment packs.zip

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing Packages
  5. Open the Packages folder and copy the files into the following folder

    C:\Windows\Temp\CheckSur\Servicing\Packages

  6. Run the System Update Readiness Tool (SURT) again.
  7. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.log
 
Checksur log contents:


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-01-20 21:42

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum
(fix) CBS MUM Missing CBS File Replaced Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum
(fix) CBS MUM Missing CBS File Replaced Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix) CBS Paired File CBS File also Replaced Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.

Checking Component Store

Summary:
Seconds executed: 175
Found 2 errors
Fixed 2 errors
CBS MUM Missing Total count: 2
Fixed: CBS MUM Missing. Total count: 2
Fixed: CBS Paired File. Total count: 2
 
Excellent, looks like everything is good :thumbsup2:

Please check for updates one more time and install any that are offered.
 
Looks like all the available updates are installed for now.
So I think everything is OK :)

If something happens again, should I just create another thread or?

EDIT: Might have been to fast. Another error with an optional update. Will update with another log.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top