Persistent "yam" Error on Login After Windows 11 Update
Hello Bungie Support,
I play on steam and I am unable to log into Marathon due to a persistent "yam" error. This issue began today immediately after installing the latest Windows 11 update. Nothing else has changed on my system, and everything else works perfectly. I have already performed extensive troubleshooting across my network, security settings, and game files, but the connection is still being blocked.
Here is a complete list of the troubleshooting steps I have already completed:
Network Steps:
-
Reset router and modem.
-
Reset Windows network settings and flushed my DNS.
-
Forwarded ports and enabled UPnP (my NAT type is currently Open).
-
Set DNS servers to Google (8.8.8.8 and 8.8.4.4).
Security & System Steps:
-
Completely disabled Windows Defender.
-
Confirmed no third-party anti-virus software is installed.
-
Manually added the Marathon
.exeto Windows Defender exceptions. -
Ran the game as an administrator.
Game & File Steps:
-
Verified the integrity of game files.
-
Fully uninstalled and reinstalled the game.
-
Manually flushed and reinstalled BattlEye.
Please let me know what the next steps are to resolve this becouse this is frankly ridicilous
Comments
Hello there,
Thank you for reaching out with your report.
We understand you are still encountering error code Yam, even after following the guidance of the troubleshooting in our article for Yam. We're sorry to hear that's the case. At this time, we have taken note of your report. For further assistance, you may wish to consider reaching out to your ISP.
Nothing has changed with my ISP nor are they blocking my connection, please let me know what to do, as I'm sad to say you "taking note" is not satisfactory I'm one of the people keeping the game alive and advocating for it every day as well as buying cosmetics, when I cant even play NOT DUE TO MY OWN FAULT you tell me you have "taken note" ? I know you people in support are probably not connected to devs in any major way but please don't push this away and fix the issue instead of pushing it away to someone else.
I ran into the same problem today. Windows hadn't updated. I got kicked out of a match and couldn't log back in—kept getting the "Yam" error. I cleared the cache and changed my DNS, but nothing helped.
Please sign in to leave a comment.