Problems installing software after booting from VHD.

Answered Problems installing software after booting from VHD.

  • Saturday, May 12, 2012 12:37 PM
     
     

    I'm trying to setup a vhd for developing applications (so that I don't have all the dev apps installed on my home system).

    I captured an image of my W7 Ultimate SP1 using imagex and applied it to a extendable vhd on another hard drive. The vhd boots-up correctly but when I try to install software (as an administrator)  I get an error stating the Windows Installer service could not be accessed. I checked several blogs and none of the stated conditions seem to apply, accept changing the identity on RPC to Local System, which doesn't seem safe. I booted back to the original HD and was able to install the software without an issue.

    Is there something I'm missing?

All Replies

  • Sunday, May 13, 2012 6:35 AM
     
     

    From Answers forum:

    Click Start, and type services.msc in the Search/Run box.  Scroll down toWindows Installer and right click on it.  Select properties.  Use the drop down to set toManual and then start the service.

    If that does not work, try this next.

    • Click Start, and then type CMD in the Search/run box.
    • Right click on CMD at the top of the results pane and select Run as Administrator
    • At the command prompt, type msiexec.exe /unregister, and then press ENTER.
    • Type msiexec /regserver, and then press ENTER.
    • Exit the CMD window

    Regards

    Milos

  • Monday, May 14, 2012 12:23 AM
     
     

    Milos,

    That did not help. I re-registered the windows installer and re-started the windows installer service to no avail.

    Thanks for the suggestion...

    Regards,

    Bob

  • Monday, May 14, 2012 9:48 AM
    Moderator
     
     

    Hi,

    Have you tried the methods in the following link.

    http://support.microsoft.com/kb/2642495

    Also, you could enable MSI logging, then try to install a msi based application.

    Furthermore, Verify Security Permissions for Administrators and System Accounts on C:\; C:\temp and %systemroot%\temp


    Juke Chou

    TechNet Community Support

  • Tuesday, May 15, 2012 2:24 AM
     
     

    Hi Juke,

    I tried all the MSI 1719 'fixes'.
    I enabled logging. All it logged was the 1719 error message.

    I verified the permissions for System and Administrators on those directories: f:\ = full control f:\windows\temp = full control

    Another thing I noticed: IE9 seems to respond differently to downloaded programs. When I boot the C drive I get a banner at the bottom of the IE window asking whether to Run or Save. When I boot the VHD I get a popup (history like) download window. Strange that it's different when the VHD is an image of the C drive...

    -Bob

  • Wednesday, May 16, 2012 7:06 AM
    Moderator
     
     Answered

    The issue may happen if Windows Installer service was configured correctly.

    Run Regmon While attempting to start the Windows Installer Service and found
    msiexec.exe whether there is any actions that are access denied or non-existent.


    Juke Chou

    TechNet Community Support

  • Monday, May 21, 2012 7:12 PM
     
     

    Hi Juke,

    I ran Procmon then ran the installation (with logging). I did this both when booted from the C drive and booted from the VHD. The log files are nearly identical except that the one from the C drive starts the install and the other stops at this point. The events that are recorded using Procman in each of these scenarios are very different. It seems that something is fundamentally wrong with the VHD image. Do I have to sysprep if I'm going to use the image on the same machine? I was assuming that step was not required since I'm not planning on distributing this image to other systems. I'm wondering if this is the problem because I've noticed that some programs are still being loaded from c:\windows, when f:\windows is the system directory (when booted from the vhd). This seems suspicious. What do you think?

    -Bob

  • Tuesday, May 22, 2012 7:08 AM
    Moderator
     
     Answered

    Hi,

    Based on my understanding, it does not matter to Sysprep if you just use it on the same box.

    You may try to imported the key from the host and rebooted the machine.
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Msiserver


    Juke Chou

    TechNet Community Support