Can't install "new Windows Update software" -errors 80004005, 800700B7

paul1149 · Dec 25, 2012

Can't install "new Windows Update software" -errors 80004005, 800700B7

Hi,

I've got a Dell netbook with a problem. It's running Win7 Starter. When I go to check for updates, it first wants to install the latest Windows updater, but that fails with error code 80004005. If I try again I get error 800700B7.

After trying system restore and running SFC, which found a trivial (I believe) tcpmon.ini error, I finally opted to restore the system to factory condition. Surprise, the exact same error persists.

I can do a lot of updating via local file stores, but I want this machine to be updateable on a continuing basis.

Also, I have a Win7 installation disk. When I tried a repair install, it tells me that the existing system is a later version and it refuses to install.

The only thing I have left is a fresh install from the disk. But I have no idea what is going on here.

NoelDP · Dec 25, 2012

Please follow the instructions at http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html and post the requested data - then we may be able to see what we're dealing with.

paul1149 · Dec 25, 2012

Ok, thanks Noel.

Most of those I had been through, but for the sake of the log here it is. No change.

Again, the first attempt brought the 80004005 error code, and every attempt after that brings the 800700b7, on both windows installations.

NoelDP · Dec 25, 2012

Code:

 Line 3091: 2012-12-25 12:22:19, Info                  CSI    00000186 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

...as you say, that's the only obvious error present

I assume you've run the following troubleshooter?? Open the Windows Update troubleshooter

A lot of the time, this sort of problem is caused by residuals of old Anti-Virus programs. What was preinstalled by the OEM? What are you currently using? (what others have been installed in the meantime?)

I don't even see anything particularly unusual outside the SFC data in the CBS log

Let's fix the tcpmon error anyhow - just in case....

I've uploaded a file - tcpmon.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
This should create a folder C:\tcpmon
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\tcpmon
hit the enter key - if you get a 'Not Found' error try
DIR D:\tcpmon
or
DIR E:\tcpmon

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\tcpmon <drive>:\windows\winsxs /y /i /s /v /h

run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your SkyDrive Public folder, and post a new link

paul1149 · Dec 25, 2012

I appreciate your looking at this.

That tcpmon.ini error I cited was from the previous install. Looks like it was baked into the cake by Dell. The AV that came installed was McAfee, which went right out the door. Currently nothing is installed.

Yes I had run the troubleshooter, but am doing so again now... This time it claimed success and told me to try to update. But update gave me the same error. Could the troubleshooter be so dense as to only check the availability of a connection to the remote host?

paul1149 · Dec 25, 2012

Slight problem with the logistics of the tcpmon.ini. There is an intermediate folder in the zip that is getting in the way. Assuming I can rename it, you want me to copy the entire folder over to sxs, not simply the .ini?

EDIT: Ok, I did the rename and copied the file over. Thanks.

NoelDP · Dec 25, 2012

No - you MUST follow the directions as given to ensure that the copy proceeds properly
You CANNOT do it in normal Windows.

If you get errors, note the exact wording and post back with details.

NoelDP · Dec 25, 2012

Not sure about what the troubleshooter actually tests - but I doubt it's very much

paul1149 · Dec 25, 2012

You misunderstood me. The folder name was a long affair, not tcpmon. I understand the repair enviro thing.

NoelDP · Dec 25, 2012

That's the idea - the whole folder is copied to the target location, not just the file (this hopefully removes any chance of permissions problems later)

paul1149 · Dec 25, 2012

When I Extracted All to C:, there was no tcpmon folder, only a long-named folder, windows....blah, blah... x86. That's why I thought I should rename it to tcpmon. The output of the command was "1 file copied", so I guess it was a success if folder structure doesn't matter.

No, I guess not. I see the tcpmon.ini is supposed to be buried within that long-named folder. I need to extract again, this time creating the c:\tcpmon folder, and proceed from there.

NoelDP · Dec 25, 2012

My mistake!
Christmas must have got to me more than usual

I normally do it slightly differently, and forgot the implications here....

I've re-uploaded the file/folder in the proper configuration - follow the original instructions

paul1149 · Dec 25, 2012

I just went through it again before you posted, adding "tcpmon" to the output folder spec of the Extract command. In the RE, windows copied that long-named subfolder over and said "1 file copied", so I think we're good. The only thing that puzzles me is I can find the previous folder/file I copied over in winsxs. I suppose it's not important.

paul1149 · Dec 25, 2012

One other odd thing - when I booted up Windows told me that updates were available. I'm set to notify of updates. This seems to parallel the troubleshooter's behavior. Part of Windows seems to think everything is fine, but something specific is preventing the new updater from installing. There might be a clue in there somewhere.

I read early on that the first error pertains to an Activation problem. But Windows is activated, and the first error is not persistent anyway. Not making a lot of sense of this.

NoelDP · Dec 25, 2012

Please follow the original instructions with the new zip file - it's very important that teh proper file gets put in the proper place (i.e. C:\Windows\winsxs\<longfilename>\tcpmon.ini)

paul1149 · Dec 25, 2012

I just checked the file/folder and it has the current date/time filespec, so I think we're good. Thanks again. And I again tried the update, and this hasn't solved the problem.

paul1149 · Dec 25, 2012

One other possible clue. What started this mess was that while I was doing updates via a local store, the machine blue-screened a couple of times. That has never happened before in my update process, so I looked deeper and found I couldn't update even from MS's servers. But if even the Dell image doesn't solve this, I see no alternative to a fresh install from an external disk.

NoelDP · Dec 25, 2012

Please post the new CBS log.

paul1149 · Dec 25, 2012

Here she is. Getting big.

paul1149 · Dec 25, 2012

Very bizarre. As I just went to shut off the machine, I noticed the update icon on the Start menu Shutdown button. I went ahead with it, and windows is now apparently installing one update. I can only surmise that update is the update agent itself. But how on earth did that get through this problem? Will add info as I get it.

EDIT:
The update hung for half an hour. I hit the power button, but that sent it into sleep or hibernation rather than shutting it off. Then I turned it off all the way. When Windows resumed, the update came back on. It took several minutes, but this time it apparently did take. Now back in Windows, I tried to update again, but nothing is changed. BTW, when the error occurs, it's immediate, as if there were no internet connection.

EDIT2:
Since I switched it to automatically download and install, Windows has been grabbing as many downloads as it can and installing when I shut off. First it was 7, now 9, plus whatever it does while the system is up. Yet it still won't install the update agent.

Can't install "new Windows Update software" -errors 80004005, 800700B7

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Three-Toed Sloth

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer