Content Modification: Updates for Windows Applications published 2021-02-10

Release Announcements Patch (Release Announcements)
1

BigFix has modified content in the Updates for Windows Applications site.

New:

  • 5055709 Webex Meetings Desktop App 41.2.4.15 Available
  • 6081708 Mozilla Firefox 85.0.2 Available
  • 6081723 Mozilla Firefox (x64) 85.0.2 Available
  • 5055684 ASP .NET Core Runtime 5.0.3 Available (x64)
  • 5055682 ASP .NET Core Runtime 5.0.3 Available
  • 5055680 ASP .NET Core Runtime 3.1.12 Available (x64)
  • 5055674 ASP .NET Core Runtime 3.1.12 Available
  • 8101431 Adobe Acrobat Reader DC 2021.001.20135 Available (MUI Installer) - Adobe Acrobat Reader DC - Continuous Track
  • 8101429 Adobe Acrobat Reader DC 2021.001.20135 Available - Adobe Acrobat Reader DC - Continuous Track
  • 8101238 Adobe Acrobat Reader DC 2020.001.30020 Available (MUI Installer) - Adobe Acrobat Reader DC - Classic Track
  • 8101236 Adobe Acrobat Reader DC 2017.011.30190 Available (MUI Installer) - Adobe Acrobat Reader DC - Classic Track
  • 9101336 Adobe Acrobat DC 2021.001.20135 Available - Adobe Acrobat DC - Continuous Track
  • 9102073 Adobe Acrobat DC 2020.001.30020 Available - Adobe Acrobat DC - Classic Track
  • 9102066 Adobe Acrobat DC 2017.011.30190 Available - Adobe Acrobat DC - Classic Track
  • 5055690 .NET Runtime 5.0.3 Available
  • 5055692 .NET Runtime (x64) 5.0.3 Available
  • 5055688 .NET Desktop Runtime 5.0.3 Available (x64)
  • 5055686 .NET Desktop Runtime 5.0.3 Available
  • 5055676 .NET Core Runtime 3.1.12 Available (x64)
  • 5055670 .NET Core Runtime 3.1.12 Available
  • 5055678 .NET Core Desktop Runtime 3.1.12 Available (x64)
  • 5055672 .NET Core Desktop Runtime 3.1.12 Available

Modified:

  • 5055699 Webex Meetings Desktop App 41.2.3.17 Available (Superseded)
  • 5055654 ASP .NET Core Runtime 5.0.2 Available (x64) (Superseded)
  • 5055656 ASP .NET Core Runtime 5.0.2 Available (Superseded)
  • 5055646 ASP .NET Core Runtime 3.1.11 Available (x64) (Superseded)
  • 5055648 ASP .NET Core Runtime 3.1.11 Available (Superseded)
  • 8101427 Adobe Acrobat Reader DC 2020.013.20074 Available (MUI Installer) - Adobe Acrobat Reader DC - Continuous Track (Superseded)
  • 8101425 Adobe Acrobat Reader DC 2020.013.20074 Available - Adobe Acrobat Reader DC - Continuous Track (Superseded)
  • 8101234 Adobe Acrobat Reader DC 2020.001.30018 Available (MUI Installer) - Adobe Acrobat Reader DC - Classic Track (Superseded)
  • 8101232 Adobe Acrobat Reader DC 2017.011.30188 Available (MUI Installer) - Adobe Acrobat Reader DC - Classic Track (Superseded)
  • 9101334 Adobe Acrobat DC 2020.013.20074 Available - Adobe Acrobat DC - Continuous Track (Superseded)
  • 9102071 Adobe Acrobat DC 2020.001.30018 Available - Adobe Acrobat DC - Classic Track (Superseded)
  • 9102064 Adobe Acrobat DC 2017.011.30188 Available - Adobe Acrobat DC - Classic Track (Superseded)
  • 5055658 .NET Runtime 5.0.2 Available (Superseded)
  • 5055660 .NET Runtime (x64) 5.0.2 Available (Superseded)
  • 5055652 .NET Desktop Runtime 5.0.2 Available (x64) (Superseded)
  • 5055650 .NET Desktop Runtime 5.0.2 Available (Superseded)
  • 5055634 .NET Core Runtime 3.1.11 Available (x64) (Superseded)
  • 5055632 .NET Core Runtime 3.1.11 Available (Superseded)
  • 5055642 .NET Core Desktop Runtime 3.1.11 Available (x64) (Superseded)
  • 5055640 .NET Core Desktop Runtime 3.1.11 Available (Superseded)
  • 6081706 Mozilla Firefox 85.0.1 Available
  • 6081719 Mozilla Firefox (x64) 85.0.1 Available

Reason for Update:

  • New update from WebEx, .Net Runtime, Adobe Acrobat and Firefox

Actions to Take:

  • None

Published Site Version:

  • Updates for Windows Applications, version 1514

Additional Links:

–
Application Engineering Team
HCL BigFix

2

Is anyone else having an issue or problem with the new Acrobat \ Reader update fixlets failing? I have run both the Acrobat and the Reader MSP manually on machines and they work. Both are failing when i try to deploy from Big Fix.

3

Same for our systems. Adobe Acrobat DC failing to install on all systems with exit code 1603.

4

@stanleyc, @aptgetgot, Fixlets worked fine in our lab Env. Could you please log a L3 ticket with BigFix support team to investigate it further.

5

I did open a case CS0206366

Thanks

6

My Big Fix administrator has also opened a case. if this helps anyone, or if HCL can verify in their lab. the update only seems to run if a user is signed onto the machine. I have deployed the fixlet to two machines that failed with no one on them, and updated when someone was logged into them.

1 Like
7

Any update on where the fix is to the adobe 1603 error?

I had every attempted install fail with 1603

Adobe Acrobat Reader DC 2021.001.20135 Available - Adobe Acrobat Reader DC - Continuous Track
Source Adobe
Source ID APSB21-09
Source Severity Critical

8

Same question as well, do we have a resolution on 1603 error for Adobe Acrobat DC failing?

9

We are awaiting the ticket to reach L3 bucket. once we get it we would analyze it further.

10

I am getting reports as well of 1603 errors, even after reboots, and verifying that no user is logged in, nor that reader is running.

Manually downloading the fixlet-referenced MSP and running it either via msiexec command line or GUI installs correctly in a few tests that I ran with a user worked, and the fixlet went non-relevant as expected.

11

It looks like Adobe is aware of this and they are working on a fix. https ://borncity.com/win/2021/02/11/adobe-reader-dc-update-feb-9-2021-drops-error-1722-in-windows/

1 Like
12

So if Adobe has acknowledged this to be an issue, how could “Fixlets worked fine in our lab” be true?

13

After the post by Helpme, I was able to work with a operator who was having 1603 errors across his whole set of machines… He had someone log in to a endpoint that had been failing, and the the next attempt of the fixlet went through. So I guess add that to the anecdotal evidence pile that it’s associated with logged-in user context due to a new UWP component (per the linked article)?

1 Like
14

I also opened a ticket with Adobe for this issue, and i just got an email saying they have released new installers.

it looks like the new version is 20138 instead of 20135.

HCL, please test and release these fixlets as soon as you can

thanks.

2 Likes
15

Especially since someone on Adobe’s side said NOT to use the workaround to skip the UWP component during install with the switch… And we need at least 20135 for some pretty serious security fixes ASAP.

1 Like
16

@ mattporter. That is good to know thanks for posting!

18

This topic was automatically closed after 30 days. New replies are no longer allowed.