AutoPatcher Forum

Most users update multiple OSes with AutoPatcher, your issue is the service packs. The XP release targets SP3, and 7, SP1. There are a few updates that will install on XP SP2 but you might have more problems with 7, SP1 is required. I'm unsure how many updates will successfully install on 7 SP0. Check the forum threads for XP and 7, there's some information about prerequisites with links to service packs should you want to install them.

Open an .apm file with notepad, pick one from XP and 7, in \Critical, notice the dependencies, what the update expects to find installed on the given OS. Don't edit the file just look

AutoPatcher's code works with the apm file to show (or hide) updates that apply to an OS based on the service pack, IE, what's needed (the dependency) for the update to properly install. I'm not sure if the AutoPatcher code for Windows 7 is up-to-date, the problem, updates that only apply to 7 SP1 will also show (cannot be hidden) on a 7 SP0 machine. The install process will fail if the update needs SP1 and it isn't in place.

A1: I used to try and get users to separate the releases but not anymore, go ahead, download everything to the same folder. It makes it easier troubleshooting a problematic release with fewer scripts, but not impossible if there are more than a few in the same \modules folder. You will have to move or copy everything from point A to point B if all is in one folder - your call.

The only problem with APUP 1x (should be fixed in 2x) is too many scripts downloading at once can choke APUP. If APUP acts up select fewer scripts per each run.

A2: The documentation is scarce and outdated, read the pinned topics, they should help. You might also read the "AP Docs", also outdated but they offer more detail regarding AutoPatcher and APUP, this may answer some questions. If you have specific questions after using AutoPatcher and APUP, search the forums (they likely were already asked), or start a new thread, someone will help you.

Once APUP v2 is released and I become familiar with it I plan on creating a pdf quick start guide for my friends still using AutoPatcher and APUP. If it's worthy and the dev hasn't already put something together I will post a link to my guide here on the forums.

The "AP Docs" are here, link in post #4 - http://www.autopatch...dpost__p__14417

A3: Assuming the correct SP level is in place, AutoPatcher should pretty much keep you up-to-date similar to MU/WU. The scripts are static, by this I mean they don't scan your system and offer updates to download (unique to the system downloading ), rather, the script is updated every Patch Tuesday (adding and removing updates according to the bulletins), as well when there's a problem with the script. The SAME release is downloaded regardless if you download it from XP, Vista, or 7 - the contents will be the same.

One note, APUP will select the script matching the installed OS APUP is run from - if you're running APUP on XP and all you want is the Windows 7 or Adobe script, uncheck XP. I call this the native OS, it will (should) always be selected by default so pay attention. Also, if you need .NET or DirectX these are separate scripts from the OS scripts, have a look at the APUP Releases window for the complete list - the list will change, scripts will get added or removed as needed.

AutoPatcher should do a pretty good job of making current an XP system that recently installed SP3, or a Windows 7 system that installed SP1 - run the latest release and the OS should match MU/WU. If something is missing, the hope is the user will post a comment with specifics, if an update needs adding, removing, or editing, it will be done, time permitting.

The point of AutoPatcher is to have a mobile (portable) and reusable collection of updates that can be burned to CD or dropped on a thumb drive, and is capable of updating the OS the release targets. Just be sure the package is Official before you do anything. It's also a good idea to copy the release to the local drive on the system being update then run AutoPatcher (autopatcher.exe) to update, or APUP (apup.exe) should you want to add more scripts to an existing collection.

Important - use good judgement when updating a system, don't select 100 updates expecting the install process to go well. Also, there may be new updates appearing as you update a system - one update may be a prerequisite for another. As well, if you plan to update IE (from 6 to 7 or 8), or DirectX, any major install -> do it individually, reboot, make sure the install went OK.

If you want trouble update IE (6 to 8), DirectX 3.5 SP1(all 300+MBs), and .NET (to v4), add 50 OS updates as well -> (in one run) - you're sure to get it! This may sound derogatory but we've had people do this then come in here screaming "AutoPatcher broke their system".