"Permission Denied in prjUpdater" error
Posted 29 December 2010 - 08:17 PM
yep.from your log:
Operating System: English (1033) Windows XP Professional Service Pack 2
autopatcher doesn't deploy service packs, only the updates. the service pack himself is too big to force all the users download it. to deploy sp3, you will require this file (warning: this file has about 316.4MB). service packs us to have issues with anti-virus and firewals. ms us to recommend that those kind of software be uninstalled first, but at this point, it's possible that this isn't required, but one warning: don't do anything else when deploying an service pack
Posted 20 January 2011 - 10:51 AM
I solved the problem by downloading the "apup131.zip" and unrar only the "apup.exe"
Posted 12 February 2011 - 01:27 AM
A screenshot of the situation is here:
Note that I opened the log file AFTER the eror-pop-ups appeared,
so the text in the log file is from AFTER the pop-ups.
For both times this pop-up appears, I click on OK.
There seems to be no clue in the log file about this error-popup!?!
Then a while later I get a "Verification Failed" pop-up.
I click on OK here to continue.
The log file of the whole process is here:
Posted 23 March 2011 - 12:58 AM
Workaround: I Temporarily Disabled AVG Antivirus 2011 and ran APUP again -- did not get the error.
Note that my D:\AUTOPATCHER-XP dir is on a FAT32 drive, so it must have been the antivirus intercepting the RMDIR commands.
Posted 23 March 2011 - 01:48 AM
probably. that action is done too fast and certain av think that this is an bad behavior. other ones (the smart ones, at least) doesn't have any issue with that. as an sample, KIS 2011 doesn't have any issue with that. avast too didn't last week, but i didn't tested with avast 6
Posted 23 May 2011 - 01:15 PM
Even with AVG free 2011 disabled, I get file KB890830-v3.17.exe downloaded as a 2kB file, which of course then fails the Verification sequence ...
I 've also stopped my ZoneAlarm, tried again.
Still can't get the named file to download completely/correctly.
Posted 23 May 2011 - 02:51 PM
Posted 24 May 2011 - 09:30 AM
Thanks for that info.
Does that mean that the script for WinXP SP3 isn't up-to-date anymore since a few months now?
Is there a location where I can search/look for all the latest patches (dated files) to fix this manually?
I downloaded the patches for WinXP-SP3+ English, DirectX and DotNet (English) ...
P.S.: does the script download all patches (in its current list) even if verification on 1 or 2 fails ?
Edited by noorman, 24 May 2011 - 11:02 AM.
Posted 24 May 2011 - 11:47 AM
i'm not sure. i never had any usage for the xp enu script and i'm not checking it. but the script has an release date
> Is there a location where I can search/look for all the latest patches (dated files) to fix this manually?
in order to work, you have to search for the first month and make an list of the links to download. an tip: any bulletin has an replaced list. so, do an list with the updates and remove from your download list the updates that already was updated. just as an sample, the IE updates us to have new versions every single month. you don't require the ones from the last month, just the current ones
> does the script download all patches (in its current list) even if verification on 1 or 2 fails ?
yes and no. sometimes, ms removes from their servers the obsolete updates, like KB890830-v3.17. in this case, the file will not be downloaded. in other cases, like rootcerts, it is downloaded anyway (the link is static), but the detection may not work, because the detection is expecting an version and was downloaded is more up-to-date. (that is just an sample. i didn't checked if this issue is happening)
Posted 24 May 2011 - 05:58 PM
after do that correlation, remove from the modules folder the updates that has an - and do the same in your correlation list, to avoid waste time with something that already was replaced. do it one by one, until the end of your correlation list. after that, download the remaining ones and, if you wish, do an module for it (it's more easy than it looks) and save the updates in a folder with the same name than your module, plus _folder
important: sometimes, you must check for dependencies. just as an sample, an IE9 module for win vista shouldn't be opened for an fresh system, because it will not work without certain updates (and no, sp2 isn't enough). if you don't set an dependency in place for it the module will fail or the user will wait it finish forever (if the user is online when deploying it, even at dial-up, this one will hang and do an endless download, deploy it and then resume IE9)
Posted 25 May 2011 - 10:32 PM
Posted 31 May 2011 - 06:06 PM
Thanks for that info !
Edited by noorman, 31 May 2011 - 06:07 PM.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users