Unable to connect profile

[Epinephrine-10mg]

Hey guys,

I launch game and I select my profile to start game but it's taking forever to launch in game, it sits on " Connecting to profile " .

I tried checking updates, and it's the latest version currently I have, and tried deleting profile folders under " ..\Documents\ProjectReality " and both trick doesn't work

Operating System: Microsoft Windows 10 Enterprise x64 (10.0.18363)

Almost a year and Yesterdat it was running flawlessly, but today first time it just having issues. Any suggestions or it's just about master server ?

EDIT: After deleting profile folders, unable to retrieve account or create new account. Both doesn't work

EDIT 2 : I just found out that I'm able to retrieve account only by e-mail, but not able to retrieve by the username. and when I click Login, it still taking forever "Connectig to profile" pop-up window.

[Epinephrine-10mg]

Today I formatted whole system drive and installed fresh new Windows and drivers and I installed PR from prbf2_1.5.0.0_full.iso and updated to v.1.5.5.3. and stuck on that screen again

[AlonTavor]

Do you get "Invalid HTTP response" when going to http://ms.prm.so:29900/ ?

[Epinephrine-10mg]

Do you get "Invalid HTTP response" when going to http://ms.prm.so:29900/ ?

When I click it on Chrome this message appears; ERR_INVALID_HTTP_RESPONSE

[AlonTavor]

So nothing is blocking you, I'm not sure why this happens...

[Epinephrine-10mg]

So nothing is blocking you, I'm not sure why this happens...

I tried with mobile 4.5G modem to connect but still same then I uninstalled PR and deleted all registries and downloaded ISO image again, installed PR and now I'm updating manually. I hope this works

[Epinephrine-10mg]

So nothing is blocking you, I'm not sure why this happens...

Manual update finished It's working flawlessly now. It seems like prbf2_1.5.4.3_to_1.5.4.4_client_patch was failing at auto update. There was so many update files and I might be confused about which exact update patch failing : But manual updating the PR solved the problem. Thanks to you all guys.