Windows XP Home

  • Thread starter Thread starter AndreJansen
  • Start date Start date
A

AndreJansen

After installing Windows XP Home edition and upgrading to
the lastest version.

1.
I have many filedate's 11-9-2002 (9-11-2002).
Is this normal? 11 september is somewhat special date.
Is there something wrong with this Windows XP Home
package or have all Windows XP Home editions this file
date.

2.
When I delete Iexplore.exe in program files\internet
explorer, it automatiqly re-apears is this normal
behaviour?

Andre
 
1.
I have many filedate's 11-9-2002 (9-11-2002).
Is this normal? 11 september is somewhat special date.
Is there something wrong with this Windows XP Home
package or have all Windows XP Home editions this file
date.

If you purchased a legitimate copy of Windows and it is working properly, I
wouldn't worry about it.
2.
When I delete Iexplore.exe in program files\internet
explorer, it automatiqly re-apears is this normal
behaviour?

You should NEVER be just deleting system files and programs from your hard
drive!!! You can remove IE by going to Control Panel and choosing
Add/Remove Programs and then click the Windows Components button.
 
-----Original Message-----

If you purchased a legitimate copy of Windows and it is working properly, I
wouldn't worry about it.


You should NEVER be just deleting system files and programs from your hard
drive!!! You can remove IE by going to Control Panel and choosing
Add/Remove Programs and then click the Windows Components button.
I know scott,
but it does not appear to me as normal Windows XP
behaviour.
Try it yourself? make a copy of iexplore.exe in \program
files\internet explorer.
delete iexplore.exe
wait 60 seconds
is it back on your system??

This system has just been installed from the original CD
but I can't remember this behaviour to be something that
is normal in Windows XP (Home?)

Andre
 
It is normal behavior because IE is a system component of Windows and unless
uninstalled correctly, it will come back on you.

It just seems like you have a working copy of Windows and are trying to
"test" it by fiddling with it. As I said, if you just did a clean install
from a legitimate copy of Windows and it's working properly, then there's no
need to tinker.
 
Back
Top