Doing a System Restore should really only be considered if the problem[s]
is/are to such a degree that it makes normal operation impossible. Also,
to be able to decide if this truly is the case, you would have to wait a
certain amount of time to see if the problems persist, symptoms change in
some way or, even, rectifies itself completely.
For want of any detail in your description of your PC or it's symptoms,
what I can say is that one possible cause might be a single [background]
application, trying to access and update itself from the network / internet
and not being able to.
Software often tries to update its program to the latest version from the
internet, and it might only take a couple of applications to do this at the
same time for it to cause a large memory resource burden. A problem like
this is transitory and needs no intervention but to wait till the tasks
complete themselves. Also, performing a System Restore would not help, I
think you will admit, in this case.
I only gave the above as an example because it shows how some causes would
be unaffected by System Restore and some would rectify themselves without
needing any help.
Rather than it being a "problem" and wanting to obtain a "fix" for it - in
my opinion (based on your very brief commentary) it is much more likely to
be a memory "bottleneck" who's cause is a coincidence in the number of
requests being received all at one time.
Some facts you can be 100% certain of : Long waits for very basic aspects
of Window's to be accessed (like waiting for "explorer.exe" to appear) are
caused by low memory resources. You can easily check this by opening the
Window's Task Manager (by right-clicking on an empty area of the taskbar
and choosing "Task Manager").
Then looking under the "Processes" tab to see which process is taking the
largest amount of "Memory Usage" (you can arrange the list in order of "Mem
Usage" by clicking on the column-header of that name until the largest are
at the top). It is then immediately apparent which process[es] is/are the
one causing delays in all subsequent operations you attempt.
Again, the remedy would be simply to wait. However, after you find which
items in "Task Manager" are responsible, you may have the opportunity to
choose for that software not to search for updates, or even stop it's being
automatically loaded at system start-up. And again, you won't be able to
investigate until you find out the items responsible.
==
Cheers, Tim Meddick, Peckham, London. :-)
"Albert" <
aml...@hotmail.com> wrote in message
news:8kio97t8aecu2s2ed...@4ax.com...