Distribution sw_lic_full_installer.msi installs two Shockwave Versions

The Distribution sw_lic_full_installer.msi installs version 11.5.0.600 in C:\WINNT\system32\Adobe\Shockwave 11 and 10.4.0.25 in C:\WINNT\system32\Macromed\Shockwave 10. Where as the sw_lic_full_installer.exe for distribution only installs 11.5.0.600 which is the new security update. I need a good msi for a silent installation package as soon as possible.

Sean,
With the past installations they only contained one version. I need to make sure that this will be secure for our environment since this is a security update. That is my concern.
DeVona
720-578-3118
303-707-6058 (Wednesdays)

Similar Messages

Issues with Shockwave 11.5.2.602 / 11.5.6.606 MSI installer

<UPDATE 8/3/09> Nearly all of the issues mentioned below are still present in the MSI installer for 11.5.6.606 - the only one that Adobe have fixed is the one where the MozillaPlugins 'Version' value is left blank by the MSI by default - this is now created correctly, but all of the other issues remain.
Personally I have given up trying to use this MSI package to deploy Shockwave until Adobe get their act together - instead I am using a wrapper to wrap the Shockwave executable inside an MSI file and deploying it that way, although this is not ideal.
I have created an MST file which will fix the MSI installer for version 11.5.6.606, which I will post to another forum shortly, but I am not planning to keep it updated for future versions as I don't really have the time.
Hi,
I've tried submitting the following via the Adobe Customer Support portal and via the Feature Request/Bug Report form, but the first told me that I needed to 'get in touch with Adobe Enterprise Solutions team for getting help' and that 'to get in touch with them you have to purchase a contract', and the second resulted in a bounced email address saying that '[email protected]' 'does not exist at the organization this message was sent to'.
In short, attempting to contact Adobe to report issues with their installers sucks, and I am posting this here in the vain hope that someone at Adobe might read this message and possibly forward it to the relevant people. Some of the issues have already been reported here on this forum, but some of them are new, and I guess others might be interested in them too.
Hi,
I would like to report some issues with most recent version of the Shockwave installer, available in MSI format from the following location:
http://www.adobe.com/cfusion/entitlement/index.cfm?k=4E6102EB-DA7C-2795-C744826EFDE2A098&l oc=en_us
This is the installer for version 11.5.2.602, with a digital signature dated 06 November 2009 10:52:21
When downloading this version of the installer in Windows Installer (MSI) format, the following issues manifest themselves, most of which are not a problem when using the Full EXE installer available from the same page.
First of all, when installing the MSI file using Group Policy Software Deployment, if you log on to the computer after the MSI file has been deployed and view a web page that contains Shockwave content, you receive the following errors in the Windows event log:
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 16/12/2009
Time: 16:51:23
User: CRGS\DefaultUser
Computer: ITO01
Description:
Detection of product '{7D0F2155-D7D3-42CE-903F-684ADD77FF89}', feature 'Adobe_Shockwave_Player_', component '{E89F323D-7BDB-46E1-A0FD-6227821F94EA}' failed. The resource 'C:\WINDOWS\system32\config\systemprofile\Application Data\Adobe\' does not exist.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 16/12/2009
Time: 16:51:23
User: CRGS\DefaultUser
Computer: ITO01
Description:
Detection of product '{7D0F2155-D7D3-42CE-903F-684ADD77FF89}', feature 'Adobe_Shockwave_Player_' failed during request for component '{3D3697FC-DB90-46D8-9ED4-5D54B4901F62}'
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
If you are logged on as an Administrator, then the computer will immediately attempt to 'repair' the Adobe Shockwave Player installation in order to create the missing folder 'C:\WINDOWS\system32\config\systemprofile\Application Data\Adobe\', which leads to a significant delay in the initialization of the Shockwave content on the web page. If you are logged on as a non-Administrator, the errors will still appear, but the 'repair' operation will fail due to insufficient permissions to create the above folder.
I have done some testing and it seems as if this problem can be easily resolved by removing the code from the installer which tells it to create an empty folder in the 'Application Data' folder called 'Adobe\Shockwave Player 11'. This code seems to be entirely unnecessary, as no files are created inside this folder as part of the installation, and I have removed it successfully from my own copy of the MSI without it causing any issues. I have found some other people who are also experiencing this problem in the following forum post:
http://forums.adobe.com/message/2379350 (post number 8)
and since this 'repair' operation causes all customised registry settings to be reset back to defaults as part of the repair, it would be very helpful if this 'feature' could be removed from future versions.
Secondly, there are a number of registry keys which are created incorrectly by the MSI installer when the above 'repair' operation takes place, which need to be corrected to prevent further issues from occurring:
Under '[HKEY_CLASSES_ROOT\CLSID\{1F3CB77D-D339-49e0-B8E4-FECD6D6F8CB8}\LocalServer32]', the 'default' value is set to the following by the MSI:
C:\WINDOWS\system32\Adobe\SHOCKW~1\SWHELP~1.EXE"
(Please note that there is a double quotation mark at the end of the value, but not at the beginning)
Whereas the executable installer creates the value as follows:
"C:\WINDOWS\system32\Adobe\Shockwave 11\SwHelper_1152602.exe"
According to a forum post (http://forums.adobe.com/message/2379350, post 15), this causes DCOM errors when Shockwave is launched, if the MSI 'repair' has taken place as described above.
The above registry value should be set to the following in the installer's Registry table:
"[INSTALLDIR]Shockwave 11\SwHelper_1152602.exe"
so that the MSI installer works the same as the executable one.
Under '[HKEY_CLASSES_ROOT\TypeLib\{6EF568F4-D437-4466-AA63-A3645136D93E}\1.0\0\win32]', the 'default' value is set to the following by the MSI:
Adobe\SHOCKW~1\SWHELP~1.EXE
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Adobe\Shockwave 11\SwHelper_1152602.exe
Also, under '[HKEY_CLASSES_ROOT\TypeLib\{6EF568F4-D437-4466-AA63-A3645136D93E}\1.0\HELPDIR]', the 'default' value is set to the following by the MSI:
Adobe\SHOCKW~1\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Adobe\Shockwave 11\
Once again, the above registry values should be set to the following in the installer's Registry table to fix the issue:
[SystemFolder]Adobe\Shockwave 11\SwHelper_1152602.exe
[SystemFolder]Adobe\Shockwave 11\
Under '[HKEY_CLASSES_ROOT\CLSID\{166B1BCA-3F9C-11CF-8075-444553540000}]', the 'default' value is NOT SET by the MSI by default:
Whereas the executable installer creates the value as follows:
Shockwave ActiveX Control
This value should be set in the installer's Registry table to fix the issue.
Under '[HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\Shockwave 10\location\common]', the 'default' value is set to the following by the MSI:
Macromed\common\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Macromed\common\
Also, under '[HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\Shockwave 10\location\coreplayer]', the 'default' value is set to the following by the MSI:
Macromed\Shockwave 10\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Macromed\Shockwave 10\
Also, under '[HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\Shockwave 10\location\coreplayerxtras]', the 'default' value is set to the following by the MSI:
Macromed\Shockwave 10\xtras\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Macromed\Shockwave 10\xtras\
The above registry values should be set to the following in the installer's Registry table to fix the issue:
[SystemFolder]Macromed\common\
[SystemFolder]Macromed\Shockwave 10\
[SystemFolder]Macromed\Shockwave 10\xtras\
The MSI installer does not create '[HKEY_CLASSES_ROOT\.dcr]', '[HKEY_CLASSES_ROOT\.dir]', or '[HKEY_CLASSES_ROOT\.dxr]'
Wherease the executable installer creates all three of these keys and populates them all with the following 'default' value:
"Content Type"="application/x-director"
These keys and values should be set in the installer's Registry table to fix the issue.
The MSI installer creates a value under the following registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OptionalComponets\SwDi r]
However this registry key is obviously misspelt (missing an 'n' in 'OptionalComponets') and should read as follows:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OptionalComponents\SwD ir]
This key name needs to be changed in the installer's Registry table to fix the issue (also pointed out in the following forum post: http://forums.adobe.com/message/2379350 (post number 10)).
Under [HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer], the 'Version' value is left blank by the MSI by default:
Whereas the executable installer creates the value as follows:
1152602
This registry value should be set to the correct version in the installer's Registry table to fix the issue.
Finally, the MSI installer creates a number of registry values under the following path:
[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer\Mime Types]
These values are *in addition* to the values created under the following path:
[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer\MimeTypes]
(Note there is no space between 'Mime' and 'Types' in the second key path)
The executable installer *only* creates registry keys under the 'MimeTypes' key, and it seems as if this is the correct formatting for the key (also pointed out in the following forum post: http://forums.adobe.com/message/2379350 (post number 11)).
The unnecessary 'Mime Types' registry keys and values should be removed from the installer's Registry table to avoid any potential issues.
I am sorry that this is such a long list, but it seems as if a number of things have been changed in the transition from 11.5.1.601 to 11.5.2.602, and it would be very helpful if these changes could be put back to how they were before, so that the MSI and the executable installers function in the same way as much as possible.
Message was edited by Borgquite - added 11.5.6.606 update

Have posted an updated version of the MST to my webspace here:
http://homepage.ntlworld.com/minkus/shockwave/shockwave115606mst2.zip
This new version fixes the following issues (changes to this version in bold):
MsiInstaller repair & errors on first run as non-admin (removes 'AppData' directory entries)
DCOM errors once Shockwave is installed (adds double quotes to the beginnning of LocalServer32 value)
Incorrect TypeLib paths in the registry (fixed to use built-in [SystemFolder] property)
Default CLSID description value missing (set to 'Shockwave ActiveX Control', as per the executable installer)
Incorrect Shockwave 10 paths in the registry (fixed to use built-in [SystemFolder] property)
Misspelt 'OptionalComponets' registry key (renamed to 'OptionalComponents')
Missing .dcr, .dir, .dxr Content Type registry values (included in the executable installer)
Fixed incorrect AppID registry key (set to use installer's [VERSION] variable)
Removed 'Launch SWDNLD.exe' shortcut created in Programs subfolder (people don't want this - see here)
I have tested this on my network and it all seems to work fine. Unfortunately my original plan to use the executable installer didn't work out as it does not include the Shockwave 10 compatibility components described here and here, so it looks like I'll have to keep this MST file up to date with the latest versions until Adobe fix the problems themselves...
If you want to see the changes that I have made, load up Adobe's 11.5.6.606 MSI file in Orca, then use Transform / Apply Transform to apply the MST, and look for the entries in green.
Please post any feedback to this thread, and I will try to respond if I can help!
Chris Hill

Please help me with msi installer file for 11.6.8.* as this is our standard version which we use for all machines in our organization

please help me with msi installer file for 11.6.8.* as this is our standard version which we use for all machines in our organization

arai-c wrote:
I have full version of this software but I am not able to install it silently because it always gives Google toolbar pop up which We dont required
arai-c wrote:
the problem is we dont have msi file for 10.6.*.* and hence I am not able to create package for it
I don't understand; two days ago you wrote that you have it, now you don't...?
If you don't have it, then why not deploy the current version 12.1.3.153 - I don't see the point of installing an old, unsecure software version.

Msi-installation: no distribution-script window

Hello together
When installing a simple application a window is showed "running pre-/post-distribution script" with a progress bar. When installing a msi-application it seems that this window isn't being showed at all - only the progress-window during the msi-installation.
I'm running a long task in the pre-distribution script (uninstallation of the previous version). During the runtime of the pre-distribution script nothing is showed, so the user could think that nothing is going on and getting nervous... ;-)
I don't expect to have an output of my distribution script, just the usual distribution-script-window.
Am I doing something wrong, is it a bug or is the only way to prevent this behaviour to create a simple application that is run before the msi-installation?
Using Zenworks 7.0.1.4
kind regards,
Stefan

dtMsgBox is a good idea, but has a strange gui. I would rather place it in the center of the screen in this case than at the top and would like to change its outfit (text, color, ...).
I'd prefer if zenworks would behave in installing msi-packages as it does with simple applications.

Is there Full Version MSI installer package for the last version of Adobe Reader?

Is there Full Version MSI installer package for the last version of Adobe Reader?
Where can we find it?
Thanks.

Hi,
The full MSI installer for the latest 9.5.0 release is available at:
ftp://ftp.adobe.com/pub/adobe/reader/win/9.x/9.5.0/en_US/AdbeRdr950_en_US.msi
However, there is no full MSI installer available for the latest 10.1.2 release, since it wasn't a single dot release. The Reader 10.1.2 installer is available as a MSP file which can be applied onto the Reader 10.1.0 or Reader 10.1.1 installation.
You could also create an AIP for the latest 10.1.2 release, which would give you a single MSI installer along with the extracted files. Please have a look at the below mentioned document for more details on the same:
http://kb2.adobe.com/cps/837/cpsid_83709/attachments/Acrobat_Enterprise_Administration.pdf
Hope this helps.
Thanks
Ankit

Deploying Shockwave version 11.6.1.629 also deploys 10.4.1.34

I have downloaded the latest version of Shockwave redistribituable from a link that Adobe sent me.
I first ran the Adobe Shockwave uninstaller (sw_uninstaller.exe) to make sure all "zombie" files are removed.
I then installed the latest Shockwave version 11.6.1.629 (sw_lic_full_installer.msi) and i noticed the following:
>> Version 11 gets installed in C:\Windows\System32\Adobe\Shockwave 11 but it also installed version 10 into C:\Windows\System32\Macromed\Shockwave 10
So two questions:
1) Why is the installer for 11.6.1.629 installing an older version of shockwave 10.4.1.34? (backwards compatibility?)
2) Is the version of Shockwave 10.4.1.34 that the installer for 11.6.1.629 installs considered Insecure, end of life or patched?
The reason I ask is because the Adobe security bulletin recommends that "Users of Adobe Shockwave Player 11.6.0.626 and earlier versions upgrade to the newest version 11.6.1.629 available here: http://get.adobe.com/shockwave/.
Thanks

1) Why is the installer for 11.6.1.629 installing an older version of shockwave 10.4.1.34? (backwards compatibility?)
It's there (as you noted) for compatibility, and only for Windows, for files created prior to D11
2) Is the version of Shockwave 10.4.1.34 that the installer for 11.6.1.629 installs considered Insecure, end of life or patched?
The reason I ask is because the Adobe security bulletin recommends that "Users of Adobe Shockwave Player 11.6.0.626 and earlier versions upgrade to the newest version 11.6.1.629 available here: http://get.adobe.com/shockwave/.
It is the current secure version of the backwards compatibility components. There is no risk posed by it (unless a new exploit is found)

Silent installation of Shockwave WITHOUT GOOGLE BLOATWARE and WITH ActiveX

I believe a lot of corporate admins are looking for the answer to this question from Adobe...
Q. How do we silently install Shockwave player on our coporate machines WITHOUT installing the GOOGLE BLOATWARE and at the same time ensure that the ActiveX is embedded with the browsers?
At this moment in time we are downloading and installing Shockwave centrally using the SLIM installers because the Full installers install the Google Toolbar bloatware. This is a dark road and Adobe going down this route is in my eyes no different from e-mail SPAM (We don't want it!).
However the issue with this installation is that the users still get prompted to install Shockwave and the associated Google Toolbar bloatware when they vist Shockwave enabled websites, even though Shockwave is successfully listed in Add/Remove/Programs. I believe this is because it's trying to install the ActiveX? This is no good if the users isn't an admin. Perhaps this is because we are using the Slim version?
Anyhow, Adobe, the question still stands....
Q. How do we silently install Shockwave player on our coporate machines WITHOUT installing the GOOGLE BLOATWARE and at the same time ensure that the ActiveX is embedded with the browsers?
P.S. Here's our current command line installation: sw_lic_slim_installer.exe /S _?=C:\WINDOWS\system32\Adobe\Shockwave 11
Thanks,

If you use the MSI installer, you don't get any bloatware.
All you need to do is fill out the licensing info on this site: http://www.adobe.com/products/players/shockwave-player-licensing-distribution.html
Then you can download the MSI installer and just install it with a command like like this: msiexec /i sw_lic_full_installer.msi /qn /log c:\support\logs\applogs\ShockWave_12.0.0.112.log
If you don't use something like SMS or SCCM you could do it through goup policy or whatever mechanism you're using now.
Also, IIRC, the exe downloaders you get from the license distribution page are different from the regular downloads, and also lack any bloatware.
Hope that helps!

Authorware MSI installer needed

Hello,
I'm looking for an Authorware MSI installer (version 7 or
later) which Macromedia provided for distribution once you filled
out the distribution agreement.
I tried to do the same with Adobe, but once you complete the
"Authorware" distribution agreement, you get a link to the Flash or
Shockwave (Director) Players ONLY.
Why is Authorware always the ugly stepchild? Is there an MSI
package out there somewhere?
Thanks!
Silvia

Hi,
The URL: http://www.adobe.com/shockwave/authorware/form/
appears to lead to a dead end with respect to network-wide installation now.
However http://www.adobe.com/shockwave/authorware/form/download/ leads you straight to the download site for the installers, although not MSIs.
'Never mind the form - feel the download!'
Regards
Don

CVI Distribution needs 2 CVI Device Drivers versions

I have an app that I am building a distribution for, it is in CVI 9.0.1, and several versions prior to that.
When I build it, it asks for CVI Device Drivers (CVI 9.0.1) from Feb 2009 and CVI Device Drivers (CVI 8.5.1) from March 2008.
Is there a way I can make this use all the stuff from the latest driver discs (the Feb 2009 disc)?
This is an app that runs on a PXI box, so it has a bunch of drivers for that that and some card in the (I think)!
Solved!
Go to Solution.

Chris,
Getting the distribution to pull from the latest versions (Feb 2009):
Find the driver that is being pulled from the old disc and install the newer version from the Feb 2009 disc.
How do I do this? I opened the Windows Control Panel Add or Remove Programs, and found National Instruments, but that lists a whole bunch of things? I tried to open the installed from the Driver DVD, but it wouldn't while the Add & Remove for NI was opened, so I took screen shots of the list of drivers installed so I had a list of what was installed.
Then, I closed the ADD & Remove for NI, and started the installer from the Driver DVD. I compared that against the list (screen shots) of what I have installed.
I went through all the components from the Driver DVD Installer, and selected "Leave this feature and its subfeatures installed locally"
I had to hunt through the sub-subfeatures to find parts the installer told me were for things not installed (like VS 2003).
Dealing with two discs during the building of the installer:
What you can do is in the driver & components menu (of the edit installer window), you can select "Cache components included from this source" for the distributions it pulls in from the driver cd. That way instead of having to insert discs each time for the build, it will just pull the required source from your hard drive.
What I had done in the past was to copy the driver discs to my hard drive. Then, when it asks for the driver CD or DVD, I would point to the copied folders on my HD. But, the new DVD set is too big for my HD, with the old DVD.
I'm hoping the selection above, to copy things locally, is how to do the caching you mention. I didn't see anything about caching the components, and hoping the language form NI is changed.
I will try the build in a while, it required a reboot, but I didn't want to loose my notes on this so far.
I will update this later today, after I rebuild my app.

MSI install appears as version 11.0 in ARM.

Why is it that after installing the MSI, Add/Remove Programs shows the version as 11.0? The EXE install does not do this. Even after the MSI installation the Registry - HKLM\Software\Adobe\Shockwave 11\..\version lists it as 1150600.

Sorry, I'm in the 10% that did not get the word about the IT change to the FTP Site for Security Reasons.
ftp://ftp.intergraph.com/adobe_1102_1103_files.zip
[ login details removed by forum moderator - this is a public website, do not post confidential information ]

What is the ETA for sw_lic_full_installer.msi 11.6.3.633/v10.4.1.35?

This looks suspiciously similar to thread 2365847 (http://forums.adobe.com/message/2365847) . . .
I'm assuming that when the updated sw_lic_full_installer.msi is released, it will install 11.6.3.633 with the 10.4.1.35 compatibility components (based on the pattern seen over the last half a dozen or so releases). Is there an ETA for its release? I'm using my quick wget script to bang on fpdownload.macromedia.com so as to avoid having to repeatedly download the thing (this way it just grabs the headers notices the Content-Length and Last-Modified values and then sleeps for 60 seconds), but it would be nice to know how long I'm going to have to wait! Things haven't been that bad for the past couple years, so I'm wondering if someone just overlooked something. Or maybe the MSI packager person always goes on vacation in November!
The EXE doesn't install the 10.4.* compatibility components, so if I have to punt to a deploy based on the EXE (which does appear to have been updated), then I'll have to turn around and write an uninstaller for that and then deploy the updated MSI once the MSI releases.

It looks like the explanation might be that the 10.4.1.35 components didn't get compiled until yesterday morning - the dates on those files are 11/8 instead of 11/7 for the 11.6.3.633 components. So the MSI had to wait for the updated compatibility components. In other news, is anyone else noticing that http://www.adobe.com/shockwave/welcome/ isn't working - it's forwarding straight to http://get.adobe.com/shockwave/. It's doing this on the old version as well, so I'm not sure what's up. Would be nice to have a robust way of verifying version numbers from within the player.

ZFDAgent.msi installer locks up during install

I have some laptops (Compaq 6715b laptop and a Macbook Pro) that during the install the zfdagent.msi installer process freezes. This happens on multiple different laptops of the above varieties. Hardware/memory test fine on them. Verified windows xp sp3 is fully updated & OEM drivers are the latest, even tried latest vendor specific drivers for nic/video/etc. Date on the zfdagent.msi is 9/15/09, so it should be the one from ZDM7SP1IR4_HP1.zip. No previous version of zfdagent currently installed.
Seems to work fine on other laptops & desktops, just the above are giving this issue.
Included is a zip of the installer log produced by
Novell Documentation
Any thoughts? Thank you.

Same issue with the zfdagent.msi in ZDM7SP1IR4_HP2!
I notice there are a slew of msiexec.exe running in the background, and if I
kill one of them (usually the smaller of the two run by SYSTEM) the install
completes.
Same story about killing the smaller system msiexec.exe when *uninstalling*.
Also, just tried to replicate this on my xpsp3/ie8/allupdated vmware
workstation 7 vm....it installed without issue as it should.....
"kkbass" <[email protected]> wrote in message
news:[email protected]..
>
> I have some laptops (Compaq 6715b laptop and a Macbook Pro) that during
> the install the zfdagent.msi installer process freezes. This happens on
> multiple different laptops of the above varieties. Hardware/memory test
> fine on them. Verified windows xp sp3 is fully updated & OEM drivers are
> the latest, even tried latest vendor specific drivers for nic/video/etc.
> Date on the zfdagent.msi is 9/15/09, so it should be the one from
> ZDM7SP1IR4_HP1.zip. No previous version of zfdagent currently installed.
>
>
> Seems to work fine on other laptops & desktops, just the above are
> giving this issue.
>
> Included is a zip of the installer log produced by
> 'Novell Documentation'
> (http://www.novell.com/documentation/...a/by1bydm.html)
>
> Any thoughts? Thank you.
>
>
> +----------------------------------------------------------------------+
> |Filename: MSIc3cdf.zip |
> |Download: http://forums.novell.com/attachment....achmentid=3623 |
> +----------------------------------------------------------------------+
>
> --
> --
> http://abeNd.org - Novell News for IT Professionals
> ------------------------------------------------------------------------
> kkbass's Profile: http://forums.novell.com/member.php?userid=9275
> View this thread: http://forums.novell.com/showthread.php?t=392323
>

How can I get a Quicktime update when the update states that an MSI for the previous version is missing

How do you get a new version of Quicktime when it states that the msi for the old version is no longer available?

Download the Windows Installer CleanUp utility from the following page (use one of the links under the "DOWNLOAD LOCATION" thingy on the Major Geeks page):
http://majorgeeks.com/download.php?det=4459
To install the utility, doubleclick the msicuu2.exe file you downloaded.
Now run the utility ("Start > All Programs > Windows Install Clean Up").
In the list of programs that appears in CleanUp, select any QuickTime entries and click "Remove", as per the following screenshot:
Quit out of CleanUp, restart the PC. Now try another QuickTime install. Does it go through properly this time?

MSI installer not working MSI 5.0 Windows 7

Hello I am trying to get MSI installer to work and when I go to install anything that has the Windows Installer Package it opens Notepad in a scrambled message. I have tried numerous avenues to no avail (regedit,copy paste regedit, troubleshooters, sfc/scannow,
command prompt etc.) I tried to choose the file association of MSIexec in System32 and it just opens this
I have tried what is suggested in this forum
https://social.technet.microsoft.com/Forums/windows/en-US/f699e632-54ba-443b-85df-269a7fd6cf1a/windows-installer-not-working?forum=w7itprogeneral and regedit says:
I have tried this http://support.microsoft.com/kb/2438651#reso1 and didn't work
I have tried changing C :\Windows\System32\msiexec.exe /V in regedit and that didn't work
I have searched event viewer and all that's in there is a warning and information of successful installs and uninstalls.
I have tried %windir%\system32\msi.dll version in Command prompt and it says that the system cannot execute the specified program
I am thinking it is just a matter of finding the correct file association that the windows installer can use to install that program but I am unable to find that!
I did a system restore but the only good restore was from earlier today and it still just opens notepad. before I did the restore I went into services and the computer couldn't find the file (windows installer) so I did a restore and now it at least sees
the file and I can start the service.
Can I please get some help fixing this? would uninstalling MSI and re-installing it work? I have been searching forum after forum and nothing has yet worked.
I did a clean install of windows a couple of weeks ago
Microsoft answers gives me thee worst answers a person could come up with.
for a complete list of what my computer is check my bio

Hi ingenuities,
Try importing these reg file under Safe mode.
If you really need this work, I am supposing the only way is to try importing them manually, if any value key is using by process, use process monitor to filter out these processes and shut them down.I monitored values under MSI.package seems like no
value was using by system.
I exported msi.package and patch to text, it is from a clean Windows 7 intallation。
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Msi.Package]
@="Windows Installer Package"
"EditFlags"=hex:00,00,10,00
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\
00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\
32,00,5c,00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,\
00,2d,00,33,00,34,00,00,00
"InfoTip"="prop:System.ItemType;System.Author;System.Title;System.Subject;System.Comment;System.DateModified;System.Size"
"FullDetails"="prop:System.PropGroup.Description;System.Title;System.Subject;System.Category;System.Keywords;System.Comment;System.PropGroup.Origin;System.Author;System.Document.RevisionNumber;System.Document.DateCreated;System.ApplicationName;System.PropGroup.FileSystem;System.ItemNameDisplay;System.ItemType;System.ItemFolderPathDisplay;System.DateCreated;System.DateModified;System.Size;System.FileAttributes;System.OfflineAvailability;System.OfflineStatus;System.SharedWith;System.FileOwner;System.ComputerName"
[HKEY_CLASSES_ROOT\Msi.Package\DefaultIcon]
@="C:\\Windows\\system32\\msiexec.exe,0"
[HKEY_CLASSES_ROOT\Msi.Package\shell]
@="Open,Repair,Uninstall"
[HKEY_CLASSES_ROOT\Msi.Package\shell\Open]
@="&Install"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,36,00,00,00
[HKEY_CLASSES_ROOT\Msi.Package\shell\Open\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,69,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00
[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair]
@="Re&pair"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,37,00,00,00
[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,66,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00
[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser]
@="@shell32.dll,-50944"
"Extended"=""
"SuppressionPolicyEx"="{F211AA05-D4DF-4370-A2A0-9F19C09756A7}"
[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser\command]
"DelegateExecute"="{ea72d00e-4960-42fa-ba92-7792a7944c1d}"
[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall]
@="&Uninstall"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,38,00,00,00
[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,78,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00
[HKEY_CLASSES_ROOT\Msi.Package\shellex]
[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers]
@="Compatibility"
[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers\Compatibility]
@="{1d27f844-3a1f-4410-85ac-14651078412d}"
[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers]
[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers\ShimLayer Property Page]
@="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Msi.Patch]
@="Windows Installer Patch"
"EditFlags"=hex:00,00,10,00
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\
00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\
32,00,5c,00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,\
00,2d,00,33,00,35,00,00,00
"InfoTip"="prop:System.ItemType;System.Author;System.Title;System.Subject;System.Comment;System.DateModified;System.Size"
"FullDetails"="prop:System.PropGroup.Description;System.Title;System.Subject;System.Category;System.Keywords;System.Comment;System.PropGroup.Origin;System.Author;System.Document.RevisionNumber;System.Document.DateCreated;System.ApplicationName;System.PropGroup.FileSystem;System.ItemNameDisplay;System.ItemType;System.ItemFolderPathDisplay;System.DateCreated;System.DateModified;System.Size;System.FileAttributes;System.OfflineAvailability;System.OfflineStatus;System.SharedWith;System.FileOwner;System.ComputerName"
[HKEY_CLASSES_ROOT\Msi.Patch\DefaultIcon]
@="C:\\Windows\\system32\\msiexec.exe,0"
[HKEY_CLASSES_ROOT\Msi.Patch\shell]
@="Open"
[HKEY_CLASSES_ROOT\Msi.Patch\shell\Open]
@="&Apply Patch"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,39,00,00,00
[HKEY_CLASSES_ROOT\Msi.Patch\shell\Open\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,70,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00
Regards
D. Wu

PowerPoint add-in is not working when installed for All Users using msi installer.

Hi All,
I have created PowerPoint add-in using c#-vsto. I have created msi installer to install this add-in with following two options:
1. Just me
2. Everyone
However, add-in is not working properly (Events and custom task panes are not working).
I have created registry key as below
1. for "Everyone" : HKLM\Software\Microsoft\Office\Powerpoint\Addins\MyAdd-in
2. for Just me : HKPU\Software\Microsoft\Office\Powerpoint\Addins\MyAdd-in
But when I set InstallAllUsersVisible property to False (When add-in is installed only for current user ), then add-in works fine for current user.
Please let me know if anything is missing!!!
Thanks

Hi,
This is the forum to discuss questions and feedback for Microsoft Office, the issue is more related to develop the add-in, you'd better post your question to the MSDN forum for VSTO
http://social.msdn.microsoft.com/Forums/en-US/home?forum=vsto&filter=alltypes&sort=lastpostdesc
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
George Zhao
TechNet Community Support

Distribution sw_lic_full_installer.msi installs two Shockwave Versions

Similar Messages

Maybe you are looking for