Original Post — Direct link

It appears to me that multiple people starting to have this error code.
I tried to fix it for 2 days now.
What I tried:

  • Port Forwarding both router and Windows
  • Reinstall Siege, Extraction and Ubisoft Connect
  • Cleared host file
  • Cleared DNS cache
  • Checked Windows 11 and even reinstalled it
  • Playing it on my laptop WHICH WORKS FINE

What "helped":
I deleted every file I could find from Siege, Extraction and Ubisoft Connect in C:Programms(x86), AppData and Regedit.
This worked for the day I did it. Today after a normal windows shutdown and start up the problem appears to be there again.
I start to think more and more that it is not a problem on the client side but more on the server side.
What can I do now because i am running out of options.

Regards Silas

about 3 years ago - ubi-smash - Direct link

@jukes_ Hello! Sorry to hear that you have been experiencing this error. If you have already tried all steps shared on our page here, I would check to see if you have any VPN or Anti-virus software that might be causing this issue. I recommend disabling the software only to test if you continue to run into the same results. If you have already exhausted everything shared here, please create a support ticket with a screenshot of your port configurations and MSINFO & DxDIAG attached so we can take a closer look into this with you.

about 3 years ago - Ubi-Milky - Direct link

Hello @jukes_ thank you for getting back to us.

The error code 4-0xFFF0BE2B is known to us and has been under investigation for a possible cause. Thank you for submitting your system files for investigation, I can see that they have been passed onto the Extraction team.

Can you confirm if you have also recently experienced this in Siege, every time you have tried to connect to the game?

If so, I would recommend commenting on your case again, to explain how this is also affecting your installation of Siege, in every game, if that is what is affecting you now.

about 3 years ago - Ubi-Nacho - Direct link

@jukes_ Thanks for confirming this information for us, it's much appreciated.

We'll be forwarding all of this information to our game team to aid in their investigation. Would you also be able to tell is who your internet service provider is please?

Thank you.

almost 3 years ago - Ubi-Milky - Direct link

Thanks for the reply Jukes and thanks for sharing this. Whilst I am happy to hear that this workaround worked for you, we can not recommend players alter their Teredo State and IPv6 settings this way, we recommend making a support ticket with us so we can advise Ubisoft approved technical troubleshooting for optimal security, as altering this can not only affect Siege but other games and software too.

over 2 years ago - Ubi-Karl - Direct link

Hey @MyMomsMyDad_, thanks for reaching out, welcome to forums and sorry to hear you have ran into this error code as well.

As far as suspension itself goes, it is something that is issued by the server-side, therefore I am afraid our Support team would not be able to adjust this for you.

In regards to troubleshooting, as you were unable to reconnect afterwards, did you try completing steps suggested by @ubi-smash at all?

over 2 years ago - Ubi-Karl - Direct link

Hey guys! @BleezeyCatz_ @Jadrankaa

Thanks for getting through to us, welcome to forums and sorry to hear about the connectivity and crash related issues you've been dealing with, as I fully appreciate the experience can be rather frustrating.

First and foremost, as far as crash issue goes, for troubleshooting purposes, make sure to complete all of the steps outlined in the following article (I can see that you've done a few already) and see if issue persists. If it does, can you advise us the following:

  1. Since when did you start experiencing crash issues?
  2. I take it that no error message is displayed after crash, is that right?
  3. Do you play using DX or Vulkan API?
  4. Did you notice if crash only occurs in any particular game modes/maps?
  5. How often do you experience it?


In regards to error 4-0xFFF0BE2B, if you haven't already, try completing steps outlined here. Should issue persist however, do mind that we have received a number of player contacts about this and it is already under further review by our development team, therefore in order to aid further investigation, can I ask you to advise us the following:

  • Do you receive any other codes besides 4-0xFFF0BE2B?
  • What is the last exact date / time you were blocked by this code?
  • What region do you live in?
  • Who is your current ISP?
  • Are you playing via Wi-Fi or Ethernet?
  • Does this error appear 100% of the time or sometimes?


Keep us updated and if you have any further queries, let us know!

over 2 years ago - Ubi-SpaceCats - Direct link

@jukes_ Hey there, thank you so much for sharing what worked for you! 😊






Recent Rainbow Six Siege Posts

about 11 hours ago - Ubi_Zurik
18 days ago - Ubi-WheelyDuck