Remember the "Unsupported Hardware" pop-ups & WUFUC?

[Lioninstreet]

I've been running w7 with a Kaby lake processor for about 18 months now. Right after the install the "Unsupported Hardware" nag started and as most others have, cured it with WUFUC.

WU was then set to check for but not install & I would install the monthly rollups and such once I saw there were no issues with them.

All was sweet until last week when support ended. The "Unsupported Hardware" nag has started to appear again. Apparently WUFUC is not working, broken, stopped working, or whatever. Re-installing it seems to have no effect.

What's odd is, figuring M$ would try to slip something in to my OS at the last minute, I DID NOT install the 01/20 updates that came up thru WU.

I suppose I could just turn off windows update to make the nag go away, but if I end up using an ESU hack, that solution won't be an option.

Anyone else seeing this?

 

[torchwood]

Hi

As EOL has been reached i would ignore it
Roll back to the day before you last installed the updates

note
as your running a non-supported OS use Intel's site for cpu/processor updates.


Roy

 

[Lioninstreet]

@torchwood, thanks for your non-technical, perspicuous solution.

The last updates install was the 12/19 rollup. With this update there was no "Unsupported Hardware" issue. And of course, this "warning" has likely been a cumulative part of all rollups since it was introduced back in 2017.

Problem is the nag keeps popping up every few hours and frankly is a PITA to deal with. It would be most helpful to find guidance for a more permanent solution besides the obvious.

 

[Lioninstreet]

Problem appears to have been solved.


Initial attempt was to search for updates that were associated with the nag. Reported by this forum and other sites they seem to be KB4012218, KB4015549, KB4048957, KB4054519, & KB4095874. Only one of these was installed (KB4095874 a .net framework 3.5-4.71 update) but after removal, the nag persisted.


The ultimate solution was to just try a reinstall of WUFUC with it's patch. After that, all is well.


I'm guessing that something triggered the nag (maybe the date of EOS??), breaking or changing the modification that WUFUC does to the OS. A couple of restarts will verify it stays fixed.

 

[erpster4]

you could try using this as an alternative instead of WUFUC:

GitHub - p-lider/WuaCpuFix: Windows Update new CPU limitation removal tool for Windows 7 and Windows 8.1


WuaCpuFix seemed to support newer Win7 updates, especially recent Win7 updates that are SHA-2 only signed
only works with 64bit Win7 - does not support 32bit Win7 though but who uses a 32bit Win7 OS on modern PCs that require a 64bit Win7


remove WUFUC first before installing WuaCpuFix

 

[Lioninstreet]

Good tip, thanks

 

[Lioninstreet]

Ive not changed the system configuration since reinstalling WUFUC a week ago, not even a restart. Was greeted with the nag again this morning. After clicking it off, the damn popup re-appears every 20-30 min or so...

But I think I'm getting closer to what's causing the problem. Last night I ran windows update to see if MS had pushed an update for the screen size error on the Jan-2020 update. No they hadn't. Today I wanted to run WUmgr just to see if it picks up the same updates I've not installed (all Jan-2020). The run starts, the unsupported hardware nag opens, and the update run fails with error 0x80240037: the functionality of the operation is not supported.

It will also immediately pop up using WU, then after about 20 seconds the update fails with the same code.

So clearly the nag now popping up again has something that was somehow triggered by Windows Updater being run...

 

[erpster4]

Ive not changed the system configuration since reinstalling WUFUC a week ago, not even a restart. Was greeted with the nag again this morning. After clicking it off, the damn popup re-appears every 20-30 min or so...

why are you still using WUFUC?
remove it and use WuaCpuFix instead
and if you still have unsupported cpu nags when running WU with WuaCpuFix installed, contact the creator of WuaCpuFix to bring up the issue