Can't even launch the game

@EA_BlueberryYes.

EDIT:

I uninstall the game and re-install it again. Still update button is available even after fresh re-install.

Try to join a game with no luck.

This is how its look like: https://vimeo.com/703146099

I cancel crossplay and join a game - it work but I cannot tell if its the problem as I able to join a match once in a while even if crossplay is on.

For example, I enable crossplay again and it work also, and I didn't try again since.

@Conv3Rs 

Can you update this thread you are sill experiencing this?

There are some various workaround fixes players have been able to find found in this thread if you want to give them a go. The team is aware of this happening to players. :\

https://answers.ea.com/t5/Technical-Issues/Stuck-on-standby-screen/m-p/10998112/highlight/true#M13241

@EA_BlueberryI think I might be on to something.
Can you approve those are the ports BF2042 use?

TCP:

5222, 9988, 1705, 20000-20100, 22990, 42127

UDP:

3659, 14000-14016, 22990-23006, 25200-25300

Me and my friend also got NAT type strict on For honor, and tomorrow I'll call my ISP to forward some ports.

That's because I cannot manually do it myself as it pre-block from ISP side.

When I read about For honor issues I've encounter at solutions that are exactly the same as suggested in that thread you post. 
What I think is that if for example BF2042 got "NAT status" indicator, that matchmaking loop issue probably happened only/more to "strict" status players.

@Conv3Rs 

We do not have our official ports publicly listed, however your ISP can walk you through steps on how to adjust your router settings so you do not have STRICT NAT. If you login to your router's administrator settings (instructions are on the router), you can check to see if you have uPnP enabled or disabled. You'll want that enabled for gaming. 

@EA_BlueberryI happy to announce that after months of matchmaking loop issue I able to finally solve this problem as I mention in my last comment here.
"Double NAT" was active from my ISP side, which means that I got external IP address and another virtual IP which I can only see at the router's administrator settings.
It means that if you forward ports it just wouldn't work because the ports never forwarded to the right IP and basically block from ISP side.
When that "double NAT" disabled I got brand new IP that I set to static, and then forward the ports that I mention to that specific static IP.
It maybe work even without forward the ports, just by disable that "double NAT" thing. In my case I took no prisoners and forward those ports.

All BF2042 mods I've tested right now work without issues, first time from game release at November.
And I must tell that I solve that NAT type at For honor to open, finally after 3 years of strict status.
Those issues connected and solved together, so I hope it will be useful information.

Cheers

@Conv3Rs 

That's amazing to hear! Thank you for also posting this in the other thread to make sure others are aware of a fix that could work for others. 🙂 

how do I check nat type in game pc ea app?