A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

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



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old September 25th 17, 01:35 AM posted to alt.comp.os.windows-10
June Bug
external usenet poster
 
Posts: 40
Default How do I debug why the HDD is at 100% CPU lately?

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?
Ads
  #2  
Old September 25th 17, 03:54 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default How do I debug why the HDD is at 100% CPU lately?

June Bug wrote:
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?


You're attempting to go from .545 to .608.

There is evidence that an install is in progress.
The question is, how can it be stopped, or can it
even be stopped.

The disk is at 100%, with little bandwidth showing, because
tiny files are being processed. That means the update
mechanism is evaluating a ton of small files.

*******

This one affects HP machines as far as I know. Doesn't
match your symptoms.

https://support.microsoft.com/en-us/...date-on-some-o

*******

So maybe what's happening, is the Delta downloader is
stuck in a wuauserv loop, working out the update. Maybe
the update isn't actually in flight yet.

You can use the gear wheel ("Settings") on the lower
left of the main desktop screen, and see if it is
in the process of preparing for .608 update. Viewing the
information in Update&Security is critical to understanding
whether this process can be stopped.

If that is the case, you can:

1) Write down the KB number of the incoming update.
It could be KB4038788.

https://support.microsoft.com/en-ca/...date-kb4038788

2) Use a web browser to download the standalone installer for it.

http://www.catalog.update.microsoft....px?q=KB4038788

2017-09 Cumulative Update for Windows 10 Version 1703
for x64-based Systems (KB4038788) 934.9MB

The file will be a .msu file.

3) Reboot the computer with the network connection disconnected.
Double-click the 934.9MB file, to start the install of the MSU.
If the install is "appropriate", the MSU can figure this out on
its own. It will call wuauserv, for help. The wuauserv service will
only listen to it, if the network is disconnected, and wuauserv will
not be working on any little projects of its own choosing.

The Service Host at the top of your Task Manager image, actually
contains wuauserv. It will stop railing after you reboot with the
network cable disconnected. And then wuauserv will be willing to
listen to the bleating of the running .msu file.

While you can delete SoftwareDistribution folder manually, you
can also look in the Control Panels for "Troubleshooter"
and see if there is a TroubleShooter for "Update" or "Windows Update".
That troubleshooter will delete files in the same way as the
script on Tenforums would do it. You can run the MSU after
that if you wanted. Using the troubleshooter might be required, if
for some reason, the .msu won't install either. I've not had
a severe enough problem to need to do it that way (yet).

Once the install phase has completed, and the dialog says it is
done and "would you like to reboot", you can re-connect or re-enable
your Wifi once the reboot has started to happen, or any time
later than that if you want.

When the reboot is done, check your Winver and see if it says
15063.608.

*******

I didn't recognize the "GlassWire" reference in your Task Manager.
It appears to be a third-party product.

"Once suspicious activity is detected you can block the potential
threat with GlassWire's built in firewall management tool.

GlassWire visualizes all your network activity on an easy to use graph.
"

And it seems to use quite a lot of resources for such a function.
As well as in one case I could find on the web, printing erroneous
information in the graph.

Paul
  #3  
Old September 25th 17, 04:50 AM posted to alt.comp.os.windows-10
June Bug
external usenet poster
 
Posts: 40
Default How do I debug why the HDD is at 100% CPU lately?

The date is 24/09/2017 19:54

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


You're attempting to go from .545 to .608.


See this first which you explained later:
http://www.bild.me/bild.php?file=6218463d9.jpg

How do you know that?
All I knew was two things before your post, but not anything more.
First: I have Win10 pro set to not update
Second: I know it will eventually update on Microsoft's schedule

Is that what it's trying to do?

There is evidence that an install is in progress.
The question is, how can it be stopped, or can it
even be stopped.


Yes. I only have two bits of evidence that an install is in progress.
First: It said days ago not to stop the install (I booted anyway).
Second: Some of the running processes seem like install processes.

The disk is at 100%, with little bandwidth showing, because
tiny files are being processed. That means the update
mechanism is evaluating a ton of small files.


I must agree with your assessment because of two things.
First: The network shows that it's not at a high percent.
Second: I killed the network at one point & it didn't matter.

This one affects HP machines as far as I know. Doesn't
match your symptoms.


It is an HP machine but I don't get a black screen.

I only got the blue screen telling me an update was in progress when I
killed the machine because I didn't know why the disk was at 100% for ten
or twenty minutes so I just rebooted but for two days the CPU was at 100%
and now every once in a while (on the third day) it still goes to 100% for
a few minutes at a time.

You can use the gear wheel ("Settings") on the lower
left of the main desktop screen, and see if it is
in the process of preparing for .608 update. Viewing the
information in Update&Security is critical to understanding
whether this process can be stopped.


THANK YOU very much for that information!
http://www.bild.me/bild.php?file=6218463d9.jpg

Here is what it says in "updates & security".
First: Updates are available.
Second: 2017-09 Cumulative Update for Windows 10 Version 1511 for x64-based
Systems (KB4038783).
Third: Update for Windows 10 Version 1511 for x64-based Systems
(KB4033631).
Fourth: Feature update to Windows 10, version 1607.

Does that mean that, finally, I was forced to update Win10Pro to the latest
Micrsosoft operating system version? (I don't keep up with the version race
because it never ends and causes trouble on the way.)

While you can delete SoftwareDistribution folder manually, you
can also look in the Control Panels for "Troubleshooter"
and see if there is a TroubleShooter for "Update" or "Windows Update".


THANK YOU for that point to the "troubleshooter".
http://www.bild.me/bild.php?file=4526800d10.jpg

I found "Troubleshooting" in the Windows Control Panel.
In Troubleshooting, I found "System and Security".
In System and Security I found "Fix Problems with Windows Update".
It asked me to "troubleshoot as an administrator".
But then it complained "Toubleshooting couldn't identify the problem".

I will reboot *AFTER* I send this (just in case I'm dead in the water).
  #4  
Old September 25th 17, 05:40 AM posted to alt.comp.os.windows-10
John Doe[_8_]
external usenet poster
 
Posts: 2,378
Default How do I debug why the HDD is at 100% CPU lately?

June Bug wrote:

http://www.bild.me/...


None of those pictures show up when I click on a link.

That is just for the original poster's information. I
won't/can't add anything to what Paul has said.
  #5  
Old September 25th 17, 05:43 AM posted to alt.comp.os.windows-10
John Doe[_8_]
external usenet poster
 
Posts: 2,378
Default How do I debug why the HDD is at 100% CPU lately?

NEVERMIND.
Scrolling down worked wonders.
  #6  
Old September 25th 17, 05:43 AM posted to alt.comp.os.windows-10
June Bug
external usenet poster
 
Posts: 40
Default How do I debug why the HDD is at 100% CPU lately?

The date is 25/09/2017 04:40

None of those pictures show up when I click on a link.

That is just for the original poster's information. I
won't/can't add anything to what Paul has said.


I wonder why.

When I single click, nothing happens but when I double click, they pop up
in my Windows 10 default web browser.

Did anyone else have a problem viewing the photos?
  #7  
Old September 25th 17, 02:21 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default How do I debug why the HDD is at 100% CPU lately?

June Bug wrote:


THANK YOU very much for that information!
http://www.bild.me/bild.php?file=6218463d9.jpg

Here is what it says in "updates & security".
First: Updates are available.
Second: 2017-09 Cumulative Update for Windows 10 Version 1511 for x64-based
Systems (KB4038783).
Third: Update for Windows 10 Version 1511 for x64-based Systems
(KB4033631).
Fourth: Feature update to Windows 10, version 1607.

Does that mean that, finally, I was forced to update Win10Pro to the latest
Micrsosoft operating system version? (I don't keep up with the version race
because it never ends and causes trouble on the way.)


My apologies.

I only glanced at your Winver, and noticed the 545 on the end.

Yes, you're way behind on Win10 Release version. Your 8027083d8.jpg picture says

10586.545

Now, look carefully though this list. It's in reverse order, in that
the most recent updates are at the top.

https://support.microsoft.com/en-ca/...date-kb4038788

15063.608 Sept.12,2017
15063.540 Aug.8, 2017
...
14393.1715 Sept.12, 2017
14393.1670 August 28, 2017
...
10586.1106 Sept.12,2017
10586.1045
10586.545 August 9, 2016 --- you are here
...
10240.17609 September 12, 2017
10240.17533 August 8, 2017

You are actually in the "unsupported" section.

Only the two most recent OS versions, which are 15063 and 14393
are supposed to receive current security patches. Yet, all four OS
versions are receiving updates (Microsoft appears to be patching all
of them!). That's not a problem then. The patching tree is alive
and well, for everyone.

Now, what is your Update&Security saying:

http://www.bild.me/bild.php?file=6218463d9.jpg

Windows Update

Updates are available

2018-09 Cumulative 1511 KB4038783

Update for 1511 KB40335631

Feature update to 1607

A restart has been scheduled.
Restart now. --- files for above, sitting in queue,
awaiting your restart

Now, if your Windows Update is "broken", it will try to download
the files again, after the update attempt fails.

One thing missing from your screen, is the Update History button.

https://s26.postimg.org/g8dan1tih/update_interface.gif

What I think could be happening, is the updates are failing
to install, after each reboot that you do. The update
is downloading again, and trying again and again.
It's been "jammed" since August 9, 2016, or about thirteen
months ago.

*******

When I work on computers, my motto is "do no harm". I do a
backup of the portion of the machine I'm working on
(at least C: and System Reserved). I'm a home user, not
an IT guy. Real computer repair people, don't do backups,
because they know exactly what they're doing. I don't
have that luxury.

To make a free backup, you can use this product. Macrium
Reflect Free V6. The version here might be V6.3.1685, as
for V7, they have not offered a free version of that (yet).

https://www.macrium.com/reflectfree

https://updates.macrium.com/reflect/v6/ReflectDL.exe

That's a stub downloader, which will download a 40MB backup
program and a 500MB+ WinPE kit from Microsoft. The download
can be done as two separate steps. The download itself
is large, and then the download program compresses the
WinPE kit to a smaller size.

https://s26.postimg.org/swndi9acp/macrium_download.gif

Once you have the two files, you can install the software.
When you start the software, it will offer to make
an emergency boot CD. You need that CD, if you ever need
to restore the OS image back on top of C: . Which would
be the case, in this case, with your C: problem. You store
the backup on an external drive, for easy access.

The various WinPE versions, have different hardware support.
WinPE5 and WinPE10 have USB3 support (for external USB
disk drive backup storage). Either of those versions
should be sufficient on modern computers.

*******

So what to do about this mess ? :-/

Good question.

After a reboot, it will try to install that mess (since the
files are already in queue). If you could see the
Update History link, you could see the failures recorded
for later.

*******

If you simply cannot find an Update History, try this.

1) Right-click Start to open an Administrator Powershell window.
These commands put you in your Downloads folder, a good place
to keep computer trivia.

cd /d %userprofile%
cd Downloads

2) In your home directory, Downloads folder, create a New Text File.
Name it "update_list.txt". Open it in Notepad.

Copy the following text into the file, Save, and Exit.

********* do not include this line **********
$Session = New-Object -ComObject "Microsoft.Update.Session"
$Searcher = $Session.CreateUpdateSearcher()
$historyCount = $Searcher.GetTotalHistoryCount()
$Searcher.QueryHistory(0, $historyCount) | Select-Object Date,
@{name="Operation"; expression={switch($_.operation){
1 {"Installation"}; 2 {"Uninstallation"}; 3 {"Other"}}}},
@{name="Status"; expression={switch($_.resultcode){
1 {"In Progress"}; 2 {"Succeeded"}; 3 {"Succeeded With Errors"};
4 {"Failed"}; 5 {"Aborted"}
}}}, Title | Export-Csv -NoType "$Env:userprofile\Downloads\update_list_out.cs v"
********* do not include this line **********

3) In the Powershell window, change the execution policy so you can run the script.

Get-ExecutionPolicy # Returns "restricted"
Set-ExecutionPolicy Unrestricted # ready to do work...
# Change it back later

4) Now, back in File Explorer, change the file extension
on the freshly-made text file. You're changing the file
extension to .ps1 as it's a Powershell script. This
is pseudo code, for the name change.

move update_list.txt update_list.ps1

5) Now, in the Administrator Powershell window, let's run it.
We moved to the correct directory in step 1, so this should work.

./update_list.ps1

6) A new file, update_list_out.csv appears in your download folder.
You can open it in Notepad if you want.

This is my output right now. Notice how two Windows Defender
updates are now properly listed. Which is more than the GUI gives.
I suspect your output will be quite "descriptive" :-)

"Date","Operation","Status","Title"
"9/25/2017 8:44:58 AM","Installation","Succeeded","Definition Update for Windows Defender - KB2267602 (Definition 1.251.1412.0)"
"9/20/2017 5:37:39 AM","Installation","Succeeded","Definition Update for Windows Defender - KB2267602 (Definition 1.251.1161.0)"
"9/20/2017 5:35:23 AM","Installation","Succeeded","2017-09 Security Update for Adobe Flash Player for Windows 10 Version 1703 for x86-based Systems (KB4038806)"
"9/19/2017 6:37:37 AM","Installation","Succeeded","Security Update for Windows (KB4038788)"

*******

If you download a 15063 DVD, you can mount the ISO
file (without even burning a DVD). And do a Repair Install
of Windows, bumping the version to 15063. You do this, by
navigating to the DVD in file explorer (after the ISO is mounted
by right-clicking the "Win10_1703_English_x64.iso" and following the prompt).
There should be a setup.exe to double-click on the fake DVD.
That can kick off a Repair Install of Windows 10.

Now, there is a slight difference, between the OS upgrade you have
queued right now, and the usage of the DVD. The DVD does not queue up
drivers for the OS installation. It *should* use the already installed
driver MSI or whatever, to put the driver back. Or, it may not.
Whereas the Windows-Update-delivered method, it downloads
drivers as part of the preparation step. That's a slight difference
between the two methods.

But I cannot in good conscience, suggest to you that you waste hours
and hours trying to get the OS to "digest" the mess it's in.

If you want, you can post the contents of your update_list_out.csv
(as it is just text), and maybe it will be apparent which update
needs to be "jammed in". We can do it that way if you want. As long
as the information in the update_list_out.csv is pretty explicit about
which update is broken, we can fix it.

Downloading the 15063 DVD and repair installing, is intended to stop
the nonsense and get the machine ready again. That's your other
option.

https://www.microsoft.com/en-us/soft...d/windows10ISO

Windows 10 Creator Update
Windows 10

English (or whatever)

64-bit download (contains Pro and Home on the same ISO)

The download will be for the March 2017 version (aka 15063)
This *partial* URL is to demonstrate what kind of file to expect...

https://software-download.microsoft....glish_x64.iso?...

When I make up these examples, I mainly assume your OS is the x64
one, but you're free to select the 32 bit choice if that's what is
on the machine right now. You must be consistent when Repair Installing.

HTH,
Paul
  #8  
Old September 26th 17, 12:50 AM posted to alt.comp.os.windows-10
June Bug
external usenet poster
 
Posts: 40
Default How do I debug why the HDD is at 100% CPU lately?

The date is 25/09/2017 06:21

My apologies.

I only glanced at your Winver, and noticed the 545 on the end.

Yes, you're way behind on Win10 Release version. Your 8027083d8.jpg picture says

10586.545


I wish I had stayed behind, as the worst thing I ever did was NOT back up
my C:\data directory before hitting the Windows reboot time waster button!
http://www.bild.me/bild.php?file=5609107a01.jpg

It literally took from 3am to 4pm to recover from the mess that the Windows
10 Pro update did to my system, and I'm only able to log in now, so there's
far more to recover from.

For example, all my custom menus are gone. Poof! Disappeared.
http://www.bild.me/bild.php?file=3361519a02.jpg

Worse, my file system was corrupted by the Windows update where every
setting in the Windows registry seems to be corrupted by the update!
http://www.bild.me/bild.php?file=9272182a04.jpg

It's clear Micrsosoft never tested their updates against the real world
conditions where %temp% and %programfiles% have been redefined.

10586.545 August 9, 2016 --- you are here


Thanks. Now I'm here!
10586.1106 Sept.12,2017


Not only did the Windows update corrupt my system, but it put me at
"Version 1511 (10586.1106) whether I wanted the update or not.
http://www.bild.me/bild.php?file=4421980a03.jpg

A restart has been scheduled.
Restart now. --- files for above, sitting in queue,
awaiting your restart


After the restart, all heck broke loose.
None of my registry entries worked anymore.
None of my folders would open up (all said they were corrupted).
All my custom menus were gone.
Even the shortcuts on my task bar no longer worked.

Many times I get a weird hex error (reminiscent of the BSOD errors of the
days in the past).

I had to re-create everything from scratch.
It took at least a dozen boots before I could get anything working again.

One thing missing from your screen, is the Update History button.
https://s26.postimg.org/g8dan1tih/update_interface.gif


This is what I get now, after a dozen reboots.
http://www.bild.me/bild.php?file=1622201a05.jpg

It says there were problems, but why on earth would I hit the "retry"
button when Windows 10 updates have (obviously) never been tested in the
real world?

What I think could be happening, is the updates are failing
to install, after each reboot that you do. The update
is downloading again, and trying again and again.
It's been "jammed" since August 9, 2016, or about thirteen
months ago.


I don't disbelieve you. In all fairness to Microsoft, I hit all the buttons
they provided to us to turn OFF updates. I turned off every button for
Cortana. I turned off everything I could. I didn't do anything fancy; I
just hit all the buttons that Microsoft provided. It took hours when I
first set it up to find all the buttons scattered about.

In addition I have the %TEMP% directories all redefined, and I use the
classic shell, and I redefine %Program Files% but all that is stuff that
Microsoft should be testing every day anyway since it's simple and common
stuff that they themselves advocate.

After a reboot, it will try to install that mess (since the
files are already in queue). If you could see the
Update History link, you could see the failures recorded
for later.


It took at least a dozen boots. I had scheduled a checkdsk extensive scan
and fix which made it just take even longer. Hours longer in fact. That
didn't help (note for the next time - make sure chkdsk isn't scheduled at
the same time as a Windows update).

I just wish Windows would never update so that I wouuldn't have to go
through that hell again. Ever. It's easier to just format the disk (after
backing up C:\data of course) and then installing a new OS from scratch,
for heaven's sake!

When I make up these examples, I mainly assume your OS is the x64
one, but you're free to select the 32 bit choice if that's what is
on the machine right now. You must be consistent when Repair Installing.


It's X64. I'm gonna try to see what that update history shows, but my
takeaway here is that it's far easier to back up the C:\data directory and
then to just wipe out the entire system and do a clean installation than it
is to allow Microsoft to do the update which screws up the entire system
for about 12 hours of work to get it back to close to where it was.
  #9  
Old September 26th 17, 01:44 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default How do I debug why the HDD is at 100% CPU lately?

June Bug wrote:
The date is 25/09/2017 06:21

My apologies.

I only glanced at your Winver, and noticed the 545 on the end.

Yes, you're way behind on Win10 Release version. Your 8027083d8.jpg picture says

10586.545


I wish I had stayed behind, as the worst thing I ever did was NOT back up
my C:\data directory before hitting the Windows reboot time waster button!
http://www.bild.me/bild.php?file=5609107a01.jpg


A quick question for you. Do you have System Restore enabled on C: ?

Maybe it set a Restore Point before messing things up.

Check your System control panel, under Protection, and
see what the status of C: is.

It could be you can roll back the system to an earlier time.

Look at Option 2, for some diagrams.

Note that, if the space allocation for System Restore is
too small, it can cause older restore points to be deleted.
If you wait too long to roll back, the Restore Point you
need can be *gone*.

Restore Points come with no guarantees, but perhaps
it could (quickly) put things back for you. Until
you can figure out a better way to move forward.

*******

And you really really have to make a backup!!!

You need materials to fall back on, at the rate you're
going there could be nothing left!!!

Make a backup now, of the busted system. If the system
becomes more busted, you're going to need that backup!!!

*******

Some versions of Windows 10, have been disabling System
Restore, and there are actually no restore points at all.
I've had that happen here. And then any discussions
of a Houdini-like escape are no longer possible.

Paul
  #10  
Old September 26th 17, 06:16 PM posted to alt.comp.os.windows-10
June Bug
external usenet poster
 
Posts: 40
Default How do I debug why the HDD is at 100% CPU lately?

The date is 25/09/2017 17:44

A quick question for you. Do you have System Restore enabled on C: ?
Maybe it set a Restore Point before messing things up.


I'm old school, so I don't do restores. I just move forward.
What I should have done is a backup before updating Windows.

Restore Points come with no guarantees, but perhaps
it could (quickly) put things back for you. Until
you can figure out a better way to move forward.


I almost never use restore points, as I'm really old (old) school.
I make them every once in a while.
And I have used them in the past.

But rarely.

And you really really have to make a backup!!!

A backup is easy, for me, since I keep everything in C:\data so that's all
I need. The problem, of course, is that C:\data is large, so I'd have to
back it to removable media, which itself is flaky (over time).

Nonetheless, you are correct.
The moral of this story is never trust a Microsoft Win10 update not to
screw up the system.

You need materials to fall back on, at the rate you're
going there could be nothing left!!!


In the future, since I keep super simple game plans, I will just do a
complete backup of C:\data and then wipe out the system instead of letting
Microsoft do the update.

Remember, I turn off every switch that is privacy related that I can, and I
use Classic Shell for the obvious reasons, and WinAero tweaks for obvious
reasons, and I modify %temp% and %progfiles% variables, etc.

Since Microsoft doesn't test their Windows 10 updates in the real world,
it's only natural that their updates will have hard coded stuff that I have
tweaked.

Make a backup now, of the busted system. If the system
becomes more busted, you're going to need that backup!!!


I've been able to re-make most of the Winaero, Classic Shell, and registry
changes, so most of the system is back working - but - the cost was
basically a dozen hours of sheer hell.

In the future, my time would be better spent backing up my C:\data
hierarchy and then just wiping out the system and starting fresh each time.

It's a lot of effort, I agree - but it's less effort and certainly less
risk than letting Microsoft update when it's clear Windows 10 wasn't tested
in the real world against registry variable changes, WinAero changes, and
Classic Shell changes.

  #11  
Old September 26th 17, 07:19 PM posted to alt.comp.os.windows-10
NY
external usenet poster
 
Posts: 586
Default How do I debug why the HDD is at 100% CPU lately?

"June Bug" wrote in message
news
The date is 25/09/2017 17:44

A quick question for you. Do you have System Restore enabled on C: ?
Maybe it set a Restore Point before messing things up.


I'm old school, so I don't do restores. I just move forward.
What I should have done is a backup before updating Windows.

Restore Points come with no guarantees, but perhaps
it could (quickly) put things back for you. Until
you can figure out a better way to move forward.


I almost never use restore points, as I'm really old (old) school.
I make them every once in a while.
And I have used them in the past.

But rarely.


Almost every time when I've tried to restore from a restore point, the PC
has taken ages (often upwards of 30 minutes) before deciding "cannot restore
from this restore point". This is on various Win XP, Vista, 7, 8 or 10 PCs
belonging to people whose computers I've been called out to fix. And it
seems to be all points - if one fails, I may try another further back and
get the same result.

It appears that System Restore is very hit-and-miss.

Of course some people disable restore points altogether. :-(

  #12  
Old September 26th 17, 09:04 PM posted to alt.comp.os.windows-10
Char Jackson
external usenet poster
 
Posts: 10,449
Default How do I debug why the HDD is at 100% CPU lately?

On Tue, 26 Sep 2017 19:19:01 +0100, "NY" wrote:

Almost every time when I've tried to restore from a restore point, the PC
has taken ages (often upwards of 30 minutes) before deciding "cannot restore
from this restore point". This is on various Win XP, Vista, 7, 8 or 10 PCs
belonging to people whose computers I've been called out to fix. And it
seems to be all points - if one fails, I may try another further back and
get the same result.

It appears that System Restore is very hit-and-miss.

Of course some people disable restore points altogether. :-(


I disable SR as part of any initial setup.

I leave it enabled if/when I build a system for someone else, but I'll
be darned if I want it enabled on any system that I use.

  #13  
Old September 26th 17, 11:57 PM posted to alt.comp.os.windows-10
June Bug
external usenet poster
 
Posts: 40
Default How do I debug why the HDD is at 100% CPU lately?

The date is 26/09/2017 13:04

I leave it enabled if/when I build a system for someone else, but I'll
be darned if I want it enabled on any system that I use.


I'm with you in that I can't remember the last time I used a system restore
point. I have used them in the past, but sparingly.

The real security, I feel, is keeping all important "things" in a single
location (D:\data for example) and then just backing *that* up.

If you have a relatively recent backup of your D:\data (or whatever you
call it), then there's nothing else but programs and operating system, both
of which inherently are relatively easy to recover.

1. Just download the ISO for the OS
2. Just re-install the programs for the apps

The only thing left are the tweaks that you did (Classic Shell, WinAero,
shortcuts, etc.).
  #14  
Old October 2nd 17, 02:20 PM posted to alt.comp.os.windows-10
June Bug
external usenet poster
 
Posts: 40
Default How do I debug why the HDD is at 100% CPU lately?

The date is 24/09/2017 17:35

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


Paul was completely right that the whole hard disk at 100% problem was due
to the Windows update that I have been trying to forestall for so long that
it finally happened.

Now look at the crap that Microsoft added to my otherwise very clean and
very well organized app hiearchy!
http://www.bild.me/bild.php?file=8101688apps.jpg

Microsoft *doubled* the number of folders from what I have considered
necessary for a decade or more. Microsoft has absolutely zero concept of
file organization. None.

This crap should go in a microsoft directory for all the Microsoft crap.
But what directory should Microsoft put its crap in?
I don't know as I didn't know this stuff was coming down the pipeline.

I've been fighting Microsoft crap for decades, so this is nothing new.
I have three choices, all of which I will have to do.
1. First I have to clean up the Microsoft crap
2. Then I have to prevent Microsoft from crapping there ever again

I think the simplest solution is either to reset all % variables in the
registry to the defaults whenever a Microsoft installation occurs. That
would let Microsoft pollute the already polluted microsoft directories
instead of polluting my clean hiearchies.

The longer-term (and probably simplest overall) solution is to NEVER set
any Microsoft % registry variable to any directory that I care about.

The good news when I do that is that Microsoft will stop polluting my clean
hierarchies. The bad news is that all programs will default to the wrong
directory upon installation.

It's a lesser of two evils choice for me.

If you ever let Microsoft update Win10, it will screw up your app
directory!
Therefore, make sure you reset the program-files variables to defaults!
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\
%ProgramFilesDir% = C:\Program Files
%ProgramFilesDir (x86)% = C:\Program Files (x86)
Otherwise your c:\apps\ hierarchy gets horribly polluted with:
archiver
browser
cleaner
== CMAK == microsoft update added this crap
editor
finance
hardware
== Internet Explorer == microsoft update added this crap
network
== NVIDIA Corporation == microsoft update added this crap
os
== Reference Assemblies == microsoft update added this crap
== rempl == microsoft crap
== Windows Defender == microsoft update added this crap
== Windows Mail == microsoft update added this crap
== Windows Media Player == microsoft update added this crap
== Windows NT == microsoft update added this crap
== Windows Photo Viewer == microsoft update added this crap
  #15  
Old October 2nd 17, 03:50 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default How do I debug why the HDD is at 100% CPU lately?

June Bug wrote:

your post came through as an empty body with an attachment
Using the howardknight archive, I've copied it back into the body

The date is 24/09/2017 17:35

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


Paul was completely right that the whole hard disk at 100% problem was due
to the Windows update that I have been trying to forestall for so long that
it finally happened.

Now look at the crap that Microsoft added to my otherwise very clean and
very well organized app hiearchy!
http://www.bild.me/bild.php?file=8101688apps.jpg

Microsoft *doubled* the number of folders from what I have considered
necessary for a decade or more. Microsoft has absolutely zero concept of
file organization. None.

This crap should go in a microsoft directory for all the Microsoft crap.
But what directory should Microsoft put its crap in?
I don't know as I didn't know this stuff was coming down the pipeline.

I've been fighting Microsoft crap for decades, so this is nothing new.
I have three choices, all of which I will have to do.
1. First I have to clean up the Microsoft crap
2. Then I have to prevent Microsoft from crapping there ever again

I think the simplest solution is either to reset all % variables in the
registry to the defaults whenever a Microsoft installation occurs. That
would let Microsoft pollute the already polluted microsoft directories
instead of polluting my clean hiearchies.

The longer-term (and probably simplest overall) solution is to NEVER set
any Microsoft % registry variable to any directory that I care about.

The good news when I do that is that Microsoft will stop polluting my clean
hierarchies. The bad news is that all programs will default to the wrong
directory upon installation.

It's a lesser of two evils choice for me.

If you ever let Microsoft update Win10, it will screw up your app
directory!
Therefore, make sure you reset the program-files variables to defaults!
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\
%ProgramFilesDir% = C:\Program Files
%ProgramFilesDir (x86)% = C:\Program Files (x86)
Otherwise your c:\apps\ hierarchy gets horribly polluted with:
archiver
browser
cleaner
== CMAK == microsoft update added this crap
editor
finance
hardware
== Internet Explorer == microsoft update added this crap
network
== NVIDIA Corporation == microsoft update added this crap
os
== Reference Assemblies == microsoft update added this crap
== rempl == microsoft crap
== Windows Defender == microsoft update added this crap
== Windows Mail == microsoft update added this crap
== Windows Media Player == microsoft update added this crap
== Windows NT == microsoft update added this crap
== Windows Photo Viewer == microsoft update added this crap


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. For example, the NVidia package
that supports recording 3D gameplay (ShadowPlay?) can fail
while it is being installed. And even though the driver
portion installed OK, the package may be queued for re-install.

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

*******

This is where CMAK came from. You turned it on!

"RAS Connection Manager Administration Kit (CMAK): This tool
allows you to create custom remote access profiles for VPNs.
Unless you know you need this to administer a network,
you don’t need it.

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

*******

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

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.

*******

Seems to be the normal level of disorder...

If you were expecting a "rolling release" OS to stay "pretty",
you're nuts :-) That's not how it works. You're expected
to chew bubble gum and update your Facebook page, and
not go looking in the file system.

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

Paul
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 06:31 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.