service pack 2 and time errors

I installed service pack 2 after i had run and updated my avg, spybot s/d and
spyware blaster , i also followed all the advice before installing, anyway, i
got it on sat. it was uninstalled by sunday night, it had froze my pc a dozen
times in that time,
i kept getting windows explorer has encountered and error blah blah, then
everything just died each time it closed everything down ,even switching my
pc off.
i tried system restore as i had created a restore point before installing,
but when i restarted it said it couldnt restore, so i uninstalled service
pack 2 , but still couldnt get connected to aol, i uninstalled that and
reinstalled went through various other things , then after uninstalling the
bt voyager modem and reinstalling i got connected again, but yesterday and
today especially, i have been getting W32 time errors . this is what comes up
in event viewer: Explanation
The Windows Time Service cannot synchronize time with its time sources.
Windows Time Service will attempt synchronization at a later time.

The W32time 29 message is usually caused by connectivity issues between a
client and its source. In some cases, the source computer is unavailable; it
may be restarting, disconnected from the network, or unreachable because of
firewall or router configurations. If the W32time 29 condition persists, you
should immediately troubleshoot the issue to ensure that successful
synchronization can resume.


User Action
To ensure that the system can connect to the source, do one or more of the
following:

Verify that the local computer is capable of contacting the desired source.
In most cases, a simple connectivity test such as “ping� is adequate.
Confirm that Windows Time Service (or other NTP Time Service) is running and
available on the source system.
If you are using a manually configured peer, such as time.windows.com,
verify that the name is typed correctly and that the system is available.
Confirm that there are no network devices that block traffic on port 123
between the local computer and the time source.

dont know what it means, if any one could explain in english please or
better still if anyone knows what to do to fix problem, thank you

-----Original Message-----
dont know what it means, if any one could explain in
english please

Basically it's saying that you may not be able to reach
the time server or you may have the wrong name. I'll add
that some third party software firewalls will do this.
(Especially older versions.)

Now I'm reaching (even more) because there isn't a lot of
detail but if you were running an old soft firewall that
Windows didn't recognize and SP2 also turned on the
Windows firewall, that could explain your other issues as
well.

" wrote:


-----Original Message-----
dont know what it means, if any one could explain in
english please

Basically it's saying that you may not be able to reach
the time server or you may have the wrong name. I'll add
that some third party software firewalls will do this.
(Especially older versions.)

Now I'm reaching (even more) because there isn't a lot of
detail but if you were running an old soft firewall that
Windows didn't recognize and SP2 also turned on the
Windows firewall, that could explain your other issues as
well.

I have the Mcafee firewall that was provided with aol 9, i have had no problems with it so rather than having two firewalls running i had switched the service pack 2 one off, since i uninstalled service pack two i keep getting these w32 time errors, i have had 8 today, it freezes the whole system but i didnt have all this before i installed service pack 2, i was wondering if anything might have been left behind,
also when i get the" windows explorer needs to close " window, each time i
send the report i am informed that i dont have service pack 2 and should get
it to solve some connection issues, and for extra security. i did want to get
it but i never had so many problems with pc in such a short space of time as
i ahd when that was on pc. think i will leave it alone. if i could just find
out what is causing this w32 time thing.i have checked the event viewer and i
ahve not had this error before, its all been today , 2 errors recorded at the
same time on 8 different occassions only a few mins apart, other errors
recorded are DCOM errors relating to memory, telling me to check ram and
increase, i do know i need more memory so im not worried about them . thanks
for replying

"=?Utf-8?B?cG9wcHk=?=" writes:
I installed service pack 2 after i had run and updated my avg, spybot s/d and
spyware blaster , i also followed all the advice before installing, anyway, i
got it on sat. it was uninstalled by sunday night, it had froze my pc a dozen
times in that time,
i kept getting windows explorer has encountered and error blah blah, then
everything just died each time it closed everything down ,even switching my
pc off.
....
dont know what it means, if any one could explain in english please or
better still if anyone knows what to do to fix problem, thank you

There have been a string of folks reporting very similar problems
to what you are reporting. Some find that anything which uses
Windows Explorer (Recycle bin, folder shortcuts, control panel,
etc) all have a similar problem. Some find that right clicks are
their major problem. Some find any click. Some find it crashes
on open. Some find it refuses any clicks. There are some claims
but I've been scanning the thousands of postings on SP2 and I don't
think you will find any with "the fix" for this, at least yet.

But, some find it will work when you boot in safe mode.

And, some find it will work when you create a new user and switch
to that user to try it.

One of those might be a temporary work-around till you get an answer.

Some claim it is all spyware and viruses but I haven't seen any
posting that confirmed this for the Windows Explorer problem. I
carefully and repeatedly checked, no viruses or spyware and my
windows explorer locks up every time. Late breaking news, after
hundreds of people reporting this problem, ONE person did let me
know that trendmicro actually found a WORM_SDDROP.A virus/worm, he
removed that and it appeared to solve his problem, so that's 10,000
times people chanting "it's all viruses and spyware" and one correct
diagnosis

Some claim it is all "bad applications" like Divx or Spy Sweeper
being installed that is responsible for this, a few people have
confirmed this but others have these and have no problem, most
reporting the problem don't have these and still have the problem.
I don't have either and it locks up every time.

Some claim it is all "ShellExtensions", little accessory gadgets
that sort of script extra cute features. The advice for that is
to install free ShellExView and to try (carefully) disabling these
features one at a time, if turning one off doesn't do anything then
turn it back on and try again. I did that with all 75 at once and
it made no difference at all. Two people have reported that
disabling one extension he had did appear to fix their problem.

You can escalate to Microsoft, go to
http://support.microsoft.com/windowsxpsp2
and give them all the details and clues and patterns you can find.
There is no guarantee that their analysis or directions will be
correct or even not make it worse. They told me I must "have some
corrupted files, repair windows back to install state and then
reinstall SP2 twice while in Safe mode." Before I did that someone
posted the "switch user" workaround that let me get by temporarily.
I sent email saying that if it worked for one user then it seemed
less likely it was "some corrupted files" and asked if they still
wanted me to blow windows away. They have not reponded to that in
a number of days now. But I can imagine what it is like inside
now.

I hope something in this helps someone. But it appears that the
large majority of people never get a fix for the "Windows Explorer"
problem. If someone tells you to try something and it doesn't help
then please make a posting so we can start accumulating what
suggestions don't do any good. And if someone tells you something
that does work then please report it.