System-level Chrome should not store data in HKCU\Software\Google\Update\ClientState\... |
|||||
Issue descriptionRather, data should end up in HKLM\Software\Google\Update\ClientStateMedium\... under a key with per-user values. Rationale: it's difficult for uninstall to remove data from user hives. We could have a period in which a system-level update would migrate per-user data from any user hives that can be loaded into HKLM.
,
Jun 8 2017
grt: Are you able to triage this?
,
Jun 12 2017
I'd call this a "nice to have". Some values may need support from Google Update. There's nothing burning here, I simply filed it to keep it on the radar as something to strive for.
,
Jun 12 2017
,
Jun 12 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 13 2018
This is basically for dr and lastrun. There may be a few other stragglers, but I don't think they're critical. dr shouldn't move, since I recall it being decided that per-install dr is the righ thing. Lastrun I'm less sure about, but I don't think this is high enough impact to be worth pursuing. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by sheriffbot@chromium.org
, Jun 8 2017Status: Untriaged (was: Available)