
Unable to find root BF2 directory. Please Reinstall.
-
spudaman
- Posts: 3
- Joined: 2015-08-05 15:52
Unable to find root BF2 directory. Please Reinstall.
Hi, This is my first post so forgive me if I make any mistakes or such. Anyway, I've been playing PR:BF2 for a while, but recently when I open the launcher it comes up with the message, "8: Unable to find root BF2 Directory. Please reinstall Project Reality: BF2". So I did just that I reinstall PR and it installs fine and plays fine. But as soon as I close it and then open it again next time I want to play PR it just says the same error message. Now if I repeat the process of uninstalling PR and then reinstalling it the same happens, plays fine until I close it and then open it and the cycle just repeats. I recently upgraded to Windows 10. So I feel that this may be a possible reason, as PR ran fine before the upgrade when I played on Windows 7. I have attached a picture of the error message just in case (I had to crop the image on paint which is why it has a weird resolution of 1915x1081 but i am natively on 1920x1080) Any help would be greatly appreciated. As having to uninstall and then reinstall PR every time I want to play is a real pain in the ***. I'm happy to provide any additional information that I can. Thanks.


-
spudaman
- Posts: 3
- Joined: 2015-08-05 15:52
Re: Unable to find root BF2 directory. Please Reinstall.
Fixed this issue.
-
ZipZopBoop
- Posts: 1
- Joined: 2015-08-15 18:02
Re: Unable to find root BF2 directory. Please Reinstall.
I'm having the same issue. How did you resolve this?spudaman wrote:Fixed this issue.
-
spudaman
- Posts: 3
- Joined: 2015-08-05 15:52
Re: Unable to find root BF2 directory. Please Reinstall.
Hi, I fixed the issue by creating a new shortcut for the PRlauncher. I don't know why this worked but it did for me. Locate your PRLauncher.exe. For me this file was in D:\Games\Project Reality\mods\pr\bin\PRLauncher.exe but it may be in the PR folder in your Documents folder. I hope this works for you.ZipZopBoop wrote:I'm having the same issue. How did you resolve this?
