seotae...@gmail.com wrote:
> Hi Paul,
>
> Thanks for the help!
>
> I did a System Restore in my Daokorea M010 computer many times and
> when I shutdown the computer as if I'm logged in as Administrator
> with the Remote Procedure Call service running it hangs at "Windows
> is shutting down...". I have to do a hard turn-off by holding down
> the Power button.
>
> In May 10th I started the computer in Safe Mode using Disk Cleanup
> and ALYac to clean up the computer. Then I restarted the computer
> in normal mode but the problem is back.
>
> In May 17th I installed the User Profile Hive Cleanup Service
> and got this problem again in normal mode with Remote Procedure
> Call service running.
>
> In May 21st I started the Malicious Software Removal Tool to do
> a full scan in my computer. The full scan took three hours. (The
> version that I have on my Daokorea M010 computer is from September
> 2015. In the system32 folder I deleted wuauclt.exe and renamed
> wuauclt1.exe to wuauclt.exe. No updates are downloaded at all.)
>
> When I kill the Remote Procedure Call service and shutdown the
> computer with Administrator in normal mode it works fine.
Just about every service on the computer,
has a dependency on the RPC service. Killing
the service *should* just about cripple the
computer instantly. If you didn't shut down
the computer immediately after doing that,
it might very well shut itself down (as
there are two services on the computer, security
related, that if those services die, the OS
cannot guarantee security, so the OS would
then decide to shut down). When WinXP suffers
a "security failure", shutdown is supposed to
happen within the next 60 seconds, with the
user having no control of the eventual shutdown.
And if the computer likes to hang, it could
*still* hang, even though the OS itself
has initiated the shutdown.
Killing RPC, really doesn't tell you anything
about "dependencies" or "guilty culprits". Since
just about every other service provided by
Microsoft, depends on RPC. So that observation,
that it behaves normally when RPC is terminated,
doesn't identify the guilty party. We still
don't get a clue as to what else is broken.
The UPHClean installation, is mainly for less-serious
kinds of "hangs" at shutdown. Whatever is wrong
with your setup, it's beyond my skill to diagnose.
It sounds like you're better at figuring this
stuff out than I am.
You can probably uninstall UPHClean, if you don't
think it is helping. It's purpose is to help
close references to open Registry hives. So you
don't have to use it. But it does seem to help
me here with things like ATI video card drivers,
the package of which tends to hold onto a
registry hive at shutdown.
There are diagnostic procedures for debugging
shutdown issues, but they don't work if you
have to hit the power button to complete
shutdown. When the computer hangs and simply
will not complete the shutdown on its own,
no diagnostic can generate a nice log for us
to tell us why. The act of pushing the power
button, is most likely to damage any log files
that are in the process of being written.
And doing a static analysis of the computer,
before even getting to the shutdown point,
is pretty hopeless.
If I didn't want to reinstall the OS from scratch,
to solve this problem, I would probably go to
one of the malware removal sites, describe
your symptoms, and have them recommend their
various scanning procedures. Maybe the damage
is from malware at some point, or perhaps
some "cleaning" of the OS has damaged it.
And some of those malware removal people
are pretty sharp, and they might spot the
thing preventing shutdown as a side-effect
of the malware scan tools. That's a form of
static analysis, but not something I'm
trained in.
What I'm finding in 2016, is commercial
packages can add all sorts of stuff to the
OS, to destabilize it. Causing WinXP to
exhibit a wide range of strange symptoms.
It's pretty difficult to keep this
OS in tip-top shape. It's not that WinXP
is a bad OS, merely that the code added
isn't all that well written. The code
used, just isn't getting tested properly
on WinXP, to make sure it works right.
There are software companies, I can trust
to test their code. And others that just
add bloat without regard for the side-effects.
It won't take you long to spot the differences
in the company products. I had one product,
where most of the trouble happens, when it
decided to self-update to the next revision.
And even though I'd paid good money for it,
it was time to uninstall it and toss it.
Lesson learned.
Paul