-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-Update to partially fix 31 #36
Conversation
I copied this from an internalised package, this is to remove the non community related bits
Isn't the problem that the original display name is not correct? Thus the uninstall key is not found which leads to the update portion not being executed. As mentioned in #32. |
@conitrade-as I did look at this original display name theory, and I couldn't confirm it. I was able to replicate the issue without Chocolatey involved, just using the x64 deliverables by Adobe. At some point the package call an Adobe exe with those arguments (the double backtick is a formatting issue, in the code is single): In some scenario that $options is expanded to include DISABLE_CACHE=1.
Please note the 2 PATCH parameters reported in the log (and the 2 REBOOT as well, in this case). |
My point is the following: There is already a code path which does run
But since the |
So indeed, the following change works for the update path: conitrade@4980a9a |
I have tested the code in this PR to update Adobe Reader in 70 devices. 64 successful updates, the 6 not successful all had logical explanations (not enough disk space, reboot needed, ..). |
I went to look at the value of DisplayName in my install base. In 80% of the deployments I found Adobe Acrobat (64-bit), but in 20% of the deployments I found Adobe Acrobat Reader. This suggests that the condition:
may need to be changed as:
@conitrade-as is your change going to support both names? |
This is to update also on computers with DisplayName set to Adobe Acrobat Reader. This was successfully tested in 200 computers.
This fix #31 (probably also #32).
The fix is partial because it only applies to the x64 version. I tested in 4 devices, 2 updates and 2 install.
It is likely something similar could fix also the x86 version, if affected, but I don't have how to test that.