Taskman dont work in XP-Pro

On Fri, 13 Jun 2014 04:40:33 -0500, BillW50 wrote:

Well I am not sure how it works, but one machine I had would always scan
the drive at boot and CHKDSK never found anything, but would still check
at every boot. I think it was on a dual boot machine come to think about
it. Another reason I hate dualboot systems! But Hard Disk Sentinel cured
it and I didn't have to worry about that problem anymore.

--

I've never had that happen on my Win98 / Win2000 dual boot machine. But
maybe XP and newer OSs are different in that regard. Now if I lose
power during due to a storm or other reason, then I might get a scandisk
at boot, but there is a reason for it, and once it's run, it's done.

Paul wrote:
Bill in Co wrote:
Paul wrote:
wrote:
On Mon, 09 Jun 2014 13:24:21 -0400, Paul wrote:

http://askleo.com/why_is_my_task_man...do_i_fix_i t/

There is a registry edit in there you can use. Look for
DisableTaskMgr.
In addition, it's possible to remove the decorations from the
outside of the Taskmgr window. So there are at least two things
that can screw up on it.

The only reason for a non-domain user such as yourself to be
seeing this problem, is malware. Malware loves to disable TaskMgr,
so you cannot kill any running processes.

*******

You can't CHKDSK with the intention of repairing something,
on the running C:. Upon a reboot, the C: partition
can be processed by CHKDSK, before it is used by any other software.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Session
Manager\BootExecute autocheck autochk *

The single line, is the "nominal" bootexecute statement. It
would do an immediate CHKDSK if the dirty bit was set on
a partition.

When a user "schedules" a CHKDSK, without the dirty bit being
used, it adds a line to that item. So there is some kind
of explicit line requesting CHKDSK of C:.

HTH,
Paul
I cant see how I could have any malware on this new install, and I do
have Security Essentials running (even if it's no longer updated). But
anything is possible I guess. Both Precess Explorer and Process Hacker
work (which are very similar), so I really dont need Taskman, but I
will
go into the registry and fix it anyhow. I'll probably be formatting
this drive soon anyhow, because I have a legitimate XP-Pro Cd coming,
but I was curious why....

So, in other words I could CHKDSK any other partition, just not C:.
This is the only computer that only has one partition. because it only
has a 40meg drive. Laptop HDDs are costly.

Thanks

Of course you can CHKDSK C:.

Just not while C: is "online".

The OS uses an opportunity early in the boot cycle, to
do the CHKDSK then. You can schedule the CHKDSK
to be run - an attempt to do CHKDSK of C: with repair selected,
it should ask you whether you want to do it on the next reboot.
In which case, the bootexecute registry key is modified
so it gets done next time. So all it takes is a reboot.
And as for an "interface", there should be an event in
Event Viewer with the word "winlogon" in it, and that
event will have the text from the CHKDSK run. It works
that way, because the OS isn't really running while the
CHKDSK is being done, so the text is stored for later.
And the Event Viewer is where you get to find out if
there was any serious repair work (or CHKDSK is stuck
in a loop etc).

I wonder if after doing this, he'll also need to reset the dirty bit
subsequentally?
I seem to recall having to do this by running "chkntfs" to prevent chkdsk
from continually running and delaying the boot up times (viz, there would
(otherwise) be a few minutes of unnecessary disk activity after each
reboot). Am I the only one that has run into this glitch?

The dirty bit is unidirectional. FSUTIL can set the dirty bit,
but not clear it. It's a way of waving a red flag and saying
"this partition needs a CHKDSK". The location of the dirty bit,
is not documented on purpose, so people won't be flipping it back :-)
(When you're stuck in a loop, people are sorely tempted to do that.)

CHKDSK knows how to clear the dirty bit, and since the flag
is a "signal to CHKDSK", it is perfectly appropriate for
CHKDSK to be the only one who knows how to clear the bit.

Paul

Paul, I wasn't using FSUTIL, just chkdsk. And at least on my computer, I
still had to run CHKNTFS after simply running chkdsk c: Apparently there's
something unique going on over here. :-) And reading the other response
from BillW, I guess someone else has seen this happen, so I don't feel quite
so bad. :-)

On 6/13/2014 10:01 AM, wrote:
On Fri, 13 Jun 2014 04:40:33 -0500, BillW50 wrote:

Well I am not sure how it works, but one machine I had would always scan
the drive at boot and CHKDSK never found anything, but would still check
at every boot. I think it was on a dual boot machine come to think about
it. Another reason I hate dualboot systems! But Hard Disk Sentinel cured
it and I didn't have to worry about that problem anymore.

I've never had that happen on my Win98 / Win2000 dual boot machine. But
maybe XP and newer OSs are different in that regard. Now if I lose
power during due to a storm or other reason, then I might get a scandisk
at boot, but there is a reason for it, and once it's run, it's done.

It happened on an XP machine that had a dualboot with Windows 7 Preview.
And I believe how it worked was every time you booted to 7, the XP
partition would be set as dirty (and CHKDSK would never find anything
wrong with it). I later dumped Windows 7 and all was well once again
except for below.

I did end up with two odd problems after this. One Paragon Drive Copy
v11 analyzes the drive before cloning and it doesn't care how it is
setup to boot, it somehow detects Windows 7 there and sets it up to boot
Windows 7 instead of XP (it thinks it is doing me a favor). There isn't
a single Windows 7 file anywhere anymore that I could find. But
Paragon's log says Windows 7 is there and even knows the correct build
number that used to be there. Go figure!

The second oddity is that Maxthon v3 doesn't remember passwords on this
machine. I haven't really investigate this problem much since that
machine is mainly used for TV recording and a huge amount of games. And
I hardly ever go online with it since it doesn't need anything online
anyway.

--
Bill
Gateway M465e ('06 era) - Kingston 120GB SSD - Thunderbird v24.4.0
Centrino Core2 Duo T7400 2.16 GHz - 4GB - Windows 7 Home SP1