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

• Changed type ingenuities Saturday, February 28, 2015 10:43 PM
• Edited by ingenuities Saturday, February 28, 2015 11:19 PM

a couple of suggestions;

A) check the current file-type-associations, here are mine (64bit Win7);

C:\Users\Don>assoc .msi
.msi=Msi.Package

C:\Users\Don>ftype msi.package
msi.package="%SystemRoot%\System32\msiexec.exe" /i "%1" %*

B) from an elevated CMD console (run as admin), try msiexec /regserver

oh my god thank you for responding I have been bouncing off the walls. not wanting to go through days and days weeks even of re-install.

my OS is windows 7 professional 64-bit

I entered C:\Users\Bill>assoc .msi in the search and it didn't find anything

I entered C:\Users\Bill>ftype msi.package
msi.package="%SystemRoot%\System32\msiexec.exe" /i "%1" %* in the search and it did not find anything

can you be a little more specific as to where I find that?

ok I went to choose default programs and here is what I see 

I went to what is shown in your screen shot and this is what I see in system32

it doesn't appear the same as yours for some reason because it doesn't have the .exe

I don't know how this happened all I know is that it is what it is and I have to fix it. I have ran the regserver and the command prompt went back to its enter state when I entered msiexec /regserver

• Edited by ingenuities Sunday, March 01, 2015 12:21 AM

I tried your default program association and went to install a program and it only opened this

would going into system32 and renaming MSIExec to MSIExec.exe work?

here is how the default programs now look

when I go to install a program it opens that first screenshot windows installer identification.

• Edited by ingenuities Sunday, March 01, 2015 12:57 AM

I wonder if copying the MSIExec.exe from another computer would work?

I went to my other computer a laptop with windows 7 home premium and this is what that MSIExec looks like

so something is apparently wrong with the MSIExec on my desktop (the effected computer)

• Edited by ingenuities Sunday, March 01, 2015 1:38 AM

I tried to rename the MSIExec to MSIExec.exe and this is what happened

it wont let me rename it.

I have previously disabled "hide extensions for known file types", so that's why my screenshot shows the .exe extension - this shouldn't matter at all for fixing your problem, so don't worry about that difference.

when you execute: assoc .msi
if yours isn't coming back with the same as mine, then you do have a file-association misconfiguration.

there also needs to be an equivalent file-association record, for the .msp, because .msi is for installing, and .msp is for patching/updating.

neither of the .msi / .msp, should be associated with Notepad - that's where your problem is coming from.

I had hoped that msiexec /regserver would have re-registered the associations for you (but maybe it doesn't :(

you can try this method to manually re-associate:

assoc .msi=Msi.Package

then,

assoc .msp=Msi.Patch

[it seems that you have more than one problem, (1) the missing parameters for .msi which need to be there in the file-type-association for msiexec.exe, and (2) similar configurations needed for .msp (not the notepad ones you seem to h

can you described how I manually re-associate those please?

So, just to re-confirm, mine looks like this, and we need to get yours looking the same.
These commands don't change anything, they only query and display your current setup:

C:\Users\Don>assoc .msi
.msi=Msi.Package

C:\Users\Don>assoc .msp
.msp=Msi.Patch

C:\Users\Don>ftype msi.package
msi.package="%SystemRoot%\System32\msiexec.exe" /i "%1" %*

C:\Users\Don>ftype msi.patch
msi.patch="%SystemRoot%\System32\msiexec.exe" /p "%1" %*

I tried to rename the MSIExec to MSIExec.exe and this is what happened

it wont let me rename it.

No need to try to do that..

can you described how I manually re-associate those please?

you can try this method to manually re-associate:

assoc .msi=Msi.Package

then,

assoc .msp=Msi.Patch

I have tried to search these and am not finding those in search and tried to enter those in command prompt and am not finding what you are describing. in C:\users\Bill there is no >assoc .msi in C:\Users\Bill there is no >ftype msi.package in C:\users\Bill there is no >ftype msi.patch

the only place I see MSIExec is in C:\Windows\System32

• Edited by ingenuities Sunday, March 01, 2015 2:42 AM

I have them manually re-associated and it currently looks like this

But when I go to start a program installer this is all I get

I have tried to search these and am not finding those in search and tried to enter those in command prompt and am not finding what you are describing. in C:\users\Bill there is no >assoc .msi in C:\Users\Bill there is no >ftype msi.package in C:\users\Bill there is no >ftype msi.patch

the only place I see MSIExec is in C:\Windows\System32

Hmm.

Click your Start button.
Type: CMD
Right-click the offered search result, and choose "Run as administrator"
[you may need to accept the UAC consent prompt, depending on your settings]
[the CMD console prompt window will open up]

Type:
assoc .msi=Msi.Package
Press Enter

Then, type:
assoc .msp=Msi.Patch
Press Enter

ok done here is what happened

I have tried installing the program and am getting the same windows installer V 5.0.7601.17514 MSIExec /Option etc. command prompt window. which has me thinking what happens if I type MSIEXEC/ u or /m or /s all registry command prompts shown in the windows installer:

• Edited by ingenuities Sunday, March 01, 2015 3:17 AM

ok done here is what happened

I have tried installing the program and am getting the same windows installer V 5.0.7601.17514 MSIExec /Option etc. command prompt window. which has me thinking what happens if I type MSIEXEC/ u or /m or /s all registry command prompts shown in the windows installer:

ok, try this troubleshooter/fixit:
http://support.microsoft.com/mats/Program_Install_and_Uninstall

I have tried that several times, so I just tried it again to see if something changed but the problem is it lists everything already installed and not the things I am trying to install. thanks but I think we need to keep trying.

• Edited by ingenuities Sunday, March 01, 2015 5:08 PM

I have tried that several times, so I just tried it again to see if something changed but the problem is it lists everything already installed and not the things I am trying to install. thanks but I think we need to keep trying.

Hmm, ok, it might be time to do some registry diving.

Can you dump out your current registry data for the related key and post here so I can check it?

(open a CMD via run-as-admin)

reg query HKCR\Msi.Package /s > c:\msireg.txt

That should create the msireg.txt file, which you can paste/post back here for review.

Here is the result of what was recommended. I copy/pasted it to CMD Prompt.

Here is the result of what was recommended. I copy/pasted it to CMD Prompt.

reg query HKCR\Msi.Package /s > c:\msireg.txt

ok thanks that went through. Sorry, I didn't know I had to add the reg query also. here is what it says:

HKEY_CLASSES_ROOT\Msi.Package
    (Default)    REG_SZ    Windows Installer Package
    EditFlags    REG_BINARY    00001000
    FriendlyTypeName    REG_EXPAND_SZ    @%SystemRoot%\System32\msimsg.dll,-34
    InfoTip    REG_SZ    prop:System.ItemType;System.Author;System.Title;System.Subject;System.Comment;System.DateModified;System.Size
    FullDetails    REG_SZ    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
    (Default)    REG_SZ    C:\Windows\system32\msiexec.exe,0

HKEY_CLASSES_ROOT\Msi.Package\shell
    (Default)    REG_SZ    Open,Repair,Uninstall

HKEY_CLASSES_ROOT\Msi.Package\shell\Open
    (Default)    REG_SZ    &Install
    MUIVerb    REG_EXPAND_SZ    @%SystemRoot%\System32\msimsg.dll,-36

HKEY_CLASSES_ROOT\Msi.Package\shell\Open\command
    (Default)    REG_SZ    NOTEPAD.EXE "%1"

HKEY_CLASSES_ROOT\Msi.Package\shell\Repair
    (Default)    REG_SZ    Re&pair
    MUIVerb    REG_EXPAND_SZ    @%SystemRoot%\System32\msimsg.dll,-37

HKEY_CLASSES_ROOT\Msi.Package\shell\Repair\command
    (Default)    REG_EXPAND_SZ    "%SystemRoot%\System32\msiexec.exe" /f "%1" %*

HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser
    (Default)    REG_SZ    @shell32.dll,-50944
    Extended    REG_SZ   
    SuppressionPolicyEx    REG_SZ    {F211AA05-D4DF-4370-A2A0-9F19C09756A7}

HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser\command
    DelegateExecute    REG_SZ    {ea72d00e-4960-42fa-ba92-7792a7944c1d}

HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall
    (Default)    REG_SZ    &Uninstall
    MUIVerb    REG_EXPAND_SZ    @%SystemRoot%\System32\msimsg.dll,-38

HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall\command
    (Default)    REG_EXPAND_SZ    "%SystemRoot%\System32\msiexec.exe" /x "%1" %*

HKEY_CLASSES_ROOT\Msi.Package\shellex

HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers
    (Default)    REG_SZ    Compatibility

HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers\Compatibility
    (Default)    REG_SZ    {1d27f844-3a1f-4410-85ac-14651078412d}

HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers

HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers\ShimLayer Property Page
    (Default)    REG_SZ    {513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}

• Edited by ingenuities Monday, March 02, 2015 4:51 PM

ok thanks that went through. Sorry, I didn't know I had to add the reg query also. here is what it says:

<....>

HKEY_CLASSES_ROOT\Msi.Package\shell\Open\command
    (Default)    REG_SZ    NOTEPAD.EXE "%1"

Ok, so there's your problem - the \shell\Open\command, is set to Notepad instead.

Mine looks like this, and so should yours. Edit yours to be the same as mine:

HKEY_CLASSES_ROOT\Msi.Package\shell\Open\command
    (Default)    REG_EXPAND_SZ    "%SystemRoot%\System32\msiexec.exe" /i "%1" %*

Ok I did this the best I could. I found the key in Regedit and tried to delete the old key with the notepad configuration but it wouldn't let me so I went and added a new key and so now it looks like this

I noticed that the MSI.Patch is also set to open notepad.

and went to try it after restarting the computer and it still opens this:

if you look at the above screenshot you will see that MSIExec/ u, and /m supposedly repair the registry for this. is that possibly an answer to the problem?

• Edited by ingenuities Monday, March 02, 2015 10:03 PM

Ok I did this the best I could. I found the key in Regedit and tried to delete the old key with the notepad configuration but it wouldn't let me so I went and added a new key and so now it looks like this

I noticed that the MSI.Patch is also set to open notepad.

and went to try it after restarting the computer and it still opens this:

if you look at the above screenshot you will see that MSIExec/ u, and /m supposedly repair the registry for this. is that possibly an answer to the problem?

the screenshot (showing the msiexec.exe usage guide) isn't referring to registry entries for msiexec, it's referring to registry entries contained within an MSI database file.

Here's another approach you could try.

Remove the dodgy fake default entry you created, since that isn't helping any.

On your other computer (which we assume is just fine), open regedit, and navigate to the HKCR\Msi.Package key.
Right-click that Msi.Package key, and choose Export.
Export to a file (.reg file).
Do that again, for the HKCR\Msi.Patch key, into another .reg file.
Copy the .reg files onto a USB stick, and then take that USB stick to your problem machine.
On your problem machine, open regedit and navigate to HKCR\Msi.Package
Highlight the Msi.Package key, and press F2, and rename the Msi.Package key to be Msi.Package.bak

Do the same rename task on the Msi.Patch key.

This gives you a backup position, just in case.

Now, go to the USB stick and double-click each of the exported .reg files - this will merge the settings from the .reg files, into your problem computer registry.

The theory here is that the reg keys will be reinstated to "known, working" values.

Oh My god it works!. at first I went to test it and it just opened the MSIExec.exe user guide.

then I thought about it and thought I am going to try open with again: and sure enough there is the windows installer that didn't show up earlier I selected that and it works!!

I didn't do the back up but I did successfully import both .reg file from the other machine.  here is what the registry looks like now:

here is what I imported first the MSI.package:

[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

Then the MSI.patch:

[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

Thank you so much DonPick, thank you for your patience, and your expertise! 

• Edited by ingenuities Tuesday, March 03, 2015 7:41 PM

it looks though I have another problem. when I try to associate the windows installer to always use the windows installer it is greyed out.

For reasons I don't know the icon for the windows installer in associate programs has the AMD Catalyst install manager icon.

do you know how I am supposed to fix this? because every time I go to install something now I have to right-click and choose open with and then windows installer. that works but if I want it to continue to just open windows installer automatically there is something else that needs to be done. do you know what that is?

• Edited by ingenuities Wednesday, March 04, 2015 4:23 AM

it looks though I have another problem. when I try to associate the windows installer to always use the windows installer it is greyed out.

For reasons I don't know the icon for the windows installer in associate programs has the AMD Catalyst install manager icon.

do you know how I am supposed to fix this? because every time I go to install something now I have to right-click and choose open with and then windows installer. that works but if I want it to continue to just open windows installer automatically there is something else that needs to be done. do you know what that is?

Hmm, there is still something not right with the MSI associations then...

In reviewing your earlier replies, I can see that you have only shown the export data for the shell\open\command data.

Did you export the complete Msi.Package keys or only the shell\open\command sub-keys ?

The complete Msi.Package keys, should include the icon and all other important keys/data.

yeah I only exported the MSI.Package and MSI.Patch keys from the shell\open\command sub keys, that is all that was in there. not sure where the complete MSI.Package keys are.

• Edited by ingenuities Wednesday, March 04, 2015 6:18 PM

yeah I only exported the MSI.Package and MSI.Patch keys from the shell\open\command sub keys, that is all that was in there. not sure where the complete MSI.Package keys are.

I've exported Msi.Package and also Msi.Patch from my Win81.64bit machine for you here
https://onedrive.live.com/redir?resid=6B44AD76D9AEEDFE!6692&authkey=!ACfSpgX8g9TNz0I&ithint=folder%2creg

If you download those, then double-click the downloaded files (one at a time), that should merge in the registry settings from mine to yours, hopefully that works for you.

thank you for responding here is what happened when I tried to import it

I have to go to class I will try more when I get back. it appears I have to turn MSI off in the windows task manager.

do you know how to find out exactly what I need to turn off to get this to work. I have tried going into MSConfig and disabling windows installer and then importing the registry and am still getting the error that some keys are open by the system or other processes.

do you know how to find out exactly what I need to turn off to get this to work. I have tried going into MSConfig and disabling windows installer and then importing the registry and am still getting the error that some keys are open by the system or other processes.

reboot the PC.

open task manager and show processes from all users.

if msiexec is a running process, watch it for a minute to see if it is idle or busy. if busy, watch until it becomes idle.

kill the process.

then merge the reg file again.

or, you could try booting in safe mode - that should assist with (temporarily) not-starting unnecessary processes.

ok here is what I have tried.

I have tried to exit out the programs that might have the keys open but am unable to find that one or two.

-opening Msconfig go to services uncheck windows installer in normal mode restart the computer. windows installer is disabled import the reg file and I am still getting that message. open keys.

-restarted the computer went into safe mode no networking and tried to import the reg file and still got the open keys message.

-opened msconfig in safe mode and went into diagnostic mode (which disables everything) and restarted the computer. in diagnostic mode I imported the reg file and again got the open keys message again. I am not sure what else I can do.

I am back in normal mode for now.

Is this relevant?

when I go to install WinZip Courier everything installs but I get this error and courier doesn't work. so I uninstalled it.

• Edited by ingenuities 4 hours 56 minutes ago

Is this relevant?

when I go to install WinZip Courier everything installs but I get this error and courier doesn't work. so I uninstalled it.

No, I don't think that's relevant.
ADX Loader is related to MS Office add-ins, I think.

I am not sure what else I can do.

I am also not sure of the next best step. I don't have these "keys are open" errors on my machine.

There is probably deeper process monitoring etc possible, but that's too difficult to do when not at the computer.

Perhaps you can seek some local technical assistance (in person), or, remote assistance from MSFT support ?

As a last resort, reinstall Windows ?