Manual Updating: Error 1212, Error 76 and Error 1301 Solution

[LITOralis.nMd]

Error 1212 occurs when the downloaded update is corrupt, usually due to a poor internet connection or some sort of internet error while trying to download. This can be solved by downloading the updates manually, as described below.

Error 76 occurs when the update failed to apply properly. First, please try to re-run the launcher. The launcher will detect a failed update, and launch the updater to attempt to fix the issue. If after several attempts the updater still fails with Error 76 (please try this several times, not just once, especially if the file it failed on is different each time), then continue with a manual update as described below.

Error 1301 occurs when you cannot reach our servers. Try adding a new DNS entry to your network device:
- Go to Network and Sharing center
- Change Adapter settings
- Press your right mouse button on local area Connection ( your network )
- Go to properties
- Press on Internet Protocol Version 4 (TCP/IPv4 )
- Go to properties
- change from '' Obtain DNS server address automatically''
- to '' Use the following DNS server addresses ''
- and enter there 8.8.4.4

Manual Updating

Step 1. If you have Error 1212, you do not need to reinstall PR:BF2, continue to Step 2. However, if you have Error 76, you DO need to reinstall PR:BF2, using the original downloaded .iso file. This is because the update is failed mid way, and you have corrupt files. The only solution is to start again.

Step 2. Now, open the launcher. If you cannot do that because it's in an auto-update loop, delete "update.lock" file from Project Reality BF2/mods/pr. Click on SUPPORT, and take note of the PR version number in the top right. For example, "PRBF2 v1.6.3.0". Depending on what version you have, this is what updates you need to start manually downloading.

Step 3. Close the Support window, and open OPTIONS -> Global. Check "Keep Update Files". This will save you needing to re-download updates if they downloaded successfully, at the cost of hard drive space. Additionally, take note of the "Update Download Location", as this is where you will be downloading updates to. This location can be changed, so if you need to change it, then be sure to press "Apply" to save the new download location.

Step 4. OK, so now you can download the updates manually. Updates are consecutive, so if you are on v1.6.3.0, then you need to install v1.6.3.0 to v1.6.3.1, then v1.6.3.1 to v1.6.3.2, then v1.6.3.2 to v1.6.3.3, etc. all the way until the latest available version. If you are on say v1.6.4.0, then you start at v1.6.4.0 to v1.6.4.1. Makes sense?
Sometimes we generate patches that cover a few versions so that you do not have to download every single patch from, let's say, 1.6.3.0 to 1.6.4.0 but instead you can download just one patch that has all patches from 1.6.3.0 to 1.6.4.0 included. Keep in mind you can not use 1.6.3.0 to 1.6.4.0 patch if your version is already higher than 1.6.3.0.

These files need to be downloaded to your "Update Download Location", which you took note of before in Step 3.

Spoiler for Older updates:

1.5.5.3 to 1.6.0.0

1.6.0.0 to 1.6.0.1
1.6.0.1 to 1.6.0.2
1.6.0.2 to 1.6.0.3
1.6.0.3 to 1.6.1.0
1.6.1.0 to 1.6.1.1
1.6.1.1 to 1.6.1.2
1.6.1.2 to 1.6.1.3
1.6.1.3 to 1.6.2.0
1.6.2.0 to 1.6.2.1
1.6.2.1 to 1.6.2.2
1.6.2.2 to 1.6.2.3
1.6.2.3 to 1.6.3.0

1.6.3.0 to 1.6.4.0

• 1.6.3.0 to 1.6.3.1
• 1.6.3.1 to 1.6.3.2
• 1.6.3.2 to 1.6.3.3
• 1.6.3.3 to 1.6.3.4
• 1.6.3.4 to 1.6.4.0

1.6.4.0 to 1.6.5.0

• 1.6.4.0 to 1.6.4.1
• 1.6.4.1 to 1.6.4.2
• 1.6.4.2 to 1.6.4.3
• 1.6.4.3 to 1.6.4.4
• 1.6.4.4 to 1.6.5.0

1.6.5.0 to 1.6.5.1
1.6.5.1 to 1.6.5.2
1.6.5.2 to 1.6.6.0
1.6.6.0 to 1.6.6.1
1.6.6.1 to 1.6.7.0
1.6.7.0 to 1.6.7.1
1.6.7.1 to 1.6.8.0
1.6.8.0 to 1.6.8.1
1.6.8.1 to 1.6.8.2
1.6.8.2 to 1.7.0.0

1.7.0.0 to 1.7.2.0

• 1.7.0.0 to 1.7.0.1
• 1.7.0.1 to 1.7.0.2
• 1.7.0.2 to 1.7.1.0
• 1.7.1.0 to 1.7.1.1
• 1.7.1.1 to 1.7.2.0

1.7.2.0 to 1.7.2.1
1.7.2.1 to 1.7.2.2
1.7.2.2 to 1.7.2.3
1.7.2.3 to 1.7.2.4
1.7.2.4 to 1.7.3.0
1.7.3.0 to 1.7.3.1
1.7.3.1 to 1.7.3.2
1.7.3.2 to 1.7.4.0
1.7.4.0 to 1.7.4.1
1.7.4.1 to 1.7.4.2
1.7.4.2 to 1.7.4.3
1.7.4.3 to 1.7.4.4
1.7.4.4 to 1.7.4.5

1.7.4.5 to 1.8.0.0

----------------------- Version of the newest installer: 1.8.0.0 -----------------------------------------------------------

1.8.0.0 to 1.8.0.1
1.8.0.1 to 1.8.0.2
1.8.0.2 to 1.8.0.3
1.8.0.3 to 1.8.0.4


Step 5. Once all the files have been downloaded successfully, open the launcher, right click PLAY, and select "Check for Updates". It should detect a new update is available, and then continue with the update process as normal. The download process should be skipped as you have manually downloaded the updates, and it should update successfully.

[Ristty]

Add prbf2_1.4.6.0_to_1.4.7.0_client_patch.prpatch pls

[Psyko]

on windows 10, how do i see these error reports?

[Ristin]

Hey Devs trying to do the manual update but every link from 1.4.9.0 to 1.4.10.0 on wards does not work, any chance the links can be fixed?

[[R-DEV]​AlonTavor]

Originally Posted by Ristin

Hey Devs trying to do the manual update but every link from 1.4.9.0 to 1.4.10.0 on wards does not work, any chance the links can be fixed?

I think someone got the links wrong, look at the link name. change it 9->10 and 10->11 etc...

[Un4Given]

Need for 1.4.18.0 to 1.4.19.0 Patch. It's doesn't make it automatically. Thx.

Nevermind, i found it)
http://files.ancientdev.com/updates/..._patch.prpatch

[Laconique]

Can someone please update the link for 1.4.2.0 patch manual install ?

Thanks.

[[R-DEV]Suchar]

Originally Posted by Laconique

Can someone please update the link for 1.4.2.0 patch manual install ?

Thanks.

You mean 1.4.19.0 to 1.4.20.0?
Here it is.

[Laconique]

Originally Posted by SucharMistrz

You mean 1.4.19.0 to 1.4.20.0?
Here it is.

Thanks !

Link was down for a reason.

[Pvt. Willie]

Can I please get a direct download for 1.5.3. It keeps saying file if corrupted.