PR 1.0 Beta Update Error 62

[The Infidel]

Every time I click on the PR Beta shortcut and starts to update. I get this error:

"Error: 62: Access to the path 'C:\Program Files (x86)\Steam\steamapps\common\Battlefield 2\mods\pr_beta\bin\PRLauncher.exe' is denied. bin/PRLauncher.exe "

Any help? It worked yesterday and now it's just starting to do this.

[LITOralis.nMd]

Run PRLauncher as admin?

Or in windows explorer, go to C:\Program Files (x86)\Steam\steamapps\common\Battlefield 2\mods\pr_beta\bin\PRLauncher.exe

right click PRLauncher.exe ,
select properties
select Security Tab
Top white box should say "Everyone"
Bottom white box should have "Allow" ticked for everything except special permissions.

If that is not the case, report back here.

[The Infidel]

Run PRLauncher as admin?

Or in windows explorer, go to C:\Program Files (x86)\Steam\steamapps\common\Battlefield 2\mods\pr_beta\bin\PRLauncher.exe

right click PRLauncher.exe ,
select properties
select Security Tab
Top white box should say "Everyone"
Bottom white box should have "Allow" ticked for everything except special permissions.

If that is not the case, report back here.

I did run the launcher as administrator. Then I checked the .exe file and everything was checked off with all the users on the list (System, administrator, and my user) Still the same issue. Possibly something to do with Steam?

EDIT: Okay I checked both the shortcut and the actual .exe file and the shortcut contains an "INTERACTIVE" user in the top box, but the .exe file does not. I tried to add the INTERACTIVE user into the .exe file and still the same issue. I'm probably going to re-install bf2 and see if that works. But I don't want it to come to that if it doesn't have to.

[LITOralis.nMd]

Congrats, you are first person to experience this bug.
We'll name it after you.

Instead of using a desktop shortcut, can you go to the directory C:\Program Files (x86)\Steam\steamapps\common\Battlefield 2\mods\pr_beta\bin\ and manually right click PRLauncher.exe and select Run As Admin?

[The Infidel]

Congrats, you are first person to experience this bug.
We'll name it after you.

Instead of using a desktop shortcut, can you go to the directory C:\Program Files (x86)\Steam\steamapps\common\Battlefield 2\mods\pr_beta\bin\ and manually right click PRLauncher.exe and select Run As Admin?

Lol, I'm flattered. But I tried doing so, and it still did not work. This issue is very interesting...

[LITOralis.nMd]

Could be a Steam issue.

Create a little 2x2 matrix

XXXXXXXXXXXXX Steam started as admin | Steam started not as Admin
-----------------------------------------------------------------------------------------------
PRlauncher as admin | |
-----------------------------------------------------------------------------------------------
PRLauncher not as admin | |


Try all 4, ....

[hyraclyon]

I had this exact same issue! I solved it by changing the permissions of every user I could find to "everyone" on the PR_beta folder, like Litoralis already said. Note I also use the steam version of BF2.

[The Infidel]

I had this exact same issue! I solved it by changing the permissions of every user I could find to "everyone" on the PR_beta folder, like Litoralis already said. Note I also use the steam version of BF2.

Hmm... No luck. Possibly I'm doing something wrong? Can you tell me step by step how to do this?

I got somewhere by deleting the ProjectRealityUpdate folder under: C:\Users\Dover\AppData\Local\Temp\
I got all the way up to the 1.0.20 update, installing all of it's contents. Only to be struck short by the infamous Error 76, and I just ended up getting another error after restarting the application. "Error 57: Update failed. Unable to copy update executable to temporary directory. C:\Users\Dover\AppData\Local\Temp\ProjectRealityUpdate

I also tried to do a whole check list with Steam as administrator. It did not work as well.

Thank you guys for your help and patience, I really appreciate it. I'm sorry for any ignorance on my part.

[The Infidel]

Okay, I found out my issue, and I'm pretty sure it was my mounting software that was the problem (Daemen Tools) or it could of been the torrent file that had a corruption or something. So I re-downloaded the ISO file and mounted it onto Virtual Clone Drive and now it works! Thanks for the help guys, I appreciate it.

EDIT: It seems that it was my anti-virus software (COMODO) was isolating the directory to the PRlauncher. I didn't realize this until it asked me if I wanted to isolate it again. I'm sure you can easily fix this by going into COMODO and un-isolating the PRlauncher with out deleting it completely, lol.

[LITOralis.nMd]

Could you please let us know exactly which Comodo product(s) you have installed.
And if you know, which Comodo product isolated PRLauncher.exe .

We would like to get this corrected before 1.0 launches , quite a few people use Comodo products.

[The Infidel]

Could you please let us know exactly which Comodo product(s) you have installed.
And if you know, which Comodo product isolated PRLauncher.exe .

We would like to get this corrected before 1.0 launches , quite a few people use Comodo products.

Sorry for the very late reply. I use COMODO Internet Security Premium. Accompanying with it is COMODO Anti-Virus and COMODO Firewall.

What was isolating the PRLauncher.exe was the COMODO Firewall. I hope you guys fix this issue. Good luck and you guys did great with the 1.0 Beta

[Serenissima]

Sorry to bump the thread - this is the only one I've found that mentions the same error number, so I thought it was more relevant than making a new one.

I am now getting the same Error 57 that the prior user started getting whenever I try to install - it seems that the problem comes when the installer tries to copy files to a temporary directory. I do have admin, but it may just be a Windows issue; as when investigating the folder, it says I require permission from myself to make changes.

[Psyrus]

Antivirus problem again?

[Serenissima]

Antivirus isn't picking anything up, and I tried with it disabled: it seems to be a problem concerning how Windows 7 handles the temporary files with this particular installer. I'm always able to apply one update - and then after that, the launcher/updater attempts to overwrite the same files again with the next update, rather than properly removing them in the Temp/ProjectRealityUpdate folder. Win7 doesn't like this 'overwrite' part. Not sure whether it's Win7 or the installer, but it also likes automatically setting them to read-only.

[Psyrus]

It's an issue with your setup in some way... not sure what, but there are a lot of people using windows 7 and updating just fine, myself included

We just need to figure out what in your configuration is causing the block. Could you detail anything about your computer/windows install/setup that may be considered 'abnormal'?

[Serenissima]

Not that I'm aware, no. Haven't had the issue before with anything else, which is what's confusing me - for some reason, it's just decided that the ProjectRealityUpdate folder requires permission from whichever user (including the hidden root admin account) is actually trying to delete it at the time. Wasn't blaming the launcher, just the way that my particular setup - however it is - seems to be handling it.

EDIT: I've found a very time-consuming workaround that has allowed me to update to 1.1.0.0: restart the machine in Safe Mode, delete the ProjectRealityUpdate folder from Safe Mode, restart again in normal mode, install one increment of the patch, and then repeat the process for each increment until fully patched. Has taken an annoyingly long time, but hopefully anyone else suffering the same issue with Error 57 might find this works for them.

[Psyrus]

May I ask what antivirus program you use? I know you said you disabled it, but I'm still curious.

[Serenissima]

Bitdefender - which didn't show up any events even before it was disabled, and didn't actually stay disabled for my eventual workaround to succeed.

[MaSSive]

Same issue just now.



I'm still holding the dialogue up, and browsing support forums in order to find a possible solution. Antivirus software doesn't do anything - its Avast Free AV. Ill try to disable it and check permissions on folders but I never had any issues until now. Win7 X64 Ultimate. Game is retail DVD so no steam part, and its on a separate partition made for games, not in C:\Program Files ( x86 )\ or alike. Running as admin all apps related to BF2.

Edit:

Ok so I managed to fix it myself.

- checked AV software quarantine and FS shields, nothing reported, so I added game folder and updater files folder to exclusion list, so it doesnt scan it, or access it, while updating.

- rechecked if all PR related apps are set to run as admin - check, all done

- closed dialogue, and attempted to launch PRLauncher again, it failed

- located prpatch files and ran file prbf2_patch_1.0.0.36_to_1.1.0.0.prpatch ( I think its called something like that ) as admin

- it flashed several times , and restarted process, or was running different patches one after another







After the last dialogue PRLauncher started on its own. I guess it was a small fil access R/W issue, or timeout, and root cause might be either file system shield from AV or prpatch not executing as admin ( no matter UAC is off, if there is a way to build this in it, you should do so, or make users manually start update process but STRONGLY advising them to run as admin )

Solved I guess. That was quick, Im still good, damn

[LITOralis.nMd]

Hiya Massive, hope you've been doing well,

Dev Ancientman hates UAC screens, I'll mention to him the UAC issue. It might actually be because UAC is turned completely off with a registry hack. AncientMan might not have programmed the patches for when

Policies\System\Enable LUA = 0

Just a guess.