WAPT user > Windows in 2.5.2
WAPT server > Debian in 2.5.2.15207
I'm experiencing Chrome package update issues on many PCs across the network. I installed the latest versions a few weeks ago and I'm encountering these kinds of problems:
Code: Select all
CalledProcessErrorOutput: Command 'msiexec /norestart /q /i "googlechromestandaloneenterprise64.msi" NOGOOGLEUPDATING=1 NOGOOGLEUPDATEPING=1' returned non-zero exit status 1603.
Output:However, I have just noticed that the error (above) returns, despite the resolution (above), following the latest versions of Chrome.
Is there a way to truly clean up all past traces of Chrome in order to "start fresh"?
Thank you in advance, best regards.
