Latest Windows update (KB5015807) causing overheating?

Quartz

Quartz

Quartz

Soldato
Joined
1 Apr 2014
Posts
19,180
Location
Aberdeen
Two friends are reporting that they've been having overheating problems with their PCs and that those problems have been resolved by removing the update KB5015807.

I have not seen this problem myself and I have that update installed. Of course, they are in SE England and I am in NE Scotland...
 
What i have noticed is CoreTemp on my taskbar sometimes reads in the high 80s, but right clicking it and refesh gets it reporting normally ~32c.

It really is very random when it does it and most of the times it is fine.

Maybe they was having the same false readings?
 
Not seen this issue, im on alder lake and my temps are well within spec even after the update. I don't use coretemp anymore but with msi afterburner reporting the cpu temps its around 55-60c with a 5.1 OC which is what i normally see. Will pay abit more attention to it and see if the figure jumps about.
 
Quartz said:
Which bit of


did you miss?
Click to expand...

I didn't miss it, it's highly unlikely unless they have identical PC builds and software to be causing overheating issues when we've just had one of the hottest weekends of the year. Looking online for that KB number and I'm yet to find any posts or reports about overheating issues, there's some for printers stopped working and edge GPO not applying correctly, usually if an update causes major issues it's posted on plenty of sites, nothing in the known issues either as yet:

Known issues in this update

SymptomWorkaround
Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later.

Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps.		To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the SSU:

  1. Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab <destination path>
  2. Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path>
  3. You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU.
If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business.
After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING".For more information and a workaround, see KB5005322.
After installing this update, IE mode tabs in Microsoft Edge might stop responding when a site displays a modal dialog box. A modal dialog box is a form or dialog box that requires the user to respond before continuing or interacting with other portions of the webpage or app.

Developer Note Sites affected by this issue call window.focus.		This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can resolve it by installing and configuring the special Group Policy listed below. For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.

Group Policy download with Group Policy name:

Important You will need to install and configure the Group Policy for your version of Windows to resolve this issue.
 
Glanza said:
I didn't miss it, it's highly unlikely unless they have identical PC builds and software to be causing overheating issues when we've just had one of the hottest weekends of the year.
Click to expand...

I have known these people for over 35 years and both of them know what they are talking about.
 
demonix said:
At least in my case, that update has been trying to install for weeks only to end in 0x80073701 errors every single time and everything I've tried to fix it hasn't.
Click to expand...

Aye it seems to not play well with MWB and .net 3.0 active, and even with them off it won't update quite a bit of the time, due to .net 3.0 not actually switching off for 'reasons' I assume MS will fix this, it seems to be becomign more and more widely reported
 
Find the correlations aside from the update, how are the two problem systems similar aside from the windows update. "These guys know what they're talking about" isn't anything to work with, like at all. What are their system specs, just for starters.
 
First thing to do would be to get out process monitor and see what is going on in the background - I've seen an increasing number of updates lately where they do background maintenance/optimisation processes in the background which get stuck in a loop, etc. which could contribute to issues.

Windows update is a clown show at the best of times so it wouldn't surprise me.
 
It took my machine 3 attempts to install this update.
In the end I rebooted and forced it to run windows update.
My machine hung at shutdown on the "preparing screen" and after 30 minutes I just power cycled, when it powered on it tried again at boot and seemingly failed again.
When it did finally work it `hangs` a lot on the installing phase inside windows update, it takes a noticable amount of time to install stuff on shutdown and then it installs even more stuff on startup.
The machine runs fine now.
FYI I run on a potatoe. A 1stgen I7 with 6GB system ram. Im also still on 21H1 rather than 21H2.
 
demonix said:
At least in my case, that update has been trying to install for weeks only to end in 0x80073701 errors every single time and everything I've tried to fix it hasn't.
Click to expand...

Am I blind? I cannot seem to find any of these KBs on my system and it's all up to date.
 
You must log in or register to reply here.
Back
Top Bottom