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.
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.
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.
Update site does not say to turn off virus scanner.
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?
It just doesn't seem like the kind of error I would
expect from collisions with an active virus scanner.
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.
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
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,042 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 141:58:47 |
| Calls: | 500,263 |
| Calls today: | 1 |
| Files: | 95,201 |
| D/L today: |
73 files (64,340K bytes) |
| Messages: | 464,545 |