Go BackTroubleshooting CS2 "Unable to Read File" Error: A Step-by-Step Guide
By Gabriele Asaro
2 min read
Updated on

Troubleshooting CS2 "Unable to Read File" Error: A Step-by-Step Guide

I recently ran into an issue where CS2 was unable to read my autoexec.cfg file. The error message was: "[InputService] exec: couldn't exec '{*}cfg/autoexec.cfg', unable to read file." If you're facing the same problem, don't worry.

I've got some solutions that might help.

First, make sure your autoexec.cfg file is in the correct folder. CS2's file structure is different from CSGO. The correct path should be: "C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg"

If that doesn't work, try this alternative location: "C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\core\cfg"

Next, check the file type. Right-click on your autoexec.cfg file, go to Properties, and look under the General tab.

The file type should be 'Configuration Source File (.cfg)'. If it shows as '.txt', you'll need to change the extension.

Windows might be hiding file extensions, causing you to create a file named "autoexec.cfg.txt" instead of "autoexec.cfg". To fix this, go to Folder Options and uncheck "Hide extensions for known file types".

If you've made these changes and the file still won't load, try executing it manually in the game console with the command: "exec autoexec.cfg"

By following these steps, you should be able to resolve the "CS2 unable to read file" error. If you're still having trouble, double-check your launch settings and make sure everything is set up correctly.

Gabriele AsaroAbout the author

Gabriele Asaro
Gabriele Asaro

I'm the Head of Research at Clash.gg. With over 7 years of experience in the Counter-Strike niche, I have developed extensive knowledge of the game, its strategies, and the competitive scene. My insights are based on years of in-depth analysis and close involvement with the Counter-Strike community.