+Enterprise, as the installer in question is the .msi.

I am able to reproduce the behavior on the reported version: 60.0.3112.101 in the GPO Windows Server 2012 R2 AD DC environment. Chrome gets installed and Chrome icon shows up on the Desktop and on the taskbar even on cancelling the installation. However not seeing any Chrome installation under Control Panel. Marking this as Untriaged for more inputs on this.

diyariq@: Could you please confirm if there is any Chrome installation shown in Control Panel?


Note: This worked fine for me when installing and cancelling the installation of desktop-5c0tCh%2F60.0.3112.101%2Fwin64-pgo%2FGoogleChromeStandaloneEnterprise in the normal Windows 10 environment. Don't have set up in the  GPO environment to bisect this hence removing the Needs-Bisect label.  

I confirm I can't see the name of Google Chrome Browser in the list at Control Panel.

  After reproduce as in the video than try to install Google Chrome Browser again? does show you an error? that is installed incorrectly and will not get install. 

Another issue with installing, with a normal package, ignored my cancel install ( After downloaded all data) during installation and complete the installation until the end, ( Completed installed and is showing in Control Panel).

  Link to video how to reproduce: https://youtu.be/yRvdTTSS_FY

  

Assigned to Julian, who works on Chrome for Windows.

Greg, should I assign this one to you or someone else instead? Happy to provide help about reproducing if needed but otherwise I think someone else should own that that knows the installer better than me.

I can take a look. This looks to be a PE issue to me, so moving to P3. Feel free to bump upward if you disagree.

This is happening because Chrome's MSI does not handle rolling back an install that fails, yet it also doesn't explicitly disable rollback. Since a proper rollback would be nearly impossible to get right (in the case of an update, we can't go back to the previously-installed version of Chrome), we should probably disable rollback altogether as per https://msdn.microsoft.com/library/windows/desktop/aa371370.aspx. While this won't make "cancel" work, I think it would result in leaving the machine in a consistent state. As it is, the Component that drops the product id+version in the ClientState key deletes the whole ClientState key during rollback, making it challenging to uninstall the version of Chrome that was just installed.

@grt recheck Comment 7 I posed a video that issue obtain with .EXE also, so not just MSI.

Thanks for that. In the case of comment 7, this is merely a UX glitch. The dialog correctly tells you that Chrome was installed before the operation could be cancelled, and Chrome is present in the Programs and Features control panel. I can see that it's not a great user experience, but at least you can recover by uninstalling Chrome. In the case of the MSI, we have a real bug as you end up with no way to uninstall Chrome.