Subj : Re: WinXP Pro x86 more Framework security updates getting halted by un
To : All
From :
[email protected]
Date : Thu Jan 31 2019 07:14 pm
Path:
eternal-september.org!mx04.eternal-september.org!mx04.eternal-september.org!.PO
STED!not-for-mail
From: "glee" <
[email protected]>
Newsgroups:
alt.windows-xp,microsoft.public.windowsxp.setup_deployment,microsoft.public.win
dowsxp.help_and_support,microsoft.public.windowsxp.general
Subject: Re: WinXP Pro x86 more Framework security updates getting halted by
uninstall errors!
Date: Tue, 4 Dec 2012 07:53:09 -0500
Organization: A noiseless patient Spider
Lines: 80
Message-ID: <
[email protected]>
References: <
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 4 Dec 2012 12:52:57 +0000 (UTC)
Injection-Info: mx04.eternal-september.org;
posting-host="ccf6a07c37fd525f116978f5ad44b4b6";
logging-data="19394"; mail-complaints-to="
[email protected]";
posting-account="U2FsdGVkX19G/jkBKjDtjd1J3Y/orcF/"
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
Cancel-Lock: sha1:4cj7uzlOOwa8HP4E8DqJXu7LFjs=
X-Priority: 3
X-MSMail-Priority: Normal
Xref: mx04.eternal-september.org alt.windows-xp:3934
microsoft.public.windowsxp.setup_deployment:2412
microsoft.public.windowsxp.help_and_support:30795
microsoft.public.windowsxp.general:105690
"Greegor" <
[email protected]> wrote in message
news:
[email protected]...
On Dec 2, 8:19 am, "glee" <
[email protected]> wrote:
>
>> >> > 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
I didn't state that an A-V, in your case MSE, would necessarily cause
it. As I stated in my reply, it could be a defect in the installer,
though one would then expect to see the issue everywhere, and it isn't
that common. That said, if an A-V is interfering with an installation,
corruption of the installation could occur in a number of places....
files not copied, or corrupted Registry entries, and so forth.
..NET updates have long been a problem, searching for the myriad causes
of the problems isn't worth the time to me.... it just seems to fragile
for prime time. I look for alternate software that doesn't use .NET
wherever possible. Vista, Win7 and 8 all have some versions built in
now.
--
Glen Ventura
MS MVP Oct. 2002 - Sept. 2009
CompTIA A+
--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
