File Verification Error - SP1 X86
Guest_Tony R._* 30 Oct 2008
I have been getting this the past few months, finally had time to track it down and spit out a log file.
here's the relevant information, this is a fresh install.
I did go download the KB943729 file, and stuck it in the appropriate dir which was empty.
Edited by Tony R., 30 October 2008 - 12:36 AM.
here's the relevant information, this is a fresh install.
I did go download the KB943729 file, and stuck it in the appropriate dir which was empty.
Missing file H:\Tech Files\AutoPatcher\APVista\modules\Components\KB943729_vista_x86.apm_files\Windows6.0-KB943729-x86.msu Item Windows6.0-KB943729-x86.msu is missing. Adding its download to the queue. --Adding http://www.download.windowsupdate.com/msdownload/update/software/updt/2008/03/windows6.0-kb943729-x86_851d9b73c18ecc8d9f04bc2d2f1be0aca0126704.msu-- ***Downloading Releases*** Files to be Downloaded: 80 windows6.0-kb943729-x86_851d9b73c18ecc8d9f04bc2d2f1be0aca0126704.msu: Valid name, no data record of requested type Download Error: H:\Tech Files\AutoPatcher\APVista\modules\NonCritical\___windows_noncritical_vista_x86.7z File size does NOT match. Expecting 18986, but found 18043!!! Download error: H:\Tech Files\AutoPatcher\APVista\modules\Components\KB943729_vista_x86.apm_files\Windows6.0-KB943729-x86.msu File does not exist!!!
Edited by Tony R., 30 October 2008 - 12:36 AM.
James
30 Oct 2008
Hi Tony R.
Welcome to the forums and thanks for the report.
I do not know why you have that problem with windows6.0-kb943729-x86_....msu, because it downloads alright for me.
The second error, for ___windows_noncritical_vista_x86.7z was a mistake in the script, which I have just corrected. Sorry about that (that was my fault).
Could you please run APUP again to confirm that this is now OK.
--
Welcome to the forums and thanks for the report.
I do not know why you have that problem with windows6.0-kb943729-x86_....msu, because it downloads alright for me.
The second error, for ___windows_noncritical_vista_x86.7z was a mistake in the script, which I have just corrected. Sorry about that (that was my fault).
Could you please run APUP again to confirm that this is now OK.
--


