Post-cleanup settings reset.

chrome/browser/prefs/chrome_pref_service_factory.cc

Index: chrome/browser/prefs/chrome_pref_service_factory.cc
diff --git a/chrome/browser/prefs/chrome_pref_service_factory.cc b/chrome/browser/prefs/chrome_pref_service_factory.cc
index 3211483fb737713001c73028c39f9f8b80c37388..c621794c4bac581ae77b4851ccf2e9fc790628d2 100644
--- a/chrome/browser/prefs/chrome_pref_service_factory.cc
+++ b/chrome/browser/prefs/chrome_pref_service_factory.cc
@@ -175,6 +175,8 @@ const prefs::TrackedPreferenceMetadata kTrackedPrefs[] = {
     {28, prefs::kSettingsResetPromptLastTriggeredForHomepage,
      EnforcementLevel::ENFORCE_ON_LOAD, PrefTrackingStrategy::ATOMIC,
      ValueType::IMPERSONAL},
+    {29, prefs::kChromeCleanerResetPending, EnforcementLevel::ENFORCE_ON_LOAD,
+     PrefTrackingStrategy::ATOMIC, ValueType::IMPERSONAL},

[gab, 2017/06/14 17:08:12]

What's the point of protecting this? Settings protection will only prevent an
attacker from forcing a reset through this (which is unexpected IMO), it won't
prevent anyone from removing the value (that's what the protection does on its
own if it's modified in any way). Since protection isn't "free", I'd say don't?

[ftirelo, 2017/06/15 03:41:23]

Done.

 #endif  // defined(OS_WIN)
 
     // See note at top, new items added here also need to be added to