• Wise Unpacker Gui V0.12 Download
• Wise Unpacker Gui Download
• Wise Unpacker Gui
• Wise Unpacker Guide

C# port of the Wise installer extractors E_WISE and Heuristic Wise-Setup Unpacker. This currently compiles as a library so it can be used in any C# application. For an example of usage, see BurnOutSharp.

TDU2: Unpacker GUI This is a completely rewritten version of my DLC2 unpacker which somehow disappeared from this board. Anyway, it does the same job as the previous one but has friendly user interface. Features: Unpacks the game into any directory (ability to run unpacked or unmodified game at a. Unpack game audio Wwise files (pck, bnk). Contribute to Vextil/Wwise-Unpacker development by creating an account on GitHub.

Of note, the majority of the code implementation stems from HWUN. The exception to this is the non-heuristic detection of archives based on the signatures detected by E_WISE. This should provide a stable combination of extraction for any unknown variants.

Contributions

Contributions to the project are welcome. Please follow the current coding styles.

• Wise Unpacker Gui Downloads For Pc; Beta 4 is planned to be the last beta version before the final release. It adds support for several new installer types, a new context menu entry 'Extract to last used directory', improved user interface, a statistics display and multiple bugfixes.
• Wise Unpacker Gui V0.12 Main features: - Recursive scanning of folders and sub-folders for archives - Multi part split archive support. Attribute can only attach to interface or abstract class. A rare insufficient precision of ruler ticks was fixed. If you want to configure default typeless resolver, you can set by Message.
• Multi Unpacker is a free tool that can recursively extract multiple RAR or ZIP archives. Main features: - Recursive scanning of folders and sub-folders for archives - Multi part (split) archive support. Nested archive handling (recursively extract archives that were packed in other archives). Choose whether to replace or to keep existing files.

jsMSIx.exe - Simple MSI/MSM Unpacker Program

jsMSIx.exe is a small program with no installation required and no extra files needed other than normal system files that are pre-installed on nearly all Windows PCs. No muss, no fuss. Just run jsMSIx.exe, browse for an MSI file, and unpack it. jsMSIx.exe can also provide MSI information, listing files and Registry settings in the MSI without unpacking it. This is the most convenient unpacker for non-technical people. It can be used as a normal Windows program or as a command-line utility.
For Linux: jsMSIx.exe is probably the best option for people using Linux because it does not require support for VBScript, Internet Explorer, or COM libraries. Everything is built into a single, small standalone program. It also has simple command line functionality to unpack an MSI and optionally select the destination folder for unpacking. The only notable dependencies are cabinet.dll, msvbvm60.dll and msi.dll. Those files are all pre-installed on virtually all Windows PCs and should all be installable (or have native versions) through WINE.
View jsMSIx screenshot
Download jsMSIx (67 KB)
SHA-256: 08112aff0c9d0d7a72e06cffec843b207ef5dc652b4eef62f1c5d0dd13341659
Back to Contents

MSI Unpacker Utility - An HTA Webpage Program

The MSI Unpacker utility is a webpage program (HTA) for working with MSI and MSM Windows Installer files. It is designed for use by anyone who might want to inspect software before installing it.
The MSI Unpacker can be used to open MSI and MSM files. It can extract files, document the contents, and list Registry entries created by the installer. It can also detail specific parts of an installation. For instance, if you are installing an office suite, the MSI Unpacker can tell you which files and Registry settings are required for just the word processor program.
You can use the MSI Unpacker to inspect software before installing, or use it to create your own, customized install/uninstall packages from the parts of an MSI package that you want. Scripts included with the MSI Unpacker can be used to generate an almost-ready-to-run script containing the Registry settings required for a given MSI program installation. That means you can rebuild an installer as a non-MSI if desired. The download includes a sample project that uses these tools to create an installer for the Microsoft Text-To-Speech runtime - a runtime that is not normally available as a separate install.
This utility does not require prior knowledge of script or MSI files. Just double-click the HTA file in the download and browse for an MSI file to unpack. But inexperienced people may prefer jsMSIx (above). The MSI/MSM Unpacker Utility is designed for people with technical expertise who may want to inspect an MSI file in detail or convert MSI installers to another type of installer.
The MSI Unpacker also works with the JSDrop drop handler component, allowing drag-drop of files onto HTAs and their shortcuts (or any other file type).
View screenshots of MSI Unpacker
Download msiext.zip (141 KB) (Last update: April, 2014. See download for details.)
Back to Contents

Simple 'One-Click' MSI Unpacker Script

The Simple 'One-Click' Unpacker is essentially the same thing as the MSI Unpacker described above, but without the Internet Explorer webpage interface, and without the extra script samples. It just unpacks MSIs and writes a log file to document the details. On Windows this is a simple drag-and-drop unpacker, useful when you just simply want to unpack an MSI and don't need to inspect the Components, Features and other technical details of the MSI.
To use this utility in Windows, first download msiext2.zip (below). Open the msiext2.zip download and extract the files into a single folder. (The MSIUnpack.vbs file and the jcabxmsi.exe file must be in the same folder.) Next, put your MSI file into an empty folder. (Unpacking can create numerous files and subfolders, so it's best to put the MSI into it's own folder before unpacking.) Finally, just drop the MSI file onto MSIUnpack.vbs. That's it. You'll get the unpacked software, with all files extracted and placed in a folder hierarchy that reflects their destination folders when the software is installed. There will also be a documentation file - an unpack log - listing included files, Registry settings that are part of the install, etc. (Note that security/permissions problems on Windows Vista/7 may prevent the drag-drop functionality from working. If you want to run with limited permissions on Vista/7 you may have to use the One-Click Unpacker via command line.)
Download msiext2.zip (32 KB) (Last update: April, 2014. See download for details.)
Back to Contents

Issues With Non-MSI Files: Getting MSIs from Inside EXEs

Microsoft's general position on software installers is that they should be created as MSI files and that those MSI files should not be 'wrapped' in other files. However, there are many types of installers and Microsoft themselves are famous for not following their own directives. Many of their downloads are actually self-executing CAB files. Some of the Microsoft program installers are actually InstallShield packages. (In both cases these are .EXE files.) And in some cases an EXE might contain multiple MSIs that call each other.
If you have an unknown installer type that you are trying to open, you might try looking at the Tweaks and Fixes page. There is a section there that has links to information and software. Perhaps the best software option is Universal Extractor, a program that's basically just a handy GUI frontend for a collection of specialized extractor executables. (For example, it includes the well-known INNOUNP.EXE for unpacking Inno Setup installers, IsXunpack.exe for InstallShield packages, etc.) Universal Extractor (UE) saves the trouble of finding, collecting and updating these various tools. But UE cannot handle MSI files in any useful way, and it will sometimes fail with other installer files due to unsupported versions. For instance, UE can open InstallShield installers, but only if they were created with older versions of the InstallShield program.
MSI files that are not MSI files
It seems that just about any error people can make with an installer gets made. Sometimes MSIs are not even MSIs. An example is some installers for Zoom videoconferencing software. The EXE installer contains an MSI file and a second EXE installer file. Except that the MSI is not an MSI. It's a misnamed .7z compressed file. When you try to unpack that MSI you'll get error 110, which means unable to open file. When you get error 110 it's possible that the problem could be permissions, but don't rule out a corrupt installer. Check the MSI in a hex editor to be sure it's actually an MSI. An MSI file is a 'compound storage file'. The initial bytes should be D0 CF 11 E0 A1 B1 1A E1.
How does a .7z ZIP file get mispackaged as an MSI? It's a very odd error. Maybe the installer is deliberately designed to thwart unpacking? Maybe it pretends to package an MSI in order to keep Microsoft happy? Or maybe it's just another bit of sloppy work by Zoom, the people who bring you insecure video conferencing.
MSI files inside EXE files
It is fairly common to find software that installs from an MSI file but which is packed inside an EXE file. Some recent version InstallShield packages are designed that way, for example. If you can't get at the contents of a given installer EXE file, it's always worth checking for a hidden MSI. Open the TEMP* folder while running the installer. Leave the setup window open while checking to see what the installer unpacks. If the installer unpacks a folder to TEMP, check there for an MSI file. If you find an MSI file, copy it to somewhere else, then cancel the install. (Setup must be left running while you check the TEMP folder because it will usually delete the files in the TEMP folder when it quits.) The resulting .MSI file will be the real program installer.
* Finding the TEMP folder: It's usually C:WindowsTemp on Win9x. It will probably be down inside the 'C:Documents and Settings' mess on XP. But XP+ can have numerous TEMP folders. If you're not sure, copy this text into Notepad, save it as findTemp.vbs, and double-click the .vbs file:
MSIs Inside EXEs Get Wacky -- the 12-09 Update
As explained above, the unpackers were updated slightly as of 12-09. Some newer installations, especially with Windows Installer v. 4.5, seem to be using a new and rather odd install method.
In general an EXE is not part of an MSI install. The MSI itself is the installer file. But some installs use an EXE, nevertheless. As explained in the last section, an EXE will dump an MSI file into the TEMP folder and then run it from there. The actual program files, in that case, are stored in a CAB file, which is usually embedded inside the MSI. The EXE is just an unnecessary 'wrapper' around the MSI. To unpack those MSIs without installing the software, the MSI must be fished out of the TEMP folder after starting an installation. Then the installation can be cancelled and the MSI unpacked.
With some newer installation files there is a new wrinkle. A good example is SQL Server 2008 Express from Microsoft. The download is an EXE file. (Microsoft have never recommended EXE 'wrappers' around MSIs, but Microsoft have never been in the habit of following their own instructions, either.) The EXE in this case is not just an MSI wrapper. It is actually a self-executing CAB file. If the download is converted to a CAB it can be seen to contain all of the install files, named with pre-installation code names that get changed on install, plus a handful of installation files, including an MSI file. The SQL Server install requires Windows Installer v. 4.5, yet Windows Installer is largely superfluous in the installation. When the EXE is run it dumps it's contents into the TEMP folder, but in the process it also unpacks the install files, copies them to a program folder tree created in the TEMP folder, and renames them all to their correct post-install names! Since there is no embedded CAB in the MSI to unpack, the MSI Unpackers do not find any files and the Program Description log file written by the unpackers therefore does not list any files.
In other words, this is an inside-out MSI. Instead of being an MSI with an embedded CAB inside, the MSI is actually inside the CAB.
Microsoft's SQL Server install is not alone in using this odd method, so you need to be aware of it for successful unpacking. You can recognize the new 'wacky mode' installers because when you open the TEMP folder you'll find not only an MSI but also a full program installation, ready to be copied to the appropriate folders. The program folder is there just as it would end up being in Program Files if you completed the install!
So the file unpacking is already done for you. You can copy those folders/files out of TEMP if you want to inspect them. But there is still an MSI file as well. The MSI still contains documentation of folders, files, Registry settings, Features, Components, etc. You can run the MSI Unpacker with that MSI file to get a log file that documents all of those things. The difference from a normal MSI is that the unpacker will not actually unpack anything, because there's nothing there to unpack. It has already been done by the installer EXE.
The 12-09 update to the unpackers includes a change to make sure that the program files and their paths are listed in the final 'Program Description.txt' log, regardless of whether those files were unpacked and renamed by the unpacker, or whether they were unpacked and renamed by the installer EXE.
Back to Contents

Solving Problems: MSI Requirements Preventing a Program Installation

Complications can be caused by an installer that asserts requirements. For instance, a common installer requirement that can thwart an install, andor thwart the unpacking of a setup EXE file, is the demand that a particular version of Internet Explorer be installed. This is an especially odd requirement. In most cases the software does not even use Internet Explorer!
For problems with Internet Explorer requirements, try changing the version number in this Registry value:
HKEY_LOCAL_MACHINESoftwareMicrosoftInternet ExplorerVersion
Also, see the MSI Editor topic below. Altering/removing install requirements is one of the uses of the MSI Editor.
A unique issue is the '.Net Framework', which is Microsoft's version of the Java 'Virtual Machine' -- a set of support files needed for software written as a .Net program. Most software does not use .Net, fortunately. (The more recent version of the support files package is over 200MB!). But what if you just want to see the software, and maybe you don't want to install all of the .Net support files? For problems with demands for .Net Frameworks, if you just want to open an installer EXE file and may not want to actually install the program in question, you can spoof .Net support temporarily. For that, see this file. That link should open in your browser as text. Copy the text, paste it into Notepad or another plain text editor, then save that as a file named Spoof Dotnet.vbs. Note that the file extension must be .VBS, not .TXT. When you double-click that file you will be given an option to add or remove the DotNet spoof from the Registry. Once added, software installers will think that whatever version of the .Net Framework they want is already installed. The script adds Registry settings that say you have all 5 .Net Frameworks. For good measure, it also tells querying software that you have Service Pack 3 of each Framework, and version 3 of Windows Installer.

Wise Unpacker Gui V0.12 Download

(Caution: This script is for limited usage, for people who just want to inspect a program they are unlikely to actually use, and who do not want to install the numerous .Net support files. The script will record in the Registry that all 5 .Net Frameworks are installed. Likewise, removing the spoof will remove those settings, even though you may have one or more frameworks installed.)
Back to Contents

Problems Unpacking MSIs in Windows 98

MSI files are a type of Microsoft-specific file known as a Compound File, Compound Storage File, or Compound File Binary (CFB). OpenOffice.org and Microsoft both provide documentation for this file type. A CFB file is a flexible format consisting of a number of segments. The segments can represent different things, depending on the file type. The purpose of the CFB format is simply to arrange those parts in an orderly structure that can be parsed. MS Word .doc files, Powerpoint files and MSI files are all CFB files.
There are two major versions of CFB files currently in use: versions 3 and 4. Version 4 was introduced with Windows 2000. Most MSIs are CFB v. 3 files; unpacking should work on Win9x regardless of the Windows Installer version. However, there are some CFB v. 4 files in use. (One example is the Libre Office installer.) A CFB v. 4 file will not be recognized on Win98. Since CFB files are native to Windows itself, it is unlikely that any kind of update will solve that problem. (On the bright side, it is very unlikely that any software packed into a v. 4 MSI file will run on Windows 9x, anyway.)
If you have trouble unpacking an MSI on Win98, the first thing to do is to check the CFB version: Open the MSI file in a hex editor. You will find that the first 8 bytes are nonsense, comprising the 'magic' bytes, which identify the file type. After that come 16 null bytes. The next 6 bytes should be either 3E 00 03 00 FE FF or 3E 00 04 00 FE FF. Those are version 3 and version 4 respectively.
Back to Contents

.MSU Files

.MSU files apply only to Windows Vista and later. An MSU is an update file. While MSUs have been tied into the Windows Installer system, an MSU is actually not a Windows Installer file at all. It's just a CAB file. If you rename a .msu file to .cab you can open it with any ZIP program. Inside you'll typically find more CABs. The update files will be inside one of those CABs. (The actual content of an update will usually be breathtakingly convoluted and overproduced, with liberal sprinklings of CLSIDs, bloated XML, etc. It's not the sort of thing that one is likely to want to dissect.)
Back to Contents

Non-JSWare Tools For Handling MSIs

There is a lot of confusion and misinformation online in regard to options in dealing with MSI files. Basically, an MSI is a storage file designed to work like a simple SQL database. Microsoft provides functionality (in MSI.DLL) to manage that database. (MSI.DLL, which provides the functionality used by Windows Installer, has a dual API -- Win32-style functions for programming languages and COM Dispatch functions for use with script. Many of the tools here are VBScript-based because the scripting API is essentially the same as the programming API, and very easy to use.)
The JSWare MSI unpackers are the only ones available, as of this writing, that can fully unpack an MSI and also document the Registry settings changed when the MSI install is run.
Other options:
• Administrative Install - An Admin install is a Windows Installer command line option using msiexec.exe. It extracts files for multiple network installations, running the steps in the AdminExecuteSequence, if present, rather than the InstallExecuteSequence. That's not quite the same thing as unpacking. Look it up in the MSI docs if you think that might be of interest. (Also note that an Administrative Install is a restricted operation. It can only be done with Administrator status. And it is not 'supported' in all MSIs.)
Some software programs available that claim to unpack or extract from MSI files are actually just graphical 'front-ends' for doing an Administrative install. They simply execute an msiexec command line so you don't have to type. (An example of that is a program named only 'MSI Unpacker'.)
• Less MSIErables - This is a free, 'open source' program that allows one to see files in an MSI and also unpack the program. Pros: Less MSIErables has an attractive, polished interface, it's easy to use, and it works. It also provides the option to extract only one specific file from an MSI installer. Cons: Less MSIErables does not provide information about Registry settings. And it has gigantic dependencies. (Other files required for it to work.) Less MSIErables is actually a simple wrapper GUI that requires the .Net Framework and a set of Microsoft libraries known as 'Wix'. So Less MSIErables is a multi-level wrapper around wrappers. (.Net wraps the Win32 API. Wix is a set of wrapper libraries around msi.dll. Less MSIErables wraps the whole mess.) The latest .Net Framework is about 500 MB! Neither .Net nor Wix is necessary for processing MSI files, so unless you already have .Net and Wix installed, Less MSIErables will add a big pile of bloat to your system for no reason.
• Universal Extractor - Universal Extractor is useful for unpacking some installer files, but it is actually just a convenient wrapper around a number of other unpacking tools. It works well with some types of installers and not so well with others. At last count Universal Extractor had 3 different methods to unpack MSI files and none of them actually worked.

• 7-Zip - Many people mistakenly believe that the free compression program 7-Zip can unpack MSI files. Even the Wikipedia page for Windows Installer says so. 7-Zip cannot unpack MSI files. Technically, 7-Zip can extract content from MSI files. If you open an MSI file with 7-Zip it will appear to show you the content, but what you'll see are binary versions of the database tables, along with internal resources such as icons displayed during installation. None of those items are of any particular value. It's analogous to dismantling a car by cutting it into slices. The slices do represent parts of the car, but they are not relevant parts.
If the MSI contains a CAB file, 7-Zip can be used to extract that from the MSI, but then all you have is a CAB full of files with incorrect names, because part of the silliness of MSI installers is that, 'by tradition', program files in the package are always given nonsense names. The only way to find the correct names and install paths of files in an MSI CAB is through a circuitous cross-referencing of multiple MSI database tables. That's what an MSI unpacker does.
So the seeming ability of 7-Zip to unpack MSI files (or any compound storage file format, such as DOC and PPT) is just a source of confusion with little or no value. (See the CFB file explanation above for more info.)
• MsiX - Some people think that MsiX is an MSI unpacker. It is not. It is a small command-line utility for working with embedded binary files in an MSI or an MSP patch file. MsiX can extract resources such as BMPs, ICOs, etc. from the _Streams table, and it can extract items from the _Storage table. In general these items are not relevant except to the author of the installer. And the latter table is generally only relevant with MSP files. If you want to extract resources see below. Extracting all files from the _Streams table is a simple operation in script.
Of all the options above, Less MSIErables is the only one that can really unpack an MSI and put the extracted files into a folder tree that represents how the program will be configured if you install it.
Overvaluing Open Source:
It is notable that the programs listed above are all so-called 'open source software' (OSS). There is a strong tendency among many people to idealize OSS. OSS has developed into somewhat of a club, such that it may sometimes be recommended even when it can't do the job required, simply because OSS followers are not aware of anything except OSS. Even apparent experts at sites such as InstallSite.org and Wikipedia make that mistake. (Both sites mistakenly list 7-Zip as an MSI extractor tool.)
Basically, OSS means that the software's source code is available. That can be helpful to programmers, but most people can't use or read the source code. And in many cases the source code is not particularly useful. In the cases of Less MSIErables and Universal Extractor, for example, both are lightweight wrappers around other software, so their source code doesn't provide anything much of value. (7-Zip, by contrast, is a very capable and highly regarded program. It just doesn't happen to work for unpacking MSIs.)
For anyone who wants 'source code', the VBScript unpackers here offer more complete source code than any other tools available. As script, all the code is in plain text. Anyone is free to reuse that code as they like. The scripts come with an extra, small program required to extract from CAB files, but the actual processing of MSI files is done entirely through MSI.DLL (the basic Windows Installer library) with VBScript. Using MSI.DLL is the most direct method. It is Windows Installer. There is no need for bloated extra dependencies such as .Net, Wix, or 3rd-party software.
For interested programmers there is a Windows Installer help file as part of the Windows SDK. That documents the two sets of methods for processing MSI files: The COM automation object model using WindowsInstaller.Installer and the Win32 functions. The JSWare tools here either demonstrate the COM automation objects (VBScript and HTA) or use the Win32 functions (jsMSI.dll, jsMSIOps.exe and jsmsix.exe). If you have sample script code it's not difficult to go from there to the Win32 API functions in MSI.DLL. That is, once you know about how MSIs work and how the Windows Installer object model works, the API versions of the same methods are fairly self-explanatory.
Back to Contents

MBase - MSI Database Editor

The MBase MSI Editor is a database editor program, created as a webpage. More specifically, it's an HTA program. (If you don't know what that is, see explanation below.) The editor can display the content of MSI files and allows you to add or remove tables, rows and columns. You can also edit individual row cells, export the text of specific tables or all tables, and export, insert, or overwrite embedded MSI CAB file data streams. All through a convenient graphical interface (Embedded CABs are the most common way to store the actual software files in an MSI/MSM installer file.)
MBase can be used to work with MSI software installation files, but it's designed to be more adaptable than that. It can also be used to create your own databases from MSI files, designing the tables for your own specific needs rather than using the standard MSI tables. (See the ZipFinder sample below.)
MBase can also be used to adjust poorly designed software installers.

View picture of MBase MSI Editor
Note The MSI Editor will also work with the JSDrop drop handler component, allowing MSI files to be opened in the editor by dropping them onto the MSI Editor program file or its shortcut.
Download MSI Editor (210 KB)
Compatibility note: The MSI-MSM Unpacker should display and function well on all Windows versions from Windows 95, with any version of Internet Explorer from 5 up. If you find any dysfunctionality, please see the note below about differences in IE versions and Windows versions.
Back to Contents

ZipFinder Zip Code and Area Code Database Program

ZipFinder is a webpage program that uses an MSI database file to hold and access approximately 55,000 US zip codes and most area codes. You can enter city/state names to return a zip code, or enter a zip code to return the respective city and state. You can also enter an area code to find its location.
ZipFinder does not require any knowledge of script or webpages. Just download the zcodes.zip file and extract the contents. You will have a folder named 'ZipFind'. Put the folder anywhere, then create a shortcut on the Desktop going to the ZipFinder.hta file inside the ZipFind folder. Double-click the shortcut to find zip code and area code information.
View picture of ZipFinder
Download zcodes.zip (678 KB)
(Note to scripters/programmers: ZipFinder is designed to be an easy-to-use utility, but it also constitutes a sample program demonstrating the use of MSI files as SQL databases. The download comes with a copy of a VBScript class for working with MSI SQL functions, and it includes a copy of the script that was used to create the zip code database.)
Back to Contents

Script to Edit MSI Files: Change installer window appearance and add information

This is a single VBScript that can do two things:
1) Change the background picture in an MSI installer 'welcome dialogue' window. (The window that shows first when you install software from an MSI file.)
2) Add custom notes and a list of file versions to the welcome dialogue window of an MSI file.
Adding custom notes provides a way to conveniently store installation information in an MSI file. For example, you might save information about date installed, or info. about problems you had with incompatible programs, or the URL of drivers that you'll need when you install this package, etc.
What the custom notes function does is to first add a scrolling text box (actually a 'RichEdit' control) to the upper left of an installer's 'Welcome dialogue' or splash screen window (provided that the installer includes a 'welcome dialogue'). It then provides an option to permanently store your custom notes text in the text window. Third, it searches the MSI for files with version numbers, such as EXE and DLL files. Then it adds a list of those files, along with their version numbers, to the same RichEdit text window.
The result is that when you open the MSI file later, the first window shown will contain any notes that you chose to save, and you will have the opportunity to check what versions of which system files the installer is likely to change on your system. In other words, the text window serves as your own, custom 'README' file, built into the installer itself.
Download msiops2.zip (6 KB)
Back to Contents

jsMSI.dll and jsMSIOps.exe - A Component for MSI Programming

jsMSI.dll is a component that provides the functionality of the 1-click unpacker and the MBase MSI class in a compiled library. jsMSIOps.exe is the exact same thing, but compiled as an ActiveX EXE, which allows it to run on 64-bit Windows without complications.

Wise Unpacker Gui Download

jsMSI.dll/jsMSIOps.exe provides a simplified API, for both script and compiled software. It wraps the awkward and error-prone SQL syntax of Windows Installer, as well as the unnecessary abstruseness of the overall design, providing simple, straightforward Win32-style functions instead: ImportTable, RemoveTable, GetValue, SetValue, AddRecord, RemoveRecord, etc. Example: AddRecord('TableName', 'Column1Value, Column2Value, Column3Value, Column4Value')

Wise Unpacker Gui

jsMSI does not really add anything that can't be done with the various JSWare scripts and HTAs. It just uses the more efficient Windows Installer API and wraps the whole thing in a single neat package. There are almost 50 functions here. No SQL needed. No superfluous XML nonsense. No need to deal with the verbose code mess of getting View objects, looping through Record objects, etc. jsMSI includes the following methods (by category):

Wise Unpacker Guide