It seems many people are posting log files to the forums for the same errors others are having, even though explanations for the errors have been given. Please stop, if your errors are the same -- the problem is being addressed by the AP Team.
There are a few people in the AP Team who maintain multiple releases, which is a daunting task - if you only knew what was involved. Please be patient and be proactive if you need the updates immediately: download them from the source -> Microsoft. When the development team repeats the same answers to the same errors over and over it means they are not working on the scripts.
By the way, the pop-ups you see with APUP are designed to alert you of errors so you will look at the log file and troubleshoot the error message yourself. Your error message won't be unique and will have likely happened before.
How can you determine if your problem is the same as what has been posted to the forums? -> check your log and compare the errors in your log to the errors shown in the numerous log files "Already" posted. If an answer or explanation has been given it will apply to you as well. There's no need to remind anyone you are having the same problem.
If for some reason you need additional help to solve your problem, that is different, of course ask for help. This is a forum full of great people who love to offer their help. The more common and often encountered errors are "Outdated Files" and "Dead Links", "Firewall Setup" issues, and an unclear understanding of APUP, AutoPatcher, their Setup, Use, and Relationship.
APUP and AutoPatcher are extraordinarily easy to setup and use but at times a little tweaking is needed. Read the "FAQs" and "Search" the forums for answers, if this should fail, by all means ask for help.
A good way to verify a dead link is to right-click the http link, copy it to notepad. Notice the "--" at the end of all the links i.e. "KBxxxxxx.exe--" , remove the "--" and then paste the edited link in your browser or download manager and try to download the file directly.
Have a look at the FAQ for info on creating a log file. Open the log file with Notepad. CTRL-F will open "Find", type what you are searching for in the box, F3 will look for the next occurrence of your "search". This is an easy way to find "similar" items in files with lots of lines of information.
If you are logged in to the forums, use the key words from your log file and use the forum "Search" feature. Search the forum for your release ie: XP SP3 x86 and search for "KB952069-x86" and you will likely be shown all the most recent posts regarding this error. I got 17 hits and this error was mentioned repeatedly with the "Most Recent" showing first.
Go to -> "Search" -> "More Search Options" -> put your Keywords in the "Search by Keywords" box -> Select the "Forum" -> in "Show Me" select "Most Recent" -> Then "Perform Search".
Remember, no "Offline Updater" like AutoPatcher or any of the others out there should be viewed as a "Complete Replacement" to Microsoft Update.
Finally, you can still run AutoPatcher to update your PC. Assuming you downloaded most of the release, try unchecking the problem files from the AutoPatcher selection list, in this case for XP x86 items "KB952069" and the "EUFontUpdate", and then proceed with the update process. Ignore the message of "Unofficial" release. This has no bearing on your PC being updated properly.
I hope this helps a bit.
Having Problems? READ THIS FIRST!
1 reply to this topic
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users