Solved How do I correct the Windows update error 800B0100 & 80073712?

[vid4763]

**My post includes the error codes from step #3 and this dropbox link for CBS.zip file created in step #4 of the thread posting instructions (CBS.log was 90mb zipped, almost no compression, not sure if I did it wrong).... I've run SURT and also uploaded CBS & checkSUR.log files

https://www.dropbox.com/s/o0ahtlnoik3gd6v/CBS.zip?dl=0

Hello and thank you for reading and for any advice and help you can offer.

This thread is not for my system specs on my profile here but for another Laptop I have that my wife and I are giving to our 10 yr old son, at the end of the school year as a gift.

Here are the basic specs for the Laptop and OS with the problem:

Samsung NP-QX410 Laptop
Seagate 120G HDD
4G dram
Windows 7 Home Premium SP1

About 2 weeks ago we resurrected this Samsung Laptop from a bad Samsung HDD and temporarily replaced it with an older model Seagate 120gb HDD. Everything has been going smooth....until a week ago when I updated the BIOS using Samsung update to version 5. Also, I installed Ccleaner and ran that. These 2 actions may or may not have anything to do with the windows update issue....

I installed many windows updates over the course of 2 days before these last 2 actions. No problems, so I find that suspicious. Now, I have 5 Windows updates that just won't install after many attempts.

I've gone to support.microsoft and tried mr fixit. Also, I've tried sfc /scannow. no issues.

Everything otherwise seems ok with laptop. (I'm ordering an SSD to replace the old Seagate 120gb 5200rpm which should make a huge difference!) But we'd really like to have this Windows update issue resolved before we give our son the laptop as a gift.

THANK YOU AGAIN FOR READING.....and let me know what you think.....here are some screenshots that may be helpful...... and the CBS.log zip file DROPBOX LINK if you missed it above...

https://www.dropbox.com/s/o0ahtlnoik3gd6v/CBS.zip?dl=0

 

[NoelDP]

CheckSUR shows the following problems...

Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_7.1.7601.22947_none_7f90c927c288b059.manifest
 winsxs\manifests\amd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_7.1.7601.18740_none_7f002870a9716207.manifest
 winsxs\manifests\amd64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.2.7601.18582_none_47658fe606346d38.manifest
 winsxs\manifests\x86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.2.7601.18582_none_eb46f4624dd6fc02.manifest
 winsxs\manifests\amd64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.2.7601.22787_none_47f430091f4d88dc.manifest
 winsxs\manifests\x86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.2.7601.22787_none_ebd5948566f017a6.manifest
 servicing\packages\Package_102_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_102_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_103_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_103_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_104_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_104_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_105_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_105_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_108_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_108_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_109_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_109_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_110_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_110_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_111_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_111_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_1_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_50_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_50_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_59_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_59_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_61_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_61_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_77_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_77_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_79_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_79_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_84_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_84_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2984981_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2984981_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_102_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_102_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_103_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_103_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_104_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_104_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_105_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_105_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_108_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_108_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_109_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_109_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_110_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_110_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_111_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_111_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_1_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_2_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_2_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_50_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_50_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_59_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_59_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_61_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_61_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_77_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_77_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_79_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_79_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_84_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_84_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2984981_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2984981_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.cat

I'll post a fix when I've caught up with the backlog!

 

[vid4763]

Thanks Noel!

 

[NoelDP]

I've uploaded a file - v63aa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder v63aain the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[vid4763]

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Noel, I seem to have another problem. My Windows\Temp has no subfolders and is empty and will not even allow me permission to open the Temp folder. (I've searched thru Help, compared permission settings with my primary pc, looked at some forum help on permissions......I'm not sure how to correct this.)

In the meantime, I've downloaded the file from your Onedrive and extracted. I am otherwise ready to go, but am stuck until this "NEW" problem is solved....

I did however find CheckSur, Winsxs, and Servicing\Packages "individual" sub-folders in the main Windows Folder. I want to be sure if these folders and locations are what we need, and still am confused as to why Temp folder is empty and inaccessible?

(I'm inclined to think that I should copy and paste the contents of Packages and Manifests into these "same" named folders I've found elsewhere, as I cannot find them anywhere else. However, as of now -see screenshot 5- Windows will not allow me to copy to even these sub folders??)

Please let me know your advice and thank you for your help.

I've included 5 screenshots showing the frustrating results....

 

[vid4763]

UPDATE @ NoelDP

I managed to work around some of the file location and accessibility issues.

I was able to copy all of the contents of packages and manifests except 5 files that were denied.

I've attached Dropbox link, below, to new cbs.zip folder. Also, ran windows update again and 2 of the 5 updates successfully downloaded and installed.

I attached updated screenshots of windows update and CheckSur and CheckSur.persist files

https://www.dropbox.com/s/y26ifc9iyo8oaba/CBS32815.zip?dl=0

 

[NoelDP]

Well done!
The problem with the Temp folder permissions is an interesting one, and probably needs to be addressed early, as it may well impact on system performance later.

By default, I don't think the folder allows access - but this is usually easily granted to any admin user.
It seems that this is not the case here.
You may need to change ownership of the folder (to the Administrators group), and then change the permissions,to the following...
I'll post a fix protocol when I can get to it, which will include not only the remaining missing files, but also a permissions hack.

 

[NoelDP]

First the permissions....

Open an Elevated Command Prompt, and run the following commands

TAKEOWN /F C:\Windows\Temp /A /R
ICACLS C:\Windows\Temp /grant AdministratorsF) /T
ICACLS C:\Windows\Temp /grant Users (CI)(S,WD,AD,X) /T
ICACLS C:\Windows\Temp /grant SYSTEMF) /T
ICACLS C:\Windows\Temp /grant "CREATOR OWNER"OI)(CI)(IO)(F) /T
ICACLS C:\Windows\Temp /grant AdministratorsOI)(CI)(IO)(F) /T
ICACLS C:\Windows\Temp /grant SYSTEMOI)(CI)(IO)(F) /T


Here are some instructions to make life easier
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.

now see if you can access the folder in the normal way.

 

[vid4763]

Noel,

Thanks again for your valuable time. I believe I did the instruction correctly, but I believe it was unsuccessful. Here are 2 captures with the results.

1 - ECP after running script
2 - ECP and attempt to access Windows\Temp post script

 

[NoelDP]

Oh boy - I suspect that this means that the folder is corrupt .

Let's take a look at the current permissions, and see if I'm missing something...

Open an Elevated Command Prompt, and run the following commands..

ATTRIB C:\Windows\Temp
ICACLS C:\Windows\Temp
REG QUERY HKU
REG QUERY HKU\S-1-5-18
REG QUERY HKU\S-1-5-19
REG QUERY HKU\S-1-5-20

post the results.

 

[vid4763]

I'll owe you more than a few pints if you're able to resolve this, which I surely couldn't without your help! Here are the results....thanks

 

[NoelDP]

That all looks normal.

Possibly itd be a good idea to run CHKDSK and see what happens...


Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
At the Command prompt, type
CHKDSK C: /R
and hit the Enter key.
You will be told that the drive is locked, and the CHKDSK will run at the next boot - hit the Y key, and then reboot.
The CHKDSK will take a few hours depending on the size of the drive, so be patient!
After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot).

After the reboot, post your event logs...

Open Event Viewer
click on the Windows logs entry in the left pane to expand it.
Now click on the Application entry - wait while it loads.
Click on 'File' in the menu bar and select Save...
Save the file as Appevt.evtx
Repeat for the System log
then zip both, and upload them.

 

[vid4763]

Noel,

Thanks for checking for on that CheckDisk log.

The Event Viewer zip logs are below.

I still have 3 updates that won't download/install, and permissions is still wacky on Windows\Temp. Any revelations on those 2 issues?? I really appreciate your time, and understand its quite generously distributed to all in need of your help. Thanks again and i'll look for your reply.....

 

[NoelDP]

The disk appears to be fine - just some minor errors which shouldn't cause this type of problem and which it managed to fix anyhow.
There is however a problem with the TrustedInstaller service.
There are also problems with a 'bpmp' driver, and you appear to have multiple languages installed (which is outside the terms of a Pro license!), two of which aren't getting properly uninstalled.

Let's check the TrustedInstaller service and a few others at the same time...

Please download the Farbar Service Scanner from

http://www.bleepingcomputer.com/download/farbar-service-scanner/

Right-click on the saved file and select 'Run as Administrator', and tick all the options, then click on the Scan button - copy and paste the report to your response.

 

[vid4763]

Here's FSS report:

Farbar Service Scanner Version: 17-01-2015
Ran by JASON (administrator) on 04-04-2015 at 07:41:17
Running from "C:\Users\JASON\Desktop"
Microsoft Windows 7 Home Premium Service Pack 1 (X64)
Boot Mode: Normal
****************************************************************
Internet Services:
============
Connection Status:
==============
Localhost is accessible.
LAN connected.
Google IP is accessible.
Google.com is accessible.
Yahoo.com is accessible.

Windows Firewall:
=============
Firewall Disabled Policy:
==================

System Restore:
============
System Restore Policy:
========================

Action Center:
============

Windows Update:
============
Windows Autoupdate Disabled Policy:
============================

Windows Defender:
==============
Other Services:
==============

File Check:
========
C:\Windows\System32\nsisvc.dll => File is digitally signed
C:\Windows\System32\drivers\nsiproxy.sys => File is digitally signed
C:\Windows\System32\dhcpcore.dll => File is digitally signed
C:\Windows\System32\drivers\afd.sys => File is digitally signed
C:\Windows\System32\drivers\tdx.sys => File is digitally signed
C:\Windows\System32\Drivers\tcpip.sys => File is digitally signed
C:\Windows\System32\dnsrslvr.dll => File is digitally signed
C:\Windows\System32\mpssvc.dll => File is digitally signed
C:\Windows\System32\bfe.dll => File is digitally signed
C:\Windows\System32\drivers\mpsdrv.sys => File is digitally signed
C:\Windows\System32\SDRSVC.dll => File is digitally signed
C:\Windows\System32\vssvc.exe => File is digitally signed
C:\Windows\System32\wscsvc.dll => File is digitally signed
C:\Windows\System32\wbem\WMIsvc.dll => File is digitally signed
C:\Windows\System32\wuaueng.dll => File is digitally signed
C:\Windows\System32\qmgr.dll => File is digitally signed
C:\Windows\System32\es.dll => File is digitally signed
C:\Windows\System32\cryptsvc.dll => File is digitally signed
C:\Program Files\Windows Defender\MpSvc.dll => File is digitally signed
C:\Windows\System32\ipnathlp.dll => File is digitally signed
C:\Windows\System32\iphlpsvc.dll => File is digitally signed
C:\Windows\System32\svchost.exe => File is digitally signed
C:\Windows\System32\rpcss.dll => File is digitally signed

**** End of log ****

 

[vid4763]

Ran Windows Update again

 

[Layback Bear]

@Hi Noel.
Just a note.

I see updates for Windows 7 Defender.
Anti virus is AVG.
Shouldn't Windows 7 Defender be turned off so not to interfere with AVG?
The two together might be fighting each other with permission.
Or better yet just use MSE by itself.

@vid4763
Because I follow many of Noels post, at times I will ask a question.
Don't do anything of what I post until Noel responds.
Noel is the expert.

 

[vid4763]

@Hi Noel.
Just a note.

I see updates for Windows 7 Defender.
Anti virus is AVG.
Shouldn't Windows 7 Defender be turned off so not to interfere with AVG?
The two together might be fighting each other with permission.
Or better yet just use MSE by itself.

@vid4763
Because I follow many of Noels post, at times I will ask a question.
Don't do anything of what I post until Noel responds.
Noel is the expert.

That's weird as Avast is installed and running as my Antivirus not AVG. AVG shouldn't even be on this laptop. Never downloaded it

 

[Layback Bear]

I went by your specs.

Antivirus AVG AntiVirus Free Edition 2015
Browser Internet Explorer 11 update version 11.0.16

Either way Avast and Windows 7 Defender at the same time is the question.

 

[Layback Bear]

You seem to have another permission problem in the works.
Has you permission problem been solved here?

http://www.sevenforums.com/software/365854-permissions-please-help.html