AutoPatcher

Infobox Software
name = AutoPatcher



caption = A screenshot of AutoPatcher's installation selection screen
author =
developer = Antonis Kaladis & Jason Kelley
released =
latest release version = 5.6.0.81 (AutoPatcher)
1.0.5 (APUP)
latest release date = release date|2008|09|7
latest preview version =
latest preview date =
operating system =
platform = Microsoft Windows
language = English (Other translations available)
genre = Software utility
license = Freeware
website = [http://AutoPatcher.com/ AutoPatcher.com]

AutoPatcher was an alternative to Microsoft's Windows Update developed by Antonis Kaladis and Jason Kelley, and a comprehensive collection of up-to-date security patches, addons and registry tweaks collated into a single package designed to update a Windows XP Service Pack 3, Windows 2000 SP4, Windows Server 2003 SP2 or Windows Vista SP1 system from a local file, without the need to use Windows Update or connect to a network each time.cite web
title = What's AutoPatcher?
publisher = The AutoPatcher team
url = http://www.autopatcher.com/whatsautopatcher/
accessdate = 2007-08-11 ]

Distribution of the program was stopped on 29 August, 2007, after more than four years of existence, as a result of several Cease and Desist orders being given to the team, Neowin and some download mirrors. Microsoft stated this was for "security reasons" but would not further clarify.cite web
title = AutoPatcher no longer allowed
publisher = Steven Parker
url = http://www.neowin.net/forum/index.php?showtopic=584427
accessdate = 2007-08-29] cite web
title = Sad day
publisher = The AutoPatcher team
url = http://www.autopatcher.com/134
accessdate = 2007-08-29] cite web
title = Cease and Desist
publisher = M2Ys4U
url = http://www.neowin.net/forum/index.php?showtopic=584427&st=60&p=588813673&#entry588813673
accessdate = 2007-08-29]

Shortly after the project was shut down, Kaladis decided to resume production of AutoPatcher. To work around Microsoft's cease and desist notices AutoPatcher is now distributed using a program that downloads the updates directly from Microsoft's servers to create the AutoPatcher package on the client's machine instead of all being downloaded as a complete package.cite web
title = The next day (What's in store)
publisher = The AutoPatcher Team
url = http://www.autopatcher.com/137
accessdate = 2007-09-03 ]

Uses

AutoPatcher was designed for:
* Users that format their hard disks or reinstall Windows frequently.
* System administrators seeking to quickly deploy updates to multiple Windows PCs.
* Security conscious users seeking to avoid prior connection to the Internet with an insecure computer, in order to download the patches needed to secure their systems.
* Users with a slow connection to the Internet could download AutoPatcher using a faster connection on another computer, and burn it to a CD or copy it to a flash drive.
* Users seeking flexibility in patch deployment (AutoPatcher includes for convenience, a number of common "add-ons", and allows for a configuration to be saved and redeployed on other machines)

cope

AutoPatcher is able to run from removable media such as CDs, DVDs and USB flash drives, running from the Network (mapped drive) or local hard disk.

Project History

Version 1.0

The original AutoPatcher release was a simple batch program created by Jason Kelley and released on the Neowin forums October 15, 2003 [cite web
title = Requesting hosting for a file?
url = http://www.neowin.net/forum/index.php?showtopic=108204 ] . This original release contained 22 updates and could only be used on Windows XP SP1. Upon its release people asked for more updates, features, and a modern GUI. Jason was contacted by Antonis Kaladis and the two of them rewrote the AutoPatcher program and began maintaining and distributing the program.

Versions 4.0 - 4.2

Versions 4.0 - 4.2 were a great stepping stone from the old batch processes and the next stage of the program. These releases saw the use of the .AXP file format [cite web
title = AutoPatcher Blog (Archived)
url = http://www.flishfun.com/blog_archive/?p=128 ] for custom programs as well as more stability. There was only one release created for this series, the Full release that contained all critical, recommended and component updates, commonly used applications such as Sun Microsystems's Java Platform, and registry tweaks.

Version 4.5

Version 4.5 (Mar '04) saw some major changes from the previous v4 releases. This release saw the first time there were multiple release packs; Full, Lite, and Ultralite releases all contained critical updates. The Lite release contained all recommended updates and a few extra applications that the UltraLite release did not have. The Full release contained critical, recommended and component updates, commonly used applications such as Sun Microsystems's Java Platform, and registry tweaks. Version 4.5 also saw the integration of an XML database, and the current icon, designed by [http://www.iconaholic.com/ Foood] . [Racing the Clock cite web
title = AutoPatcher Blog (Archived)
url = http://www.flishfun.com/blog/?p=156 ]

Version 5.1

There were three 'release types' used in the 5.1-era; Full and Lite releases both contained critical, recommended and component updates, commonly used applications such as Sun Microsystems's Java Platform, and registry tweaks. The Lite release contained fewer extra applications than the Full release. Update releases were for updating previous months releases with the latest copies of files found in the latest Full & Lite releases, these smaller downloads were designed to reduce the amount of bandwidth needed for distribution.As of May 2007, the 5.1 releases are no longer being distributed.

Version 5.6

Version 5.6 of the AutoPatcher engine included a new user interface, and more "intelligent" [Intelligent in the sense that it can act on a wider variety of detected software/settings] scripting than the previous version, 5.1.

Changes from version 5.1 include:
* Support for Windows Vista and Windows XP Media Center Edition;
* New detections: Windows Media Player, Windows Live Messenger/MSN Messenger, DirectX, .NET and Windows Installer;
* Microsoft Office components detection: Word, Excel, PowerPoint, Outlook, Access, Project, Publisher, OneNote, FrontPage, InfoPath, Visio, SharePoint Designer and Groove;
* Detect hotfixes that were slipstreamed.

Windows

New releases using this version started with the May 2007 release with a change in release terminology.
*Full releases were replaced with Core releases. The Core releases still contain the critical updates, recommended updates, optional updates, and various tweaks present in the Full releases, but most of the large add-ons were moved to separate Add-On packs.
*Lite releases no longer exist, due to add-ons being moved to their own packs.
*Update releases remained the same, and are available every month to update the Core release.

AutoPatcher Core releases are ; previous versions are not required.AutoPatcher Update releases are ; All of the previous Update releases since the latest Core release need to be installed first.Thus, the order in which to install the releases is:

Core + Addon(Optional) + Update [+ Update [+ ...]

Office

The first AutoPatcher Office packages were released on August 20, 2007, consisting of AutoPatcher Office 2002 Core, AutoPatcher Office 2003 Core, AutoPatcher Office 2007 Core and AutoPatcher OfficePack Addon. [Release threads: [http://www.neowin.net/forum/index.php?showtopic=582275 2002] [http://www.neowin.net/forum/index.php?showtopic=582276 2003] [http://www.neowin.net/forum/index.php?showtopic=582277 2007] [http://www.neowin.net/forum/index.php?showtopic=582278 Addon Pack] ]

The AutoPatcher Office releases follow the same naming structure as the AutoPatcher Windows releases.

Custom Modules

It is possible to produce custom "Stand Alone" modules for use with AutoPatcher to install other third-party programs, tweaks etc. This can be useful, for example, inside businesses where bespoke software needs to be maintained.

The AutoPatcher team maintain a list of stand alone modules that have been authenticated, signed and packaged for use with AutoPatcher, but that are not eligible for inclusion into the add-on packs. [cite web
title = Stand-Alone Modules for AutoPatcher
url = http://www.neowin.net/forum/index.php?showtopic=570386
accessdate = 2007-08-18 ]

Project Shutdown

The AutoPatcher team shut down the project after receiving email from Microsoft requesting them to stop distribution on 29 August, 2007. This came after four years of existence, and surprised many. Microsoft mentioned the security risks of third party distribution of their patches, but it is unclear if this is the full reason behind the decision. They denied that the possibility of circumventing their Windows Genuine Advantage protection with the software was behind it. To at least partially support their decision, Microsoft stated that Firefox users could now access the Windows Update website for pre-Windows Vista systems. However, the Windows Update and Microsoft Update websites still require IE 5 or later.cite web
title = Microsoft Windows Update
publisher = Microsoft
url = http://www.update.microsoft.com/windowsupdate/v6/thanks.aspx?ln=en&&thankspage=5
accessdate = 2007-09-05]

Despite the fact that the software was commonly used for offline and network installs, and not merely as an alternative update client to avoid Internet Explorer, Microsoft did not address the issue.

Comeback

Antonis revealed in the AutoPatcher Blog that his biggest concern after the project was shut down by Microsoft was that "people around the globe [would] start writing their own custom modules and start redistributing their own releases." He added that one of the security features in AutoPatcher "would automatically flag these releases as unofficial", but if end-users only had a choice of unofficial releases, the spread of malicious software would be very easy.

As a result the AutoPatcher Updater, or APUP, tool was created to automatically download the required patches from Microsoft's web servers and store them in the same file structure used in previous AutoPatcher releases. Once the files have been downloaded "everything remains as you know it."

Team

The AutoPatcher Team consisted of several personnel with deep knowledge on the Microsoft's new releases of updates. These people gathered the resources needed to come up with new Update releases each month. Translations were also made by the appropriate team member. The main AutoPatcher Team members were:

* [http://www.autopatcher.com/about/antonis-kaladis/ Antonis Kaladis] - Project Manager & Lead Developer
* [http://www.flishfun.com/blog/ Jason Kelley] - Original Creator & Original Release Manager (Retired)
* [http://www.autopatcher.com/about/lyndon-brown/ Lyndon Brown] - Release Manager (AutoPatcher 2000/XP/2003 x86) & PDMS Maintainer (Retired)
* [http://www.autopatcher.com/about/renato-ribeiro/ Renato Ribeiro] - Release Manager (AutoPatcher Vista/XP/2003 x64) & Portuguese AutoPatcher Maintainer
* [http://www.autopatcher.com/about/marcin-wawer/ Marcin Wawer] - Polish AutoPatcher Maintainer
* [http://www.autopatcher.com/about/torstein-nicolaysen/ Torstein Nicolaysen] - Norwegian AutoPatcher Maintainer (Retired?)
* [http://www.autopatcher.com/about/paul-deen/ Paul Deen] - Dutch AutoPatcher Maintainer
* [http://www.autopatcher.com/about/pascal-bekkering/ Pascal Bekkering] - Dutch AutoPatcher Maintainer
* [http://www.autopatcher.com/about/giannis-skevakis/ Giannis Skevakis] - Greek AutoPatcher Maintainer (Retired?)
* [http://www.autopatcher.com/about/domenico-guarnaccia/ Domenico Guarnaccia] - Italian AutoPatcher Maintainer
* [http://www.autopatcher.com/forums/index.php?showforum=25 Cristiano Portela] - Brazilian Portuguese AutoPatcher XP Maintainer
* [http://www.autopatcher.com/forums/ Erik Ramey] - AutoPatcher 2000 ENU/XP ENU/Vista/Office ENU Maintainer

References

ee also

* Offline Update
* Project Dakota
* Slipstream (computing)

External links

* [http://www.autopatcher.com/ AutoPatcher Homepage]
* [http://www.autopatcher.com/forum AutoPatcher Forum]
* [http://www.webuser.co.uk/news/170801.html What's next for Autopatcher?] Feature and interview with Kaladis on Webuser.co.uk