You can log in to your account on your web browser to CHAT as well. It works fine. The coding is completely different for the Steam UI so it no longer connects properly using Steam 2023. This seems to be the most stable source sdk 2007 fix for now. Thank goodness it works. Happy New Year to all of you      

Edited title to clarify that this is an unofficial (community-supplied) fix.

Please note that this is not sanctioned or tested by the GE:S team. Proceed at your own risk.

GOLDENEYE SOURCE WORKING SOURCE SDK 2007 FIX

Step 1: Force Downgrade the Client
You can use a command-line argument to force Steam to download an older version of its own client files from the Internet Archive.

Completely close Steam (ensure it is not running in the system tray).

Right-click your Steam Shortcut on your desktop and select Properties.

In the Target box, add a space after the existing text and paste the following:

-forcesteamupdate -forcepackagedownload -overridepackageurl http://web.archive.org/web/20230531113527if_/media.steampowered.com/client -exitsteam

Note: This specific URL points to a May 2023 version. You can replace the date (20230531...) in the URL if you need a specific version found on the Wayback Machine.

Click Apply and launch Steam via this shortcut.

Steam will open, download the older package files, and then immediately close itself (due to the -exitsteam command).

Step 2: Block Auto-Updates
If you launch Steam now, it will immediately detect it is "out of date" and update back to the latest version. You must disable this check.

Navigate to your Steam installation folder (usually C:\Program Files (x86)\Steam).

Create a new text file and name it steam.cfg (ensure it is not steam.cfg.txt).

Open the file with Notepad and paste the following lines:

Plaintext

BootStrapperInhibitAll=Enable
BootStrapperForceSelfUpdate=False
Save and close the file.

Step 3: Cleanup and Launch
Go back to your Steam Shortcut properties.

Remove all the extra commands you added in Step 1 so the target ends with steam.exe".

(Optional) If you want to use the classic UI, you can add -vgui to the end of the target.

Launch Steam.


NOTE:  Your FRIENDS list may not be accessible due to this older version of the client however it does fix GESOURCE   Just use a web browser if you have to use chat to talk to friends   MultiplayerX

This is a known issue affecting all Source 2007 mods since the Dec 19 Steam update.

The only current known fix is to roll back the Steam client, but we're not releasing those instructions publicly as we don't want to encourage people to run outdated clients.

Edit: Note, however, you can still play with bots by creating a new server and ticking the "Run on LAN" checkbox. This also works for LAN parties, you can set `sv_lan 1` on your server and local clients should be able to connect.

Thanks for looking into this and keeping everyone updated.
A lot of us are affected by this change, so we really appreciate you taking the time to investigate a proper fix.
Looking forward to any news.

Im trying to find a FIX for this. I will keep everyone posted once I do. It's really ticking me off too!  MultiplayerX

My game was running but hadn't yet updated... after the latest Steam update I'm now getting the same error as the users above.

We are seeing the same thing I was hoping that someone would come up with a workaround as it has stopped working since this weeks steam update!

Hello everyone,

I'm experiencing a persistent issue with Steam and some Source-based games (including GES). Every time I try to log in, I get the error message:

"Account Used Elsewhere"

I've tried multiple solutions:
- Logging out of all devices and forcing logout remotely
- Changing my Steam password
- Enabling Steam Guard
- Restarting my PC and router
- Verifying game files
- Trying with a different Steam account

Even after all these steps, the problem persists. It happens both with my main account and with a secondary test account.

Has anyone else experienced this recently? Is there a workaround for Source SDK Base 2007 or related mods that prevents this error? Any advice or tips would be greatly appreciated!

Thank you in advance.

Was done in error.
We are currently doing a large review of internal systems, it will be corrected or a new path will be implemented.