Microsoft Update - delayed delete

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Does anyone know how to diagnose the process that XP goes through to update
system files in use. During a Microsoft Update,there are sometimes files can
not be replaced and require a reboot.

My system does not complete the file updates after the reboot. If you read
the KB#.log file located in the Windows directory after the installation,
there will be a reference to a file and the tmp file that will be used to
replace the file upon reboot. If you check the versions of the file it was
to replace, it will still be the old version. If you check the version of the
..tmp file, it will be the newer version.

This tells me that the update process has not completed and the system has
some of the files updated but not all of them. It has really caused some
weird functionality. To temporarily fix some of the effects I have run PE
and renamed the .tmp files and over written the older versions with the
updates. This has helped, but the process is cumbersome and time consuming.

I have been looking for the reason that the system can't update files on
reboot. I suspect some form of trojan or spyware that has disabled this
functionality. Todate I haven't been able to resolve this.
 
Although this is Microsoft Update related I do not believe it is any issue
with Microsoft Update. The updates complete successfully. The OS doesn't
finish the udpate after the reboot. That is where the problem lies. ANY
system file update that requires a reboot will fail. That is why I have
posted here since there isn't a specific category for the XP OS System File
update process.

--
MD


S.Sengupta said:
Hi,
Kindly post here:-
http://tinyurl.com/8h5ev

regards,
S.Sengupta[MS-MVP]

Mark said:
Does anyone know how to diagnose the process that XP goes through to update
system files in use. During a Microsoft Update,there are sometimes files can
not be replaced and require a reboot.

My system does not complete the file updates after the reboot. If you read
the KB#.log file located in the Windows directory after the installation,
there will be a reference to a file and the tmp file that will be used to
replace the file upon reboot. If you check the versions of the file it was
to replace, it will still be the old version. If you check the version of the
.tmp file, it will be the newer version.

This tells me that the update process has not completed and the system has
some of the files updated but not all of them. It has really caused some
weird functionality. To temporarily fix some of the effects I have run PE
and renamed the .tmp files and over written the older versions with the
updates. This has helped, but the process is cumbersome and time consuming.

I have been looking for the reason that the system can't update files on
reboot. I suspect some form of trojan or spyware that has disabled this
functionality. Todate I haven't been able to resolve this.
Click to expand...
Click to expand...
 
If it is spy ware causing the problem, I also believe it could be. Down load
spyware doctor from pctools.com. I had simular problems alonge with others.
I had run all the popular spyware programs. that I will not mention here
because, It may cause a problem, after i ran those programs and deleated all
the spyware they found. and didn't fix my problem, I came accross the
spyware doctor from pctools, It found 2209 spyware ware thats right 2209, I
had to purchass the program but it deleated the spyware and fixed my
problem, also it will keep it from happening again. It may not be your
problem but it may.
I hope this helps.

Boris


Mark D said:
Although this is Microsoft Update related I do not believe it is any issue
with Microsoft Update. The updates complete successfully. The OS doesn't
finish the udpate after the reboot. That is where the problem lies. ANY
system file update that requires a reboot will fail. That is why I have
posted here since there isn't a specific category for the XP OS System
File
update process.

--
MD


S.Sengupta said:
Hi,
Kindly post here:-
http://tinyurl.com/8h5ev

regards,
S.Sengupta[MS-MVP]

Mark said:
Does anyone know how to diagnose the process that XP goes through to
update
system files in use. During a Microsoft Update,there are sometimes
files can
not be replaced and require a reboot.

My system does not complete the file updates after the reboot. If you
read
the KB#.log file located in the Windows directory after the
installation,
there will be a reference to a file and the tmp file that will be used
to
replace the file upon reboot. If you check the versions of the file it
was
to replace, it will still be the old version. If you check the version
of the
.tmp file, it will be the newer version.

This tells me that the update process has not completed and the system
has
some of the files updated but not all of them. It has really caused
some
weird functionality. To temporarily fix some of the effects I have run
PE
and renamed the .tmp files and over written the older versions with the
updates. This has helped, but the process is cumbersome and time
consuming.

I have been looking for the reason that the system can't update files
on
reboot. I suspect some form of trojan or spyware that has disabled
this
functionality. Todate I haven't been able to resolve this.
Click to expand...
Click to expand...
Click to expand...
 
Thanks Boris. I did run it and it found 51 more. Couple were not that
important so I am must thinking about whether to buy. Still not sure that
would fix it anyways.

I have been avoiding the reload the whole OS because the state this computer
is in is very interesting. What would stop the process of renaming temp
files to system files. Just hoping someone here knows where to look so I can
determine what is really wrong with this system.
--
MD


BORIS BELCHOFF said:
If it is spy ware causing the problem, I also believe it could be. Down load
spyware doctor from pctools.com. I had simular problems alonge with others.
I had run all the popular spyware programs. that I will not mention here
because, It may cause a problem, after i ran those programs and deleated all
the spyware they found. and didn't fix my problem, I came accross the
spyware doctor from pctools, It found 2209 spyware ware thats right 2209, I
had to purchass the program but it deleated the spyware and fixed my
problem, also it will keep it from happening again. It may not be your
problem but it may.
I hope this helps.

Boris


Mark D said:
Although this is Microsoft Update related I do not believe it is any issue
with Microsoft Update. The updates complete successfully. The OS doesn't
finish the udpate after the reboot. That is where the problem lies. ANY
system file update that requires a reboot will fail. That is why I have
posted here since there isn't a specific category for the XP OS System
File
update process.

--
MD


S.Sengupta said:
Hi,
Kindly post here:-
http://tinyurl.com/8h5ev

regards,
S.Sengupta[MS-MVP]

Mark D wrote:

Does anyone know how to diagnose the process that XP goes through to
update
system files in use. During a Microsoft Update,there are sometimes
files can
not be replaced and require a reboot.

My system does not complete the file updates after the reboot. If you
read
the KB#.log file located in the Windows directory after the
installation,
there will be a reference to a file and the tmp file that will be used
to
replace the file upon reboot. If you check the versions of the file it
was
to replace, it will still be the old version. If you check the version
of the
.tmp file, it will be the newer version.

This tells me that the update process has not completed and the system
has
some of the files updated but not all of them. It has really caused
some
weird functionality. To temporarily fix some of the effects I have run
PE
and renamed the .tmp files and over written the older versions with the
updates. This has helped, but the process is cumbersome and time
consuming.

I have been looking for the reason that the system can't update files
on
reboot. I suspect some form of trojan or spyware that has disabled
this
functionality. Todate I haven't been able to resolve this.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top