Jump to content


Photo

[RA3] CA Public Key Patching Routine Failed (FIX POSTED)


Best Answer thugle , 12 April 2018 - 11:31 PM

Found my own fix......

 

 

Restart your computer

Launch the game the first time through steam (only if its never been launched before)

close the game

Open the launcher

hook the game

close the launcher

go to steam

go to the game

click launch

the launcher comes up

click the game in the launcher, and boom, it works that way........... and for some reason not with the launcher

 

 

works perfectly every time now if i launch the launcher through steam...

Go to the full post


  • Please log in to reply
5 replies to this topic

#1 thugle

thugle
  • New Members
  • 2 posts

Posted 12 April 2018 - 08:56 PM

Hello, i have tried to change compativility mode to windows 7, windows xp both SP 3 & 2

 

im using the Steam version on windows 10

 

 

logs said:

 
 
----- C&C:Online Launcher Start -----
Game: Red Alert 3
Red Alert 3 Install Path: D:\Program Files (x86)\Steam\steamapps\common\Command and Conquer Red Alert 3\
Started game with: "RA3.exe "
Caught CREATE_PROCESS_DEBUG_EVENT from Red Alert 3. Detaching...
Found game.dat process. PID 12880
*** Starting CA public key patching routine ***
ERROR: Reading process memory failed. Error: Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
 
 
ERROR: Reading process memory failed. Error: Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
 
 
ERROR: CA public key differs from expected value. Not patching.
 
 
----- C&C:Online Launcher Start -----
Game: Red Alert 3
Red Alert 3 Install Path: D:\Program Files (x86)\Steam\steamapps\common\Command and Conquer Red Alert 3\
Started game with: "RA3.exe "
Caught CREATE_PROCESS_DEBUG_EVENT from Red Alert 3. Detaching...
Found game.dat process. PID 128806160
*** Starting CA public key patching routine ***
ERROR: Reading process memory failed. Error: Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
 
 
ERROR: Reading process memory failed. Error: Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
 
 
ERROR: CA public key differs from expected value. Not patching.
ERROR: CA public key patching routine failed.
ERROR: CA public key patching routine failed.
 

Edited by thugle, 13 April 2018 - 12:46 AM.


#2 thugle

thugle
  • New Members
  • 2 posts

Posted 12 April 2018 - 11:31 PM   Best Answer

Found my own fix......

 

 

Restart your computer

Launch the game the first time through steam (only if its never been launched before)

close the game

Open the launcher

hook the game

close the launcher

go to steam

go to the game

click launch

the launcher comes up

click the game in the launcher, and boom, it works that way........... and for some reason not with the launcher

 

 

works perfectly every time now if i launch the launcher through steam...


Edited by thugle, 13 April 2018 - 12:49 AM.


#3 Delier

Delier
  • New Members
  • 3 posts

Posted 15 April 2018 - 07:18 PM

What is the difference between the launcher and the game?



#4 Srg.Timpa

Srg.Timpa
  • New Members
  • 1 posts

Posted 19 April 2018 - 10:24 PM

Hi, I am using steam on Windows 10 - 64 bit aswell.

 

I have tried the exact thing you say worked for you but in the end I don't get the game to acctually start up.

 

I hook RA3

Close the C&C Online launcher

start RA3 as adminstrator

The C&C Online launcher comes up

I launch RA3 in the C&C Online launcher

Wait like 20 seconds and then the little loading screen pops up 

When thats done it disappears but the game never acctually launches.

 

Absolutley nothing happens and I can't find any log either.

 

Help?

 

(P.S. I even tried to run it in compatibillity mode but that didn't work either.)



#5 Zeta1125

Zeta1125
  • Members
  • 5 posts

Posted 19 September 2019 - 06:27 PM

Hi,

I have the same problem you do. Did you ever get this fixed?

#6 Zeta1125

Zeta1125
  • Members
  • 5 posts

Posted 19 September 2019 - 06:27 PM

Hi,

I have the same problem you do. Did you ever get this fixed?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users