Return of Reckoning

Posted: **Fri Oct 06, 2023 9:41 am**

UPDATE :

New .reg file to add missing registry keys, the older had a missing "/" on some path. Link below

EDIT : Solved ! (Normaly)

Thanks to Tualens, we've found a solution (not sure if its work for everyone)

Certain version of windows force the use of a wrong TLS (a service that work in pair with .NET).

Solution is to add new key in your regedit that force your windows to use another version of TLS.

Two method possible to do that :

1. Hard way, opening regedit and adding each new key manualy

adding the following registry keys:

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001

2. Easy way, thanks to Nellkee and Tualens, we have a .reg file that automaticaly add these keys to your regedit.

https://we.tl/t-eMeSRtiPDQ <- Here is the link to the .reg file.

Download it, launch it, it will ad needed key, then launch the RoRLauncher and it will be fine, normaly.

____________________________________

Hey all,

Some new/returning players of my guild encounter a weird issue with the launcher (Can't access web and login server). Log return :

[23/09/23 18:01:10] I Web : Trying to Download XML
[23/09/23 18:01:10] E Web : Failed to Download XML
[23/09/23 18:01:10] E Web : XML Download Error...retrying in 10
[23/09/23 18:01:20] I Web : Trying to Download XML
[23/09/23 18:01:20] E Web : Failed to Download XML
[23/09/23 18:01:20] E Web : XML Download Error...retrying in 10

About specs :

- One is on windows 10, the other on windows 11, so not an OS related issue
- One is based in France and the other in Belgium, with different kind of connection and internet provider
- One use a 5G box provider and the other a classic box provier
- No special character or whatsover in the path name / OS Session Name / etc

What we had tested so far :

- Installing / reinstalling NET and Direct X
- Putting DirectX DLL directly in WAR folder
- Test to launch the game through a VPN with differents localizations
- Trying to reach the XML file through the web browser : Worked.
- Trying to download the latest RoR Updater and launcher exe and replace existent in the WAR folder
- Trying both installation methods (RoRInstaller and Direct Download)
- Trying to set static IP and DNS
- Trying to launch the game through a shared connection by the phone
- Done a tracert to 147.135.130.126, some test had timed out, but not related to the issue I suppose, I've done this tracert on my machine and same timed out (but my launcher work).

Currently one of those guy is installing a VM to test through that if its work or not.

Any help or suggestion will be really appreciated ! Thanks

Posted: **Fri Oct 06, 2023 12:29 pm**

After testing, RoR works on the virtual machine with Windows 11. So it's not network related.
Certainly a specific software or process that blocked something. Or maybe .NET related issue.

We'll continue to investigate

Posted: **Fri Oct 06, 2023 1:59 pm**

After many investigations, the issue is coming from recent windows update (22H2 probably, the four players that have the XML error have this windows version), update that brings minor updates and modifications to .NET Framework. This is as predicted a .NET related issue.

Trying to solve the issue right now. We'll update this thread if we find a solution.

Posted: **Fri Oct 06, 2023 2:07 pm**

Error from RoRUpdater from one player with the XML issue :

Code: Select all

Error Downloading updater:
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.ComponentModel.Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm
   at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc)
   at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential)
   at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, X509Certificate2 selectedCert, Flags flags)
   at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint)
   at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output)
   at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest, Boolean renegotiation)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest, Boolean renegotiation)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Net.TlsStream.CallProcessAuthentication(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback asyncCallback, Object asyncState)
   at System.Net.TlsStream.UnsafeBeginWrite(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback asyncCallback, Object asyncState)
   at System.Net.PooledStream.UnsafeBeginWrite(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)
   at System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result)

Posted: **Fri Oct 06, 2023 3:50 pm**

I have the exact same error. Did you find something?

Posted: **Fri Oct 06, 2023 4:05 pm**

We are working on it. No real solution was found at the moment.

You can try to install .NET Framework 4.0 and tell me if it works for you.

Anyway, can you list your .NET Framework installed on your computer ? You can find the list at C:\Windows\Microsoft.NET\Framework\

Posted: **Fri Oct 06, 2023 4:17 pm**

1031
v1.0.3705
v1.1.4322
v2.0.50727
v3.0
v3.5
v4.0.30319

I try now the windows Update 2023-09 Windows 10 Version 22H2 for x64 (KB5030300)

Posted: **Fri Oct 06, 2023 4:25 pm**

it didn`t fixed the problem. I have installed the Update .NET KB5031041

Posted: **Fri Oct 06, 2023 4:31 pm**

I think I finally found the solution:

I had the same issue and solved it (finally after a whole day of trying) by adding the following registry keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001

Try it with caution as, like usual, editing the register is always a risk.
The issue looks like my Windows defaulted to use the TLS 1.0 instead of the TLS1.2 and adding those registry keys kind of force the use of TLS1.2.

I am currently updating the game through the Launcher !!

Posted: **Fri Oct 06, 2023 4:46 pm**

I think, that was the solution. I am now online and connected to my account

Return of Reckoning

[LAUNCHER] Failed to download XML

[LAUNCHER] Failed to download XML

Re: [LAUNCHER] Failed to download XML

Re: [LAUNCHER] Failed to download XML

Re: [LAUNCHER] Failed to download XML

Re: [LAUNCHER] Failed to download XML

Re: [LAUNCHER] Failed to download XML

Re: [LAUNCHER] Failed to download XML

Re: [LAUNCHER] Failed to download XML

Re: [LAUNCHER] Failed to download XML

Re: [LAUNCHER] Failed to download XML