Adobe Acrobat Reader DC consistently fails with error 1328 when upgrading Win 10 32-bit computers

Win 10 64-bit computers do not exhibit this issue (even though they are installing the same 32-bit Reader  updates).  Win 10 32-bit computers fail in almost all circumstances, especially when running the MSP (or even the full installer) of any versions of Reader DC 24.005.20399 or above (24.003.20112 was the last version to install without error on Win 10 32-bit clients).

It kicks out this very common Adobe error every time it fails:

"Error 1328. Error applying patch to file c:\Config.Msi\PT1CB2.tmp. It has probably been updated by other means, and can no longer be modified by this patch. For more information contact your patch vendor. System Error: 8"

The failures are very consistent when running the installation from a command line (e.g. packaged distribution).  This happens whether kicking the update off from an external installer (e.g. PSExec) or by manually kicking off the command line on a client.  We also experience this error most times when just trying to manually execute the MSP or full installer of the newest versions on the client as well.

Some iterations of CMD line examples we have tried:

"%~dp0AcroRdrDC2400520399_MUI.exe" /qb /sall /msi /l*v "C:\Program Files\AppLogs\AcroRdrDC2400520399_MUI.exe.log"

(Full silent installation.)

msiexec.exe /p "%~dp0AcroRdrDCUpd2400520421_MUI.msp" /qn /l*v "C:\Program Files\AppLogs\AcroRdrDCUpd2400520421_MUI.msp.log"

(MSP silent installation)

msiexec.exe /p "%~dp0AcroRdrDCUpd2400520421_MUI.msp" /qn /l*vx "C:\Program Files\AppLogs\AcroRdrDCUpd2400520421_MUI.msp.log"

(The x on the /l*vx switch was at the suggestion of another Adobe Community post.)

The above command lines are run in CMD files.  They run just fine on Win 10 64-bit.  But they fail on Win 10 32-bit.  Again, the older versions of Reader installed ok using the same command lines as above.  It is just the newer ones that fail.

We are running some Win 10 LTSC 32-bit clients (both 1607 and 1809) in our manufacturing environment on older processes which require 32-bit.  The end of life of 1809 LTSC is Jan 2029.  So we would hope that Adobe Reader could be used on those builds until the end of support life.  We have to keep Reader patched for the occasional security vulnerabilities.  So it is important to get these patches working.

We have eliminated antivirus software as the possible cause.  We have tried another community suggestion of cleaning out the C:Windows\Installer\$PatchCache$\Managed folder for Reader.  We have tried uninstalling Reader completely, then running the latest AdobeAcroCleaner_DC2015.exe to clean it up, then do a fresh install of the newer version.  It fails consistently even at that (it installs v15, then it fails on applying the latest MSP in the package, then it rolls back).

If we run the MSP file manually on a Win 10 32-bit computer, it will almost always stop with the same error.  If we chose the "ingore" option each time the error comes up, then we can force it to install.  However, we do not trust that these will not have future upgrade issues by using this method.

Again, we can consistently get 24.003.20112 to install on clients.  But none of the newer versions will install.  So I am guessing that something changed in those new versions which causes it to fail on Win 10 32-bit.