How do I debug why the HDD is at 100% CPU lately?

On Mon, 2 Oct 2017 13:20:39 +0000 (UTC), June Bug
wrote:

How the heck can the HD CPU be at 100%? The question makes no sense.

If the CPU is at 100%, press CTRL-ALT-DEL and determine which
application is at fault. If it's always a different application,
chances are that you're looking at a failing HD.

"June Bug" wrote in message news
How do I debug why the HDD is at 100% CPU lately?
http://www.bild.me/bild.php?file=5916755d1.jpg

It "seems" to be related to a Microsoft Win10 Pro update:
http://www.bild.me/bild.php?file=8258449d2.jpg

But, even after this happening for two days, there's no update:
http://www.bild.me/bild.php?file=8984019d3.jpg

I rebooted and got a light blue screen saying not to power down:
http://www.bild.me/bild.php?file=7501100d4.jpg

But I powered down a few times anyway but it still happens:
http://www.bild.me/bild.php?file=3681737d5.jpg

When it happens, I can't kill the process easily:
http://www.bild.me/bild.php?file=1172648d6.jpg

Because it tells me that it will power everything down:
http://www.bild.me/bild.php?file=3391370d7.jpg

Two days later, I still have the same Win10 Pro build as before.
http://www.bild.me/bild.php?file=8027083d8.jpg

How do I debug why the HDD is at 100% CPU lately?

++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++

Go to "Task Manager"

Click "Processes"

Look under the "CPU" column.

You will see which process is hugging up the resources.

Jim Dandy wrote:


"June Bug" wrote in message news How do I debug why the HDD is at 100% CPU lately?

Go to "Task Manager"

Click "Processes"

Look under the "CPU" column.

You will see which process is hugging up the resources.

Task Manager has a Resource Monitor button on one of the
pages, and that actually shows what task is doing disk I/O.

If the item was defined as a SVCHOST, then one of the
services inside the SVCHOST is doing it. Then you need
"tasklist /svc" or the usage of Sysinternals Process Explorer
(run as Administrator), to get additional info about that PID.

Some disk I/O is virtually un-monitorable. You may see
it charged to "System" or the like. I've even seen a
case where a task had somehow changed its name to
blank, and the I/O was successfully obfuscated. It's not
a given that you can find out, in every case, what's doing it.

Paul

The date is 02/10/2017 07:50

The OS calls the NVidia Installer, to install a driver.
The Nvidia-provided driver unpacks the archive into an
NVidia folder. The bad part about the NVidia installer,
is it is a multi-part installer, and if one part of the
installer fails, the package can have install attempts
made over and over again.

Thanks for the detail. I certainly didn't create that Nvidia folder in my
app hierarchy! So "something" did, but I didn't install any Nvidia drivers,
so, I agree with you that Microsoft Win10 Update screwed that up, not me.

The Apps folder, yes, Microsoft will fill it with crap.
That's a given.

This is a lesson learned for me.
I didn't realize Microsoft will fill my carefully tended app hierarchy with
their ill-organized crap.

The good news is that the solution is simple, which is to delete my
customization of the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\
%ProgramFilesDir% = C:\apps
%ProgramFilesDir (x86)% = C:\apps

Where these are the current dozen settings:
http://www.bild.me/bild.php?file=7991555programfilesdir.jpg
(Default) = value not set
CommonFilesDir = C:\Program Files\Common Files
CommonFilesDir (x86) = C:\Program Files (x86)\Common Files
CommonW6432Dir = C:\Program Files\Common Files
DevicePath = %SystemRoot%\inf
MediaPathUnexpanded = %SystemRoot%\Media
ProgramFilesDir = C:\apps
ProgramFilesDir (x86) = C:\apps
ProgramFilesPath = %ProgramFiles%
ProgramW6432Dir = C:\apps
SM_ConfigureProgramsName = Set Program Access and Defaults
SM_GamesName = Games

Anything that Microsoft sets in the registry is like a spot on the road
that has a spot for everyone to dump their garbage such that it becomes an
unusable disorganized mess of crap.

My mistake was in thinking on that the %CommonFilesDir% was where Microsoft
dumped their disorganized crap, but they also dump disorganized crap into
the %ProgramFilesDir% it seems, but only when Windows 10 updates.

To solve the problem of Microsoft dumping on the side of the road all their
crap, I have changed the registry back to this (I wasn't sure what to set
the ProgramW6432Dir to though?).
http://www.bild.me/bild.php?file=9229058programfilesdir_reset.jpg
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\
%ProgramFilesDir% = C:\apps
%ProgramFilesDir (x86)% = C:\apps

Where these are the current dozen settings:
http://www.bild.me/bild.php?file=7991555programfilesdir.jpg
(Default) = value not set
CommonFilesDir = C:\Program Files\Common Files
CommonFilesDir (x86) = C:\Program Files (x86)\Common Files
CommonW6432Dir = C:\Program Files\Common Files
DevicePath = %SystemRoot%\inf
MediaPathUnexpanded = %SystemRoot%\Media
ProgramFilesDir = C:\Program Files
ProgramFilesDir (x86) = C:\Program Files (x86)
ProgramFilesPath = %ProgramFiles%
ProgramW6432Dir = C:\Program Files
SM_ConfigureProgramsName = Set Program Access and Defaults
SM_GamesName = Games

Are those the correct default original settings for Microsoft dumping of
their garbage in a disorganized unsightly mess on the side of the road?

In the Windows Features Utility CMAK is disabled by default,
so it is not used unless the user deliberately turns it on.

If I turned it on, I didn't do it knowingly.
I'll try to turn it off if I can find out where to do that.

And why would the ProgramFiles environment variables change ?
That would break things.

I admit the main reason I change the ProgramFile variable is that I never
use C:\Program Files (or any of its variants) but half the installers (at
least the ones that are written well) default to starting at the
%ProgramFilesDir% location.

So it only saved me a few button clicks since I store nothing in any
hierarchy already polluted by Microsoft such that the stench is unbearable
just to step into the directory structure.

Of course, half the installers out there are horribly written because the
idiots who write them /hard code/ the %ProgramFilesDir% paths into the
installer (hint ... Apple, Motorola, Adobe, etc.) such that these badly
written installers still defaulted to C:\Program Files anyway.

This change to C:\apps for the variable worked fine for a year because I
was able to stave off Microsoft updates - but the moment Microsoft updated
Windows, it polluted my carefully crafted clean landscaped hierarchy.

In a way, it's a "good thing" that at least Microsoft honored their own
%ProgramFilesDir% variable when dumping their stinky garbage into my nice
clean well-manicured hierarchy.

It could change, if the *user* moved them, and there was
an OS update. Even though the OS supports modular storage
and allows using reparse points for home directory or
program files, the *OS Installer* does not tolerate it.
This means the feature is basically... broken. Don't
redirect things, unless you like the smell of... trouble.

I have learned many lessons in dealing with Microsoft's propensity to dump
their smelly unsightly garbage on our nicely groomed front lawns - one of
which is to never put anything I care about into a directory that Microsoft
knows about.

My mistake was that by setting the %ProgramFilesDir% variable, suddenly
Micrsoft knew about my nicely manicured well groomed hierarchy, and they
****ed and pooped in it because they found out about it.

The trick will be to remember to never do that again (like most of my
lessons, it was hard won and borne of experience).

Seems to be the normal level of disorder...

The disorder may be "normal" to most users but to me it's like the litter
on the side of the road. It's unsightly. It serves no useful purpose. And
it's the wrong place for Microsoft to litter our directories.

What I do with Microsoft litter is I assume that Microsoft lives on the
other side of the tracks, where I strive to never go into that "bad" part
of town. I keep my own lawn clean and well groomed, and I stay out of the
bad sections of town, such as %ProgramFilesDir% as much as I can.

Apparently CMAK turned itself on, after some particular
Windows Update came in.

Thanks for catching that because (a) I never heard of CMAK until now, and
(b) I don't remember turning it on.

In general, I turn everything off.

June Bug wrote:

message had empty body

This post came through as an empty body with
an attachment too. I was able to read it on
howardknight OK.

http://al.howardknight.net/msgid.cgi...ia.aioe.org%3E

And looking at the header of your message, I cannot
figure out why my client is doing this to it...
If the word "MIME" was in here, I could understand,
but your message looks perfectly ordinary. Obviously
some convention I'm not familiar with, is at work
here. A brokenness I cannot see...

https://s1.postimg.org/2vtt1ka0cv/me...dy_missing.gif

Paul

The date is 02/10/2017 09:20

How the heck can the HD CPU be at 100%? The question makes no sense.

If the CPU is at 100%, press CTRL-ALT-DEL and determine which
application is at fault. If it's always a different application,
chances are that you're looking at a failing HD.

It wasn't a failing hard drive at all.

Paul accurately reported that the Microsoft Win10 update was killing the
hard drive for hours on end over a span of days.

June Bug wrote:

%ProgramFilesDir% = C:\apps
%ProgramFilesDir (x86)% = C:\apps

That seems as good a way to break a 64 bit windows install as I've seen]

The date is 02/10/2017 18:24

This post came through as an empty body with
an attachment too. I was able to read it on
howardknight OK.

Sorry about that. I don't know why as it looks OK to me.
(I saw your other message about the same thing.)

Anyway, I'm learning more and more and more to hate Windows 10 update!
http://www.bild.me/bild.php?file=6626319winupdatepercent.jpg

I didn't realize Microsoft was going to reboot my machine right as I was
working on it yesterday - when - right in the middle of what I was doing,
Microsoft scheduled an update!

To be fair, it said "something" about an update reboot being needed and I
just dismissed it, and then a short time later (maybe a half hour?) it
rebooted.

So I stupidly let it do its thing. OMG. Was it slow! After running all
night, I just couldn't take waiting any longer as I could load a new
operating system faster than it takes Microsoft to update an existing one.

It stayed on 87% forever. Hours. The little spinning thing was spinning but
it wasn't changing their percentage. This is another strike against
Microsoft coders who couldn't care less about providing users with anywhere
near a "progress bar" concept that has any semblance to reality.

So I killed it at the "forever 87%" and it lost some of my shortcuts
(again) but not as many as last time. For example, the shortcut to Iron,
one of my chrome-based browsers, is dead saying:
"C:\Program Files (x86)\browser\ch-based\iron\chrome.exe
The specified path does not exist.
Check the path and try again.
http://www.bild.me/bild.php?file=5838815chrome_shortcut.jpg

I can forgive Microsoft for screwing up on my shortcuts because at least
Microsoft is "guessing" using the %ProgramFilesDir% variable and not
guessing using a hard-coded path to C:\Program\Files.

Even so, in the end, the more I experience Windows 10 update, the more I
realize that Microsoft never even bothered to test the update in the real
world on machines where the settings are set differently from the basic
defaults.

The lesson is the following:
1. Never (ever!) let Microsoft update your Windows 10 installation, and,
2. If MS forces you to update, then do a full ISO install instead.
(Because a complete installation will take far less time than a Microsoft
Update will.)

The date is 03/10/2017 00:37

%ProgramFilesDir% = C:\apps
%ProgramFilesDir (x86)% = C:\apps

That seems as good a way to break a 64 bit windows install as I've seen]

In a way, since Microsoft doesn't test Windows 10 updates in the real
world, you are completely correct that something as simple as changing a
variable that is meant to be changed will screw up the Windows 10 update.

I can't disagree with you that the most basic of changes causes Microsoft
Update to fail, since it seems to be the case for me, time and time again.

However, that just proves two valid points:
1. Microsoft doesn't test Win10 updates in the real world, and,
2. Because of that - never let Microsoft update your Win10 installation!

The second rule is a result of the first.
The first rule is a result of two things itself:
a. The update will fail anyway, wasting your time (time and again), and,
b. It's far faster to just back up data, load a new ISO, and set it up.

Here are just two screenshots that show that Microsoft never tested their
Windows 10 update in the real world (where switches are flipped).

The update last night, which is about the third time in the past week,
failed yet again, taking interminably long such that I had to manually
reboot as it was stuck on 87% forever... (although it was spinning).
http://www.bild.me/bild.php?file=6626319winupdatepercent.jpg

After the reboot, about 1/3 of my program shortcuts were broken by the
Microsoft Windows 10 update process. Here's just one:
http://www.bild.me/bild.php?file=5838815chrome_shortcut.jpg

That second problem above I can't blame Microsoft too much for, as, yes,
they screwed it up, but I did change the %ProgramFilesDir% variable between
the time that Iron was installed and the time that Microsoft updated
Windows 10.

However, it's still clear that Microsoft simply *guesses* at where programs
will be, where I never put programs in "Program Files" (for all the obvious
reasons similar to why I don't eat my food out of a smelly garbage dump).

The end recommendation holds firm, and is a lesson borne of experience.
1. Never allow Microsoft to update a Windows 10 system!
2. If finally forced to update, then install the new OS yourself.

On Tue, 3 Oct 2017 02:09:28 +0000 (UTC), June Bug
wrote:

The date is 02/10/2017 09:20

How the heck can the HD CPU be at 100%? The question makes no sense.

If the CPU is at 100%, press CTRL-ALT-DEL and determine which
application is at fault. If it's always a different application,
chances are that you're looking at a failing HD.

It wasn't a failing hard drive at all.

Paul accurately reported that the Microsoft Win10 update was killing the
hard drive for hours on end over a span of days.

Good to know, thanks!

The date is 02/10/2017 10:02

Some disk I/O is virtually un-monitorable. You may see
it charged to "System" or the like. I've even seen a
case where a task had somehow changed its name to
blank, and the I/O was successfully obfuscated. It's not
a given that you can find out, in every case, what's doing it.

Hi Paul,
Windows 10 Update tried again today, where I couldn't find any way to stop
it. It gave me a half hour notice but there was no way to stop if (and of
course it failed). At least this time it was quicker (It was less than an
hour but it failed nonetheless.)

Here's my troubleshooting log in progress.

.. Troubleshoot why your Windows 10 update keeps failing
https://support.microsoft.com/en-us/help/10164

.. Check messages from the OS

https://support.microsoft.com/en-us/...erating-system
Start Settings Control Panel Security & Maintenance
Mine says: Check backup settings
Windows cannot find the disk or network location where your backups
are being saved. Backup date 10/1/2017 5:00 PM

.. Start Settings PC Settings Update & Security
Feature update to Windows 10, version 1607.
Details: Downloading updates 23%

.. Start Settings PC Settings System About
Windows 10 Pro Version 1511 OS Build 10586.1106

.. Get the latest Windows 10 release
https://www.microsoft.com/software-download/windows10

.. Download the Windows Update Troubleshooter https://aka.ms/wudiag
This saves the 191KB file named "wu170509.diagcab"

.. Doubleclick on wu170509.diagcab & hit Next to see
"Issues might be found troubleshooting with administrator privilages"
"Try troubleshotting as an administrator"

.. Click on that "Try troubleshotting as an administrator" link & hit Next.
It will say...
"Windows Update"
"Detecting problems"
"Checking for pending updates"
"Checking Registry Keys"
"Starting Bits service"
"One troubleshooting step to resolve WU issues is to delete and
re-download updates to your computer. Would you like to try this step
now?
Depending on your network configuration, you may incur download costs."
"Apply this fix" or "Skip this fix"

.. Press "Skip this fix" (since it won't work anyway) & it will go on to
say:
"Windows Update"
"Resolving problems"
"Checking registry keys..."

.. Determine your system type:
Start Settings Control Panel System About System type
System Type = 64 bit operating system, x64 based processor

.. Download the SSU (KB4035631) that matches your version of Windows
from the Microsoft Update Catalog.
http://www.catalog.update.microsoft....px?q=KB4035631
2017-08 Update for Windows 10 Version 1607 for x64-based Systems
(KB4035631)
windows10.0-kb4035631-x64_{long number}.msu

http://download.windowsupdate.com/d/msdownload/update/software/crup/2017/08/windows10.0-kb4035631-x64_{long
number}.msu 11.4MB

But when I doublecked on that MSU file, it said:
"Windows update standalone installer"
"This update is not applicable to your computer"

.. Download the most recent KB

https://support.microsoft.com/en-us/...update-history
"Find the most recent update KB for the version of Windows 10 you have,
it+IBk-s usually at the top of the list and either write the KB number
down or copy it.
KB4040724 (OS Build 15063.632)

.. You need to run both the DISM and SFC commands shown below,
not just one of them.

.. Administrator command line run DISM
DISM.exe /Online /Cleanup-image /Restorehealth
(this takes hours to run so it's still running)

----- stuff below this point hasn't been run yet -----

.. Administrator command line run
sfc /scannow

.. Perform an in-place upgrade by downloading the Media Creation Tool
https://www.microsoft.com/en-us/soft...load/windows10

.. Use the MCT to perform an in-place upgrade of Windows 10
https://mix.office.com/watch/3qnnlpnv43zu

.. Download the Windows 10 Media Creation Tool (MCT) and use it to
perform a clean install of Windows 10.
https://mix.office.com/watch/1dbgpfktgysig

.. Contact the "Answer Desk"
https://support.microsoft.com/en-us/contactus/

The date is 03/10/2017 15:40

. You need to run both the DISM and SFC commands shown below,
not just one of them.

Here is the result from the DISM command

C:\ DISM.exe /Online /Cleanup-image /Restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.10586.0

Image Version: 10.0.10586.0

[==========================100.0%================== ========]

Error: 0x800f0906

The source files could not be downloaded.
Use the "source" option to specify the location of the files that are
required to restore the feature. For more information on specifying a
source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
(That log file is huge.)


Here is the result from the sfc command:

C:\ DISM.exe sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

(That log file is also huge.)

The date is 03/10/2017 15:40

Windows 10 Update tried again today, where I couldn't find any way to stop
it. It gave me a half hour notice but there was no way to stop if (and of
course it failed).

I think I finally figured out how to turn OFF the Microsoft Windows 10 Pro
updates that were killing my system. Time will tell.

The bad news is that all my task bar shortcuts were broken after the last
failed update, only one of which is problematic to re-install, which is
Microsoft Edge - so I posted separately just now a fix for "reinstalling"
Microsoft Edge.

Here's how I (hope I) turned off the problematic Windows 10 Pro updates.

Turn off "Windows Update":
Services: Windows Update Properties General Startup type
Mine first said "Manual" (which is what it's supposed to be).

But yesterday I changed it to "Disabled" hoping that would stop the
incessant Windows 10 Pro failed updates.

Same with "Background Intelligent Transfer Service".
C:\WINDOWS\System32\svchost.exe -k netsvcs

Same with "Cryptographic Service".
C:\WINDOWS\system32\svchost.exe -k NetworkService

The hope is that turning each of those to "disabled" will stop
Windows 10 Pro from updating forever and failing every single time.

Time will tell. But today Windows 10 Pro didn't try to update (AFAIK).

June Bug wrote:

The hope is that turning each of those to "disabled" will stop
Windows 10 Pro from updating forever and failing every single time.

Actually, there's more.

There is Update Orchestrator.

And Task Scheduler has Update Orchestrator entries that
could potentially "put back" the stuff you disabled.

In some ways, updates are arranged like malware. If you
disable one agent, there is a second waiting in the wings
to do stuff. I've not tested to see (over a period of time),
just what that stuff will do.

*******

If your intention is to use this OS (i.e. it's activated),
then it is probably better to repair it. Somehow. I have
VM installs here, where I've "ripped the wings off it",
but doing that doesn't serve much long-term purpose. It
doesn't correct the design deficiencies. It makes you
feel better for a couple minutes.

Paul

The date is 04/10/2017 21:02

June Bug wrote:

The hope is that turning each of those to "disabled" will stop
Windows 10 Pro from updating forever and failing every single time.

Actually, there's more.
There is Update Orchestrator.

Thanks for that update Paul!
http://www.bild.me/bild.php?file=296...kscheduler.jpg

The goal is to "control" when/if I want an update, which, I would think,
everyone would want who has customized their Windows 10 in such a way that
Microsoft screws it up with every update.

So far I haven't received any Windows 10 Pro updates so I think the three
worked, but if Update Orchestrator Service is only for the updates, I'm
happy to turn it off also.

This is how to permanently (we hope) turn off Windows 10 Pro updates!
Start Settings Control Panel Services Administrative Tools Services
or
Start Run services.msc

Services:
Windows Update Properties General Startup type Disabled
Background Intelligent Transfer Service Properties General Startup type Disabled
Cryptographic Service Properties General Startup type Disabled
Update Orchestrator Service Properties General Startup type Disabled

And Task Scheduler has Update Orchestrator entries that
could potentially "put back" the stuff you disabled.

I'd be happy to turn off "Task Scheduler", but I can't.
http://www.bild.me/bild.php?file=296...kscheduler.jpg

Any idea why the others were easy to turn off but Task Scheduler is not?

In some ways, updates are arranged like malware. If you
disable one agent, there is a second waiting in the wings
to do stuff. I've not tested to see (over a period of time),
just what that stuff will do.

I realize someone has to test this stuff!
I was so frustrated with the Windows 10 Pro updates failing time after time
after time after time, and then again ... that it was worth the risk to
just try to turn off Windows 10 Pro updates.

It seems to work (so far) after a few days - but - who knows *what* makes
Windows 10 Pro updates attempt to update. I certainly don't know what
prompts them because I certainly don't ask for them.

If I want to update, I'll just do an organized update this way:
1. I'll back up my data and my program installers
2. I'll download & burn to DVD disc the Win10 Pro iso
3. I'll wipe the system clean & format anew
4. I'll reinstall the OS & the programs & my user data
5. I'll customize the setup to my liking

Certainly there's utterly no doubt that this manual process is
fantastically quicker and inherently far more reliable than allowing
Windows 10 Pro to update itself (screwing up everything in that process).

If your intention is to use this OS (i.e. it's activated),
then it is probably better to repair it.

It's activated. It's legit. Windows 10 Pro wouldn't be trying to update if
it wasn't anyway. So it might actually be *better* if it was not activated,
but that's water under the bridge. It was activated under the free upgrade
period long ago so Microsoft will re-activate it when I install a new ISO.

Somehow. I have
VM installs here, where I've "ripped the wings off it",
but doing that doesn't serve much long-term purpose. It
doesn't correct the design deficiencies. It makes you
feel better for a couple minutes.

You want me to "repair" it, but there's nothing to repair. I *want* my
customizations. It's my humble opinion that Microsoft never tested Windows
10 Pro updates in the real world where people customize stuff.

I've redefind the %temp% variables (there are four, I think), and I've
redefind (but put back) the %programfilesdir% variables (again, there are
multiple ones) and I use WinAero tweaks and I use the Classic Start Menu
tweaks, and I've probably employed another couple dozen tweaks (e.g.,
context menu additions, App Paths additions, removal of all idiotic
Microsoft-polluted "My Crap" folders and references, I change my username
frequently, and I change my eth0 Mac address frequently, and I change my
home directory and machine name frequently, etc.

Maybe it's *one* of those customizations or a combination of them, but
Windows 10 Pro updates *always* fail but there's nothing to *repair*
because I *want* to customize my system.

My system isn't broken.
Microsoft update can't handle a customized system.

It has been that way for decades with all updates but in the past we had
far more control over *when* and *if* we were updated. Only in Windows 10
has the update become more sinister, but I think these steps have turned it
off.

Here is what I'm currently on:
Start Run winver
Version 1511 (OS Build 10586.1106)