Autopatcher.net

Bug in AutoPatcher Windows 7 SP1 (x64) 17-dec-2014:

\modules\Windows_Seven_x64\NonCritical\NonCritical_files\Windows6.1-KB2773072-x64.msu:

The update package contains the x86 version of the KB2773072 update.

Thanks for that fragXpert, will correct and upload..

Update: Have corrected the issue, uploaded edited script and new rtiz file, now on main list dated December 20..

AutoPatcher Windows 7 SP1 (x64) 20-dec-2014

Found a couple of unused files:

\modules\Windows_Seven_x64\Critical\Critical_files\Windows6.1-KB3006226-x64.msu (removed update)
\modules\Windows_Seven_x64\Critical\KB2875783_seven_x64.apm (replaced by KB2961072)

@fragXpert --

\modules\Windows_Seven_x64\Critical\KB2875783_seven_x64.apm

is an orphan and will be removed from the archive..DONE (not yet uploaded)

My question is in relation to

\modules\Windows_Seven_x64\Critical\Critical_files\Windows6.1-KB3006226-x64.msu (removed update)

, what do you mean by removed update (according to my script it contains both a module and an installer)... please elaborate...

KB3006226 was an update which caused some minor compatibility issues with certain software, so I thought the .apm is missing because the update was removed from AutoPatcher... My bad, sorry

Microsoft update the security bulletin to include another update which resolves the issue.
More information can be found in the security bulletin at https://technet.microsoft.com/library/security/MS14-064.
No need to aplogize,we all make errors at some time or other, I however seem to make more !!

Will upload the corrected archive shortly...DONE

I noticed an unexpected (Apup) Verification Failed message after downloading Win7x64 Critical.. Here is the corresponding error in Apup log:

----
***Downloading Releases***

Files to be Downloaded: 1
Download queue processed. Proceeding to next phase.

Download Error: D:\AUTOPATCHER\Apup_1_4_38_Win7_Win8\temp_bin\___windows_critical_seven_x64_sp1.7z
File size does NOT match. Expecting 19556, but found 19566!!!
----

This happens on every attempt, and may need some attention. Cheers.

apeman wrote:I noticed an unexpected (Apup) Verification Failed message after downloading Win7x64 Critical.. Here is the corresponding error in Apup log:

----
***Downloading Releases***

Files to be Downloaded: 1
Download queue processed. Proceeding to next phase.

Download Error: D:\AUTOPATCHER\Apup_1_4_38_Win7_Win8\temp_bin\___windows_critical_seven_x64_sp1.7z
File size does NOT match. Expecting 19556, but found 19566!!!
----

This happens on every attempt, and may need some attention. Cheers.

Confirmed - downloaded critical 7x64 7z is Size=19566

apeman, if you're up to it, should be, you're an apeman Check the log file, it will show you what 7x64 critical apm files are missing and where they go. Just download the 7x64 critical .7z file by itself (directly from the link in the log), extract (or view in portable 7-zip) the contents, your missing files should be in there. Move or Copy the files you need (in this case) to \modules\Windows_Seven_x64\Critical\

Rerunning AP and either loading the release (is it official) or downloading the script again (any missing files)..? The script error will remain until it's fixed but your release should be good to go. FYI, it took longer to type this post than to perform the quick update fix. In this case, the issue seems to be a small nit with the size error listed in the script for the critical 7z, but the 7z contents (the apm files) should be accurate (official status will let you know). If there is an error in an apm file, this is different, the apm needs fixing so this manual update would be pointless. Fear not, Sweeper is effective with finding the strays (extras), run Sweeper to remove any unwanted files. Give it a try, if something is amiss, run Sweeper to do some house cleaning, then give the script another go when the appropriate edit has been made.

This fix works 99% of the time on recently updated scripts! The archives are usually the last files that get their size/hash updated, after old files/links are removed, new files/links are added, a new rti is created, and so on - then the archives. If a new apm file should fail for some reason after it has been extracted, this info is also helpful to the script maintainer.

Again, this info is for the tech-mined AP user, most users will find it best to simply wait for a fix.

Have uploaded the updated script, so all should be honky dory. Give it another shot if you will and report back.... I'M A BAAAAD BOY !!!!!

Amended a NonCritical apm, and as such updated, uploaded to server, script dated January 1 2015

changelog: @KB2511250;