<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Does anyone have a decent way to create a package for Google Chrome that works reliably?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Being a simple MSI, it should be straightforward. But our finding is that some of the time, in an inconsistent and unpredictable way, the enterprise version of Chrome sometimes installs itself with the MSI version number rather than the
Chrome version number (from the current version: ’68.12.49287’ vs ’84.0.4147.135’). Obviously this triggers wpkg to think there’s a new version when there isn’t as the versions don’t match. The installer itself knows not to update which doesn’t clear the
problem – the version number showing in Add/Remove remains the MSI version until the next update. If it was consistently one way or the other, it would be trivial. But I’d estimate it gets it right about 80% of the time. There’s been an open issue on the
Chromium issue tracker about it doing this for 10 years with still no fix, or even acknowledgement that there’s a problem to fix:
<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=67348">https://bugs.chromium.org/p/chromium/issues/detail?id=67348</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In normal circumstances, I would (and have done for some time) just leave it, it doesn’t cause any harm to have it try to reinstall Chrome. But in these strange times, I have a lot of staff remote working via remote desktop, and they are
reluctant to reboot their PCs remotely at the end of the day. As a result I’ve been trialling ‘sonicnkt’s fork of wpkg-gp plus the system tray client that notifies of pending updates, and the problem now is that when Chrome has installed itself like this,
the tray tool pops up an update notification every 30m or so, for an update that simply won’t go away.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Steve.<o:p></o:p></p>
</div>
</body>
</html>