Odd overheating and sluggish problem

Topic

New Reply

Wondering if anyone else has experienced this. I have experienced the below on multiple win10 and win11 devices, different manufacturers, home and pro versions, for the past several years.

I use pause to stave off windows updates until the all clear from our expert Susan Bradley.

Not every update cycle, but more than half, my devices will begin overheating and running sluggishly, though no CPU, memory, GPU, disk, etc. usage is present via Sysinternals Process Explorer while they are paused for updates.

It seems to occur soon after windows updates are staged for my devices, as soon as I unpause, the updates begin downloading and installing immediately.

I run my device power configurations as 100% performance when plugged in (except for smart charging of battery) as they are 99.9% of the time plugged in. I used the stock balanced plan on battery. Have tweaked all plugged in settings to maximum cooling, do not turn off USB, etc. If there is a setting for maximum performance and instant availability, I probably have it to the max.

I can stop the overheating (but not the sluggishness) by unplugging the power or tweaking the plugged in settings to something less. I can also stop the overheating (but not the sluggishness) while plugged in, by killing processes like runtime broker (and others that vary with device, for instance on Surface devices by killing nearly all surface-related processes). That is temporary as of course those processes eventually restart and overheating resumes. None of these processes show any CPU, disk, memory, network, GPU, etc. usage beyond a very small amount, and are often zero or nearly so. I do not experience overheating or sluggishness at any other time, even when consuming large amounts of memory, CPU, GPU, etc.

I have used repair install (reset and keep settings) multiple times on all devices, does not cure – may stop the issue this time but will come back probably next update cycle. On my Surface Laptop 5 I also tried fresh reset/reinstall (reinstall without keeping settings or data) without cure. I am going to do a format SSD and fully fresh install on that laptop as soon as I have it ready (imaged and all data file backups are availble on another device).

I haven’t listed here everything I’ve tried, it is fairly extensive. If anyone has any suggestions for me to try before I do the format and fresh install, and if I haven’t tried already I will. Thank you for any ideas and insight.

Reply | Quote

Replies

This Topic is in the Win11 24H2 Forum.
Win11 24H2 has not been released to the general Consumer yet.
Are you in the Insider Program using a Preview Build of Win11?
Would the PC Hardware Forum be more appropriate? We can move the Topic.

1 user thanked author for this post.

appyface

Reply | Quote

My error in picking the version, 23H2 and older depending on device. Never any insider/dev builds.

Can this post be moved to the correct classification? Is there a way for me to correct it?

My apologies, and thank you.

Reply | Quote

appyface wrote:

for the past several years.

With the same PC ?

How much RAM your PC has ? What type of storage and how much free space ?

This looks like cooling problem.

Run Core Temp app

Reply | Quote

From my post:

appyface wrote:

I have experienced the below on multiple win10 and win11 devices, different manufacturers, home and pro versions, for the past several years.

Alex5723 wrote:

appyface wrote: for the past several years. With the same PC ? How much RAM your PC has ? What type of storage and how much free space ? This looks like cooling problem. Run Core Temp app

I have two newer top of line Dell XPS laptops, an older Surface Pro 3 (top of line at the time), and a top of line Surface Laptop 5 just over two yeas old. Top of line meaning all hardware bells and whistles possible such as max RAM, max SSD size, most graphics power offered, etc.

The “SL5” (Surface Laptop 5) is my daily driver and the one I plan to format and fresh install soon to see if it solves anything on the next update cycle. Both Dell’s have had the issues from win10 through to win11 (all Pro), the Surface Pro 3 was Win10 home but upgraded to Win10 pro and still there, and the SL5 shipped win10 home but I upgraded immediately to win11 pro, so I don’t know if it had the problem under win10 like the others did.

I know it could be a cooling problem, but as I wrote when under heavy usage they don’t overheat, such as multiple calc-intensive large spreadsheets open and running VBS code, for example. It appears to only happen when windows updates are trying to be pushed to my devices and they are paused. If I unpause and allow the updates to install, the overheating stops until the next month.

I loaded Core Temp to SL5 and see nothing unusual, but it is not overheating at the moment. I will check when it happens again. Have been battling it for the past few days so it should return soon I think.

1 user thanked author for this post.

Alex5723

Reply | Quote

On my 6 years old Lenovo Y530 (32GB RAM, 256GB SSD, 160GB free space) normal usage temps are 45c-50c.
Running Windows update the temps can reach 80c+ for a short period.

Pausing updates doesn’t pose any stress on a PC.

Reply | Quote

appyface

appyface wrote:

via Sysinternals Process Explorer

You are obviously an experienced user, and it seems very likely you have already used this simplified approach.  However, less is more sometimes, so in brief:

I’ve never had an overheating or sluggishness issue that wasn’t clearly visible as high CPU or GPU usage as software OR “System”.

I have found the simplest tool for finding the culprit is the Windows Task manager, not Sysinternals Process Explorer.

Below are two screenshots of my Task Manager.  One sorted by the CPU column, the other sorted by the GPU column. That’s it.  It tap on the column header to sort the column. Hope this helps.

Desktop mobo Asus TUF X299 Mark 1, CPU: Intel Core i7-7820X Skylake-X 8-Core 3.6 GHz, RAM: 32GB, GPU: Nvidia GTX 1050 Ti 4GB. Display: Four 27" 1080p screens 2 over 2 quad.

Reply | Quote

appyface wrote:

It seems to occur soon after windows updates are staged for my devices, as soon as I unpause, the updates begin downloading and installing immediately.

Settings App\Windows Update\Advanced Options\Delivery Optimization
What are your settings? Is it possible that your computers are sharing the updates on your local network, i.e., passing the updates\parts of updates among themselves. That could explain the sluggishness of the network and the computers when Windows Update is unleashed.

1 user thanked author for this post.

satrow

Reply | Quote

Agreed, common factors have to be checked and tested first. Router + network + internet connections = common to all devices.

Reply | Quote

SL5 (Surface Laptop 5) overheating and jerky, sluggish, unusable last night as typically happens every month with updates paused. I unpaused and let the two July updates (cumulative for win11 and for .net) run.

As soon as they were installed the overheating went away. Same experience I have almost every month with all four devices – not always every month but most on both win10 and win11. The ancient Surface Pro 3 tablet can get pretty hot under heavy computing load and fan runs, but otherwise doesn’t suffer any heat problems. The other three do not get hot and fan is not audible, except during the push of updates while paused.

Some more details common to all, may/may not have any relevance since I’ve not been able to find any connection, but to state.

I do not have any of the four signed in to microsoft accounts, they are all local accounts only. I’m the only account and Administrator on all machines, and hidden administrator turned on. (I have my reasons, please stay on topic.)

All machines delivery optimization turned off.

All machines are allowed to download over metered connections, though there never is any as my home wifi isn’t set as metered.

None have any configured update policies.

All machines are connected via wifi not ethernet. All private network, use device MAC not random, and windows firewall for private networks is turned off.

Current home network setup. Spectrum cable modem -> Protectli Vault VP4630 2.5G ports,  running OPNSense firewall and router, DHCP server -> Cisco Business 110 16 port unmanaged plain ethernet gigabit switch -> ASUS AX5400 natively configured as Wifi Access Point (house coverage is small, no need for mesh or multiple WAPs).

The Protectli is way overkill for my network. has Intel® i3-10110U Dual Core / 4 Thread at 2.1 GHz (Turbo up to 4 GHz but not turned on), 6 Intel® 2.5 Gigabit Ethernet NIC ports, Kingston 32G memory, Kingston 1TB NVMe NV2-1000G, Samsung SSD 870 EVO – 1TB. I have never seen any resource be consumed more than 60% and then only for infrequent spikes.

My overheat problems at update time go back several years, whereas the Protectli is about a year old, the Cisco switch replaced another gigabit switch a couple of months ago, and the ASUS AX5400 just replaced another WAP that I moved to my Dad’s house. So nothing in my network goes anywhere near back to when the overheat problems started, which was pretty much my first Win10 computer (the SP3 – Surface Pro 3).  The only other thing in common are the devices and other computers that are plugged into the switch via ethernet cable, 12 all told including the uplink, those are all ancient and have always been plugged in to a switch of one kind or another going back a decade or more. None of them are windows devices and none of them overheat when they receive updates.

Yes these four win10/win11 devices can get warm when actually updating, but not hot and the fan is not audible except for the ancient SP3 on occasion. When updates are paused and they are pushed, the SP3 might shut down for overheat warning. The other three do not shut down but they are uncomfortable to touch and the fans are very very loud. I shut them down and let them cool off before using again, not ideal. Or, unplug the power cable so they are on balanced battery settings – the fan will not be as loud and they aren’t quite as hot to the touch, but the battery depletes more rapidly than even when under heavy computing usage. All four are using the power adapters that came with them, or one of my extra power adapters that are genuine from Dell or Microsoft. No knockoffs.

I have no clue why this happens. The only other thing common is they are all Intel CPUs and chipsets. Two Dell’s have Nvidea graphics and the two Surface devices have Intel graphics.

Would love to have a solution, but I have a feeling I’m looking for one needle across several haystacks…

Reply | Quote

So the next common factor down the line appears to be Wifi.

Reply | Quote

Yes but as mentioned the problem existed for years whereas the WAPs have changed a lot over that time.

And, why are they not overheating at any other time? What is it about updates being pushed that is driving win10 and win11 into overheating?

Also, I didn’t mention, but they’re pretty vanilla installs of win10 pro and win11 pro, no scripts to debloat or remove telemetry etc. Pretty common installs of apps and programs too, and somewhat different mix on the different machines.

Reply | Quote

I wouldn’t call stock Dell/any other brand installs vanilla.

How about a connection + building diagram to aid in visualising how it all fits together? Background temperatures per room/hotspot might also be helpful.

“somewhat different mix” – what’s common to the majority/all is what you ought to be looking for.

How many have, eg. Killer NICs, can any/all of those be ‘downgraded’ to simpler Intel drivers?

The i3-10110U-powered machine, it has a 15-25w TDP, why aren’t you running it as designed rather than restricting it? Surely not to save energy… ? You might save more by running those debloat scripts.

How about ensuring the products overheating are all given adequate airflow/cooling during the times when you know they’ll be working hard and fast to finish the tasks of keeping you updated and safe?

You’re the one with the bottleneck(s), try reducing by 50% the # of machines active for a while to see if the problem remains or reduces and by how much, what % or proportion, above or below expectations?

Strip your network back to minimal and rebuild it as required, making notes along the way – but don’t just rebuild in exactly the same manner, take into account that you’re troubleshooting – make changes that might enable you to pinpoint where weak links and/or hot spots are.

If we’re not very careful, we could end up pointing the finger at the user(s) as everything else is ruled out without any or minimal testing.

Reply | Quote

What was the answer on the Delivery Optimization settings? That is a common factor in the updating process for all machines.

1 user thanked author for this post.

satrow

Reply | Quote

I said no delivery optimization in my reply.

Reply | Quote

That could mean all the machines that are turned on at the same time are trying to download the updates individually at the same time. Unless you do the updating one by one.

Reply | Quote

Yes, but that typically isn’t the case – they seem to stagger but are within a couple of days of each other. I mean the push to the devices is staggered. If I let then all auto-apply there is no overheating of any, even when they all come in at once. Only a machine that is paused overheats. I have unpaused indivdually, all at once, makes no difference when updates are applied as that solves the issue. Only leaving them paused until I let the updates apply causes the issue.

Reply | Quote

I submitted a huge reply about 10 minutes ago, it was accepted (and stats above show I updated about 10 minutes ago) but I cannot see my reply. Is there a way to find out what happened to it?

Reply | Quote

If you submit/edit/submit etc too fast, the system can’t keep up and the post gets caught in the spam bucket. I think the system “thinks” you are multi-entering. Let us know when it happens and we’ll fish it out.

Slow down a bit between operations.

Reply | Quote

I don’t see it here, can you check? Thx.

Reply | Quote

Scroll up. Is that it?

1 user thanked author for this post.

appyface

Reply | Quote

Yes, it is showing for me now, wasn’t there a bit ago. Thank you. Should all replies after it be deleted so it is the last thing showing? If you agree please do else it stands. Thank you.

 

Reply | Quote

satrow wrote:

I wouldn’t call stock Dell/any other brand installs vanilla. How about a connection + building diagram to aid in visualising how it all fits together? Background temperatures per room/hotspot might also be helpful. “somewhat different mix” – what’s common to the majority/all is what you ought to be looking for. How many have, eg. Killer NICs, can any/all of those be ‘downgraded’ to simpler Intel drivers? The i3-10110U-powered machine, it has a 15-25w TDP, why aren’t you running it as designed rather than restricting it? Surely not to save energy… ? You might save more by running those debloat scripts. How about ensuring the products overheating are all given adequate airflow/cooling during the times when you know they’ll be working hard and fast to finish the tasks of keeping you updated and safe? You’re the one with the bottleneck(s), try reducing by 50% the # of machines active for a while to see if the problem remains or reduces and by how much, what % or proportion, above or below expectations? Strip your network back to minimal and rebuild it as required, making notes along the way – but don’t just rebuild in exactly the same manner, take into account that you’re troubleshooting – make changes that might enable you to pinpoint where weak links and/or hot spots are. If we’re not very careful, we could end up pointing the finger at the user(s) as everything else is ruled out without any or minimal testing.

OK “vanilla” might not mean the same thing to different people. I mean as delivered, then I uninstalled any pre-installed programs such as Norton AV, etc. that I didn’t need (most) via normal user uninstall routes, not special reg key settings, scripts, etc.

I’m not sure what is needed besides the topography I already gave for my network, can you share what would a diagram would cover that I haven’t? House is a rectangle, one story, pretty much dead center is my home office and the equipment mentioned, wired as mentioned. Also, all Wifi signals have been strong on every WAP I have had over the years, no interference. There are no wifi problems that I’ve ever seen with any devices.

Office is usually 72F as is the rest of the house, I live in a hot climate so a/c runs continuously 24×7 through summer. Office reaches 77F max when in milder seasons and a/c is not running constantly.

The only common software, besides windows preinstalled apps, is Microsoft Office Professional Plus 2016 in click-to-run format. On the two Surface devices there is also Microsoft’s own Surface package with drivers, firmware, troubleshooters, software, etc. whatever Microsoft requires on Surface devices.

Sorry, don’t understand “downgrade to simpler drivers”. The drivers all work as far as I can tell, and I’m not having any overheating or even hot issues under normal usage, only when updates are pushed. I don’t think I should change what isn’t broken until proved it is? The old IT saw, If it ain’t broken, fix it til it is – don’t want to go that route.

As far as the Protectli box, I don’t know what you’re asking about? It is as delivered, turbo is not enabled by default. Same with OPNsense, very few tweaks (turn on DHCP, set IP range, set reserved IP’s outside of range, a little logging). Both took less than 45 minutes to set up and deploy.

I have disconnected all but one device, start of patch week. Updates paused. Device begins to work hard and overheat when othewise idle (but not sleeping, none of the devices sleep or hibernate), there is minimal activity in process explorer, task manager, resource monitor – yet machine is hot and fan is running hard. As soon as I connect the other three, they soon exhibit the same. I let the updates apply and all goes back to normal until next cycle usually (only a few cycles were spared over the years).

I don’t want to debloat anything further than what I already removed, I already removed what I don’t need through OS menus, everything works as expected other than this strange issue. I can take my chances and just never pause updates and overheating problem 100% solved. Have done that multiple times and it always works. Let them apply as they come in, and machine may work a little harder, but nothing like this.

Reply | Quote

Poking in the murk –
Satrow 2687725 queries wireless.
Would it be feasible to connect one of the devices via ethernet instead of Wi-Fi? To see if this makes any difference during a Pause?

These are laptops, and not conveniently dis-covered like a desktop. Is it certain that overheating emanates from the CPU? Is there any way to localize or narrow the source(s?) of the heat within the case?

1 user thanked author for this post.

appyface

Reply | Quote

Appreciate the murky poke.

None of the four devices (two Dell XPS, two Microsoft Surface) have an ethernet port. But it is a good idea, and an adapter is not expensive. I can get one and try in August on one of the devices.

I have no idea what is causing the overheating, nothing shows on Process Explorer, Task Manager, Resource Manager. I have installed core temp on my Surface laptop 5 and will check the temps if/when it happens in August.

Unfortunately neither Surface has a user-openable case, and the Surface laptop 5 is still under warranty anyway. The Dells are under warranty. I can’t open anything without voiding the warranty. So far I can’t think of any way to isolate to component but it is a good thought.

The current WAP is wifi 6 and automatically chooses the radios for 2.4gHz and 5gHz devices. The previous wifi (in use for 1 1/2 years until a few months ago when current was installed) was also wifi 6 with auto-switching, and also the router until the Protecli vault with OPNsense was installed. The wifi before that one, in use for a couple of years, was a dual 2.4gHz/5gHz with separate SSIDs and handled B/G/N and A/N/AC and was also the router. The wifi before that was only 2.4gHz B/G/N and again was also the router.

Reply | Quote

appyface wrote:

I can’t open anything without voiding the warranty

Check your warranty.

Usually you can open laptops, desktops under warranty to upgrade RAM, Storage, wi-fi card, clean fans, replace battery…without losing warranty as long as you don’t damage components during the process.

* You can find How to in iFixit

Reply | Quote

Alex5723 wrote:

Check your warranty. Usually you can open laptops, desktops under warranty to upgrade RAM, Storage, wi-fi card, clean fans, replace battery…without losing warranty as long as you don’t damage components during the process.

Sure. You do you. I’m not opening them, especially when I have two good options: 1) Send them back for overheating, 2) 1-second fix by stop pausing updates.

Reply | Quote

The problem device, if indeed there is one, is likely to be out of warranty by now.

Anyhoo, not wasting my time on this any longer, good luck.

Reply | Quote

satrow wrote:

Anyhoo, not wasting my time on this any longer, good luck.

And I stop wasting my time by retyping my answers to you. Best of luck.

Reply | Quote

when it comes to using laptops during the summer months (and/or in regions w/ hot weather), I put some of my laptops on top of certain laptop cooling pads. never had any kind of overheating problems with the laptop pcs I use because of using such cooling pads

1 user thanked author for this post.

satrow

Reply | Quote

The so-called badness of updates, for home users is pretty unlikely.  In the distant past, if you had an antivirus that was not Microsoft’s, or a weird configuration like dual boot, occasional problems would pop up.  Recently even conflicts with game software’s anti-cheat are well detected by Microsoft and will cause them to automatically delay giving you a bad update.  If you have your user data backed up often and multiple devices available so that if one failed you could still do your daily tasks, you can probably comfortably turn automatic updates on, leave here and have a happy life.

Exception – shell replacement software to give more classic menus, like StartIsBack, Open-Shell, WindowBlinds or anything by Stardock do still occasionally cause unusual behavior with updates.  And businesses, especially ones using deprecated technologies like NTLM or old software in general, will need a more considered strategy.

I am hoping for your use case you can just forget about using pause if it is giving you trouble.  A different popular solution around here is to let WUMGR take over updates, using it instead of pause.

1 user thanked author for this post.

appyface

Reply | Quote

appyface wrote:

1-second fix by stop pausing updates.

Pausing has no affect on heating nor on sluggish performance.

Updating PCs using wi-fi connection is unreliable and prone to interference from other wi-fi networks (same channel).

1 user thanked author for this post.

satrow

Reply | Quote

Alex5723 wrote:

Pausing has no affect on heating nor on sluggish performance.

I never said it did. I said when I don’t pause I don’t have the issue. And I have zero overheating problems at any other time, including applying those updates.

Reply | Quote

deimos wrote:

A different popular solution around here is to let WUMGR take over updates, using it instead of pause.

WUMGR is something I hadn’t considered, I will look into it. I was only pausing because of Susan Bradley’s recommendations to do so, to avoid some of m$ gaffes. I’ve definitely been a victim of some of them. Not using pause is a 1-second fix. Was just hoping someone else might have run into this and have a clue what it could be, as I’d like to follow Susan’s recommendations and use pause. It’s not the end of the world if m$ bites me again with one of their updates. Thanks for the suggestion.

(Also, I’m not using classic menus, stardock, etc. No games. My laptops are used for business and are pretty close to stock, I removed some delivered apps and programs through standard user menus, and installed some mainstream programs like MS Office.)

 

Reply | Quote

EP wrote:

when it comes to using laptops during the summer months (and/or in regions w/ hot weather), I put some of my laptops on top of certain laptop cooling pads. never had any kind of overheating problems with the laptop pcs I use because of using such cooling pads

Thanks, but I don’t have overheating any other time than when updates are paused and they’re being pushed to my devices.

If you read my earlier comments, house is 72F, office is usually the same (or lower, right now 70F). This is in full summer when a/c is running continuously. Office may reach 77F in milder times of year when a/c is not running constantly and house may reach 73-74F. None of the four (laptops and tablet) are in the office. The office has the network devices.  77F doesn’t seem excessively hot to me, and it is only that warm a few months out of the year.

Thanks, I’m aware of external fans, cooling pads, etc. for hot running devices. My ancient Surface Pro 3 tablet used to need a bit of that under really really heavy computing in a hot area (80F or more). None of the other devices have any overheating, at most mildly warm, except for the paused update issue. Yes I could do some of that extra cooling when the paused update issue occurs, and may still do in order to keep working… but shouldn’t have to. Just wish I knew what this was.

Reply | Quote

satrow wrote:

The problem device, if indeed there is one, is likely to be out of warranty by now.

Last time I’m going to repeat what I already wrote to you. All four devices have the problem, and only one – the ancient Surface Pro 3 tablet – doesn’t have any warranty.

Clearly no one has any real idea about why this happens – and that’s totally fine. I posted about it here on a longshot and wasn’t really expecting anyone would solve it.

Reply | Quote

Murky poke 2 – and – inviting an off-topic slap down:

“hidden administrator turned on. (I have my reasons, please stay on topic.)”
– per 2687694.

So it is true that ALL the devices have the built-in Administrator account on?
Is this another ‘common factor’ to be eliminated as involved – somehow, mysteriously? Or did I miss that it already has been dismissed?

1 user thanked author for this post.

appyface

Reply | Quote

PaulK wrote:

Murky poke 2 – and – inviting an off-topic slap down:

Murky poke 2 welcome as well. You are keeping up with this overly complicated comment thread. No slap down for informed questions…

Yes all four devices (three laptops one ancient tablet) all have the hidden administrator account turned on. I have had it on in various windows OS for years, going back to XP for sure, perhaps earlier that I don’t know. I never had a problem that was solved or affected by turning it off, so I hadn’t considered it as a factor at all. Very easy to try turning it off just before the next patch cycle to see what happens. Thanks.

Reply | Quote

appyface wrote:

All machines are allowed to download over metered connections, though there never is any as my home wifi isn’t set as metered.

@appyface –

So, if you don’t have any metered connections, why allow Windows Update to download over them? Go into Settings>Update & Security>Advanced options and turn the slider off on one machine and see if it makes a difference come August.

I’ve never had your overheating “experience” when pausing updates, but I also have WU prohibited from downloading over metered connections by way of the setting I just described.

I will readily admit that it sounds like it shouldn’t make a difference, but it just might for some reason.

For your machines that have the Pro version of Windows on them, there are settings available to you within Group Policy that will help you control Windows Update so that you don’t have to resort to using the Pause updates setting any more. If my suggestion about turning off the metered connection download permission doesn’t do the trick for stopping your issue, then these other settings just might for the machines that have Windows Pro on them. If these settings work to eliminate the overheating and sluggishness on your Pro machines, there are registry settings that mirror most of them that can be used on your machines that have Windows Home on them.

Since you say that ALL of your computers become sluggish and begin showing signs of overheating as soon as Windows Update discovers monthly updates are available for them, but you have the Pause updates feature set to (it sounds like) ANY length of time, then I believe that there’s something deep within Windows Update that’s not quite right AND that wasn’t successfully repaired by the repair routine you put all the machines through because they acted up the very next update cycle after the “repair the Windows installation but keep all my data” routine you put them through.

I’d rather you not have to do a “bare metal” reinstallation of Windows on all the machines, but it might come down to that. Fingers crossed that it doesn’t! 

1 user thanked author for this post.

appyface

Reply | Quote

Bob99 wrote:

Since you say that ALL of your computers become sluggish and begin showing signs of overheating as soon as Windows Update discovers monthly updates are available for them, but you have the Pause updates feature set to (it sounds like) ANY length of time, then I believe that there’s something deep within Windows Update that’s not quite right AND that wasn’t successfully repaired by the repair routine you put all the machines through because they acted up the very next update cycle after the “repair the Windows installation but keep all my data” routine you put them through.

Yes you understand correctly.

I have also done a repair install without keeping settings on my Surface Laptop 5 (last year, after a windows update wrecked some things) but of course I put my common settings back and apps afterwards. The only difference I noticed with doing that (which required me to download ISO for USB stick and install from there) vs. full format and install is just the formatting of the disk vs. allowing the install to work with the existing partitions. So it doesn’t seem such a leap to me to try format and install as last ditch effort. (Side note, m$ doesn’t include any drivers for Surface devices in their install media, and not enough ports to have mouse and keyboard attached at same time. I had to buy a port extender. Thanks m$.)

The only reason I have OK to download over metered enabled, is on the rare occasion when one of the laptops leaves it’s OK with me to download over metered. I agree it shouldn’t make any difference but easy to try turning that off, I’ll add it to my August updates list of things to try.

I don’t have any Windows Home devices. The four devices are Pro and all become sluggish. I will look at GPO for alternates to using “pause” if the problem persists after trying the other suggestions.

Thanks.

 

Reply | Quote

appyface wrote:

…I have experienced the below on multiple win10 and win11 devices, different manufacturers, home and pro versions, for the past several years.

That statement in your original post was what made me think that you had a mix of Home and Pro windows installations. My apologies for the misunderstanding.

Reply | Quote

Bob99 wrote:

That statement in your original post was what made me think that you had a mix of Home and Pro windows installations. My apologies for the misunderstanding.

No, my apologies!  The two surface devices shipped with home (the two Dell’s were ordered with pro already installed). The ancient Win10 Surface Pro 3 tablet I ran for a short while on home (3-4 months maybe?) before I upgraded it to pro. The Surface Laptop 5 I upgraded immediately to pro after verifying no issues on receipt.

The ancient Surface Pro 3 with win10 home overheated on paused updates, one of the reasons I upgraded it to pro – hoping to solve that. Yes under home the SP3 had all those same settings for hidden administrator, etc. unless one wasn’t possible under home (I don’t recall not being able to set all, but that was 10 years ago… they have definitely been set since pro upgrade).

Reply | Quote

I have two machines, and on one of them, the built-in Administrator account is disabled, not hidden, and on the other one, the built-in Administrator account is enabled. Neither of these machines has the setting for Windows Update to download updates over metered connections enabled and neither one has their networking connection set to being a metered connection.

Both machines are, and always have been, Windows 10 Pro 64 bit.

Reply | Quote

Good to know. Here’s my list of suggestions to try in August (separately, then in combinations):

1. Ethernet cable instead of wifi
2. Disable allow downloads over metered connections

If those don’t work, may try:

1. WUMGR to manage updates instead of pause
2. GPO policies to manage updates instead of pause

Honestly, at this point it is hardly worth much effort beyond those. Even if I were to identify a m$ cause, they’ll declare it an edge case and do nothing anyway. (Been there done that with employer’s machine issues in the past.)

Reply | Quote

I did a full format and install of Win11 Pro 23H2 to my Surface Laptop 5, using the latest m$ ISO build in May 2024. I did this because my camera stopped working a few months ago, and windows reset with/without keeping settings didn’t restore function. (I did let it update to current after each reset.) Still thinking it was a hardware issue, was going to send it back under my warranty, but first did the full format/install (and paused updates immediately) to confirm. Camera working again. Took a full image (I use Macrium Reflect) then unpaused to allow updates to install. Camera broken again. I found a few posts regarding Surface camera (but none for Laptop version, many for Surface Pro X). I tried all I could find and nothing worked except to restore my Laptop back to fresh. I have gone through my steps to remove unwanted apps and install my apps and programs, and camera is still working. But laptop remains un-updated from May ISO.

Before I experiment on this laptop during the update cycle in August for the overheating issue in this thread, I would like to find out which update is causing the problem. Do you know of an easy-ish way to individually apply updates until I hit the one that kills the camera? I can keep restoring and try until I have isolated the culprits. But, I have never used WUMGR or GPO policies for windows update before, are either of these relatively straightforward to stop all updates and choose to let one at a time apply? If it’s a more involved process I’ll open a new thread so’s not to clog this one. Thanks if there’s a quick and dirty approach someone can mention.

Reply | Quote

WUMgr can do the best job of stopping/hiding updates. Since they will include both OS updates and driver updates issued by MS, consider also installing drivers one by one.

Type winver in the taskbar search box and hit Enter to find the Build you are currently on. You can download and install manually the monthly CUs from the MS Update Catalog by entering the numeric part of the KB number in the search box. Find the monthly Build nos. and KB numbers by month here. Also in Susan’s Master Patch List. No previews! Restart in between installs.

You can do the same with the .NET updates one by one. Info here or in the Master Patch List.

Then the driver updates using WUMgr to control which one you install.

Tedious at best.

2 users thanked author for this post.

satrow, appyface

Reply | Quote

I have used the catalog for my Win7 machines many times in the past but I forgot about it! Thanks for the mention. That might be the easiest way in this case since I will (probably) be installing and restoring several times to find the update or the combination. For sure I will be looking at all changes including drivers, .net, etc. Hopefully not too time consuming to find the culprit(s) as the camera broke back in May. Worst case I don’t do anything and leave it all on pause while I wait for the August cycle. So far everything is working as it should without the recent updates.

Meanwhile I haven’t turned on the hidden administrator account, nor the setting for updates to download over metered connections. TBC…

Reply | Quote

Be careful if you have the PC on Pause.
When you “Resume updates” it will be immediate download/install of whatever updates are currently available.
Also, WUMgr, wushowhide and Windows Update all use the Windows Update Service to scan for updates. If you have Pause enabled, you disable the Windows Update Service so NONE of them can scan for updates. So none of them will show current availability.

Reply | Quote

PKCano wrote:

Type winver in the taskbar search box and hit Enter to find the Build you are currently on. You can download and install manually the monthly CUs from the MS Update Catalog by entering the numeric part of the KB number in the search box. Find the monthly Build nos. and KB numbers by month here. Also in Susan’s Master Patch List. No previews! Restart in between installs.

Are you saying I can’t leave Win11 on pause and follow the above suggestion? If I can’t leave WU on pause (or prevent updates with another approach) how would I implement using the catalog suggestion? Win10/Win11 have installed updates immediately when pause is removed, nothing new there, so I’m not understanding how what you’re saying applies? <confused>

Reply | Quote

On Pause, WUMgr, wushowhide, and Windows cannot scan for updates.
Get the settings in WUMgr set right (it does not install, it is a portable app). But it will not be able to scan while Updates are Paused.
Download the first CU from the Catalog and try to install it manually. After the restart, check to see if Pause is still set. If not, you have set WUMgr to control updates. If it is, manually install the next CU.

But remember, If Pause is set, none of the scanning for updates works. That is what Pause is for. So DO NOT set Pause once you have WUMgr in control.

Reply | Quote

appyface wrote:

Are you saying I can’t leave Win11 on pause and follow the above suggestion?

You don’t need pause on a Pro Windows.
Use GPEdit Notify=2 (you will get notice of new updates. None will download/install.
Use WUmgr to hide updates and unhide and install when you want.
Block drivers, firmware in Windows update using GPEdit.
Download drivers for your hardware from OEM.

Reply | Quote

MS is OEM for Surface.

1 user thanked author for this post.

satrow

Reply | Quote

Alex5723 wrote:

You don’t need pause on a Pro Windows. Use GPEdit Notify=2 (you will get notice of new updates. None will download/install.

@appyface , what Alex is talking about with that comment is a certain setting that’s available for you to use within Group Policy, since your 4 computers are all running a Pro version of Windows. Please take a look (slow and careful look because there’s a lot of info) at the following post from @PKCano regarding some of the settings in Group Policy to help you control Windows Update. Although it’s just over 4 years old, it’s still very pertinent to this setting that Alex mentioned above. Pay very close attention to the screenshot in the post, as that will show you exactly where this setting is located in the Group Policy Editor:

https://www.askwoody.com/forums/topic/2000016-guide-for-windows-update-settings-for-windows-10/#post-2275043

You can click on the screenshot in that post to enlarge it (VERY strongly recommended).

The Group Policy editor (file name of gpedit.msc) is usually located in the \Windows\system32 directory. Just double click the file to launch it.

If you don’t feel like taking the “plunge” into Group Policy, no harm, no foul, as I realize that it’s not for everyone.

Reply | Quote

The setting is in Administrative Templates\Windows Components\Windows Updates\Manage End User Experience\Configure Automatic Updates in Win11, instead of the path in AKB2000016 for Win10.

3 users thanked author for this post.

satrow, Alex5723, Bob99

Reply | Quote

PKCano wrote:

MS is OEM for Surface.

MS isn’t OEM of the hardware (CPU, GPU, network, wi-fi, sound, BT, camera, SSD…)
MS is the OEM of the plastic shell.

Reply | Quote

I came home to my Surface Laptop 5 this afternoon, which is still paused to August 21, it was overheating and loud fan. (The other three devices are also still paused but are current with July updates and none were overheating.)

I checked the windows software distribution folder, it had been updated about 30 minutes before I got to my laptop. I tried to look at a log file (which I forgot, is not text) and I now have a tabbed Notepad program, which I did not have as of this morning.

I am a local login, not signed in to Microsoft with any app, have not even opened the Microsoft store (which I understand is where the tabbed notepad can be installed from. Not sure if it is also deployed another way.)

This machine is still ‘supposed’ to be the May 23H2 fresh install from the m$ ISO. I have only added back Office 2016, Snagit, Notepad++, Firefox Nightly, and VLC Media player, and those were done days ago after I restored back trying to fix my camera.

I guess I need to restore again and try WUMGR and/or GPO. (@Bob been using GPO for literally decades, just never looked at the settings for windows update. No fear here. I also prefer to keep my home machines as “stock” as possible. Hence my interest in using the catalog updates instead of configuring GPO.)

Reply | Quote

appyface wrote:

I came home to my Surface Laptop 5 this afternoon, which is still paused to August 21, it was overheating and loud fan.

appyface wrote:

…I now have a tabbed Notepad program, which I did not have as of this morning.

appyface wrote:

I guess I need to restore again and try WUMGR and/or GPO. (@Bob been using GPO for literally decades, just never looked at the settings for windows update. No fear here. I also prefer to keep my home machines as “stock” as possible. Hence my interest in using the catalog updates instead of configuring GPO.)

Good to hear about your experience with GP, it might have prevented your Surface’s d/l of the new version of Notepad.

I say “might” because I’m running Windows 10, not 11, so I don’t know if on Windows 11 the new Notepad program with tabs is an app from the MS Store or if it’s an actual program that is d/l’d by WU and quietly installed. On Windows 10, the settings for WU don’t do a thing to stop d/l’s from the MS Store because the Store is a separate thing altogether.

However, if you apply the setting shown in the image I linked to in the AKB article by PK, and then follow PK’s subsequent guidance in the post right below mine to find that setting in Windows 11’s GP, you’ll at least prevent the Surface from getting any updates that are normally retrieved by WU without it telling you it’s available in the first place. That setting is supposed to prohibit WU from downloading and installing any updates without your permission for it to do so in the form of clicking a button for that update in WU to begin with.

Reply | Quote

I’m sure the tabbed Notepad came from the m$ store, and in addition to windows update deploying a few things while on pause, the microsoft store did quite a lot too. Not just notepad, but about half the apps on my laptop that come from the store were updated. As mentioned I’m not signed in to m$ account anywhere – have not yet even entered my credentials anywhere – and I never opened the store, but clearly that didn’t stop m$ from pushing those updates. So just like win10 the store is independent of windows update in Win11. In looking at the software distribution folder, it seems windows update downloaded nine packages of considerable size, and installed a defender security update. Yes it’s still paused to 8/21.

I have a script from spiceworks that we used a lot at my employer, it stops BITS and other services, renames the software distribution folder, and reboots. I ran it right after posting earlier, since then the Surface Laptop 5 is cool and working well again. I’ll be restoring back to fresh install backup anyway as I’ll be trying to find the update that breaks my camera so I figured the script was worth a shot. (I had to do something, the keyboard on this thing becomes literal physical mush to the touch when it gets that hot, the letters appear in slow motion several seconds after typed, and the trackpad is erratic as well. Nearly impossible to use it in that state. Next step was restore but that takes about 2 1/2 hours and I needed to get some work done ASAP.)

Reply | Quote

Launch store app and block updates.

Reply | Quote

Alex5723 wrote:

Launch store app and block updates.

Yep did that already for a test, as soon as I saw m$ store updated the apps. Around 9:30pm, no overheating, but saw activity and my event log was flooded with 600+ of these messages:

event 2007 warning Microsoft-Windows-Store/Operational Microsoft-Windows-Install-Agent InstallService InProc Caller. Current Thread not impersonating. Using current process (LocalSystem)
Error: Unknown HResult Error code: 0xefffffff
Function: CallerContext::_getCallerToken
Source: onecoreuap\enduser\winstore\installservice\lib\callercontext.cpp (85)

I’ve just restored back to fresh install and will start looking for the update that broke the camera. The camera app was updated yesterday afternoon and camera is still working, so I’ll be focusing on windows update plus drivers, firmware, etc. as planned. There was one firmware update issued for this laptop but it was issued after the camera was already broken. The event log had an error in a biometrics DLL when the camera stopped working (and every time I tried to use the camera after that), so I didn’t expect the Surface firmware/drivers package to fix it, and it didn’t.

I don’t mind experimenting on this laptop as I have the time, but at some point I need to address all four devices that overheat until the current paused windows update cycle is allowed to install. The m$ store updates have never been a source of overheating as far as I’m aware  – they obviously have been flowing on their own schedule and if I don’t pause windows updates none of the devices overheat at any time for months on end.

Reply | Quote

Poke 3. Observation: Problem always somehow is updating related.
{Thinking} Assumption: CPU intensive; not other components.
But cannot capture CPU usage attributed to any process. Which, why, how?
There is repeated discussion around communications. Can’t imagine how modem could impact. But how about the router? Seems unlikely. But?

Some more far-fetched ideas to pursue?
During a fever episode, even though response is torpid, Disable the Wi-Fi adapter.
– If heat continues, then (hypothesis) bug is in Update code. Looping.
– If it cools, then (hypothesis) somehow the router is instigating problem. Or, symbiotic.

If [cools], confirm that router is suspect: With all(?) devices hot, power off the router. (Or, since other devices must be retained on-line, log into router and kill the IP or MAC addresses of cooking units. But this may not be possible to effect without power cycling.) (Note: Not accusing router of malfunctioning, just involved.)

If router is cause: Review ALL settings. As possible, simplify or reverse variables; QoS, …

Yes, multiple routers have sequenced through; have options been propagated down the chain?

{Pause Thinking} to let cool.

Reply | Quote

Alex5723 wrote:

You don’t need pause on a Pro Windows. Use GPEdit Notify=2 (you will get notice of new updates. None will download/install. Use WUmgr to hide updates and unhide and install when you want. Block drivers, firmware in Windows update using GPEdit.

Bob99 wrote:

that will show you exactly where this setting is located in the Group Policy Editor: https://www.askwoody.com/forums/topic/2000016-guide-for-windows-update-settings-for-windows-10/#post-2275043

I have set the group policy option to block m$ store apps from auto-updating and installing.

For Windows Update:

I have Configure Automatic Updates enabled and set to option 2.

I have Enable Optional Updates set to disabled.

I have Do not include drivers with Windows Updates set to enabled.

Here I am stuck with the linked article. I do not have Windows Updates for Business option. I do have options for Feature Updates, Quality Updates, and Set Target Version options under Manage Updates Offered from Windows Update, but they don’t match the article so I’m not sure what to set.

So I set nothing further than the above, disabled my firewall rule blocking internet from my laptop, and unpaused Windows Update. Immediately got a flood of windows updates downloaded and installed. No m$ store updates were pushed so that’s addressed. But the above settings did not stop windows update.

I’ve blocked internet, restored again, and have the above set. Do I also need the feature and quality settings, and what should they be if so?  I did not configure WUMgr as I thought the above would stop the updates from downloading, I thought I just need WUmgr to pick and choose which ones to download and install when I’m ready. Do I also need WUMgr configured before I disable my firewall rule and unpause windows updates?

Reply | Quote

If you have Pause set, then you will get immediate download/install when you unPause.
DON’T USE PAUSE. You shoot yourself in the foot.

1 user thanked author for this post.

satrow

Reply | Quote

PaulK wrote:

Poke 3

Thanks for your post…In brief, stopping internet by any of several methods kills the (attempted?) downloading/installing of windows updates, and that in turn stops the resource utilization and laptop cools off. When overheating, CPU is not heavy (around 44%), memory consumption is low. Disk is hammered though and network is very busy. Disk stops being hammered and network stops being busy when internet is killed (makes sense) and laptop cools off. I’m fairly certain none of the network devices are involved beyond their normal function.

Reply | Quote

appyface wrote:

I do not have Windows Updates for Business option.

appyface wrote:

Immediately got a flood of windows updates downloaded and installed. No m$ store updates were pushed so that’s addressed. But the above settings did not stop windows update.

That’s because of the pause. For now on notify=2 will stop downloads and WUmgr will able to hide any new updates.

Reply | Quote

Nope.

 

Reply | Quote

The “2” setting will prevent download/install ONLY if the update queue has been cleared. When you use PAUSE – anytime – you kill protection from download/install b/c unpause will ALWAYS cause the immediate reaction.

You have to set the “2” after the reinstall and BEFORE you go on the Internet for the first time. Then the first ever attempt for the computer to scan for updates is covered. If you set Pause just once, you’re SOL.

Reply | Quote

Alex5723 wrote:

That’s because of the pause. For now on notify=2 will stop downloads and WUmgr will able to hide any new updates.

Backup has the windows update pause. So I have to restore that way. What to do different then? Without a solution your statement doesn’t help the current situation.

Reply | Quote

Still no solution to the current problem of trying to control updates so I can find out what broke my camera and get back to the issue of this post – why overheating on pause.

1. No internet connection when I restore from backup after fresh install.
2. Backup image already has pause set.  (There was never any internet connection during fresh install and pause, as surface drivers for wifi had not been added yet and m$ ISO does not have generic drivers for it. No connection to the internet so nothing had been staged unless it was already part of m$ ISO.)
3. Set above mentioned GP, enabled internet, unpaused. Slammed with updates.
4. Unpaused (gave error offline but still unpaused), set GP, enabled internet. Slammed with updates.
5. Set GP, unpaused (offline error), enabled internet. Slammed with updates.

There can not have been any updates staged after fresh install and before the backup, unless they came with m$ ISO. GP documentation says configure updates takes effect immediately. So what is the solution?

 

 

Reply | Quote

You can unpause updates without having to click the Resume Updates button (which causes Windows to download all pending updates) by making the following changes in the registry.

Open regedit as Admin

Goto HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UpdatePolicy\Settings and change the values of PausedFeatureStatus and PausedQualityStatus to 0 (zero).

Goto HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings and Delete these keys:

PauseFeatureUpdatesEndTime
PauseFeatureUpdatesStartTime
PauseQualityUpdatesEndTime
PauseQualityUpdatesStartTime
PauseUpdatesExpiryTime

The first step reset the pause status back to unpaused and the second one removes the actual dates/times that where set for the pause.

Once you’ve done this, the Windows Update screen will no longer show Updates paused but, since you didn’t actually click the Resume updates button, Windows shouldn’t download anything because you’ve now got the Group Policy in place asking it to prompt you before downloading.

Note: if the Windows Update screen is open when you make those changes, you won’t see the status change until you close/reopen it.

3 users thanked author for this post.

Cybertooth, wavy, appyface

Reply | Quote

n0ads wrote:

You can unpause updates without having to click the Resume Updates button (which causes Windows to download all pending updates) by making the following changes in the registry.

Thank you, I will try this.

Reply | Quote

appyface wrote:

Thank you, I will try this.

No updates coming in, thanks again. Now I can get on with the camera issue before returning to the thread topic.

Side note, no overheating (not really even very warm) but resource monitor showed disk and network being hammered while still no internet connection (LAN activity is possible but all windows devices are disconnected at the mo), event logs filled up with connectivity issues (6400+ warnings and errors alone). Guessing this is all normal. After enabling internet, activity stepped up but again no overheating not even very warm. Taking another backup now so I can work with WUmgr and the camera issue later when I get back to this. Thanks again.

Reply | Quote

OK, Surface Laptop 5 now up-to-date with all my apps, all windows and apps updates applied (as of yesterday), camera is working, all seems to be working well with no overheating or sluggishness. No GPO or registry tweaks now. Windows update is not yet paused but will next week.

The windows updates as of yesterday are current through 2024-07 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5040442), and 2024-07 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 23H2 for x64 (KB5039895).

This morning, I am being offered  this?
2024-07 Cumulative Update Preview for Windows 11 Version 23H2 for x64-based Systems (KB5040527) is available.
Download & Install (button)

I didn’t think that preview should be offered to me, since the actual cumulative update has already been installed. Thoughts?

Reply | Quote

appyface wrote:

Windows update is not yet paused but will next week.

Don’t pause. Use Notify=2 and than WUmgr to hide updates.

Reply | Quote

Thanks but no thanks, need to use pause and find out what is happening to the four devices (refer you back to opening post).

Reply | Quote

Preview updates are offered on the fourth Tues of the month. Susan does not recommend installing Preview patches.
Preview patches are for testing future fixes/features in an Enterprise environment.

Reply | Quote

Still the question, why am I being offered 2024-07 preview when I’ve already installed the actual updates?

Reply | Quote

Because the Preview CU, which was offered after the Security update CU on Patch Tuesday, superseded the Security CU. Notice that the KB number of the former is greater than the latter.

CUs are Cumulative. The current one superseded (and contains) the previous ones. So the Preview contains and supersedes the past Security CUs and past Preview CUs.

You are seeing the Preview because Microsoft offered it to Windows Update. And you are using Windows Update.

Reply | Quote

1. Today is Saturday, not Tuesday (for me) when the update came in
2. Why would a newer preview for July be issued after actual updates have already been issued?

Reply | Quote

The Preview is a preview for changes that will be offered in the Aug. CU. But it is issued in July, hence the 2024-07 is the correct dating of the update.

https://support.microsoft.com/en-us/topic/windows-11-version-23h2-update-history-59875222-b990-4bd9-932f-91a5954de434

Reply | Quote

Has anyone suggested keeping MS from updating drivers??

Just because you don't know where you are going doesn't mean any road will get you there.

Reply | Quote

PKCano wrote:

changes that will be offered in the Aug. CU. But it is issued in July

OK.

wavy wrote:

Has anyone suggested keeping MS from updating drivers??

Yes.

Reply | Quote

wavy wrote:

Has anyone suggested keeping MS from updating drivers??

I did numerous times : block drivers and firmware updates.
Can be done on Pro and Home versions.

Reply | Quote

Alex5723 wrote:

I did numerous times

Yes and it still doesn’t help answer the original question, which I am now back to.

Reply | Quote

Wednesday evening 8/14 one paused Dell began overheating. Yesterday afternoon 8/15 the other paused Dell began overheating. This evening 8/16 my Surface Laptop 5 (the test machine for this thread) began overheating. None of the machines were doing anything intensive or were doing nothing at all except powered on and not sleeping. (The ancient Surface Pro 3 tablet bit the dust last week so is out of the picture now.)

After the format/install of Win11 Pro 22H3 (May edition from m$ website ISO) on 7/17, I did not enable hidden administrator mode, did not allow downloads over metered updates, have been using an ethernet cable (via an adapter as the SL5 doesn’t have an ethernet port) since last weekend. I think I eliminated all the weird variables we thought might be having an impact.

The SL5 is all but unusable now, so before I go ahead and let August updates apply – what can I look at?  I’ve attached the task manager view while it is overheating and super laggy right now. 

Reply | Quote

appyface wrote:

Wednesday evening 8/14 one paused Dell began overheating

What about temperature reports for each CPU core in each PC ?

Reply | Quote

appyface wrote:

super laggy right now

What approximate % are the kernel times running at?

‘lag’ range:-
~2-5% almost imperceptible for most bar the most sensitive users
5-8% noticeable, windows ‘stutter’ across screen when dragged
8% > becoming quite difficult to use, gaming almost impossible, waiting time post-click increases.

Similar can occur when a software approaches some invisible/artificial/buggy ‘resources’ limit (sometimes RAM, other times ‘unknown’) but that’s usually limited to that software, or disappears very soon after the offending Process is killed.

Reply | Quote

After I posted here, I shut all three laptops down so they were not overheating all night. Powered them back on next morning. Usually within minutes to possibly hours they would all be overheating again. As soon as the overheating resumed I’d get the above info and reply.

Except the overheating hasn’t resumed. All three have been powered on full time since then, and in use daily. They’ve haven’t even gotten warm.

All three are still on WU pause.

As far as changes, only the SL5 had format/install win11 fresh in July. The two Dells haven’t had a windows reset or any other changes to their settings (except for updates) in 1-2 years.

Also. OPNsense released a full upgrade earlier this month, I installed that upgrade soon after I powered the laptops back on two days ago. That shouldn’t have anything to do with anything… this overheating is literally a years-old issue starting with Win10 and I’ve only had the Protectli Vault and OPNsense since February.

I’ll come back when (if?) the overheating resumes. Laptops will remain on WU pause.

1 user thanked author for this post.

satrow

Reply | Quote

Dells are not overheating (yet), SL5 just started overheating about five minutes ago.

Core Temp from SL5.

 

CPU/Kernel times from SL5. I got them from resource manager; task manager looks different from that screenshot above and doesn’t offer the option. I am not sure if the resource manager is showing kernel times, I seem to recall they used to be shown in red but I haven’t looked at this for a long time, so I don’t know if these graphs help. Snagit had a little trouble stiching multiple screens together but the graphs are there – nothing much going on.

 

Disk and network are the busiest at the moment.

Reply | Quote

appyface wrote:

SL5 just started overheating about five minutes ago.

45c – 51c is not overheating. 90c is.

Reply | Quote

Your statement isn’t helping Alex. I wish for you to stop with these kinds of interjections.

By overheating, I am talking about fan very loud and the laptop body is too hot to comfortably hold. The heat coming up through the keyboard is uncomfortable. The keyboard becomes laggy – letters appearing in a delay or long pause and then spurt. All programs are laggy and respond slowly or pause, long delays switching windows.

This is happening with all three laptops (two Dells, one SL5). All laptops are on risers and have good airflow around the bodies. They’re all in clean environments and the internal fans are not dirty or blocked as best I can determine. External fans help make them more usable but they’re still very very warm.

Reply | Quote

Post your core temps from when it is overheating, please.

Reply | Quote

Already did.

Reply | Quote

Remind me – which CPU core(s) are overheating – temperatures?

Reply | Quote

No cores are elevated, they always look normal.

Reply | Quote

So temperatures are normal.

Reply | Quote

If you mean CPU cores, yes they always seem to be when I experience the overheating.

Reply | Quote

How is your blood circulation, have you, or parts of you (eg. hands, feet, ears) been more sensitive recently?

Reply | Quote

???

Reply | Quote

I don’t see any high(er than ‘normal’) temperatures listed to account for your description and that led me to thinking that something like Reynaud’s might account for the occasional temperature spikes that you’ve been describing.

Reply | Quote

I appreciate your out of the box thinking. But it’s strictly device problem.

To recap:

1. Three people here with three devices (was four, my old tablet died recently)
2. All devices overheat
3. Overheating only occurs once a month when windows updates are being pushed and the laptops are on windows pause
4. Laptops overheat whether plugged in or on battery
5. Laptops overheat whether in our home or away from home*
6. Multiple people have observed the overheating

*Laptops are not away from home much, but always have internet connection when they are. At home I have tried disabling the wifi adapter and overheating stops.

Reply | Quote

appyface wrote:

All devices overheat
Overheating only occurs once a month

Are you sure the overheating isn’t being suggested by the noise of fans?

I’ve still yet to see any stats suggestive of overheating, have you tried tuning the cooling fan behaviour of the devices in the BIOS or Control Panel, etc.?

Reply | Quote

Read my description: https://www.askwoody.com/forums/topic/odd-overheating-and-sluggish-problem/#post-2698545

Since multiple people including outside my household state the laptops are uncomfortably hot, this seems proof enough. Neither I nor anyone else to date has come up with any stat program that can point to the cause.

Reply | Quote

Some folks are more suggestible than others, fans blowing hot air are doing what they are designed for, if you can’t log high temps, they’re not high. Fan noise might be fooling y’all.

Reply | Quote

satrow wrote:

Some folks are more suggestible than others, fans blowing hot air are doing what they are designed for, if you can’t log high temps, they’re not high. Fan noise might be fooling y’all.

If you can’t even hold the thing how is fan noise fooling everyone who touches them?

Reply | Quote

Yesterday I applied August updates to the Dells and so far they are running cool, that is typical.

For the SL5, just now I’m trying a test. I blocked LAN/WAN access (via rules in OPNsense), ran my WU reset script, paused updates again (paused now through 9/27), allowed LAN/WAN traffic again. The SL5 cooled immediately. We’ll see if it resumes overheating.

Reply | Quote

All three machines are still paused following windows update in August, and none have overheated so far in September. Will leave them paused and continue waiting.

Reply | Quote

Applied September updates to all three machines when Susan Bradley gave the all clear, then repaused all of them. None overheated through the October updates so far.

I do not know what could have changed with all three. The SL5 had the format/install of win11 fresh, via this thread we used registry and GPO settings to manually stop updates including microsoft store and got my camera working again (and then removed those tweaks, to go back to using just WU pause). I did not do anything with the Dells except unpause WU and apply updates when they became so hot and laggy as to be unusuable.

I can only hope m$ has fixed something since I’m pretty sure I haven’t. If the issue should resurface on any of the three I’ll come back and start a new post.

Reply | Quote