premiere pro update (now install) fails -- unable to write registry key IAMEWMEncodingHelper

[ZimFromIRK]

The Creative Cloud Desktop has been nagging me to install a Premiere Pro Update for weeks now. 

I'm on Microsoft Windows Version 10.0.19044.1415, fully updated 

However, every time I Install, it says

There was a problem in Premiere Pro Update

Unable to write the registry value. Check permissions and then try again (Error Code: 160)

When I view the error log, it reveals

Exit Code: 160
-------------------------------------- Summary --------------------------------------
 - 2 fatal error(s), 0 error(s), 1 warnings(s) 

FATAL: Error (Code = 160) executing in command 'SetRegistryValueCommand' for package: 'AdobePremierePro22AllTrial', version:22.1.2.1
FATAL: Error occurred in install of package (Name: AdobePremierePro22AllTrial Version: 22.1.2.1). Error code: '160'
WARN: Error Setting Registry - Start 64-bit:1 root:0 key:Interface\{3A853ADC-E868-44D6-8B24-AE98E810890A} name:Default type:REG_SZ data:IAMEWMEncodingHelper. Check for Registry permissions. (Error: Error 5 Access is denied.)
-------------------------------------------------------------------------------------

 I checked the registry key and it's fine.  I rebooted several times before attempting the install, with the same result each time.
I have now uninstalled Premiere Pro and the installation failed with the same results.

Any suggestions?

[Jeff Bellune]

Are you an admin on the PC?

If so, please try running Creative Cloud as an administrator and see if that helps.

[ZimFromIRK]

Thanks for replying. I already did that once -- started Creative Cloud elevated -- but just tried it again.

Same result, same error.

There are three CreativeCloud.exe processes: the main one, which I confirmed is now "elevated" and the other two CreativeCloudHelper.exe processes which are not. I killed all three and they restarted in the same way.

I then looked at the 64-bit registry key that it can't write to:

HKEY_CLASSES_ROOT\Interface\{3A853ADC-E868-44D6-8B24-AE98E810890A}

It has a Default value that is not set.  For grins, I tried setting a value in the registry editor (again, running elevated/as administrator) and I couldn't write to the key either -- got "permission denied". However, I was able to rename the key and I added -hidden" to the end of the key name to get it out of the way, and then repeated the Creative Cloud elevated installation.

The result was exactly the same. The installation appears to have re-created the registry interface key in a way that it cannot write to the key after creation.  So now I have two of these keys: the newly created key, and the -hidden key from last time.

I changed the permissions on the newly created key to grant full permissions to all accounts, but I still can't modify it, even though the permissions allow me to do so.  However, I can write to the previously renamed key -- where I added "-hidden to the name". 

If I had to speculate, there are two mechanisms: some process has this key locked, but then I wouldn't be able to rename it either.  More likely, I'd say that this particular interface ID is protected by Windows since it apparently will not allow this value to be written.  There are keys in this category, where changes would break Windows, but I've never seen this particular GUID or the value the Premiere installer is attempting to assign before.

Hopefully you have some pull and can forward this to Adobe development.  I see no other place to file a bug report but will do so, if you'll send me a link.

In the meantime, I can't reinstall Premiere at all right now.  Fortunately, I don't need it at this very moment.

[Jeff Bellune]

Please try to uninstall everything Adobe using the Creative Cloud cleaner tool. 

Then reinstall and see if things go more smoothly. 

[ZimFromIRK · Accepted solution]

After waiting a week, with Premiere Pro uninstalled, I just repeated the install and this time it succeeded.  I believe Windows Update updated Windows during this time, so maybe that fixed something, or maybe I got a new version of the Creative Cloud installer and that fixed it, or maybe Premiere Pro was updated and that fixed it.

In any case, it seems fine now.  Thanks, all!