Since March 11th (20 days ago) i began receiving a logged error in the Event Viewer.
It was around this time that i noticed an odd hesitation occasionally while running / moving long distances.
It was not until today that i checked the event viewer after the game crashed to the desktop while i was in AH.
Game still loads/plays…just a noticable “studder” every five minutes.
Does not hurt PVE…but would be unacceptable in PVP.
The logs show 2,039 identical errors appearing every five minutes.
Two other threads on this forum indicate it has something to do with the anti-cheat software.
Steps to resolve:
Updated to N-1 version of Nvidia drivers.
Verified file integrity
Disabled security & anti-virus software.
System:
Win10 19044
64Gb RAM
2x 2080 ti
4x SSD
i7 on ROG Max H XI
Hi there. There is nothing wrong with your OS (at least, not so far as this error is concerned). First, definitely DON’T update Windows to attempt to fix this error. Unnecessary Windows updates are a great way to cause more/other/worse problems with your system.
Same is true for running SFC; don’t do it unless you know how to read CBS logs and perform manual restoration operations, because it can cause more problems than it can fix.
In any event, neither will help with this issue.
This specific error message is caused by a well-known and -documented bug in the Easy Anti-Cheat software. It has been around forever, and I have no idea why AGS hasn’t made a note of it and published information about it in the FAQ.
An EAC bug affecting its inherited permissions is causing it to miscommunicate with Steam and the game client. This issue is not specific to New World, so if you happen to find this thread while troubleshooting this error in relation to any other EAC-enabled game, this may help you as well.
Here is how to fix this:
Close Steam and New World completely.
Navigate to …\steamapps\common\New World\EasyAntiCheat and execute EasyAntiCheat_Setup.exe AS AN ADMINISTRATOR (right click > Run as Administrator).
Click on Repair Service and wait for the installation to finish. If you receive an error at this point or the installation does not complete successfully: execute EasyAntiCheat_Setup.exe again as an administrator, Uninstall instead of Repair, delete the EasyAntiCheat folder when the uninstall finishes, then verify game files, then start over at step 1.
Navigate to your Steam installation root folder and configure Steam.exe to Run as Administrator. (Right click on file, Properties > Compatibility > “Run this program as an adminstrator” > Apply > OK).
Navigate to …\steamapps\common\New World and configure NewWorldLauncher.exe to Run as Administrator. (Same steps)
Navigate to …\steamapps\common\New World\Bin64 and configure NewWorld.exe to Run as Administrator. (Same steps)
Done.
Unfortunately, even if you do all of this correctly, you may now encounter a different error on game launch that prevents the client from starting; if this occurs in games other than New World, you may be able to workaround it by deleting “steam_appid.txt” from the folder containing the game’s binary (not applicable to New World) and then verify game files to recreate it - but if that doesn’t solve the problem (or if it occurs for New World) you will need to reinstall the game then repeat steps 5 and 6. This is caused by a separate bug regarding inherited system permissions in Steam itself.
In rare cases, if the above steps do not stop the errors from occurring, you may also need to navigate to …\steamapps\common\New World\Bin64, delete “NewWorld.exe.eac,” then verify game files, then run “EasyAntiCheat_Setup.exe” again and Repair.
