A Poll On Your AutoPatcher Use 
Posted 28 July 2012 - 04:55 AM
Rustygun (a rustygun is something that doesn't work anymore I'm retired and this is my Hobby)
Posted 28 July 2012 - 05:10 AM
Posted 28 July 2012 - 08:32 PM
Posted 28 July 2012 - 10:01 PM
Thanks for your help
So APUP (apup.exe) will run but AutoPatcher (autopatcher.exe) wont? Have you tried running as admin (right-click autopatcher.exe)? Check all your security software, make sure nothing is blocking the program from running, including 'DEP' in the OS. You may have set DEP up but a Microsoft update may have reset security to default settings - don't let any AV, firewall, spyware, or malware program block either 'apup.exe' or 'autopatcher.exe' from running.
You may try again running APUP, select only 2 scripts to download, 'AutoPatcher Updater' (APUP) & 'AutoPatcher Engine' (AutoPatcher Program), make sure you get a complete download, this should eliminate missing files to start the program.
Now, I don't want to offend but if you look at the 2 terms I highlighted above, you make a very confusing statement, can you elaborate on what you mean here? It reads as if you're saying - "last month you got an error, AutoPatcher wont load, a main module issue but, ... after 300 MBs of updates it will load and run...!" What does this mean? The lack of periods (.) and commas (,) make this statement very hard to interpret.
Running the latest script shouldn't cause any problems, something is interferring with AutoPatcher, a screenshot of the error might help.
Posted 30 July 2012 - 03:51 AM
Posted 30 July 2012 - 04:06 AM
Posted 30 July 2012 - 04:21 AM
Now for your main problem. AP/Apup should have no problem starting at all regardless of the updates your computer already has. They were written in VB6 so the code is completely native to windows and all things it would require are already part of windows. If it has a problem... the only thing I can remotely think of is an Anti-Virus, firewall, the path has Unicode characters in it(AP and apup are not Unicode friendly), or improper admin rights issue. There is also the possibility that the slip streamed CD's are not proper but, we can probably rule that out.
Edited by ViroMan, 30 July 2012 - 04:24 AM.
Posted 30 July 2012 - 04:45 AM
P.S. I get a sever error message when I click the download button
Edited by rustygun, 30 July 2012 - 04:48 AM.
Posted 30 July 2012 - 08:14 AM
Posted 30 July 2012 - 11:06 AM
I understand completely, no need to apologize
It is really hard at times knowing ewxactly what the user on the other end is doing, and if the post lacks specifics it can take a long time getting to the root of the problem.
Posted 30 July 2012 - 11:34 AM
Ditto ViroMan's suggestion.
A good rule of thumb is to always copy or move the AutoPatcher release package, the \apup folder, to a local drive when either updating the release or updating the system itself.
If you were updating a system and you have a copy on the thumb drive then simply delete the folder (on the system) when the machine is fully updated.
If you were updating the release, you can make use of a backup practice on the thumb drive, naming older versions (folders) accordingly, then move the latest package back to the thumb drive once updated. This is one way a friend of mine does it,
The first 2 examples are \apup folders 'renamed' with their Patch Tuesday months used, and the \apup folder is the most recent or most up-to-date. There are many ways to maintain backups, it's good to have at least a one month Patch Tuesday backup.
The backup should be as close to the most recent Patch Tuesday as possible, a very old release may cause problems with those systems that also update via MU/WU.
Posted 01 August 2012 - 02:36 PM
Posted 01 August 2012 - 10:06 PM
Posted 02 August 2012 - 04:45 PM
Posted 09 August 2012 - 12:33 AM
Posted 10 August 2012 - 05:51 AM
Posted 14 August 2012 - 06:12 PM
Posted 15 August 2012 - 12:29 AM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users