Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Looking at mine, last modified two days ago. Some game I play still looks at it.
Actually, it's Payday 2. Deleted and it immediately recreated when PD2 launched.
Most jobs are, for this reason, performed by the Steam Client Service, which is a service that runs on startup.
Steam.exe might actually be trying to write the ClientRegistry.blob file and failing due to permission issues.
On some systems, all users have full access to the Steam directory, thus it probably succeeds for that reason—and as such the file would exist for them.
The Steam flush config command can achieve the same thing as deleting the blob file.