http://bugs.winehq.org/show_bug.cgi?id=7573
jeff jmgreen7@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jmgreen7@gmail.com
--- Comment #27 from jeff jmgreen7@gmail.com 2007-08-23 22:42:27 --- I also checked HKCU/software/valve/steam/users/<uid>/licenses and it begins with "01 00 00 00 ..." After looking at the code for regedit and trying to import new registry keys with similar values it seems that there is a very serious bug in how regedit parses hex valued keys. From my initial tests it seems that any value that starts with 0 causes a "regedit: ERROR converting CSV hex stream. Invalid sequence at ..." error when importing a key with that value. So any hex value of the form "0x" (where x is a digit from 0-e) in the comma separated list causes an error.
It seems like this might affect Steam by Wine not parsing the "licenses" value correctly and Steam thinking that you don't actually own the games you purchased. So when you delete the key from the registry, Steam can't check the value in the registry and must rely on it's own server-side data to determine what games you own. It would also explain why even when my purchased games show up as purchased I still can't start some of them and get a "You do not have a valid subscription" error. The "licenses" key is stored in the registry again and when Steam needs to check the value when starting the game Wine parses it incorrectly. Could anyone who has working purchased games please check the value of HKCU/software/valve/steam/users/<uid>/licenses, since if it has any "0x" digit pairs then my speculation would be wrong.