[2022] 'Update required' and then error 0-0x00000001 after updating to the latest version

Hey everyone!

Our teams are still investigating this issue - I've passed all the new information to them.

Please continue monitoring this thread and our social media for more information, as soon as we know more, we'll post updates there, thanks!

Hi everyone! The issue resulting in error 0-0x00000001 might be connected to a recent update to anti-cheat software.

In order to try and fix this issue, please try to do the following:

• Find r6siege folder in localappdata (the default path is: %localappdata%\ubisoft\r6siege\ and you an access it by pressing Win+R on the keyboard to open the 'Run' dialog and paste the path there).
• Right-click the r6siege folder and select Properties.
• Go to Advanced Attributes and make sure that Encrypt contents to secure data at the bottom is turned off.

This should change those settings for any subfolders as well, but you can also check them to ensure this. Encryption of the contents might interfere with how the game works, so it's important that this box is unticked for all of them.

If the r6siege folder doesn't exist in the path mentioned above, please try to create it manually and launch the game again.

Let us know if that fixes the issue for you, thanks!

@Seb-26 @patouf35 @OMUOTOKO-River @Meshui @Lucette_ @Kierokezoazul @Jovi2000 @Gu1zz1 @Firewall

Hi everyone, thank you for your patience with this error! For anyone seeing this following a more recent update could you please ensure the following:

• Your C Drive has at least 50MB of free space. While you do not have to install the game itself to C, please make sure there is sufficient space left on the drive
• If any files have been manually encrypted in the following space please un-encrypt the files: Users\username\AppData\Local\
  • For Windows users you can reverse a file encryption by right clicking the file, selecting Properties then Advanced options from the General tab. Uncheck the 'Encrypt' box.

Please let me know if the workaround does not resolve this error and I will make sure the teams are aware.