Received: by 10.66.79.6 with SMTP id f6mr1947545pax.3.1354493993468;
        Sun, 02 Dec 2012 16:19:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.50.108.200 with SMTP id hm8mr1549812igb.10.1354493993267; Sun,
 02 Dec 2012 16:19:53 -0800 (PST)
Path:
eternal-september.org!mx04.eternal-september.org!mx04.eternal-september.org!fee
der.eternal-september.org!news.glorb.com!kr7no15494713pbb.0!news-out.google.com
!6ni21476pbd.1!nntp.google.com!kt20no16385710pbb.1!postnews.google.com!6g2000pb
h.googlegroups.com!not-for-mail
Newsgroups:
alt.windows-xp,microsoft.public.windowsxp.setup_deployment,microsoft.public.win
dowsxp.help_and_support,microsoft.public.windowsxp.general
Date: Sun, 2 Dec 2012 16:19:53 -0800 (PST)
Complaints-To: groups-abuse{at}google.com
Injection-Info: 6g2000pbh.googlegroups.com; posting-host=199.189.229.221;
posting-account=5SXNEQkAAAC6SFadCHPE9O-jLMHq7h-Y
NNTP-Posting-Host: 199.189.229.221
References: 
 

 

 

 

 

 
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1;
 Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152;
 .NET CLR 3.5.30729; .NET4.0C),gzip(gfe)
Message-ID: 
Subject: Re: WinXP Pro x86 more Framework security updates getting halted by
 uninstall errors!
From: Greegor 
Injection-Date: Mon, 03 Dec 2012 00:19:53 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Xref: mx04.eternal-september.org alt.windows-xp:3929
microsoft.public.windowsxp.setup_deployment:2407
microsoft.public.windowsxp.help_and_support:30784
microsoft.public.windowsxp.general:105675

On Dec 2, 8:19 am, "glee"  wrote:
> "Greegor"  wrote in message
>
> news:d2a0554a-76b3-4103-81af-b9fe3e14bfc6{at}b4g2000pby.googlegroups.com...
>
>
>
> >On Dec 1, 2:40 pm, "glee"  wrote:
> >> "Greegor"  wrote in message
>
>
>>news:d55a1497-2211-4586-86bd-e5ab0629f92f{at}m4g2000pbd.googlegroups.com....
>
> >> > Glen wrote:
> >> >> The errors you are seeing are due to some registry information
> >> >> being
> >> >> missing, or some files that have been corrupted,
from the original
> >> >> installation of the .NET Framework.
>
> >> >It's doing it on 2 of my working systems which DO have
> >> >clean installs and never once ran up regedit.
>
> >> Interesting.... nothing has been installed except an stock clean
> >> install
> >> of the OS? Is an anti-virus installed at the time of the .NET
> >> installation, and is it active at the time?
>
> >MSE installed and running in the order it was offered up
> >by the update site.
>
> I assume you mean the updates were offerred... Windows Update doesn't
> automatically offer MSE itself.
>
> >Update site does not say to turn off virus scanner.
>
> No, but it I always do when installing updates to .NET or Internet
> Explorer, at the least.  AV's vary.... Norton has a history of
> interfering, as well as some others (ESET did for a while)... other AVs
> don't cause any trouble most of the time.
>
> >Are problem with installers looking for necessary files in
> >crazy places with long random character names a
> >common symptom caused by a virus scanner operating?
>
> That 'symptom' is usually the uninstaller looking for the original
> temporary folder that was used (or recorded as used) during the original
> installation.  Often those folders are deleted by the installer at the
> end of the installation, or by the user during maintenance.

That seems to be exactly what is going wrong.
How could a virus scanner like MSE possibly
cause this sort of malfunction?

How could it cause the record of where crucial
code or overlays are, to refer to the WRONG
directory?

I will try to test for this effect, maybe next week.

> >It just doesn't seem like the kind of error I would
> >expect from collisions with an active virus scanner.
>
> No, probably not.  It could be a defect in the installer, but if it was,
> one would expect to see the issue everywhere, and it is actually not
> that common.

> > snip
> >> But why are you installing .NET Framework if you have no software
> >> that
> >> uses it? .NET Framework 4 is not pushed on Windows Update, it is an
> >> optional update listed separately. I don't think any .NET flavor is
> >> pushed any longer for XP on Windows Update if it isn't already
> >> present
> >> due to some 3rd-party software. I'll have to look at my clean install
> >> on another machine.
>
> >Just in case!   But not any more.
>
> There's no good reason to install any .NET version if you don't have
> software asking for it during installation, in order to run the
> software.

I certainly won't.
--- Platinum Xpress/Win/WINServer v3.1