Force restoration of Chrome's shortcuts when Active Setup kicks in in response to a major OS upgrad…

chrome/installer/setup/install.cc

Index: chrome/installer/setup/install.cc
diff --git a/chrome/installer/setup/install.cc b/chrome/installer/setup/install.cc
index 4a18004e547b6e84e7230be8d818af3b1427e7eb..f491d1f61290772a0492e78b0f2cf9c6a62e7105 100644
--- a/chrome/installer/setup/install.cc
+++ b/chrome/installer/setup/install.cc
@@ -655,6 +655,13 @@ void HandleActiveSetupForBrowser(const base::FilePath& installation_root,
                                  const installer::Product& chrome,
                                  bool force) {
   DCHECK(chrome.is_chrome());
+
+  // If the shortcuts are not being forcefully created we may want to forcefully
+  // create them anyways if this Active Setup trigger is in response to an OS
+  // update.
+  force = force || InstallUtil::UpdateLastOSUpgradeHandledByActiveSetup(
+                       chrome.distribution());
+
   // Only create shortcuts on Active Setup if the first run sentinel is not
   // present for this user (as some shortcuts used to be installed on first
   // run and this could otherwise re-install shortcuts for users that have