AutoPatcher Forum

This is in regards to the apup update for Windows XP SP3.

I have gone over the entire forum and found similar problems to mine and various reasons. I tried all the fixes mentioned, nothing seems to work. I did finally by just clicking on apup to finally got what appears to be a complete download and all the current files. There is just one problem. The title bar on top of Autopatcher tells me that this is an Unknown Unofficial Realease and also Unnofficial/Unsupported Release. If this is truly the case I'l just wait until the "Official" release happens. I've seen no mention of notices about official or unofficial releases in regards to the August 08 release for WinXPSP3 so I'm not sure what is really happening here. Nothing has changed on my system. I re-installed a working XP partiton image that worked with the last apup for July 2008 on a backup machine just to make sure.

I too get that dreaded "Run-time error '0'" and "One or more files failed verification. Would you like to continue at your own risk?" I notice that at around the 32% or so mark the amount of download changes from 172.16MB to 169.45MB. I'm not going to go through all that send in the log file stuff, I'm just reporting my experiences here as I'm not really interested in a dialog at the moment, too busy doing real life business stuff if you know what I mean.

I also notice that when I run apup for the first time apengine.exe does not unzip and turn into autopatcher.exe. Autopatcher.exe appears when I run apup a second time. I get the messages mentioned above no matter how often I click on apup to redownload (into the same folder I just downloaded previously).

I have used your excellent software for as long as you were around. I find it really does help save time when doing a new installation from scratch. I personally hate to do installations or updates that involve being connected to the internet. I always update to an clean up-to-date (backup) image. Thats just how I do things and sites like your are a great help in that regard. I liked your last system before MS got on your case, but this one works as long as Microsofts servers are working and the files haven't been changed around on their servers which means using a current apup download I suppose.

Like I mentioned before I'll wait a while longer to update with apup until the bugs get worked out.

> Unknown Unofficial Realease
not all releases are signed right now. due that, in some scripts you in deed see that. just also a sample, i didn't have the time to figure how to use the tool to sign the modules. the reason is pretty simple: this avatar that i'm choosing right now shows my broken scapula bone, in my right arm (i'm not sure about the translation). so, right now, i'm more concerned about fix it at once than sign the modules

plus, there's an issue regarding an autopatcher translation, that i believe that will be fixed soon.

by the way: what is the language of the script that you are downloading?

[]s

I normally use Enlish (Canadian), yes I'm from Canada, and the last apup's always worked for me before. I have gone to "Regional & Language Option" in Control Panel and changed everything to US. I get the same results either way. I'm not to paranoid about using "unsigned" apps as long as they are known to work, so I'm not too bothered by that. Its just that I have never come across this problem (mentioned in my first post) before. If you think the updater will work, I'll give it a go on my test rig and check to see if all the updates are truly installed. Its still better then going through Microsoft Update or that other site, which is OK, but not as convienient as yours Part of the fun is finding out how to work around problems, so I agree the "unsigned" problem isn't a major catastophe, just one of those litlle pains in the derriere. Thanks for the feedback and good luck on fixing those bugs. Also, I hope you guys are here to stay.

Just a last reply before I get back to my work. Installing the updates works if you get the updater fully downloaded, even with the "unsigned" problem. The quirky part is downloading things to your computer and making sure apup takes. What worked for me was clicking on apup (with everything still in the same folder) until everything seemed to be there and then running the updater to make sure its all there. It can be kind of tricky as the results may not always be fully consistant so you got to keep trying. Also I noticed that there have been slowdowns and changes with how Microsofts servers seem to work. I did a scratch install of XP for a client and they noticed that The "runonce" page on MS servers for IE7 as down, just kept wanting to go to that page. A small patch fixed that problem. Yes I know its not related to apup per se, but MS's servers are a part of the apup system. So I'm just wondering about that. It may just be a combination of coincidences.

microsoft changes the revisions of hotfixes frequently if they spot a bug etc
the hotfix KB951618 got a v2 version
autopatcher expects file at http://download.microsoft.com/download/a/f...618-x86-ENU.exe
but microsoft changed to http://download.microsoft.com/download/a/f...-v2-x86-ENU.exe
so autopatcher gives an error '0' that means no file found
download the missing file at http://rapidshare.com/files/136895338/Wind...618-x86-ENU.exe and put it to modules\NonCritical\KB951618_xp_x86_enu.apm_file
re-run autopatcher and the problem is fixed

I just had a free moment so I decided to check on my thread here. Thanks 4NNuN4kI. I looked up KB951618. It for the Saming OneKey recovery software driver Safnt.sys in recommended updates which I really have no use for, nor have I heard of any people I deal with use it either, but then again you never know. I did manage to get the apup installer to work and it updates what I need up to August 08, I guess thats all that counts for now. Since KB91618 is not critical for me I'm not going to worry about that. I'm sure the guys here at Autopatcher will fix that problem in the next incarnation of the apup engine and help out the people that need that particular update. It's not easy when MS moves things around on you. I'm sure that other people around here will appreciate your fix though in the meantime.

Just one last post before I leave this thread, a partner of mine tried what 4NNuN4kI suggested during an idle moment and found that after replacing the "0" byte KB951618 file with a full KB951618 file the AutoPatcher turned into an "Official Release" (see above posts in this thread for details). I guess the apup engine did not load the needed file because MS changed something and choked in the process. Anyway by adding this file things are OK. All this trouble over a file that could not be downloaded properly from MS. AutoPatcher is running OK for me now and I can update all those new installs without a worry now, unless MS themselves screwed up a KB update, wouldn't that be a bugger! Ha, Ha.

The XP release has been updated to include v2.

I won't be able to generate a new RTI for now which means the XP thread will show as "Unoffical" until it's updated.