When you install a Setup program that is based on Windows
Installer Setup technology, you may receive the following Windows Installer
This installation package could not be
opened. Verify that the package exists and that you can access it, or contact
the application vendor to verify that this is a valid Windows Installer
If you have a verbose log file of the Setup program, the
following information also appears at the end of the log file:
MSI (c) (6C:54): Package name extracted from package
path: 'somesetup.msi' MSI (c) (6C:54): Could not create LFN path for package:
'H:\tmp\apps\coreapps\somesetup\somesetup.msi' This installation package could
not be opened. Verify that the package exists and that you can access it, or
contact the application vendor to verify that this is a valid Windows Installer
package. MSI (c) (6C:54): MainEngineThread is returning 1619.
This behavior occurs if both of the following conditions
- You install the program from an NTFS file system-formatted
volume where the user has been denied the List Folder/Read
Data permissions to the installation folder.
- You try to install the program on a computer on which
version 2 of the Windows Installer with the Windows Installer DLL file, Msi.dll
version 2.0.2600.0, is installed.
NOTE: Windows Installer with Msi.dll version 2.0.2600.0 is included
with Microsoft Windows XP and is also available as a redistributable file for
download for Windows 2000 and Windows NT 4.0.
This problem occurs because of a bug in the Windows Installer
version 2.0 engine.
this problem, obtain the latest service pack for Windows XP. For additional
information, click the following article number to view the article in the
Microsoft Knowledge Base:
How to Obtain the Latest Windows XP Service Pack
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note
If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note
The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
The English-language version of this fix should
have the following file attributes or later:
Date Version Size File name
11-Feb-2002 2.0.2600.28 1,994,240 bytes Msi.dll
Use one of the following methods to resolve this issue.
Update to Service Pack 3
This issue is resolved when you update Windows 2000 with Service
Pack 3 (SP3). SP3 for Windows 2000 includes Windows Installer 2.0 with Msi.dll
version 2.0.2600.1, which resolves this issue.
For additional information about how to obtain
Service Pack 3 for Windows 2000, click the article number below to view the
article in the Microsoft Knowledge Base:
How to Obtain the Latest Windows 2000 Service Pack
Update Windows Installer
Update Windows with the latest version of Windows Installer. To
obtain the latest version of Windows Installer, visit the following Microsoft
On the directory in which the .msi file is located, and in
all subdirectories, assign List Folder/Read Data
permissions to the user who starts the Setup program.
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was first corrected in Windows XP Service