WINDOWS UPDATE does not download update files

[NoelDP]

Windows Update works exactly as it's supposed to - as it has worked for the past 20 years.
You always have the option of learning how to create slipstreamed media - but for occasional installs it takes longer than it's worth.

 

[betaupsilon]

Windows Update works exactly as it's supposed to - as it has worked for the past 20 years.
You always have the option of learning how to create slipstreamed media - but for occasional installs it takes longer than it's worth.

If it is working correctly then why do I have to run the SUR tool every single time concurrently with the UPDATE tool to complete the downloads? I do not recall doing that in the past. I thought you only had to install & run the SUR tool a SINGLE time.

Am I mistaken?

 

[NoelDP]

Why are you running the CHeckSUR Tool? Is it being offered by WU?

 

[betaupsilon]

Why are you running the CHeckSUR Tool? Is it being offered by WU?

I don't know MAN. You are the presumed EXPERT here. Your website @ the link below ADVOCATES the SUR tool & the UPDATE utility does not seem to work without running it. So you TELL me what is going on! Are you not aware of the link below?

http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html

I did a FRESH install or what you may coin as a "CLEAN INSTALL" & the UPDATE utility does not work by itself. If anything on a FRESH install it should work, not on a corrupt or OLD system.

 

[Layback Bear]

Lets see if I can help clear the muddy water.

When a system is having a problem and one decides to do a Clean install I do not believe in taking short cuts.

We know that a fresh install of Windows Updates takes a long time, we have done it. That is just the way it is. When ever thing is work proper all programs should also be a clean install. The whole purpose of this, is not to drag old problems into the Clean Install.

Moving things from a old install of Windows 7 that was having problems could very easy also move the problems to the new Clean Install and that includes moving the Windows 7 Update over to the Clean Install.

Their are two basic installs, Clean Install and Repair install they both have their purpose.

Clean Install is not a coined phrase, it is a exact phrase.
This tutorial by Brink explains things.

http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

Now their is a Repair Install that has a different purpose and when done correctly will fulfill that purpose.

It's explain quit well in this tutorial by Brink.

http://www.sevenforums.com/tutorials/3413-repair-install.html

Either one that is chosen Windows 7 Update should be in my opinion be new gotten through Windows 7 Updates. (New)
Yes we know their are other ways but they defeat the Clean part of install.

Hopefully we are on the same page now.

I think at this time it would be helpful if you could state exactly what the problem is you are having at this time.
Please do it in a polite fashion.

With all the post back and forth it gets very confusing to understand the exact problem you are having now.

NOTE:

Noel is not a presumed expert. He is a expert on this forum and many others. He is also one of the few experts that offers his free time to help others. Some times he gets overwhelmed with request it take a little while to get to some of them.

Layback Bear

 

[betaupsilon]

Lets see if I can help clear the muddy water.

When a system is having a problem and one decides to do a Clean install I do not believe in taking short cuts.

We know that a fresh install of Windows Updates takes a long time, we have done it. That is just the way it is. When ever thing is work proper all programs should also be a clean install. The whole purpose of this, is not to drag old problems into the Clean Install.

Moving things from a old install of Windows 7 that was having problems could very easy also move the problems to the new Clean Install and that includes moving the Windows 7 Update over to the Clean Install.

Their are two basic installs, Clean Install and Repair install they both have their purpose.

Clean Install is not a coined phrase, it is a exact phrase.
This tutorial by Brink explains things.

http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

Now their is a Repair Install that has a different purpose and when done correctly will fulfill that purpose.

It's explain quit well in this tutorial by Brink.

http://www.sevenforums.com/tutorials/3413-repair-install.html

Either one that is chosen Windows 7 Update should be in my opinion be new gotten through Windows 7 Updates. (New)
Yes we know their are other ways but they defeat the Clean part of install.

Hopefully we are on the same page now.

I think at this time it would be helpful if you could state exactly what the problem is you are having at this time.
Please do it in a polite fashion.

With all the post back and forth it gets very confusing to understand the exact problem you are having now.

NOTE:

Noel is not a presumed expert. He is a expert on this forum and many others. He is also one of the few experts that offers his free time to help others. Some times he gets overwhelmed with request it take a little while to get to some of them.

Layback Bear

To clarify I did a CLEAN install!!

No programs have yet been installed. I attempted to update the system 1st & foremost before embarking on such endeavors. The fact of the matter is WU is not working unless I execute the SUR tool either beforehand or concurrently. I have to do this EVERY single time I select another upgrade to install. Since this is a CLEAN install I do not attempt to install the entire update suite at once. I try to do them in a reasonable chronologic selection in order to avoid FAILURES.

Why I have to run SUR to get the job done indicates to me that WU is not working. Am I wrong?

To circumvent the downloading problem I copied the downloads from the previous CLEAN install that reside in the SOFTWARE DISTRO directory. The previous CLEAN install was 3 hours before the last one.

So if I ever have to go through any CLEAN installs in the future how can I get the WU to work in the streamlined fashion? My impression is that the WU would have the least problems on a CLEAN install case versus some old system configuration.

So far I have not heard a thing about the files I uploaded. Do they indicate anything? No one has answered that yet!

Also, do you have a prescribed procedure on installing updates upon a CLEAN install. If there are deviations from how WU typically works that would HELP.

 

[betaupsilon]

The lack of definitive response baffles me. Is my UPDATE utility working correctly OR no one has an explanation?

 

[derekimo]

The lack of definitive response baffles me. Is my UPDATE utility working correctly OR no one has an explanation?

You seem to think someone here owes you an immediate response like you paid for the volunteer help.

And your use of all caps is seen as shouting, I suggest a change in attitude and patience.

 

[Layback Bear]

I'm not a Windows Update expert but my thoughts.

If you need to use a CHeckSUR Tool before every Windows 7 Update their is something breaking Windows 7 Update path.

Because you have a Clean Install that should not be happening unless the media you used to install Windows 7 is corrupt.

Do this tutorial by Brink and post the log here. The log might give us a clue.

http://www.sevenforums.com/windows-...ne-activation-issue-posting-instructions.html


We do know how frustrating these problems can be.
We also have problems and help other members with problems 24/7/365.

Like Noel and derekimo, I spend many hours every day on this forum trying to help others.

derekimo being a moderator spends a lot of his time moderating the forum and it activities.


Example:
I have been gone according to the time stamp on the top of the page 18 hours. Some of that time doing personal things and some of the time sleeping and watching Hulu.

Keep this in mind that we all have our lives and do not need to explain to anybody why we are not on the forum.
We do not get the post counts we have without spending a lot of time helping others on the forum.
We will help you if at all possible. We do need your help in order to help you.

 

[betaupsilon]

I'm not a Windows Update expert but my thoughts.

If you need to use a CHeckSUR Tool before every Windows 7 Update their is something breaking Windows 7 Update path.

Because you have a Clean Install that should not be happening unless the media you used to install Windows 7 is corrupt.

Do this tutorial by Brink and post the log here. The log might give us a clue.

http://www.sevenforums.com/windows-...ne-activation-issue-posting-instructions.html

For what this is worth it is a campus wide volume license. I have attached the MGA results. I installed from a CD & I assume it is OK since the system runs.

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-2VJC9-XBBR8-HVTHH
Windows Product Key Hash: k/l/EMDQdwK9OvdCkPtHG1YdosE=
Windows Product ID: 00392-918-5000002-85284
Windows Product ID Type: 1
Windows License Type: KMS Client
Windows OS version: 6.1.7601.2.00010100.1.0.004
ID: {698417CC-5E97-46B9-9E42-84C7849C36B6}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Enterprise
Architecture: 0x00000000
Build lab: 7601.win7sp1_gdr.150722-0600
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->
File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{698417CC-5E97-46B9-9E42-84C7849C36B6}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.004</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-HVTHH</PKey><PID>00392-918-5000002-85284</PID><PIDType>1</PIDType><SID>S-1-5-21-2246171005-3118550015-2927330856</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>OptiPlex 755                 </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A12</Version><SMBIOSVersion major="2" minor="5"/><Date>20081209000000.000000+000</Date></BIOS><HWID>03AA3F07018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL  </OEMID><OEMTableID>B9K    </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, Enterprise edition
Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
Activation ID: ae2ee509-1b34-41c0-acb7-6d4650168915
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00392-00170-918-500000-03-1033-7601.0000-2322015
Installation ID: 018740771136109992636395822215772896589885417594282171
Partial Product Key: HVTHH
License Status: Licensed
Volume activation expiration: 252240 minute(s) (175 day(s))
Remaining Windows rearm count: 1
Trusted time: 8/25/2015 6:15:02 PM

Key Management Service client information
    Client Machine ID (CMID): fd9a96da-7a9b-4960-9e45-dee9f5f13ea5
    KMS machine name from DNS: its-kms.unl.edu:1688
    KMS machine extended PID: 06401-00206-405-033053-03-1033-9600.0000-2172015
    Activation interval: 120 minutes
    Renewal interval: 10080 minutes
    KMS host caching is enabled

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Not Registered - 0x80040154
Admin Service: Not Registered - 0x80040154
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: MAAAAAEABAABAAEAAAABAAAAAQABAAEA6GE2EJxOki6KKCivOuxSUn7H2rmUCkbK

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x0
OEMID and OEMTableID Consistent: yes
BIOS Information: 
  ACPI Table Name	OEMID Value	OEMTableID Value
  APIC			DELL  		B9K    
  FACP			DELL  		B9K    
  HPET			DELL  		B9K    
  BOOT			DELL  		B9K    
  MCFG			DELL  		B9K    
  SSDT			DELL		st_ex
  ASF!			DELL  		B9K    
  TCPA			DELL  		B9K    
  ____			DELL  		B9K    
  SLIC			DELL  		B9K

 

[Layback Bear]

Well I think I see what are some problems. These problems could be your update problems. I have asked a expert to take a look. Just hang in their.

KMS Client

Product Name: Windows 7 Enterprise

File Scan Data-->
File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]

5"/><Date>20081209000000.000000+000<

Your (My System Specs) show

Computer type PC/Desktop
OS Windows 7 Home Prem 32 bit

 

[Layback Bear]

Because what I know about KMS you could put on the head of a pin. This is what I'm looking for.

***Does a Windows License Type: KMS Client get it's updates through the campus Server or can they be download from the internet with out the use of the campus Server.

Edit:
Have you asked your campus I.T. Department for help?

 

[betaupsilon]

Because what I know about KMS you could put on the head of a pin. This is what I'm looking for.

***Does a Windows License Type: KMS Client get it's updates through the campus Server or can they be download from the internet with out the use of the campus Server.

Edit:
Have you asked your campus I.T. Department for help?

Not to confuse matters, but I saw a WIN7 HOME reference. That is a separate system on another partition. We are dealing with WIN7 ENTERPRISE, but the UPDATE utility is exhibiting similar behavior on that machine as well. Did I submit info on the WIN7 HOME? If so that was an accident.

Regarding our IT dept. They have gone through a restructuring & are not to swift on responding or even fixing problems. I find this site more informative than what they have provided in the past. So at this point I have left them out of the loop.

Regarding "KMS Client", I think I am getting updates through the web, not a local server. Can I do anything to confirm this?

 

[Layback Bear]

The only thing I can think of is get with the I.T. Department of the University.
Only they would know how they have their KMS Client methods set up.

Well my 3 brain cells and knowledge are exhausted on this problem.

 

[betaupsilon]

I iterated on another experiment & ONLY THINK what may have happened. I reverted back to the image without the updates having been installed or downloaded. Instead of selecting a SUBSET install of the UPDATES I checked everything & allowed the entire set of UPDATES to be downloaded. I patiently watched the progress bar until 100% of the downloads completed & then terminated the installment.

I then checked the downloads in the SOFTWARE DISTRO directory & it seemed fully populated. From that point I could do incremental updates in subsets.

Previously, I would select a subset immediately after the CHECKING FOR UPDATES completed & install. My guess is the entire suite of updates never downloaded. So upon restart & doing another update of another subset the UPDATE utility maybe was confused & could not recognize what had or had NOT been downloaded?

That is when I started to use the SUR tool in conjunction with the UPDATE utility. Is this is probably a BUG that MS should address or was I using the UPDATE utility beyond the scope of its intended designed? At the very least the installation process should not be initiated prior to downloading the entire suite of updates or this problem will manifest itself.

 

[Layback Bear]

I really don't know if your problem will come back. Lets be happy for now you got all your updates.

I'm glad you method of updating worked. On my systems I do it different but that really doesn't matter. You found a way to do it on your system and that does matter.

Happy computing

 

[UsernameIssues]

Is this is probably a BUG that MS should address...

If you meant to make a statement:
"This is probably a BUG that MS should address..."
Then you can contact MS about this if you want. Making a thread here is not contacting MS.

If you meant to ask a question:
"Is this a BUG that MS should address..."
Then the answer is: there is no evidence of a bug. If there were a bug in Windows Update (WU), then all of those who select a few updates at a time would all be experiencing the same bug. We would also be seeing multiple posts on the topic. I have several W7 64bit and 32bit virtual machines that only have SP1 installed (8GB VDI). I have brought those VMs up to date a few patches at a time several times this year (24GB VDI). Once I exit the VM, all of the patches are gone. Not once did I see the problem that you mention.

...was I using the UPDATE utility beyond the scope of its intended designed?...

No.

...At the very least the installation process should not be initiated prior to downloading the entire suite of updates or this problem will manifest itself.

This is not true. The cause of your WU download problems* has not been determined. Why would you state how things should be done based on your tiny set of experiences? There are lots of Windows users who select a few updates at a time, download just those updates, install just those updates and the start the process all over again.


*If I had to guess as to the cause or causes:
...campus gateway limits the number of simultaneous connections to MS WU servers
...impatience
...bad timing

 

[betaupsilon]

Is this is probably a BUG that MS should address...

If you meant to ask a question:
"Is this a BUG that MS should address..."
Then the answer is: there is no evidence of a bug. If there were a bug in Windows Update (WU), then all of those who select a few updates at a time would all be experiencing the same bug. We would also be seeing multiple posts on the topic. I have several W7 64bit and 32bit virtual machines that only have SP1 installed (8GB VDI). I have brought those VMs up to date a few patches at a time several times this year (24GB VDI). Once I exit the VM, all of the patches are gone. Not once did I see the problem that you mention.

...At the very least the installation process should not be initiated prior to downloading the entire suite of updates or this problem will manifest itself.

This is not true. The cause of your WU download problems* has not been determined. Why would you state how things should be done based on your tiny set of experiences? There are lots of Windows users who select a few updates at a time, download just those updates, install just those updates and the start the process all over again.


*If I had to guess as to the cause or causes:
...campus gateway limits the number of simultaneous connections to MS WU servers
...impatience
...bad timing

YEP, I meant to ask a ? if it is a possible bug. Regarding the cause you are right in that I have a limited sample size to definitively assess anything. However, the behavior seems repeatable on my end. Nonetheless, I will make personal notes to avert this issue if it ever crops up again.