[Solved] Xp Auto Patcher update error
Started by g12345567, Mar 07 2009 10:54 AM
9 replies to this topic
#1
Posted 07 March 2009 - 10:54 AM
I the process of doing an update and the following error message appears
WindowsXP-KB958655-x86-ENU.exe:404 - file not found
One or more files fas failed verification. Please re-run Auto Pacher Updater
Did a search and found the following on MS wed site
http://www.microsoft.com/downloads/details...;displaylang=en
6th march 2009
File Name: WindowsXP-KB958655-v2-x86-ENU.exe
Brief Description: Install this update to resolve an issue in MSI Installer 4.5.
I guess this is the new update of the above file not found.
If so Auto Patcher updater for xp needs to be updated to reflect the above change.
Untill this is done, I am nolonger able to complete downloading the updates as the updater will just exit as soon as the error is encounted.
WindowsXP-KB958655-x86-ENU.exe:404 - file not found
One or more files fas failed verification. Please re-run Auto Pacher Updater
Did a search and found the following on MS wed site
http://www.microsoft.com/downloads/details...;displaylang=en
6th march 2009
File Name: WindowsXP-KB958655-v2-x86-ENU.exe
Brief Description: Install this update to resolve an issue in MSI Installer 4.5.
I guess this is the new update of the above file not found.
If so Auto Patcher updater for xp needs to be updated to reflect the above change.
Untill this is done, I am nolonger able to complete downloading the updates as the updater will just exit as soon as the error is encounted.
#2
Posted 07 March 2009 - 11:48 AM
Hi g12345567...
Thanks for the report.
This is the nature of the beast, links will become outdated when new files are released. I'm sure the
development team will edit the XP script to reflect the change soon. In the mean time, your XP release
is good except for the MSI issue. I would install from the link you provided and when the script is updated
you will have the installer added to your XP release for later use which is how AutoPatcher/APUP works.
It is a good idea to run APUP once a week so it will pick up on the changes that are made and update the
release accordingly, and always run APUP when you know the script has been updated.
Again, AutoPatcher is not meant as a replacement for MU/WU for daily on the spot updating. The development
team isn't sitting around a table waiting for Microsoft to update a file or change a server.
It is a good idea to run "apup.exe /log" to determine the status of the release, there is good info in the APUP log.
The reports provided by the users are what help keep AutoPatcher/APUP Up-To-Date and they are much appreciated.
Mike
Thanks for the report.
This is the nature of the beast, links will become outdated when new files are released. I'm sure the
development team will edit the XP script to reflect the change soon. In the mean time, your XP release
is good except for the MSI issue. I would install from the link you provided and when the script is updated
you will have the installer added to your XP release for later use which is how AutoPatcher/APUP works.
It is a good idea to run APUP once a week so it will pick up on the changes that are made and update the
release accordingly, and always run APUP when you know the script has been updated.
Again, AutoPatcher is not meant as a replacement for MU/WU for daily on the spot updating. The development
team isn't sitting around a table waiting for Microsoft to update a file or change a server.
It is a good idea to run "apup.exe /log" to determine the status of the release, there is good info in the APUP log.
The reports provided by the users are what help keep AutoPatcher/APUP Up-To-Date and they are much appreciated.
Mike
Edited by gUiTaR_mIkE, 07 March 2009 - 06:18 PM.
#4
Posted 10 March 2009 - 04:26 PM
As a temporary measure, download of the non-existent file WindowsXP-KB958655-x86-ENU.exe has been removed from the script.
This will prevent Apup from stalling/crashing with a 404 error, until the script is updated properly.
--
This will prevent Apup from stalling/crashing with a 404 error, until the script is updated properly.
--
#5
Posted 12 March 2009 - 05:22 PM
Hi
Autopatcher allways show this update (KB958655-v2), but this is allready install.
Autopatcher allways show this update (KB958655-v2), but this is allready install.
#6
Posted 12 March 2009 - 07:28 PM
That is correct behaviour.
If you have already installed KB958655 (v1), then KB958655-v2 will show as already installed.
There is NO CHANGE to the files in the update between v1 and v2.
--
If you have already installed KB958655 (v1), then KB958655-v2 will show as already installed.
There is NO CHANGE to the files in the update between v1 and v2.
--
#7
Posted 12 March 2009 - 09:03 PM
Misunderstanding
KB958655-v2 allways stays checked, even its install by Autopatcher
KB958655-v2 allways stays checked, even its install by Autopatcher
#8
Posted 15 March 2009 - 05:46 PM
It says solved but how is it solved when my autopatcher still has the box for KB958655-v2 is still check market???
#9
Posted 15 March 2009 - 06:43 PM
Quote
TechSwap Posted Today, 10:46 AM
It says solved but how is it solved when my autopatcher still has the box for KB958655-v2 is still check market???
It says solved but how is it solved when my autopatcher still has the box for KB958655-v2 is still check market???
I believe the "Solved" was regarding 404 - file not found, but I will admit I'm not totally sure...
Quote
[Solved] WindowsXP-KB958655-x86-ENU.exe: 404 - file not found
Mike
Edited by gUiTaR_mIkE, 15 March 2009 - 11:14 PM.
#10
Posted 16 March 2009 - 08:42 AM
That's exactly right:
If you read the topic title:
Then you will see that the problem has been solved.
If you have another problem, please start a new topic.
--
If you read the topic title:
Quote
Xp Auto Patcher update error, WindowsXP-KB958655-x86-ENU.exe:404 - file not found
Then you will see that the problem has been solved.
If you have another problem, please start a new topic.
--
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users











