New
#11
OK, that's it. Case closed. Thanks
Is it as clear cut as NoelDP makes out?
Like many I've had the issues referred to by others in this thread.
However, I've also seen that in the windowsupdate.log file, since this update has been applied, the log reports all but one event (= file?) as "Microsoft Signed: NA" whereas previously everything was "Microsoft Signed: Yes".
Can anyone explain this as it certainly does not instil confidence?
The reason for those NA response is that the files concerned are simple compressed xml files - and cannot be signed.
I suspect that it's a hold-over, and not relevant any longer - but my coding skills aren't good enough to know for certain.
I also suspect that MS haven't yet switched on the servers fully - and that when they do, the situation will resolve itself as the 320 version self-updates again.
Certainly doesn't sound like XML to me - this is what I see:
Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
WuSetup has finished. Exit code is 0x00000000
Microsoft signed: NA
Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMPC6B8.tmp with dwProvFlags 0x00000080:
Microsoft signed: NA
WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194
WARNING: DownloadFileInternal failed for http://ds.download.windowsupdate.com...1-wuredir.cab: error 0x80190194
WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194
WARNING: DownloadFileInternal failed for http://download.microsoft.com/v11/2/...1-wuredir.cab: error 0x80190194
Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\v6-win7sp1-wuredir.cab with dwProvFlags 0x00000080:
Microsoft signed: NA
Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\v6-win7sp1-wuredir.cab with dwProvFlags 0x00000080:
Microsoft signed: NA
Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
Microsoft signed: NA
Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP1EED.tmp with dwProvFlags 0x00000080:
Microsoft signed: NA
Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
Microsoft signed: NA
Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP1F1D.tmp with dwProvFlags 0x00000080:
Microsoft signed: NA
Whereas previously (at same apparent point in process):
Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:
Microsoft signed: Yes
Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:
Microsoft signed: Yes
Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
Microsoft signed: Yes
Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
Microsoft signed: Yes
Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
Microsoft signed: Yes
Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
Microsoft signed: Yes
Apples and Oranges.
If you notice, there is an error code prior to each 'NA' response - which means that the content is not available on the server.
When the updater did not work i ran cintrip and treaking.com and it fixed the issue much easier than most fixes I found
Can someone help me please.
I got 2 updates on Thursday Nov. 27 - at least I thought I did - but this morning I got a notification of 122 - yes 122 important updates - some as far back as 2011 and already installed according to the update history.
I checked and saw that Update Agent 7.6.700.320 had also been on installed on the 27th. I have never see Update Agent before. But here I am with a note to install 122 updates even though they were done years ago. So what should I do? I'm a senior citizen (ie. not a computer expert by any means).
Thank you,
JenAnne Victoria BC CANADA
PLease post your C:\Windows\windowsupdate.log file, as well as the following...
Please follow the Windows Update Posting Instructions and post the requested data
If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)
Well, I found the log file but how many lines of stuff do I have to post - just from Nov. 27th; what kind of file. I don't have Word
I read the Update Posting Instructions but that was to much for a senior non-computer person. Sorry, but I don't like installing things on my PC that I don't understand.
I just can't understand why this Agent has suddenly been installed in 2014 and wants to redo files from 2011.
Did you even bother to read the instructions in the posted tutorial?
The Windows Update Agent controlswhat happens with Windows updates since the date of issue - 2013, at least.
Either post the requested data, or make room for those that will follow instruction.