Visual-Studio severely damages Vista

Discussion in 'Windows Vista Security' started by Jim Kay, Apr 7, 2008.

  1. Jim Kay

    Jim Kay Guest

    Way back in Nov of 2006, when Vista appeared for download on MSDN, I began
    testing it. One of the early things I did was install Visual-Studio 2005
    with its SP1. I discovered that multiple critical update processes were
    failing to get access to c:\config.msi (a directory) and I was NOT being
    prompted by UAC for administrative rights. There were scads of messages
    about this on the Visual-Studio forum but silence from Microsoft. Every time
    I update the access rights to that directory, something in Vista/V-S sets
    those rights back to where they were.

    Because I did not know the cause of the problem I totally rebuilt the
    machine and installed my software more slowly. This time I discovered it was
    specifically the install of Visual-Studio 2005 with its SP1 that caused the
    problem.

    I totally rebuilt the machine another time (each time takes about three
    days) and then I installed Visual-Studio 2008 believing Microsoft MUST have
    fixed the problem in the new Visual-Studio. Boy was I WRONG!!! Eventually, I
    reconfigured c:\config.msi to inherit its rights from the root and I gave
    myself full control there. This has made the problem a bit better but even
    that gets reset in mysterious ways.

    Now I am having trouble with McAfee Total Protection for Small Business
    which decides it cannot update it's registry entries so it stops downloading
    the latest virus signatures. (For now I may have found a workaroud: as soon
    as I logon, I stop McAfee and restart it using run as administrator.)

    But this mess is totally INSANE! I have several Vista systems running for
    testing and this is the only machine where I have installed Visual-Studio.
    It's the only machine having these problems which began IMMEDIATELY after I
    installed V-S again (fool that I am).

    Is there any hope that Microsoft is going to acknowledge this mess and
    figure out how to fix it?
     
    Jim Kay, Apr 7, 2008
    #1
    1. Advertisements

  2. Jim Kay

    Alun Harford Guest

    If I remember correctly c:\config.msi is Office 2000 idiocy.

    IIRC SYSTEM needs to have full control on that folder.

    Alun Harford
     
    Alun Harford, Apr 7, 2008
    #2
    1. Advertisements

  3. Jim Kay

    Mr. Arnold Guest

    I don't know man. I have installed VS 2005 with SP1 and uninstalled it. I
    went to VS 2008 and installed that. I don't know what you're talking about,
    but i did do the installs with Run as Administrator.
     
    Mr. Arnold, Apr 8, 2008
    #3
  4. Hello,

    Thank you for your post.

    According to your description, my understanding is that after you installed
    Visual Studio 2005 or Visual Studio 2008 on your Vista machine, some update
    processes failed because the access to C:\cinfig.msi is denied. After you
    uninstalled Visual Studio, the issue gone. You concern is to verify whether
    it is the Visual Studio that cause this issue and find a solution to solve
    this issue.

    If there is any misunderstanding, please let me know.

    According to the symptom, it seems that there are some compatibility issues
    between Visual Studio and Vista. As we are not Visual Studio expert, I'd
    like to suggest that you also submit a post in the following MSDN newsgroup
    so that this issue can be resolved efficiently.

    microsoft.public.msdn.general

    The engineers and newsgroup members there are more experienced on Visual
    Studio related issues, and should be able to provide you with suggestions
    on this issue.

    Meanwhile,I'd like to share with you some basic information.

    Based on my research, this issue might be caused by not properly installing
    Visual Studio 2005/2008.

    I recommend you follow the below steps to uninstall Visual Studio 2008 and
    reinstall it.

    1. Please follow the below article to uninstalling Visual Studio
    2008
    http://msdn2.microsoft.com/en-us/vs2008/bb968856.aspx

    2. Install the latest Windows updates.

    3. Check if there is any anti-virus or antispyware running. Turn
    them off before installation.

    4. Make sure that the installation media is healthy. If the
    installation from DVD is not working well, you can try copying the contents
    of the disc to the hard disk and try the installation from the hard disk.

    5. Temporarily disable/dismiss Windows Update during installation
    (especially in Vista see:
    http://blogs.msdn.com/astebner/archive/2007/11/13/6190778.aspx)

    6. Run the installation as administrator.

    After the installation is finished, please check whether the issue still
    exists.

    If yes, I recommend you to contact to MSDN support engineers for further
    investigation.

    Thanks.

    Sincerely,
    Neo Zhu,
    Microsoft Online Support
    Microsoft Global Technical Support Center

    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.
     
    Jian-Ping Zhu [MSFT], Apr 8, 2008
    #4
  5. Jim Kay

    Jim Kay Guest

    There are two things in your understanding that are a little off:

    1. removing Visual Studio does not fix the problem. My Vista machines remain
    permanently broken and must be totally rebuilt to fix them.
    2. there are many messages in the MSDN forums of people complaining about
    trouble with access to c:\config.msi directory but there are no (that I ever
    found) responses from anyone at Microsoft that acknowlegeds the connection
    to Visual Studio installation. I have proven to my own satisfaction that
    installing Visual Studio is the cause of the problem. But it cannot, as far
    as I know, ever be reversed other than format the drive and start over with
    everything.

    I have posted in MSDN but Microsoft just ignores the problem and doesn't
    respond to ANYONE.
     
    Jim Kay, Apr 8, 2008
    #5
  6. Jim Kay

    Bob Guest

    What post?
    When posting, please quote relevant information so that others know what you’re
    talking about.
     
    Bob, Apr 9, 2008
    #6
  7. Jim Kay

    SG Guest

    Here is the post Bob,

    Quote:
    Way back in Nov of 2006, when Vista appeared for download on MSDN, I began
    testing it. One of the early things I did was install Visual-Studio 2005
    with its SP1. I discovered that multiple critical update processes were
    failing to get access to c:\config.msi (a directory) and I was NOT being
    prompted by UAC for administrative rights. There were scads of messages
    about this on the Visual-Studio forum but silence from Microsoft. Every time
    I update the access rights to that directory, something in Vista/V-S sets
    those rights back to where they were.

    Because I did not know the cause of the problem I totally rebuilt the
    machine and installed my software more slowly. This time I discovered it was
    specifically the install of Visual-Studio 2005 with its SP1 that caused the
    problem.

    I totally rebuilt the machine another time (each time takes about three
    days) and then I installed Visual-Studio 2008 believing Microsoft MUST have
    fixed the problem in the new Visual-Studio. Boy was I WRONG!!! Eventually, I
    reconfigured c:\config.msi to inherit its rights from the root and I gave
    myself full control there. This has made the problem a bit better but even
    that gets reset in mysterious ways.

    Now I am having trouble with McAfee Total Protection for Small Business
    which decides it cannot update it's registry entries so it stops downloading
    the latest virus signatures. (For now I may have found a workaroud: as soon
    as I logon, I stop McAfee and restart it using run as administrator.)

    But this mess is totally INSANE! I have several Vista systems running for
    testing and this is the only machine where I have installed Visual-Studio.
    It's the only machine having these problems which began IMMEDIATELY after I
    installed V-S again (fool that I am).

    Is there any hope that Microsoft is going to acknowledge this mess and
    figure out how to fix it?
    End Quote

    --
    All the best,
    SG

    Is your computer system ready for Vista?
    https://winqual.microsoft.com/hcl/

    SNIPPED
     
    SG, Apr 9, 2008
    #7
  8. Jim Kay

    SG Guest

    Hi Jim,

    Here's a few things I picked up on the Net that "may" help you.

    "" Insufficient access to C:Config.msi message when installing
    This error occurs when the installer cannot write a file to the C:Config.msi
    folder for some reason. A common cause is that a Windows Explorer window is
    open that locks this folder. Clicking retry will usually allow the setup to
    continue. Close all open applications and restart the installation if the
    "retry" method does not work.""

    Here are a few links that doesn't necessarily deal with Visual-Studio, but
    may lead to a clue to help you.

    http://www.pcreview.co.uk/forums/thread-2080929.php

    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=723876&SiteID=1

    Take a close look at this one......
    http://www.vistax64.com/vista-insta...onfig-msi-various-errors-many-installers.html

    http://glovario.wordpress.com/2008/01/19/error-1310-error-writing-to-file-cconfigmsixxxxrbf/

    You can search Google for the words C:\cinfig.msi
    They are several hits and maybe something can help you.

    --
    All the best,
    SG

    Is your computer system ready for Vista?
    https://winqual.microsoft.com/hcl/
     
    SG, Apr 9, 2008
    #8
  9. Hello Jim,

    Thank you for the reply.

    I have done some further research and I find that Vista's UAC prompting
    might cause this problem. Also running Visual Studio with normal user
    permissions on Vista might cause some issues.

    To narrow down this issue, I recommend you follow the steps below and have
    another try.

    1. Enable the Administrator account and log in as Administrator.
    2. Disable Vista's UAC prompting.
    To do this, please
    1). Go to Start, Run, and enter "MSCONFIG"
    2). Go to the Tools menu.
    3). Halfway down the list, enable 'Disable UAC Disables User Account
    Control (Requires Reboot)'
    4). Reboot.

    3. Please uninstall Visual Studio and reinstall it again following the
    steps I mentioned in my last mail.

    After that, please check whether the issues still occur.

    If yes, please tell me in detail that what operation causes the issue.
    Please also check whether there are any error messages recorded in Event
    logs and let me know. If possible, please capture a screenshot of the error
    message and mail the screenshot to me.

    To capture a screenshot:
    ===================
    1. Please press the Print Screen key (PrtScn) on your keyboard.
    2. Click "Start", click "Run", type "mspaint", and click "OK".
    3. In Paint, click Paste under the Edit Menu, click Save under the File
    menu, type a file name for the screenshot, choose JPEG as "Save as type",
    click "Desktop" on the left pane, and click Save.
    4. Please find the screenshot on the Desktop and send it as an attachment
    to:

    More information
    ==============
    The following information is for your reference:

    Visual Studio 2005 on Windows Vista Issue List when running with normal
    user permissions:
    http://msdn2.microsoft.com/en-us/vs2005/aa972193.aspx

    Contents of Microsoft Visual Studio 2005 Setup Issues Readme file
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;908452

    I look forward to hearing from you. Thanks.

    Sincerely,
    Neo Zhu,
    Microsoft Online Support
    Microsoft Global Technical Support Center

    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.

    --------------------
    | Reply-To: "Jim Kay" <>
    | From: "Jim Kay" <>
    | References: <>
    <>
    | In-Reply-To: <>
    | Subject: Re: Visual-Studio severely damages Vista
    | Date: Tue, 8 Apr 2008 18:18:30 -0400
    | Lines: 99
    | Organization: James S. Kay, Consulting
    | Message-ID: <>
    | MIME-Version: 1.0
    | Content-Type: text/plain;
    | format=flowed;
    | charset="iso-8859-1";
    | reply-type=original
    | Content-Transfer-Encoding: 7bit
    | X-Priority: 3
    | X-MSMail-Priority: Normal
    | X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18000
    | X-MS-CommunityGroup-PostID: {816E56EE-FDE6-4F47-854D-267DC270FFB5}
    | X-MS-CommunityGroup-ThreadID: 14AAFE37-9C21-418B-83F2-1B503B4EB86F
    | X-MS-CommunityGroup-ParentID: EFF53A96-D331-46E8-875C-318DE978E604
    | Newsgroups: microsoft.public.windows.vista.security
    | Path: TK2MSFTNGHUB02.phx.gbl
    | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.vista.security:14738
    | NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
    | X-Tomcat-NG: microsoft.public.windows.vista.security
    |
    | There are two things in your understanding that are a little off:
    |
    | 1. removing Visual Studio does not fix the problem. My Vista machines
    remain
    | permanently broken and must be totally rebuilt to fix them.
    | 2. there are many messages in the MSDN forums of people complaining about
    | trouble with access to c:\config.msi directory but there are no (that I
    ever
    | found) responses from anyone at Microsoft that acknowlegeds the
    connection
    | to Visual Studio installation. I have proven to my own satisfaction that
    | installing Visual Studio is the cause of the problem. But it cannot, as
    far
    | as I know, ever be reversed other than format the drive and start over
    with
    | everything.
    |
    | I have posted in MSDN but Microsoft just ignores the problem and doesn't
    | respond to ANYONE.
    |
    | | > Hello,
    | >
    | > Thank you for your post.
    | >
    | > According to your description, my understanding is that after you
    | > installed
    | > Visual Studio 2005 or Visual Studio 2008 on your Vista machine, some
    | > update
    | > processes failed because the access to C:\cinfig.msi is denied. After
    you
    | > uninstalled Visual Studio, the issue gone. You concern is to verify
    | > whether
    | > it is the Visual Studio that cause this issue and find a solution to
    solve
    | > this issue.
    | >
    | > If there is any misunderstanding, please let me know.
    | >
    | > According to the symptom, it seems that there are some compatibility
    | > issues
    | > between Visual Studio and Vista. As we are not Visual Studio expert, I'd
    | > like to suggest that you also submit a post in the following MSDN
    | > newsgroup
    | > so that this issue can be resolved efficiently.
    | >
    | > microsoft.public.msdn.general
    | >
    | > The engineers and newsgroup members there are more experienced on Visual
    | > Studio related issues, and should be able to provide you with
    suggestions
    | > on this issue.
    | >
    | > Meanwhile,I'd like to share with you some basic information.
    | >
    | > Based on my research, this issue might be caused by not properly
    | > installing
    | > Visual Studio 2005/2008.
    | >
    | > I recommend you follow the below steps to uninstall Visual Studio 2008
    and
    | > reinstall it.
    | >
    | > 1. Please follow the below article to uninstalling Visual Studio
    | > 2008
    | > http://msdn2.microsoft.com/en-us/vs2008/bb968856.aspx
    | >
    | > 2. Install the latest Windows updates.
    | >
    | > 3. Check if there is any anti-virus or antispyware running. Turn
    | > them off before installation.
    | >
    | > 4. Make sure that the installation media is healthy. If the
    | > installation from DVD is not working well, you can try copying the
    | > contents
    | > of the disc to the hard disk and try the installation from the hard
    disk.
    | >
    | > 5. Temporarily disable/dismiss Windows Update during installation
    | > (especially in Vista see:
    | > http://blogs.msdn.com/astebner/archive/2007/11/13/6190778.aspx)
    | >
    | > 6. Run the installation as administrator.
    | >
    | > After the installation is finished, please check whether the issue still
    | > exists.
    | >
    | > If yes, I recommend you to contact to MSDN support engineers for further
    | > investigation.
    | >
    | > Thanks.
    | >
    | > Sincerely,
    | > Neo Zhu,
    | > Microsoft Online Support
    | > Microsoft Global Technical Support Center
    | >
    | > 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.
    | >
    | >
    | >
    |
    |
     
    Jian-Ping Zhu [MSFT], Apr 9, 2008
    #9
  10. Jim Kay

    Bob Guest

    Bob, Apr 9, 2008
    #10
  11. Jim Kay

    Jim Kay Guest

    McAfee did not cause this problem. It was very specifically the install of
    Visual-Studio 2008 that did it.

    At that particular time, I was using F-Secure, not McAfee.
     
    Jim Kay, Apr 10, 2008
    #11
  12. Jim Kay

    Jim Kay Guest

    Some of the time I do get a prompt telling me that access to C:\Config.msi
    was denied. "Retry" never helps. BUT, if I configure Windows Explorere to
    show hidden and system files, I can access C:\Config.msi directly and then I
    see that my account permissions have been automagically removed again so I
    give myself 'full control', then 'retry' works.

    So I know for certain that no other program or process is blocking that
    directory. Unfortunately, my access permissions get removed again
    automagically, sometimes during the very same install process and I have to
    put the permissions back again.

    The biggest problem is that many 'automatic update' services from Microsoft
    and other vendors, do not ever give me the option to 'retry' but they just
    fail. If I'm quick about it when one of them is running (Adobe is a big one)
    I can put my permissions back on and the update works.
     
    Jim Kay, Apr 10, 2008
    #12
  13. Jim Kay

    Jim Kay Guest

    Dear Jian-Ping Zhu,

    I thank you for your honest response about this problem. It's the first one
    I've gotten from Microsoft. Of course, UAC and Visual Studio aren't playing
    well together. (Even though you only acknowledge this between the lines, I
    appreciate it.)

    My personal account is a member of the Administrators group.
    When the permissions get reset on c:\config.msi, the administrators group
    retains 'full control' as would be expected.
    One would expect that disabling UAC would bypass the permissions problem on
    that folder and it certainly does that. It was one of the first things I
    tried.

    Perhaps I should have been explicit about having disabled UAC in the past.
    But I get tired of being pestered to turn it back on and, basically, I think
    it's better for me to have UAC working.

    But you seem to be acknowledging that Visual Studio and UAC don't play well
    together. That's pretty sad now that Vista has been retail since late
    November of 2006 and Microsoft is holding firmly to the position that
    reduced user permissions is a reasonable and necessary approach to limiting
    the risks of rogue software. In fact, I fully agree with Microsoft on this
    point.

    Microsoft is also holding the position that conflicts with UAC are totally
    the responsibility of the application vendors who should either fix their
    product so it doesn't require full administrator rights or should be certain
    their product prompts the user when that is truly necessary.

    OK, I agree. But, of course, Microsoft is ALSO the application vendor for
    Visual Studio and that department hasn't gotten the message about being in
    compliance with UAC.

    I'm certainly old enough and experienced enough to understand that an
    organization as large as Microsoft will inevetibly be inconsistent; even
    seriously inconsistent. But now that Vista has been retail for one year and
    five months, I think it fair of the user community to expect a clear
    acknowledgment and warning from Microsoft about this problem; and really I
    think it should have been fixed LONG AGO!

    In any case, I removed Visual Studio 2008 long ago but the problem remains
    as it has every time before. I am now in the process if reinstalling Visual
    Studio 2008 using the method you provided. With UAC disabled, I am nearly
    certain I won't have the permissions problem as that would be very strange
    indeed.

    So I suppose I get to choose between two alternatives:
    1. totally rebuild my Vista system AGAIN and live without Visual Studio on
    any Vista machine until Microsoft steps up the problem and fixes it.
    2. run without UAC until Microsoft steps up to the problem and fixes it.

    I do wonder how I'm going to know that the problem has actually been fixed
    so I can turn UAC back on. (I'm not at all in the mood to do yet another
    total rebuild. But if something else forces me to, I may go back to running
    Visual Studio on an XP virtual machine which I have already experimented
    with doing.)

    Shie Shie (Thats the best I can do transliterating 'thank you' from
    Mandarin)
    Jim Kay
     
    Jim Kay, Apr 10, 2008
    #13
  14. Jim Kay

    Bob Guest

    I see. So you have tested this and uninstalled McAfee to see if it solves
    the problem?
     
    Bob, Apr 10, 2008
    #14
  15. Hello Jim,

    Thank you for your reply.

    I fully understand your feeling on this issue. Generally speaking, we will
    always try our best to solve and reduce compatibility issues between
    applications and systems. We try to will do full tests before releasing our
    products. Some known issues will be included in the release note together
    with a guide or instruction telling you how to prevent or resolve these
    kinds of issues.

    To this specific issue, I recommend you follow the installation guide
    strictly when installing Visual Studio. If not, some unexpected issues
    might occur. For example,it is recommended to "Run as Administrator" to
    install Visual Studio SP1 in Visual Studio 2005 Service Pack 1 Release
    Notes as Visual Studio installation requires elevated privileges. If you
    run the installation without elevate privileges, you might get some
    problems during the installation or the problem occurs after the
    installation is finished or even after the program is uninstalled.

    You could refer to the following Visual Studio 2005 Service Pack 1 Release
    Notes when install Visual Studio:
    http://support.microsoft.com/kb/928957/

    During the development of Windows Vista, several key investments were made
    to vastly improve overall quality, security, and reliability from previous
    versions of Windows.

    I also notice that the Visual Studio 2005 Service Pack 1 Update for Windows
    Vista is available for download. The Visual Studio 2005 Service Pack 1
    Update for Windows Vista addresses areas of Visual Studio impacted by
    Windows Vista enhancements. If you haven't installed this update, I
    strongly recommend you install this update after the Visual Studio 2005 SP1
    is installed and have another test.

    You could download this update here:

    Visual Studio 2005 Service Pack 1 Update for Windows Vista
    http://www.microsoft.com/downloads/details.aspx?FamilyID=90e2942d-3ad1-4873-
    a2ee-4acc0aace5b6&displaylang=en

    If possible, please test Visual Studio 2005 SP1 together with Update for
    Windows Vista and Visual Studio 2008 on different Vista machines.

    Moreover, the following information is for your reference:

    Visual Studio on Windows Vista FAQ
    http://msdn2.microsoft.com/en-us/vs2005/aa948854

    Visual Studio 2005 on Windows Vista Issue List - Running with normal user
    permissions
    http://msdn2.microsoft.com/en-us/vs2005/aa972193

    Visual Studio 2005 on Windows Vista Issue List - Running with elevated
    administrator permissions
    http://msdn2.microsoft.com/en-us/vs2005/aa964140

    Visual Studio .NET 2003 on Windows Vista Issue List
    http://msdn2.microsoft.com/en-us/vs2005/bb188244.aspx

    I hope this helps. Thanks.

    Sincerely,
    Neo Zhu,
    Microsoft Online Support
    Microsoft Global Technical Support Center

    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.

    --------------------
    | Reply-To: "Jim Kay" <>
    | From: "Jim Kay" <>
    | References: <>
    <>
    <>
    <>
    | In-Reply-To: <>
    | Subject: Re: Visual-Studio severely damages Vista
    | Date: Thu, 10 Apr 2008 09:13:32 -0400
    | Lines: 283
    | Organization: James S. Kay, Consulting
    | Message-ID: <>
    | MIME-Version: 1.0
    | Content-Type: text/plain;
    | format=flowed;
    | charset="iso-8859-1";
    | reply-type=original
    | Content-Transfer-Encoding: 7bit
    | X-Priority: 3
    | X-MSMail-Priority: Normal
    | X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18000
    | X-MS-CommunityGroup-PostID: {A2B86BF4-215C-4546-AD3C-F2E989FB99EC}
    | X-MS-CommunityGroup-ThreadID: 14AAFE37-9C21-418B-83F2-1B503B4EB86F
    | X-MS-CommunityGroup-ParentID: 3940BEB2-5A3D-4DC6-AA54-442408EF818B
    | Newsgroups: microsoft.public.windows.vista.security
    | Path: TK2MSFTNGHUB02.phx.gbl
    | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.vista.security:14776
    | NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
    | X-Tomcat-NG: microsoft.public.windows.vista.security
    |
    | Dear Jian-Ping Zhu,
    |
    | I thank you for your honest response about this problem. It's the first
    one
    | I've gotten from Microsoft. Of course, UAC and Visual Studio aren't
    playing
    | well together. (Even though you only acknowledge this between the lines,
    I
    | appreciate it.)
    |
    | My personal account is a member of the Administrators group.
    | When the permissions get reset on c:\config.msi, the administrators group
    | retains 'full control' as would be expected.
    | One would expect that disabling UAC would bypass the permissions problem
    on
    | that folder and it certainly does that. It was one of the first things I
    | tried.
    |
    | Perhaps I should have been explicit about having disabled UAC in the
    past.
    | But I get tired of being pestered to turn it back on and, basically, I
    think
    | it's better for me to have UAC working.
    |
    | But you seem to be acknowledging that Visual Studio and UAC don't play
    well
    | together. That's pretty sad now that Vista has been retail since late
    | November of 2006 and Microsoft is holding firmly to the position that
    | reduced user permissions is a reasonable and necessary approach to
    limiting
    | the risks of rogue software. In fact, I fully agree with Microsoft on
    this
    | point.
    |
    | Microsoft is also holding the position that conflicts with UAC are
    totally
    | the responsibility of the application vendors who should either fix their
    | product so it doesn't require full administrator rights or should be
    certain
    | their product prompts the user when that is truly necessary.
    |
    | OK, I agree. But, of course, Microsoft is ALSO the application vendor for
    | Visual Studio and that department hasn't gotten the message about being
    in
    | compliance with UAC.
    |
    | I'm certainly old enough and experienced enough to understand that an
    | organization as large as Microsoft will inevetibly be inconsistent; even
    | seriously inconsistent. But now that Vista has been retail for one year
    and
    | five months, I think it fair of the user community to expect a clear
    | acknowledgment and warning from Microsoft about this problem; and really
    I
    | think it should have been fixed LONG AGO!
    |
    | In any case, I removed Visual Studio 2008 long ago but the problem
    remains
    | as it has every time before. I am now in the process if reinstalling
    Visual
    | Studio 2008 using the method you provided. With UAC disabled, I am nearly
    | certain I won't have the permissions problem as that would be very
    strange
    | indeed.
    |
    | So I suppose I get to choose between two alternatives:
    | 1. totally rebuild my Vista system AGAIN and live without Visual Studio
    on
    | any Vista machine until Microsoft steps up the problem and fixes it.
    | 2. run without UAC until Microsoft steps up to the problem and fixes it.
    |
    | I do wonder how I'm going to know that the problem has actually been
    fixed
    | so I can turn UAC back on. (I'm not at all in the mood to do yet another
    | total rebuild. But if something else forces me to, I may go back to
    running
    | Visual Studio on an XP virtual machine which I have already experimented
    | with doing.)
    |
    | Shie Shie (Thats the best I can do transliterating 'thank you' from
    | Mandarin)
    | Jim Kay
    |
    | | > Hello Jim,
    | >
    | > Thank you for the reply.
    | >
    | > I have done some further research and I find that Vista's UAC prompting
    | > might cause this problem. Also running Visual Studio with normal user
    | > permissions on Vista might cause some issues.
    | >
    | > To narrow down this issue, I recommend you follow the steps below and
    have
    | > another try.
    | >
    | > 1. Enable the Administrator account and log in as Administrator.
    | > 2. Disable Vista's UAC prompting.
    | > To do this, please
    | > 1). Go to Start, Run, and enter "MSCONFIG"
    | > 2). Go to the Tools menu.
    | > 3). Halfway down the list, enable 'Disable UAC Disables User Account
    | > Control (Requires Reboot)'
    | > 4). Reboot.
    | >
    | > 3. Please uninstall Visual Studio and reinstall it again following the
    | > steps I mentioned in my last mail.
    | >
    | > After that, please check whether the issues still occur.
    | >
    | > If yes, please tell me in detail that what operation causes the issue.
    | > Please also check whether there are any error messages recorded in Event
    | > logs and let me know. If possible, please capture a screenshot of the
    | > error
    | > message and mail the screenshot to me.
    | >
    | > To capture a screenshot:
    | > ===================
    | > 1. Please press the Print Screen key (PrtScn) on your keyboard.
    | > 2. Click "Start", click "Run", type "mspaint", and click "OK".
    | > 3. In Paint, click Paste under the Edit Menu, click Save under the File
    | > menu, type a file name for the screenshot, choose JPEG as "Save as
    type",
    | > click "Desktop" on the left pane, and click Save.
    | > 4. Please find the screenshot on the Desktop and send it as an
    attachment
    | > to:
    | >
    | > More information
    | > ==============
    | > The following information is for your reference:
    | >
    | > Visual Studio 2005 on Windows Vista Issue List when running with normal
    | > user permissions:
    | > http://msdn2.microsoft.com/en-us/vs2005/aa972193.aspx
    | >
    | > Contents of Microsoft Visual Studio 2005 Setup Issues Readme file
    | > http://support.microsoft.com/default.aspx?scid=kb;EN-US;908452
    | >
    | > I look forward to hearing from you. Thanks.
    | >
    | > Sincerely,
    | > Neo Zhu,
    | > Microsoft Online Support
    | > Microsoft Global Technical Support Center
    | >
    | > 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.
    | >
    | > --------------------
    | > | Reply-To: "Jim Kay" <>
    | > | From: "Jim Kay" <>
    | > | References: <>
    | > <>
    | > | In-Reply-To: <>
    | > | Subject: Re: Visual-Studio severely damages Vista
    | > | Date: Tue, 8 Apr 2008 18:18:30 -0400
    | > | Lines: 99
    | > | Organization: James S. Kay, Consulting
    | > | Message-ID: <>
    | > | MIME-Version: 1.0
    | > | Content-Type: text/plain;
    | > | format=flowed;
    | > | charset="iso-8859-1";
    | > | reply-type=original
    | > | Content-Transfer-Encoding: 7bit
    | > | X-Priority: 3
    | > | X-MSMail-Priority: Normal
    | > | X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
    | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18000
    | > | X-MS-CommunityGroup-PostID: {816E56EE-FDE6-4F47-854D-267DC270FFB5}
    | > | X-MS-CommunityGroup-ThreadID: 14AAFE37-9C21-418B-83F2-1B503B4EB86F
    | > | X-MS-CommunityGroup-ParentID: EFF53A96-D331-46E8-875C-318DE978E604
    | > | Newsgroups: microsoft.public.windows.vista.security
    | > | Path: TK2MSFTNGHUB02.phx.gbl
    | > | Xref: TK2MSFTNGHUB02.phx.gbl
    | > microsoft.public.windows.vista.security:14738
    | > | NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
    | > | X-Tomcat-NG: microsoft.public.windows.vista.security
    | > |
    | > | There are two things in your understanding that are a little off:
    | > |
    | > | 1. removing Visual Studio does not fix the problem. My Vista machines
    | > remain
    | > | permanently broken and must be totally rebuilt to fix them.
    | > | 2. there are many messages in the MSDN forums of people complaining
    | > about
    | > | trouble with access to c:\config.msi directory but there are no (that
    I
    | > ever
    | > | found) responses from anyone at Microsoft that acknowlegeds the
    | > connection
    | > | to Visual Studio installation. I have proven to my own satisfaction
    that
    | > | installing Visual Studio is the cause of the problem. But it cannot,
    as
    | > far
    | > | as I know, ever be reversed other than format the drive and start over
    | > with
    | > | everything.
    | > |
    | > | I have posted in MSDN but Microsoft just ignores the problem and
    doesn't
    | > | respond to ANYONE.
    | > |
    | > | | > | > Hello,
    | > | >
    | > | > Thank you for your post.
    | > | >
    | > | > According to your description, my understanding is that after you
    | > | > installed
    | > | > Visual Studio 2005 or Visual Studio 2008 on your Vista machine, some
    | > | > update
    | > | > processes failed because the access to C:\cinfig.msi is denied.
    After
    | > you
    | > | > uninstalled Visual Studio, the issue gone. You concern is to verify
    | > | > whether
    | > | > it is the Visual Studio that cause this issue and find a solution to
    | > solve
    | > | > this issue.
    | > | >
    | > | > If there is any misunderstanding, please let me know.
    | > | >
    | > | > According to the symptom, it seems that there are some compatibility
    | > | > issues
    | > | > between Visual Studio and Vista. As we are not Visual Studio
    expert,
    | > I'd
    | > | > like to suggest that you also submit a post in the following MSDN
    | > | > newsgroup
    | > | > so that this issue can be resolved efficiently.
    | > | >
    | > | > microsoft.public.msdn.general
    | > | >
    | > | > The engineers and newsgroup members there are more experienced on
    | > Visual
    | > | > Studio related issues, and should be able to provide you with
    | > suggestions
    | > | > on this issue.
    | > | >
    | > | > Meanwhile,I'd like to share with you some basic information.
    | > | >
    | > | > Based on my research, this issue might be caused by not properly
    | > | > installing
    | > | > Visual Studio 2005/2008.
    | > | >
    | > | > I recommend you follow the below steps to uninstall Visual Studio
    2008
    | > and
    | > | > reinstall it.
    | > | >
    | > | > 1. Please follow the below article to uninstalling Visual
    | > Studio
    | > | > 2008
    | > | > http://msdn2.microsoft.com/en-us/vs2008/bb968856.aspx
    | > | >
    | > | > 2. Install the latest Windows updates.
    | > | >
    | > | > 3. Check if there is any anti-virus or antispyware running.
    | > Turn
    | > | > them off before installation.
    | > | >
    | > | > 4. Make sure that the installation media is healthy. If the
    | > | > installation from DVD is not working well, you can try copying the
    | > | > contents
    | > | > of the disc to the hard disk and try the installation from the hard
    | > disk.
    | > | >
    | > | > 5. Temporarily disable/dismiss Windows Update during
    | > installation
    | > | > (especially in Vista see:
    | > | > http://blogs.msdn.com/astebner/archive/2007/11/13/6190778.aspx)
    | > | >
    | > | > 6. Run the installation as administrator.
    | > | >
    | > | > After the installation is finished, please check whether the issue
    | > still
    | > | > exists.
    | > | >
    | > | > If yes, I recommend you to contact to MSDN support engineers for
    | > further
    | > | > investigation.
    | > | >
    | > | > Thanks.
    | > | >
    | > | > Sincerely,
    | > | > Neo Zhu,
    | > | > Microsoft Online Support
    | > | > Microsoft Global Technical Support Center
    | > | >
    | > | > 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.
    | > | >
    | > | >
    | > | >
    | > |
    | > |
    | >
    |
    |
     
    Jian-Ping Zhu [MSFT], Apr 11, 2008
    #15
  16. Jim Kay

    Julian Guest

    FWIW, VS 2008 also completely broke my (pre-SP1) Vista HP installation,
    likewise requiring a full rebuild.as a result of key/critical services that
    no longer ran atuomatically and couldn't be started manually.

    It was also the longest most disoncerting installation I have ever seen...
    about an hour IIRC.

    It is perversely reassuring to know that this was perhaps not a purely
    random issue.

    If you ever get VS08 installed with the rest of the system running correctly
    please post back - I'd love to know how to do it... but in the meantime this
    laptop is too valuable for me to be experimenting with (it's taking up too
    much time just debugging regular BSOD's since SP1...)

    It's nice to know that MS does at least peer at these groups... would be
    nice if they could perhaps provide some effort to answering specific
    questions that otherwise go unanswered (such as, "How do I log off iSCSI",
    which I've answered for myself... at least when Vista *allows* me to log
    off... but that's another story).

    WRT McAfee - intercepting it at log on and then running as Admin - you could
    try disabling the current run source and setting it to run via the Task
    Scheduler where you can give it Admin rights *with no UAC prompts* at
    run-time... I use this work-around on a number of things...

    Good luck and HTH
     
    Julian, Apr 11, 2008
    #16
  17. Jim Kay

    SG Guest

    SG, Apr 12, 2008
    #17
  18. Jim Kay

    Jim Kay Guest

    I will run this but I should point out that I've not had any installation
    problems with Visual Studio. It's all the other stuff that gets into trouble
    AFTER Visual Studio has been installed (and uninstall doesn't help; only a
    fresh rebuild of Vista helps.)

    Jim
     
    Jim Kay, Apr 12, 2008
    #18
  19. Jim Kay

    Jim Kay Guest

    Thanks for posting. It helps me remember I'm not crazy.

    For the time being, I am running this workstation with UAC turned off. This
    makes everything happy. I logon as a member of the administrators group and
    everything I do has those permissions automagically.

    But this isn't making me very happy.
     
    Jim Kay, Apr 12, 2008
    #19
  20. Jim Kay

    SG Guest

    Hi Jim,

    I didn't have setup problems either, but it did fix a long time annoying
    rouge Registry entries that no matter what I tried I could not modify nor
    delete them. After running SubInACL I was able to fix this problem without a
    hitch. I think it's at least worth a try.

    --
    All the best,
    SG

    Is your computer system ready for Vista?
    https://winqual.microsoft.com/hcl/
     
    SG, Apr 12, 2008
    #20
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.