Account restricted

Just bought a new PC finally and cannot get into Battlefield servers because of "account restriction" appears that since I came from Xbox and now am on pc they told me there are merging issues that is currently under investigation. Any advice?

Hello,  

I tried to play BF6 redsec on my pc.  After install i was presented with Account Restricted.  I dont know why.

Error code 1:86001S:51009S:-17636452900:4128769Q

I had to change my HDD partition from MBR to GPT in order to force secure boot and install the game. Thats the only thing I changed recently. I dont think that would trigger anything because it was required for install.

I dont cheat, never have, dont know how to.

I emailed EA a week ago without any response.

Any help would be greatly appreciated.

Thank you 

Can you stop marking all the restricted account posts as solved? you obviously don’t know what you’re talking about when support themselves are saying that this is not a ban & it’s an issue they are aware of. Do a better job man, geez 

This is getting ridiculous! I've contacted EA Support/Help several times, and first of all, it takes them 20 minutes for them to understand what the problem is, and then they don't do anything about it? It's been online here for 8 days ( https://forums.ea.com/ blog/battlefield-game-info-hub-en/info-battlefield-6-redsec-known-issues-1-1-1-0/12845152 ) on their own website... NOTHING IS BEING DONE ABOUT IT!

EA_Aljo​ Yes, This is getting ridiculous! I've contacted EA Support/Help several times, and first of all, it takes them 20 minutes to understand what the problem is, and then they don't do anything about it? It's been online here for 8 days (https://forums.ea.com/ blog/battlefield-game-info-hub-en/info-battlefield-6-redsec-known-issues-1-1-1-0/12845152) NOTHING IS BEING DONE ABOUT IT!

Posting to see a fix for this. Bought on Xbox series X with Phantom edition upgrade and now launching on aptop which was also used to play the beta

EA error 1:86001S:51009S:-1763645290O:4128769Q

So, I own the game on Steam, have my accounts fully linked and working. The game runs on Steam just fine. But I do also have the EA discount through GamePass, so I bought the season pass through the EA app. 

It hasn't credited to my account. It's been over a week of back-and-forth with support not even reading my tickets.

I had the idea to try and log into the game through the RedSec download on the EA app. But when I do, I get the "this account is restricted from online play" pop-up. But the account still works on Steam and I have no record of any bans/suspensions/etc on my account page... 🤔

EA support seems to keep dodging actually reading my tickets. Has anyone else been able to get the game to launch the same EA account via two different platforms?

i keep having a restricted account and this has happened twice now and after a day of playing with no issues the next day i will have the same thing happen again and it seems like there is nothing that works to fix this.

did you refund the game? I purchased on EA the day before release and the game was unplayable during the first few days, I saw someone from DICE suggest getting a refund from EA  for the EA app version and purchase the game on steam. I thought I'd try and play Redsec on the EA app so I downloaded it again as on steam redsec is almost unplayable and I barely finish a whole game. I started the game on the EA App and it said my account was restricted when it tried to connect to multiplayer, I knew it can't be so and must have been because I refunded the game on EA. I switched back to Steam and I can play no problem but my game always crashes anyway.

EA must not separate properly the MP and BR status's, so if you refunded the game and try and download to play BR it still doesn't allow you to connect possibly because of your history refunding so it's stopping access to MP "services". IMHO they need to better separate the MP entitlements and BR which should be open in our data files like your data you can download from EA.

EDIT: I fixed the above crashing issue I had with crashing by disabling hyperthreading, I know it's the last thing you want to do but the it's due to security patches in the Motherboard BIOS. I'm going to try the very first BIOS that added these security updates as since then it's capsuled and you can't go any further back then that point. It might explain why I didn't have the issue I'm the beta as I was running a different BIOS.

"The hypervisor did not enable mitigations for side channel vulnerabilities for virtual machines because HyperThreading is enabled. To enable mitigations for virtual machines, disable HyperThreading"

You got any solution for it ?