Photoshop Elements 14 Update Failure U44M1I210 on Windows 11 Resolved

[EWG2015]

I just installed Photoshop Elements 14 on a new Windows 11 Pro desktop.  The download file from account.adobe.com/products was for the original release, 14.0.

Shortly after installation a window popped up advising that updates for Photoshop Elements (to 14.1) and Adobe Camera Raw (to 9.5) were available.  The ACR update installed successfully.

The 14.1 update failed with error code U44M1I210. This attempt was in a standard account and the appropriate user account control permission to change the system had been granted.  It continued to fail even after restarting Windows.

A search for the error code found a support article from 2018 for Adobe Creative Cloud and Creative Suite CS6 (https://helpx.adobe.com/creative-suite/kb/error-u44m1i210-installing-updates-ccm.html), that suggested five solutions, the first of which was to install the update using an administrator account.  A post on another bulletin board suggested this article was valid for more than the stated products. The update using an administrator account worked.

Another support article for unspecified products from this year (https://helpx.adobe.com/creative-cloud/kb/update-error-u44m1i216.html), but apparently somewhat dated as it refers only to Windows XP, Vista, 7 and 8, suggests deleting the updater folder.  I don't know whether this would work because the update using the administrator account did work. 

The standard and administrator accounts were both local accounts, not Microsoft accounts. The updater program (updatercorehelper.exe) had been added to the Windows Controlled Folder Access allowed list at installation time.

[EWG2015]

While installing Photoshop Elements 14 on a new PC that came with Windows 11, an error window popped up saying that the program could not run on this device because a driver was incompatible with Core Isolation with Memory Integrity turned on.  The setting is in the Device Security menu under Windows Security. 

Memory Integrity had been turned on as a default by the PC manufacturer.  The installation file was downloaded from Adobe Support earlier today — the support rep supplied a link to it and said that it came with all available updates and was thus better than the original CDs.

I turned Memory Integrity off, restarted the PC and completed the installation.

After verifying that the program would run, I turned Memory Integrity back on.  I was pleasantly surprised to see that the program ran without another incompatability error.  "All's well that ends well."  Tomorrow I'll see if the phantom reappears when I install Premiere Elements 14.

Note: the Adobe updater program and the Photoshop Elements editor had to be added to the list of allowed programs under the Ransomware-related Controlled Folder Access feature.  By now I am used to this having turned Controlled Folder Access on in my now defunct Windows 10 PC.

[kglad]

<moved>

[Christina25146590dnrx]

I was able to follow instructions from EWG2015, and Elements 14 (both photo and video) finally got installed, but when I went back to switch memory integrity back on, it wouldn't let me, saying there was an incompatible driver. On further examination, it said it was Corel Corp. PxHlpa64.sys (I don't know if that's a 1 or an l...)

Does anyone know how to fix this or who to contact?  Corel has products listed, but not Elements.  I've looked under Device Manager and checked for updates, and found one under Communications that got updated, but I don't think it was related as it didn't change anything.

 

[kglad]

you should install and run using compatibility mode.

[Christina25146590dnrx]

Not sure I understand. So uninstall both photo and video programs? Where do I find compatibility mode? Sorry, I'm a bit of a neophyte...

[kglad]

before installing, right click the installation file > click properties > click compatibility mode > enable compatibility > win 10.

to run pse 14 on win 11, right click > etc enable compatibility > win 10

[Christina25146590dnrx]

Okay, I'll give it a go.  But will this allow the memory integrity switch to be turned back on after re-installation?

[kglad]

that, i do not know.