Fix CS 1.6 Settings Not Saving – 5 Working Fixes

Last updated: May 8, 2026

CS 1.6 settings not saving is one of the most common problems on Windows 10 and 11. You change your sensitivity, crosshair, or key bindings, close the game, and the next time you launch everything has reset to default. The problem is almost never the settings themselves – it is Windows preventing the game from writing changes to your config files. These are the five fixes that resolve the CS 1.6 config not saving issue, ordered from most to least common cause.

Table of Contents

1. config.cfg is set to Read-only
2. Run CS 1.6 as Administrator
3. Force save with writecfg
4. autoexec.cfg or userconfig.cfg is overwriting settings
5. VirtualStore and corrupted install

Fix 1 – config.cfg is set to Read-only

The most common reason CS 1.6 settings keep resetting is that config.cfg has the Read-only attribute enabled. When this is active, the game can read and load the file but cannot write any changes back to it. Every setting you change in-game disappears the moment you quit because the save fails silently.

Find your cstrike folder:

Version	Path
Steam	Steam\steamapps\common\Half-Life\cstrike
Non-Steam	C:\gaming\CS 1.6\cstrike or your install path

Right-click config.cfg, open Properties, go to the General tab, and uncheck Read-only. Click Apply and OK. Do the same for userconfig.cfg if it exists. Launch CS 1.6 and change a setting, then close the game normally. Reopen the file in Notepad to confirm the value was written.

Fix 2 – Run CS 1.6 as Administrator

Windows 10 and 11 protect folders inside C:\Program Files and C:\Program Files (x86). If your CS 1.6 is installed in one of these directories, Windows blocks file writes unless the game runs with administrator privileges. This causes the CS 1.6 config reset to happen every session even when config.cfg is not set to Read-only.

Right-click your CS 1.6 shortcut or hl.exe directly, go to Properties, open the Compatibility tab, and check “Run this program as an administrator”. Click Apply. This also fixes a second related issue: some CS 1.6 settings are stored in the Windows Registry under HKEY_CURRENT_USER\Software\Valve rather than in cfg files. Without admin rights, Windows blocks writes to this registry key and those settings reset every restart.

The simplest way to avoid this entirely is to install CS 1.6 outside of Program Files – a folder like C:\Games\CS16\ or on a secondary drive such as D:\CS16\ does not require administrator rights for file writes.

Fix 3 – Force save with writecfg

CS 1.6 normally writes config changes to disk when you quit the game through the menu. If you close the game by killing the process, alt-F4, or if the game crashes, the save does not happen and your settings revert. The writecfg console command forces an immediate write of all current settings to config.cfg without waiting for a normal quit.

Open CS 1.6, apply your settings, then open the console with ~ and type:

writecfg

This overwrites config.cfg with everything currently active in memory. Use it any time you change settings you want to keep, especially before closing the game. If you always close CS 1.6 by killing the process rather than using the quit menu, running writecfg first is the reliable way to guarantee your settings are saved.

Fix 4 – autoexec.cfg or userconfig.cfg is overwriting settings

If your CS 1.6 settings save correctly but then reset to a specific value every time you restart the game, another cfg file is overwriting them. Both autoexec.cfg and userconfig.cfg execute after config.cfg loads. Any command in those files that conflicts with what you set in the menu will override it every session.

Open both files in Notepad and look for commands that set the values you are trying to change – sensitivity, crosshair color, key bindings, name, and so on. Delete or comment out any line that conflicts with the setting you want to keep. Save the files and restart CS 1.6 to confirm the conflict is gone.

Symptom	Cause	Fix
Settings reset to default after every session	config.cfg is Read-only or no write permission	Fix 1 or Fix 2
Settings reset to a specific non-default value	autoexec.cfg or userconfig.cfg is overwriting	Fix 4
Settings disappear when process is killed	Normal quit never happened, no save triggered	Fix 3 (writecfg before closing)
Settings reset on some PCs but not others	Install path is inside Program Files on affected PC	Fix 2 or reinstall to D:\

Fix 5 – VirtualStore and corrupted install

Windows uses a folder called VirtualStore to redirect file writes from protected directories when an application does not have permission. If CS 1.6 is writing your config to VirtualStore instead of the actual game folder, the game loads the original empty config on each launch and your changes never appear where the game looks for them.

Check for a VirtualStore copy of your config at:

C:\Users\[YourUsername]\AppData\Local\VirtualStore\

If you find a cstrike folder there containing a config.cfg, delete it. Then move your CS 1.6 installation out of Program Files to a path without write restrictions, such as D:\CS16\ or C:\Games\CS16\. After moving, the game writes directly to the correct folder and the VirtualStore redirect no longer applies.

If the installation is corrupted beyond these fixes, a clean reinstall to a non-protected path resolves all config write issues at once. For more on saving config settings manually, see the CS 1.6 settings save guide. If your sensitivity or other specific values are behaving unexpectedly after a fix, the mouse sensitivity fix guide covers those separately.

If none of these fixes work, download a clean CS 1.6 build pre-configured for modern Windows – all config and file permissions work correctly on Windows 10 and 11 without manual changes.