Convert MSI to CPIO
Turn MSI archives into CPIO. The files the installer would copy, in the folders it would put them in, such as Program Files.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop MSI files on the dialor turn it to pick what to do
The files inside an installer, in one archive.The installer's files come out in their install folders, stored as a CPIO archive.
What you get
One CPIO file that holds the files the installer would copy. They sit in the folders the installer would put them in, such as Program Files.
The archive uses the new-format (SVR4) cpio layout, the kind used by initramfs images and RPM packages.
What it leaves behind
Only files are kept. Registry entries, shortcuts and install actions are left out, so the archive does not set anything up on its own.
The result is a plain set of files, not a working installer. You cannot run it to install the program.
Options
This conversion has no options. Every MSI is handled the same way and produces one file.
MSI and CPIO.What each format is.
The formats
Windows Installer
Windows installer packages. The files inside sit in an OLE container.
- Extensions
- .msi
- MIME type
- application
/x -msi - Kind
- Archives
cpio Archive
The Unix cpio archive, still used inside RPM packages and initramfs images.
- Extensions
- .cpio
- MIME type
- application
/x -cpio - Kind
- Archives
In your code.The same MSI to CPIO conversion through the API, for your app or your agent.
$ cv convert archive.msi archive.cpio$ cv convert archive.msi archive.cpioQuestions.What people ask about MSI to CPIO.
The files the installer would copy, in the folders it would put them in. Registry entries, shortcuts and install actions are not included.
The new-format (SVR4) cpio archive. Initramfs images and RPM packages use the same kind.
No. Install actions and registry entries are left out, so it holds the files only.
No. The conversion produces one CPIO file. See every MSI conversion or every CPIO conversion for other routes.