S
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/
"Jim Kay" <joschka@newsgroup.nospam> wrote in message
news:2C22397F-44A9-4691-8148-66B360E2E4EA@microsoft.com...<span style="color:blue">
>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
>
> "SG" <sorry@nomail.com> wrote in message
> news:u3s2$uEnIHA.1280@TK2MSFTNGP05.phx.gbl...<span style="color:green">
>> Hi Jim,
>>
>> Found something that "may" help you.
>> http://blogs.msdn.com/astebner/archive/200.../04/739820.aspx
>>
>> Note the section:
>> Example of a setup failure that was fixed by SubInACL
>> A customer contacted me with a problem installing Visual Studio 2005
>>
>>
>> --
>> All the best,
>> SG
>>
>> Is your computer system ready for Vista?
>> https://winqual.microsoft.com/hcl/
>>
>> "Jim Kay" <joschka@newsgroup.nospam> wrote in message
>> news:B3E74237-110A-479A-A36C-8110ACB8F534@microsoft.com...<span style="color:darkred">
>>> 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.
>>>
>>> "Bob" <bob@nowhere.net> wrote in message
>>> news:b8qdnUKN_ttMf2HanZ2dnUVZ_tmhnZ2d@comcast.com...
>>>> McAfee is known to cause problems in Vista. Sometimes they don’t show
>>>> up immediately.
>>>> Replace McAfee with the free AVG http://free.grisoft.com/ or Avast
>>>> http://www.avast.com/eng/avast_4_home.html, and Windows Firewall and
>>>> Windows Defender. Disabling McAfee is not enough. You need to
>>>> completely uninstall it.
>>>> McAfee Consumer Product Removal Tool
>>>> http://www.softpedia.com/get/Tweak/Uninsta...oval-Tool.shtml
>>>> -------
>>>> Report back, please
>>>>
>>>> "SG" <sorry@nomail.com> wrote in message
>>>> news:eWE7kUgmIHA.1680@TK2MSFTNGP06.phx.gbl...
>>>>> 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/
>>>>>
>>>>> "Bob" <bob@nowhere.net> wrote in message
>>>>> news:U4adnftau6XE3WHanZ2dnUVZ_sKqnZ2d@comcast.com...
>>>>>> What post?
>>>>>> When posting, please quote relevant information so that others know
>>>>>> what you’re talking about.
>>>>> SNIPPED
>>>>
>>></span>
>></span>
> </span>
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/
"Jim Kay" <joschka@newsgroup.nospam> wrote in message
news:2C22397F-44A9-4691-8148-66B360E2E4EA@microsoft.com...<span style="color:blue">
>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
>
> "SG" <sorry@nomail.com> wrote in message
> news:u3s2$uEnIHA.1280@TK2MSFTNGP05.phx.gbl...<span style="color:green">
>> Hi Jim,
>>
>> Found something that "may" help you.
>> http://blogs.msdn.com/astebner/archive/200.../04/739820.aspx
>>
>> Note the section:
>> Example of a setup failure that was fixed by SubInACL
>> A customer contacted me with a problem installing Visual Studio 2005
>>
>>
>> --
>> All the best,
>> SG
>>
>> Is your computer system ready for Vista?
>> https://winqual.microsoft.com/hcl/
>>
>> "Jim Kay" <joschka@newsgroup.nospam> wrote in message
>> news:B3E74237-110A-479A-A36C-8110ACB8F534@microsoft.com...<span style="color:darkred">
>>> 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.
>>>
>>> "Bob" <bob@nowhere.net> wrote in message
>>> news:b8qdnUKN_ttMf2HanZ2dnUVZ_tmhnZ2d@comcast.com...
>>>> McAfee is known to cause problems in Vista. Sometimes they don’t show
>>>> up immediately.
>>>> Replace McAfee with the free AVG http://free.grisoft.com/ or Avast
>>>> http://www.avast.com/eng/avast_4_home.html, and Windows Firewall and
>>>> Windows Defender. Disabling McAfee is not enough. You need to
>>>> completely uninstall it.
>>>> McAfee Consumer Product Removal Tool
>>>> http://www.softpedia.com/get/Tweak/Uninsta...oval-Tool.shtml
>>>> -------
>>>> Report back, please
>>>>
>>>> "SG" <sorry@nomail.com> wrote in message
>>>> news:eWE7kUgmIHA.1680@TK2MSFTNGP06.phx.gbl...
>>>>> 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/
>>>>>
>>>>> "Bob" <bob@nowhere.net> wrote in message
>>>>> news:U4adnftau6XE3WHanZ2dnUVZ_sKqnZ2d@comcast.com...
>>>>>> What post?
>>>>>> When posting, please quote relevant information so that others know
>>>>>> what you’re talking about.
>>>>> SNIPPED
>>>>
>>></span>
>></span>
> </span>