RE: Installer v2 + Disk Properties

From: Alex Zhang (v-qiz_at_online.microsoft.com)
Date: 04/08/04

  • Next message: Alex Zhang: "Re: NetBios name change after upgrading NT4 to Win 2003"
    Date: Thu, 08 Apr 2004 01:15:10 GMT
    
    

    Hello Robert,

    Thank you for your reply.

    You may try the following steps:

    Run Registry Editor:
                                    
    1. Click "Start", and then click "Run".
    2. In the "Open" box, type "regedit" (without the quotation marks), and
    then click "OK".
    3. Locate and click the following registry key:
                                                             
    "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer".

    4. In the right pane of Registry Editor, double-click "ImagePath".
    5. In the "Edit String" dialog box, make sure the string in the "Value
    data" box contains the correct path to the Msiexec.exe file. The following
    is the correct path, where <C> is the drive in which Windows is installed:
                    
    <C>:\Windows\System32\msiexec.exe /V

    6. On the "File" menu, click "Exit" to exit Registry Editor.
    7. Start your computer in Safe Mode.
    8. Register the Msiexec.exe file:
                                                             
    a. Log on to the computer.
    b. Click "Start", and then click "Run".
    c. In the "Open" box, type "msiexec /regserver" (without the quotation
    marks), and then click "OK".

    9. Shut down your computer, and then restart your computer as usual.

    I hope the information proves helpful.

    If you have any other issues, please feel free to let me know. I am glad to
    be of assistance.

    Have a nice day!

    Thanks and regards,

    Alex Zhang
    Microsoft Partner Online Support
    Get Secure! - <www.microsoft.com/security>
    =====================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
    | Thread-Topic: Installer v2 + Disk Properties
    | thread-index: AcQbTlM0J/Pb+jtAREalxOxfAKdsuQ==
    | X-Tomcat-NG: microsoft.public.windows.server.migration
    | From: =?Utf-8?B?Um9i?= <anonymous@discussions.microsoft.com>
    | References: <EB491C29-7087-4BB1-BEA2-963EA24BDCE3@microsoft.com>
    <Us58wlMGEHA.660@cpmsftngxa06.phx.gbl>
    <bvuxgjZGEHA.612@cpmsftngxa06.phx.gbl>
    | Subject: RE: Installer v2 + Disk Properties
    | Date: Mon, 5 Apr 2004 13:41:09 -0700
    | Lines: 10
    | Message-ID: <92778C2C-1B6C-4DE1-BC44-A9510C95E077@microsoft.com>
    | MIME-Version: 1.0
    | Content-Type: text/plain;
    | charset="Utf-8"
    | Content-Transfer-Encoding: 7bit
    | X-Newsreader: Microsoft CDO for Windows 2000
    | Content-Class: urn:content-classes:message
    | Importance: normal
    | Priority: normal
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
    | Newsgroups: microsoft.public.windows.server.migration
    | Path: cpmsftngxa06.phx.gbl
    | Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.migration:9570
    | NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
    | X-Tomcat-NG: microsoft.public.windows.server.migration
    |
    | Hello Alex

    Unfortunately this doesn't work. This is the standard answer that I've come
    across a hundred times in the last week. It's the normal answer Microsoft
    will provide in their tech online.

    I also came across some other rare information which describes how the
    ROOT_CLASSES in the registry need SYSTEM priveledges, how the boot
    partition needs SYSTEM privs, how to check the RPC server, how to
    re-install the service, how to make sure the service has proper login
    priveledges, etc. I've spent a good week trying to solve this problem but
    the problem persists. For example, Windows 2003 places additional
    restrictions on the Windows Installer Service and its runtime logon
    privledges, which could sort of make sense on a Windows 2000 to 2003
    upgrade (much of the security has been tightened up for 2003 as I've found
    out).

    I would need a non-stock answer to describe the very basic requirements of
    letting the Windows installer run. From reading other online FAQs, and
    digging deeper into Microsoft online help, I know that there are a number
    of additional requirements beyond the basic quick fix of the previous
    message.

    Thanks for your consideration.

    |


  • Next message: Alex Zhang: "Re: NetBios name change after upgrading NT4 to Win 2003"

    Relevant Pages

    • RE: Error 1402
      ... >Microsoft Corporation ... >>This is a permissions issue that must be fixed through ... >>the Windows operating system. ... >>Do not use the registry key given in the Microsoft ...
      (microsoft.public.windowsxp.security_admin)
    • RE: Error 1406
      ... please post the screen capture of the error message: ... >the Windows operating system. ... >Microsoft document drticle number Q236592, ... >Do not use the registry key given in the Microsoft ...
      (microsoft.public.windowsxp.security_admin)
    • error 1406 with Norton
      ... >the Windows operating system. ... >Microsoft document drticle number Q236592, ... >Messages Starting Office Program, or Program Immediately ... >Do not use the registry key given in the Microsoft ...
      (microsoft.public.windowsxp.security_admin)
    • RE: Error 1402
      ... Produced By Microsoft MimeOLE V5.50.4910.0300 ... >>Online Support Professional ... >>>the Windows operating system. ... >>>Do not use the registry key given in the Microsoft ...
      (microsoft.public.windowsxp.security_admin)
    • error 1406 with Norton
      ... >>the Windows operating system. ... >>Microsoft document drticle number Q236592, ... >>Messages Starting Office Program, or Program ... >>Do not use the registry key given in the Microsoft ...
      (microsoft.public.windowsxp.security_admin)