• Re: WinXP Pro x86 more Framework security updates getting halted by un

    From glee29@spamindspring.com@1:124/5013 to All on Thu Jan 31 19:14:17 2019
    Path: eternal-september.org!mx04.eternal-september.org!mx04.eternal-september.org!.PO STED!not-for-mail
    From: "glee" <glee29@spamindspring.com>
    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: Sat, 1 Dec 2012 15:40:13 -0500
    Organization: A noiseless patient Spider
    Lines: 41
    Message-ID: <k9dpv5$gml$1@dont-email.me>
    References: <ef7629fc-2255-4a41-aa1d-7745ab787f39@y8g2000yqy.googlegroups.com> <k6iec7$3mh$1@news.mixmin.net> <a0ec576e-b2c6-4535-836f-b5b12d5b31c8@z2g2000yqj.googlegroups.com> <k6o6jq$211m$1@adenine.netfront.net> <fb9e60a5-49aa-4543-9057-9bfe8bcf8089@h9g2000yqd.googlegroups.com> <k80l7v$tig$2@speranza.aioe.org> <6fedde6b-1462-4434-b831-437aa62f029a@v9g2000yql.googlegroups.com> <k93smk$89u$1@dont-email.me> <d55a1497-2211-4586-86bd-e5ab0629f92f@m4g2000pbd.googlegroups.com> Mime-Version: 1.0
    Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
    Content-Transfer-Encoding: 7bit
    Injection-Date: Sat, 1 Dec 2012 20:40:05 +0000 (UTC)
    Injection-Info: mx04.eternal-september.org; posting-host="ccf6a07c37fd525f116978f5ad44b4b6";
    logging-data="17109"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18hIICF4me43vjRmFd84x1b"
    X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
    X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
    Cancel-Lock: sha1:IHB8eT14V4B1pC7KERLi2sBG0yw=
    X-Priority: 3
    X-MSMail-Priority: Normal
    Xref: mx04.eternal-september.org alt.windows-xp:3923 microsoft.public.windowsxp.setup_deployment:2401 microsoft.public.windowsxp.help_and_support:30778 microsoft.public.windowsxp.general:105654

    "Greegor" <greegor47@gmail.com> wrote in message news:d55a1497-2211-4586-86bd-e5ab0629f92f@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?


    No telling what caused the damage (the registry cleaners you use to
    'fix' things can cause errors like this), but you need to use Aaron
    Stebner's tool to remove all .NET Frameworks on XP, and then manually
    download and install only what you need.

    I think I'll go one better and do a new install
    without any Framework of any version. Ever.

    Why are you installing .NET Framework 4.x?
    Do you have software that
    requires it? Don't install it if you don't need it.

    Building a clean master with all updates for my
    little fleet of 5 identical off lease OEM computers.

    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.
    --
    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)
  • From glee29@spamindspring.com@1:124/5013 to All on Thu Jan 31 19:14:17 2019
    Path: eternal-september.org!mx04.eternal-september.org!mx04.eternal-september.org!.PO STED!not-for-mail
    From: "glee" <glee29@spamindspring.com>
    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: Sun, 2 Dec 2012 09:19:01 -0500
    Organization: A noiseless patient Spider
    Lines: 75
    Message-ID: <k9fo0o$sj9$1@dont-email.me>
    References: <ef7629fc-2255-4a41-aa1d-7745ab787f39@y8g2000yqy.googlegroups.com> <k6iec7$3mh$1@news.mixmin.net> <a0ec576e-b2c6-4535-836f-b5b12d5b31c8@z2g2000yqj.googlegroups.com> <k6o6jq$211m$1@adenine.netfront.net> <fb9e60a5-49aa-4543-9057-9bfe8bcf8089@h9g2000yqd.googlegroups.com> <k80l7v$tig$2@speranza.aioe.org> <6fedde6b-1462-4434-b831-437aa62f029a@v9g2000yql.googlegroups.com> <k93smk$89u$1@dont-email.me> <d55a1497-2211-4586-86bd-e5ab0629f92f@m4g2000pbd.googlegroups.com> <k9dpv5$gml$1@dont-email.me> <d2a0554a-76b3-4103-81af-b9fe3e14bfc6@b4g2000pby.googlegroups.com> Mime-Version: 1.0
    Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
    Content-Transfer-Encoding: 7bit
    Injection-Date: Sun, 2 Dec 2012 14:19:04 +0000 (UTC)
    Injection-Info: mx04.eternal-september.org; posting-host="ccf6a07c37fd525f116978f5ad44b4b6";
    logging-data="29289"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/XxTkss5kr+WOsTq10G7S1"
    X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
    X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
    Cancel-Lock: sha1:l2UpC29M15jYSdwwXU6g3pSrdSA=
    X-Priority: 3
    X-MSMail-Priority: Normal
    Xref: mx04.eternal-september.org alt.windows-xp:3926 microsoft.public.windowsxp.setup_deployment:2404 microsoft.public.windowsxp.help_and_support:30781 microsoft.public.windowsxp.general:105661

    "Greegor" <greegor47@gmail.com> wrote in message news:d2a0554a-76b3-4103-81af-b9fe3e14bfc6@b4g2000pby.googlegroups.com...

    On Dec 1, 2:40 pm, "glee" <gle...@spamindspring.com> wrote:
    "Greegor" <greego...@gmail.com> wrote in message

    news:d55a1497-2211-4586-86bd-e5ab0629f92f@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.


    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.
    --
    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)
  • From glee29@spamindspring.com@1:124/5013 to All on Thu Jan 31 19:14:17 2019
    Path: eternal-september.org!mx04.eternal-september.org!mx04.eternal-september.org!.PO STED!not-for-mail
    From: "glee" <glee29@spamindspring.com>
    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: <k9krn9$iu2$1@dont-email.me>
    References: <ef7629fc-2255-4a41-aa1d-7745ab787f39@y8g2000yqy.googlegroups.com> <k6iec7$3mh$1@news.mixmin.net> <a0ec576e-b2c6-4535-836f-b5b12d5b31c8@z2g2000yqj.googlegroups.com> <k6o6jq$211m$1@adenine.netfront.net> <fb9e60a5-49aa-4543-9057-9bfe8bcf8089@h9g2000yqd.googlegroups.com> <k80l7v$tig$2@speranza.aioe.org> <6fedde6b-1462-4434-b831-437aa62f029a@v9g2000yql.googlegroups.com> <k93smk$89u$1@dont-email.me> <d55a1497-2211-4586-86bd-e5ab0629f92f@m4g2000pbd.googlegroups.com> <k9dpv5$gml$1@dont-email.me> <d2a0554a-76b3-4103-81af-b9fe3e14bfc6@b4g2000pby.googlegroups.com> <k9fo0o$sj9$1@dont-email.me> <af9ba75b-2913-4806-a79b-a05362fd06f4@6g2000pbh.googlegroups.com>
    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="abuse@eternal-september.org"; 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" <greegor47@gmail.com> wrote in message news:af9ba75b-2913-4806-a79b-a05362fd06f4@6g2000pbh.googlegroups.com...
    On Dec 2, 8:19 am, "glee" <gle...@spamindspring.com> 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)