Adobe Acrobat updates for 23.006.20320 32-bit and 64-bit missing from the SCCM/SCUP catalog CAB file

[Travis5EC2]

In the SCCM/SCUP catalog CAB file for Acrobat DC that is available here (https://armmf.adobe.com/manifest/arm-manifests/win/SCUP/AcrobatCatalog-DC.cab) I do not see the patches for "Adobe Acrobat Update 23.006.20320" and "Adobe Acrobat (x64) Update 23.006.20320" listed.

I see the corresponding 23.006.20320 patches in the Adobe Reader catalog CAB file, but they are not present in the Adobe Acrobat DC catalog CAB file.

Also, the MSP files for the missing Acrobat DC 23.006.20320 patches are listed and available for download on the Enterprise Release Notes page here (https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/continuous/dccontinuoussep2023.htm...), they are just not in the SCCM/SCUP catalog CAB file.

I need to deploy these patches. When are they going to be published in the catalog?

[Travis5EC2]

Bump

[kglad]

<moved from enterprise&teams>

[Travis5EC2]

Thank you

[kglad]

(you're welcome. hopefully, someone in the acrobat forum can help.)

[iCharles · Accepted solution]

Hi @Travis5EC2 ,

The SCUP/SCCM catalogs have now been updated. Could you please try once again and let us know how it goes?

[Bob324800141pu7]

This catalog is still NOT working. It does NOT contain this update"Adobe Acrobat (x64) Update 23.006.20320".

[Travis5EC2]

Both the 32-bit and the 64-bit patch are present in the Adobe XML file now. I would suggest syncing your third party update catalogs in SCCM, and then doing a full software update catalog sync. Sometimes I have noticed I have to do this twice before I see any new patches appear in my console.

[Travis5EC2 · Accepted solution]

Thank you @iCharles. I was able to sync the catalogs and find the two patches that were missing earlier.

[Bob324800141pu7]

I was not clear on my last post. The problem I'm having is that our systems are running Adobe Acrobat Reader (x64) 2023.003.20244. They will not upgrade to Adobe Acrobat Reader (x64) Update 23.006.20320 because there is no Adobe Acrobat Reader (x64) Update 23.006.20320 in the catalog. You can see that there is no "Adobe Acrobat Reader (x64) Update 23.006.20320" in your screen shot. Now If I turn on auto updates they will upgrade from the Adobe website to "Adobe Acrobat Reader (x64) 23.006.20320" within ten minutes. However I don't have the luxury  of turning that on in my environment. Feedback welcome.

[Bob324800141pu7]

It's been almost two weeks and no reply. What is Adobe's position on this? iCharles........Anybody ??

[Travis5EC2]

I do not know the specifics of your environment but I am going to guess here that you are looking for a patch which does not exist.

Typically Adobe released 7 patches per cycle. All 7 are now visible in the catalog for APSB23-34.

If I had to guess, you are running the Adobe Acrobat x64 unified installer branded with a an Adobe Acrobat Reader product code...  a while back Adobe combined the 64-bit variants of Acrobat and Reader into a single unified installer. 

Forget the product name that is visible in appwiz.cpl or when you open the program. Instead do this:

- On a target machine in your environment check C:\Program Files\Adobe[...] folder location.

- Do your machines have AcrobRd32.exe or Acrobat.exe executable at this location?

If your machines are not taking the Reader patch then I would guess you are using the unified installer, which installs as Acrobat using a limited "reader license", and as such you need to patch using the Acrobat patch.

I would suggest opening a new thread for further assistance.

[unkownuser32865587at2l]

SCCM adobe Acrobat reader update (thrid party catalog) Octobr month patch is released?

[Lance5FB4]

What I've noticed in my enviornment is that Acrobat (not reader) cab updates way later, sometimes many days after the manual downloads are available.  Reader is always there the same time Microsoft releases thier updates.  I've downloaded the CAB file and run searches against the released and it's never there on time.

Updates were released yesterday and they still haven't hit the cab file as I write this.