MSI Installer Cache & "Persist in Client Cache"

Hello,
I'm predominantly using the Application Model and just a few Packages. I'm noticing on Software Deployments that the Downloaded Content eventually gets purged and then when a user goes to launch the software it states that it cannot find the reference
MSI within CCMCache. I talked to some other people and they said that Packages would automatically put the cache in the Windows Installer Database to eliminate that issue and weren't sure how the Application Model handled this. Is the only way
for me to fix this to set the application to 'Persist in Client Cache?' If so, I have a lot of things to redo.
Looking for advice and how this is supposed to work under both the Application and Package Model.
Thanks!

As long as you supply the product code at the bottom of the Programs tab on the Deployment Type, then the same thing will happen for applications. Essentially, the client agent adds a location from the DP to the source path for the MSI to enable
repairs.
Jason | http://blog.configmgrftw.com
Hmm. These were standard MSI's that were imported so all of those codes should have imported in correctly? Not sure why I'd be seeing issues from clients.

Similar Messages

Cannot update, repair, uninstall itunes in Windows7-64bit. Have itunes v10.5.0.142 installed but is missing "itunes64.msi" file . Need copy of itunes64.msi file which is located in the file folder ProgramData\Apple Computer\Installer Cache. Thanks.

Cannot update, repair, uninstall itunes in Windows 7-64bit. I have itunes version 10.5.0.142 installed but is missing the "itunes64.msi" file. Would like to obtain a copy of this file which is located in the file folder ProgramData\Apple Computer\Installer Cache. If someone could supply a copy of this file on this site, it would really be appreciated. Thanks in advance.

See Troubleshooting issues with iTunes for Windows updates for general advice.
If you want to install an older version of iTunes see http://support.apple.com/downloads/#itunes or OldApps.com.
tt2

Deleting "Installer Cache" Software for iTunes, Quicktime & Safari

Can Old "Installer Cache" Software for iTunes, Quicktime & Safari be deleted?

I know the university has updated its DNS server addresses this month, but since I am using DHCP nothing is supposed to change and a test indicated that I am connected to the new servers.
It sounds like a DNS problem, all right. It can't hurt to put these servers at the top of your list:
208.67.222.222
208.67.220.220
See it that makes a difference, it'll only take a minute.

Installer Cache error occurred.

I want to update to the newest itunes,while i am installing , there is the message said (An error occurred while attempting to create the directory:C:\ProgramData\apple\installer cache ,and i cant do anything.

That one's consistent with disk/file damage. The first thing I'd try with that is running a disk check (chkdsk) over your C drive.
XP instructions in the following document: How to perform disk error checking in Windows XP
Vista instructions in the following document: Check your hard disk for errors
Windows 7 instructions in the following document: How to use CHKDSK (Check Disk)
Select both Automatically fix file system errors and Scan for and attempt recovery of bad sectors, or use chkdsk /r (depending on which way you decide to go about doing this). You'll almost certainly have to schedule the chkdsk to run on startup. The scan should take quite a while ... if it quits after a few minutes or seconds, something's interfering with the scan.
Does the chkdsk find/repair any damage? If so, can you get an install to go through properly afterwards?

Instller cant make "C:\ProgramData\Apple Computer\Installer Cache\Quicktime

My girlfriends computer (Inspiron 1440; Windows 7) was running iTunes fine for awhile. the upon an update it started to get the 2330 error. a disk check worked once, but it soon reverted back to the 2330 error. so here we were unable to install or uninstall iTunes + QT. upon the advice of another post we got a 3rd party uninstaller (Revo Uninstall Pro) and successfully (it seems) uninstalled iTunes + QT. then when we tried to run the installer again we received this error: "an error occurred while attemping to create the directory: "C:\ProgramData\Apple Computer\Installer Cache\Quicktime"<version#>. I'm no noob when it comes to trouble shooting computers and using the internet and forums for problem solving (however i haven't been in the windows world since XP), but i'm finding little to no info on this issue. Some of the only things i have found suggest permission issue, but it's running under the Admin with the UAC off.
Any help would be GREATLY appreciated on this seemingly obscure issue.
thanks in advance

"an error occurred while attemping to create the directory: "C:\ProgramData\Apple Computer\Installer Cache\Quicktime"<version#>.
I'm suspecting disk/file damage again, as per the the 2330, rocklebee.
If a disk check isn't cleaning that up, the following workaround might help.
First we'll need to adjust some view settings. (I think ProgramData might be hidden by default on Windows 7.)
1. From the Start menu, click Open.
2. In the Organize menu, click Folder and Search Options.
3. Click the View tab.
4. In the "Advanced settings" pane under "Hidden files and folders" make sure that the "Show hidden files and folders" option is selected.
5. Click OK.
Now, in Computer open your C drive.
Open the ProgramData folder.
Open the AppleComputer folder.
Attempt to rename the Installer cache folder *Installer CacheOLD.*
If you can rename her, reboot the PC and try another install. Does it go through properly again?

Old versions in Installer Cache

While cleaning up my Dell Laptop, I noticed in Documents and Settings/All Users/Application Data .... an Apple Computer/Installer Cache directory. It is > 500 Mb of old iTunes/QuickTime/Safari information. Can I safely clean this out? Do I need to just keep the current version of each of these programs? It's an old laptop with a small disc and I could really use space.
Thanks.

I've deleted them from my PC.

MSI Installation - persistent problems

This is an issue that has been going on for many versions. I tried to draw Adobe's attention to it many times, many other users also had this problem, but now there's reader 11 and it's still the same.
In the MSI installation the location of PDF icon is hardcoded as [windowsfolder]installer\[productcode]\pdffile_8.ico . If the installation is performed per-user, such as by GPO, then this location is invalid, and the result is generic Windows icon of the PDF files.
I wonder, why is this not addressed?
More generally speaking about this installation, the hardcoded icon is gross violation of best Installer practices, and more specifically, this approach makes impossible adversiting of Reader and install-on-demand. The extension .pdf should be advertised in the installation by normal Installer means. All this, as I understand, because Adobe wants to give the users a choice of Acrobat vs. Reader being the default handler of extension pdf - for those users who have both. Given the fact that percentage of such users is small, and that even among them the percentage of those who will actually appreciate and use this choice is negligible, I wonder, is it worth to sacrifice advertising, install-on-demand, and even self-repair to this choice?
In my records I see that I tried to have this issue addressed back in 2009, and I received the following reply from Adobe's Chief Software Architect Tom Malloy:
===========
Vadim,
I just want to let you know that I forwarded your message to Acrobat quality engineering. They confirm that they know of this shortcoming. It is something we would like to fix but we have not made a decision to prioritize the engineering required, at least yet.
My QE contact is checking with Acrobat program management to see if there is any additional information. If I hear anything more that is worth sharing I will pass it along.
Thanks for making the effort to get through to me. Sorry I can't give you a firm commitment regarding when we will make this better.
Regards,
Tom Malloy
Sr. Vice President
Chief Software Architect
Advanced Technology Labs
Adobe Systems, Inc.
===========
So, 3 years ago Adobe was already aware, but still haven't found the time to prioritize the engineering. Ironically, apparently there was no shortage of engineering talent to implement all these hardcoded workarounds and thus to break the installation standards.
Vadim Rapp

Thatz Y... I won't switched to XP until it has really settle down...
lambethduke, I know where you've got things wrong and its a common mistake as I have accidentally did it myself before ... You must have direct right click on your Display adapter driver and un-install... This will cause the screen to go blank during startup whenever you wanna install the drivers again, though you may be able to see part of the windows starting up... Next time, juz un-install the driver by double clicking on the driver and inside the profile click on un-install and this problem will never exist to you anymore...
All the Best... :D!!!

Download MSI Installer Link downloads 10.3.181.34 not 10.3.183.5

Hi,
When going to http://www.adobe.com/products/flashplayer/fp_distribution3.html
Click on "Download MSI Installer" for Windows - Internet Explorer, it downloads OK but installs version 10.3.181.34.
The "Download EXE Installer" is the correct latest version 10.3.183.5 but I would like the msi please, Can you update the download link?
Thanks

The link contains the 10.3.183.5 MSI installer.
Are you inside a corporate firewall? Make sure that any download caches are cleared, so you will not get an old cached file.

MSI installer closes with error 1327, Invalid drive on Win 7 Ultimate when My Documents is moved to a network drive

I have several computers with Windows 7 Ultimate installed here at the Pioneer Library System. We have ~20 workstations running XP Pro on a Active Directory domain and are planning on rolling out Windows 7 this fall. I am running Windows 7 to test our programs
(have since RC1) but I am running into an issue when installing software.
The problem I am running into is that when I try to install any program that uses the MSI installer on Windows 7 , it fails with a 1327 error at the point where it is preparing to install and says "Invalid Drive H:\".
All the users in our domain have the "Home Folder" on their active directory profile set to
H:\ (which is mapped to \\PrimaryDC\user$ in the same place). We have also moved the
C:\Users\user\Documents folder to H:\ so as to keep all documents on the server where they get backed up regularly.
If I move "Documents" back to C:\Users\user\Documents the MSI installer works fine. When I look into the registry as suggested in
this thread I found that in "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders " and in "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell
Folders " the key "Personal" points to "H:\".
But, H:\ is a valid connected network drive. Installing from the same account on an XP computer with
C:\Documents and Settings\user\My Documents moved to the H:\ drive works fine.
I have tried setting up another 7 machine and get exactly the same results on it.
Is there a workaround for this besides creating a admin account that does not have Documents mapped to the network drive
H:\ to use for installing programs?
Thanks
Aaron Z
PLS

I do not have the option with some of these files to pass parameters to the MSI installer. For example, if I download the Acrobat Reader installer from http://ardownload.adobe.com/pub/adobe/reader/win/9.x/9.3/enu/AdbeRdr930_en_US.exe and run AdbeRdr930_en_US.exe
it extracts the MSI file to C:\Users\USER\AppData\Local\Adobe\Reader 9.3\Setup Files and then runs it.
To reproduce this an a Windows 7 computer (does not have to be on a domain):
Prep Work:
Create a user (test1)
Create a folder on the root of C (C:\Test)
Set permissions on C:\Test to allow the test1 user to have full access to it
Share the C:\Test folder as test1 (again, set the permissions to allow the test1 user full access)
Set the "Home Folder" for the test1 user connect to Z: and point that to \\127.0.0.1\test1
Login as test1
Check that you have Z:\ mapped and that it works
Check that it works:
Install Acrobat Reader 9.3 from the link above
Note that it works
Uninstall Acrobat Reader 9.3 using "Programs and Features"
Break it:
Login as test1
Check that you have Z:\ mapped and that it works
Go to C:\Users\test1
Right click on the Documents folder and click on properties
Click on the Location tab
Click on "Browse" and select the Z drive
Allow Windows to move the files to the new location
Check that it is broken:
Check that you have access to the new Documents folder at Z:\
Install Acrobat Reader 9.3 from the link above
Note that it extracts itself to C:\Users\test1\AppData\Local\Adobe\Reader 9.3\Setup Files
and runs the MSI installer from there
Note that after the MSI installer is started it pops up an error saying Error: 1327, Invalid drive Z:\.
I also see this with various other install programs (VMWare vSphere Client, VMWare Player and Kaspersky Antivirus for example)
Is there any reason why this should not work? Is there something that I should be doing differently?
Thanks
Aaron Z

Latest Skype .msi installer

I would greatly it if someone could please send me a direct link to download the latest version of the .msi installer for Skype.
I need to update Skype on my Windows 7 Professional 64 bit system and also on my Windows 8.1 Professional 64 bit system. (With regard to the latter, Windows Update offered the update but it failed to install 3 times, and I was unable to find a link to download the standalone version).
Thanks and regards,
Roy
Solved!
Go to Solution.

nedim.samp wrote:
i have problem for skype , i cannot install / uinstall skype , please help me
ScreenShot: http://prntscr.com/4moz9p
Please send me answer on e-mail : [e-mail removed for privacy and security]
Please help me fast
sorry for my bad english
Try to clear any currently installed version using this MS Fix It:
http://support.microsoft.com/mats/Program_Install_and_Uninstall/en
If this will still not help, then try this:
http://community.skype.com/t5/Windows-desktop-client/Impossible-to-install-v6-13-0-104-Error-1603/m-...
Be aware that if you want to install the currently latest 6.20.0.104 version, then you should use this msi-installer link in order to extract the Skype.exe and Login.cab files:
http://download.skype.com/msi/SkypeSetup_6.20.0.104.msi

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

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

MSI installation returned 1625 This installation is forbidden by system policy (BizTalk IAAS Azure)

Hello guys,
I'm trying to install the developer tools on a azure VM (BizTalk standard image). I try to go to the folder where the installation files are, and after run setup and selecting the developer tools, the installer fails. When I look at the log file I have this
error:
MSI installation returned 1625 This installation is forbidden by system policy
Any idea that could help?
Thanks

Hi Ricardo,
Please try bellow steps taken from
this similar thread. Hope it will work for you.
Click Start -> Control Panel
Open Administrative Tools
Open Local Security Settings
Click Software Restriction Policies
If no software restrictions are defined, right click the Software Restriction Policies node and select New Software Restriction Policy
Double click Enforcement
Select "All users except local administrators"
Click OK
Reboot the machine
If this answers your question please mark as answer. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Automaticly run Program\Script After and MSI Installation

Hi All,
Today I started looking into the use of Application Model in SCCM 2012.
It was easy to create an application by using the import MSI function, which automatically created the application, deployment type and detection rule. But I'm struggling with how to run a script afterwards, when the MSI installation was successful.
I've looked into creating 2nd deployment type making the first deployment type as it's dependency, but it's mandatory that I also need to make an detection rule. And this is where I'm stuck ass the detection rule I want to have the same as
for the first deployment type which will make it impossible to run because the condition will be evaluated ass already installed.
Is there a way to avoid the detection rule? If not is if possible trigger something after the first deployment type based on the errorlevel after the MSI installation.
My goal is to write a regkey somewhere in HKLM\Software\<company name> after an successful installation of an application. This location we've included in our hardware inventory for reporting purposes.
Any suggestions to achieve this goal are welcome .
Regards,
Daniel

I've resolved it with using the AddDploymentTypebyMISInstallerAuto function from the Add-CMDeployment command and provided an InstallationProgram parameter to override the default InstallationProgram.
The comman-line looks like
Add-CMDeploymentType
-ApplicationName <Name>
-AutoIdentifyFromInstallationFile
-ForceForUnknownPublisher $True `
-InstallationFileLocation
<MSI
File> -MsiInstaller
-DeploymentTypeName
Test1 –InstallationBehaviorType InstallForSystem
-InstallationProgram
< Custom
Script>
In this way I have the detection based on the MSI GUID and the ability to use a wrapper script.

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 Installer Cache & "Persist in Client Cache"

Similar Messages

Maybe you are looking for