Archebuddy will no longer load the game client after the update

[darkstar]

Account is successfully launched.
3:36:46 PM: Authentication success! Checking for store products. This may take a while.
3:36:46 PM: Done. Receive info about 0 buddy store plugins.
3:37:48 PM: Client initialization timeout!


Then sometimes I will get a pop up saying

[1] Error while loading game_pak. Recheck the path to game_pak. Without properly loaded game_pak some functionality will not work.


The path is correct. This is some default message because Archebuddy can not load the client like it used to before the update.



OUT,

What is the fix for this? Do I have to wait for another update?



The pattern has been, sleep after using Archebuddy for 10hrs. Wake up, get another patch and have issues with the application. Wait for another patch or fix. [repeat].




---

Reviewed the following most recent posts with other having the same issue:


https://www.thebuddyforum.com/archebuddy-forum/archebuddy-support/178161-client-initialization-timeout.html

https://www.thebuddyforum.com/archebuddy-forum/archebuddy-support/223385-client-initialization-timeout.html

https://www.thebuddyforum.com/archebuddy-forum/archebuddy-support/210732-client-initialization-timeout.html


AV is always set to exclude Archebuddy folder and files.

Inject method 2 : Client initialization timeout!
Set application to Admin : Client initialization timeout!
Reinstall Archebuddy : Client initialization timeout!

Windows 8.1
.NET Framework : 4.5, 4.5.1, 4.5.2 I write programs in Visual Studio that require different versions.



I am out of ideas and exhausted trying to figure out why I am getting a Client initialization timeout! after the latest patch. How can I get on the older version without updating?

 

[tankhead]

Same problem

 

[darkstar]

Account is successfully launched.
3:36:46 PM: Authentication success! Checking for store products. This may take a while.
3:36:46 PM: Done. Receive info about 0 buddy store plugins.
3:37:48 PM: Client initialization timeout!


Then sometimes I will get a pop up saying

[1] Error while loading game_pak. Recheck the path to game_pak. Without properly loaded game_pak some functionality will not work.


The path is correct. This is some default message because Archebuddy can not load the client like it used to before the update.



OUT,

What is the fix for this? Do I have to wait for another update?



The pattern has been, sleep after using Archebuddy for 10hrs. Wake up, get another patch and have issues with the application. Wait for another patch or fix. [repeat].




---

Reviewed the following most recent posts with other having the same issue:


https://www.thebuddyforum.com/archebuddy-forum/archebuddy-support/178161-client-initialization-timeout.html

https://www.thebuddyforum.com/archebuddy-forum/archebuddy-support/223385-client-initialization-timeout.html

https://www.thebuddyforum.com/archebuddy-forum/archebuddy-support/210732-client-initialization-timeout.html


AV is always set to exclude Archebuddy folder and files.

Inject method 2 : Client initialization timeout!
Set application to Admin : Client initialization timeout!
Reinstall Archebuddy : Client initialization timeout!

Windows 8.1
.NET Framework : 4.5, 4.5.1, 4.5.2 I write programs in Visual Studio that require different versions.



I am out of ideas and exhausted trying to figure out why I am getting a Client initialization timeout! after the latest patch. How can I get on the older version without updating?

-------------------------------------------------


Also attempted on a Win7 64bit machine with the same results.

 

[darkstar]

Account is successfully launched.
3:36:46 PM: Authentication success! Checking for store products. This may take a while.
3:36:46 PM: Done. Receive info about 0 buddy store plugins.
3:37:48 PM: Client initialization timeout!


Then sometimes I will get a pop up saying

[1] Error while loading game_pak. Recheck the path to game_pak. Without properly loaded game_pak some functionality will not work.


The path is correct. This is some default message because Archebuddy can not load the client like it used to before the update.



OUT,

What is the fix for this? Do I have to wait for another update?



The pattern has been, sleep after using Archebuddy for 10hrs. Wake up, get another patch and have issues with the application. Wait for another patch or fix. [repeat].




---

Reviewed the following most recent posts with other having the same issue:


https://www.thebuddyforum.com/archebuddy-forum/archebuddy-support/178161-client-initialization-timeout.html

https://www.thebuddyforum.com/archebuddy-forum/archebuddy-support/223385-client-initialization-timeout.html

https://www.thebuddyforum.com/archebuddy-forum/archebuddy-support/210732-client-initialization-timeout.html


AV is always set to exclude Archebuddy folder and files.

Inject method 2 : Client initialization timeout!
Set application to Admin : Client initialization timeout!
Reinstall Archebuddy : Client initialization timeout!

Windows 8.1
.NET Framework : 4.5, 4.5.1, 4.5.2 I write programs in Visual Studio that require different versions.



I am out of ideas and exhausted trying to figure out why I am getting a Client initialization timeout! after the latest patch. How can I get on the older version without updating?

--------------------------------


Here is how I solved this problem. I had a Windows 10 machine and took that Archebuddy copy and placed it on to my Win7 machine. Then I setup the firewall using the new update.exe (or whatever you want to call it) I think the naming convention has something to do with machine name but I can't remember what OUT said.

It is now working.

---------------------------------

Right after I closed AB and restarted it, I was no longer able to load the client using AB.
This was tested with NO antivirus and NO firewall.

This behavior only happens on my Win 7 machine. In my opinion they can detect your injection technique and are blocking AB from loading the client.

 

[darkstar]

OUT,


So I upgrade the Win 7 machine to Win 10 and did a fresh installation of AB. It is now working as it used to.


This does not solve the question as to why after your group (or the individual) who updated the AB client caused such an issue. To have to update your OS to get the product to function again, well I don't need to explain anything there....