/build/static/layout/Breadcrumb_cap_w.png

Error 1722 - Adobe Flash Palyer ActiveX

Hi all,
When i try to upgrade Flash player Activex 9.0.28.1 to Flash player Activex 9.0.115.0, i get the error 1722.
In the event viewer i can see the following message:
Error 1722:
Product Adobe Systems Flash player Activex 9.0.28.1 - error 1722 There is a problem with this...... Support personal or package vendor.
Action RegReset25, location c:\windows\installer\MSI15.tmp, command on "HKCR\CLSID\{D4304B....70C2} -ot reg -actn trustee- trst.n1:"Everyone";s1:n;ta:remtrst;w:dacl -silent.

i dont have any action by the name:RegReset25 and i dont have a copy of Activex 9.0.28 either.(But still, been asked to work on it.. [:@])
I searched thru this forum but cudnt get any solution close to this.. I dont get this error everytime when i try to install the package. It occurs randomly. And also i dont get this error in any pattern, in the sense, it occurs once in a while even if i follow the same installation procedures.. (like installing various other applications and then installing this one).

Can somebody help me in yhis.. Thankx in advance...

1 Comment   [ + ] Show comment
  • You may also get this error if you try to install Flash player Active X on Widows 8. Windows 8 already contains Flash Player Active X. - BW~Merlin 10 years ago

Answers (12)

Answer Summary:
Include a CA after Installinitialise (call exe from installation; includ the flash.exe(of the current version) file by passing the parameter "C:\WINDOWS\system32\Macromed\Flash\FlashUtil9c.exe -uninstallUnlock "). This clears all the permission locks on the registries and makes the system available for proper installation
Posted by: anonymous_9363 16 years ago
Red Belt
0
One can tell from the command line arguments that the package is trying to run SetACL (which it extracts from a binary stream in the MSI as MSI15.tmp to c:\windows\installer) against a CLSID registry entry beneath HKEY_CLASSES_ROOT\CLSID. From what little I know about this part of SetACL, the actual command will remove the group 'Everyone' as a Trustee (the 'remtrst' parameter is used).

Quite why it's doing that bemuses me. Mind you, quite why Adobe sees fit to trash my workstation permissions in the first place is a bone of contention. Remember the debacle of the early incarnations of Reader 8.0, anyone? LOL...

Anyway, use a transform and stop this Custom Action from running by setting an impossible-to-meet condition for it.
Posted by: rayz_0020 15 years ago
Senior Purple Belt
0
Its quite interesting to see my old amateur posts here......

Hmmm, Anyway i have got an issue with Flash player upgrade again...
The previous version on uninstall leaves behind the following registry
HKCR\TypeLib\{D27CDB6B-AE6D-11CF-96B8-444553540001}
And in the permissions, special permissions are denied for the group "Everyone".

I wanted to handle it in my version and i included a setacl command to remove the trustee but due to the deny permissions, it fails.
Also a setacl CA to set full permissions to this group fails when the deny permissions are present.
I have used the following commands:

-on "HKCR\TypeLib\{D27CDB6B-AE6D-11CF-96B8-444553540000}" -ot reg -actn ace -ace "n:Everyone;p:full;m:set;w:dacl" -rec yes

-on "HKCR\TypeLib\{D27CDB6B-AE6D-11CF-96B8-444553540000}" -ot reg -actn trustee -trst n1:"Everyone";s1:n;ta:remtrst;w:dacl -silent

Without any deny permissions both the above commands work fine...

Can i forcibly remove trustee or overwrite permissions using SetAcl when deny special permissions exists .............

Or is der any other option to handle this.. i need the trustee removed b4 the installation of my app starts(i mean before InstallInitialize).........

Any pointers ????????

Thanks,
Rajesh.
Posted by: anonymous_9363 15 years ago
Red Belt
0
Or is der any other option to handle this.. You know what? Firstly, I would begin a series of phone calls to Adobe, working your way higher and higher through their heirarchy, to have them provide you with a solution. Who the hell do they think they are, messing about with workstation security?!?

Secondly, you could do worse than back up a broken workstation, then try the registry recovery routine detailed here http://support.microsoft.com/kb/307545

BTW, one of the v7 flavours of ZoneAlarm (Free version - don't know about Pro) does a similar thing with its folders.
Posted by: rayz_0020 15 years ago
Senior Purple Belt
0
Who the hell do they think they are, messing about with workstation security?!?

None but a contracted employee committed to my client to package applications that would upgrade all their previous versions irrespective of the errors they would introduce...

This registry issue comes up due to the uninstallation of the previous version (Packaged by them and not a direct Vendor App install). I mean this issue arises only after install and uninstall of the previous version of this application... So i don't see any reason why i shouldnt't be messing up with this registry....

Thanks for the help anyway.....
Posted by: anonymous_9363 15 years ago
Red Belt
0
You misunderstood. Read my post again:Who the hell do they think they are...
I was railing against Adobe's messing with security. They did the same with an early release of Acrobat Pro v8 and quickly (well, "quickly" is a relative term for Adobe...) released a patch with that "feature" removed. As I say, I'd be badgering Adobe going ever higher up the hierarchy until someone provides you with a fix.
Posted by: rayz_0020 15 years ago
Senior Purple Belt
0
You misunderstood.

Thats right Ian... [:(] My bad.... really bad........... [:-]
Sry abt tat..
Posted by: rayz_0020 15 years ago
Senior Purple Belt
0
Got a fix finally.........
Included a CA after Installinitialise (call exe from installation; included the flash.exe(of the current version) file by passing the parameter "-UninstallUnlock").
This clears all the permission locks on the registries and makes the system available for proper installation...

http://kb.adobe.com/selfservice/viewContent.do?externalId=4da116d3

Cheers,
Rajesh.
Posted by: anonymous_9363 15 years ago
Red Belt
0
Excellent work, Rajesh. Would you please post this in the 'Package KB'?
Posted by: AngelD 15 years ago
Red Belt
0
Ian,

This is already mentioned in the Package KB for Flash Player 9.x.
Uninstall String: C:\WINDOWS\system32\Macromed\Flash\FlashUtil9c.exe -uninstallUnlock
Posted by: anonymous_9363 15 years ago
Red Belt
0
It's in the Software KB, not the Package KB. No wonder I couldn't find it! :)

Because of its location, there's no extra text available to tell you what that switch does. I still think it's worth adding it to the Package KB, with an appropriate note.
Posted by: AngelD 15 years ago
Red Belt
0
So; to not confuse anyone:
It is in the Package KB for the "Flash Player 9.x" package and defined in the "Software Knowledge Base" category.
Posted by: rayz_0020 15 years ago
Senior Purple Belt
0
Would you please post this in the 'Package KB'?
Done. I have included in the Package KB for the "Flash Player 9.x" package and defined in the "Notes" category.


This is already mentioned in the Package KB for Flash Player 9.x.
Uninstall String: C:\WINDOWS\system32\Macromed\Flash\FlashUtil9c.exe -uninstallUnlock


It is in the Package KB for the "Flash Player 9.x" package and defined in the "Software Knowledge Base" category.


As per my understanding, the command "C:\WINDOWS\system32\Macromed\Flash\FlashUtil9c.exe -uninstallUnlock" will only unlock the control to OCX and registry keys. I dont think this will be uninstalling the application. Have someone actually tried it and achieved a proper uninstallation?
I tried and I couldn't...
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ