MDOP 2013 embeds APP-V MSI’s inside of EXE files

If you are looking for the MSI installer files for APP-V 5 SP1, you will need to manually extract them from the EXE files. The App-V 5.0 SP1 (Client/Server) MSI's can be extracted using this command:

appv_xxx_setup.exe /Layout /LayoutDir="<path>"



c:\temp>appv_client_setup.exe /Layout /LayoutDir="c:\temp")


The language pack MSI will be laid out with the client or server MSI in the location/path specified in /LayoutDir.


This command is documented here

Comments (10)
  1. Jack Fetter says:

    Having an issue, just downloaded 5.1 HF2 today to troubleshoot an issue but it won’t install, says base product is not installed and log shows;

    [12BC:116C][2016-07-18T10:21:13]i105: Detected package: CoreX86Patch target: {B2A6CCDE-5E94-43D8-B47E-A455CEF33C4B}, state: Absent

    But IS installed, both installed and functioning (here’s the registered MSI info);


    5.1 was installed on Windows 7 via WDS deployment, it’s not an upgrade and works fine, been in our environment for many years. Tried to extract MSI from EXE to be sure it’s not an MSI-over-EXE problem and exe launches endless processes but never does anything, seems to be stuck in a loop when run via;

    AppV5.1RTM_Client_KB3139245.exe /Layout /LayoutDir=”C:\Sequences”

    Error log indicates;

    [2230:2234][2016-07-18T10:17:25]e000: Error 0x800700ce: Failed to launch parent process with unelevate disabled: C:\Sequences\App-V 5.1 HF2\AppV5.1RTM_Client_KB3139245.exe
    [2230:2234][2016-07-18T10:17:25]e000: Error 0x800700ce: Failed to launch unelevated process.
    [2230:2234][2016-07-18T10:17:25]e000: Error 0x800700ce: Failed to run per-machine mode.

    I am logged on as an Admin (member of Local Administrators Group).

  2. Which MDOP installer version or we talking about? The one for 2015?

  3. Brachus12 says:

    The /layout switch does not work

  4. Thank you very much for your information and insight, Stephan. I will forward on your feedback.

  5. Anonymous says:

    hi this command not working for me what is wrong?

  6. Which command Nuni/OOSOO? Stephan, thanks for the catch!

  7. OMG, could someone update the article "Whats new…." and give the hint, that not only the language pack MSI-files are to extract but also the client MSI itself? Because the language pack MSI's are already "standalone" on the ISO-image, no one would try to extract this exe if they read the article… was my cause and i cried for help in the forum, altough i read this article… but i thought, i already have the language pack MSI-files so never mind this Whats new article…

    Strange idea from Microsoft to pack the msi files in the exe (not as it was before) and don't mention it anywhere exactly… but our luck is, there are great people in your forums which are never tired to help!

  8. Anonymous says:

    Not working for me too

  9. Rorymon says:

    Saving people from themselves I guess?

  10. Great Steve, thanks for forwarding this!

    One little hint for anyone who tries to install the client with the MSI file via GPO:

    you need to add the following to the property table in a MST file -> property ACCEPTEULA (in UPPERCASE!! important!) and the value is 1.

Comments are closed.

Skip to main content