Replies

Thanks, Susan.

KB5050411 had been lingering in WuMgr for a while, but since I already installed it in April I guessed that was an error. But then I saw you wrote in the Master Patch Listing that 5050411 “May need to install second time”, so I reinstalled it again. That went well, and no restart needed.

Since there were no security updates for .NET I didn’t install KB5055683 yet. Also because I couldn’t find the 3.5 and 4.8 specific update – only that parent KB.
However, I saw that you also put the 3.5 and 4.8 specific KB5054977 in the List, I decided to install that one.

Thirdly I installed 2025-5 Cumulative Update for Windows 10 Version 22H2 for x64 KB5058379 before you gave a “go” because of the Windows Kernel Vulnerable Drivers.

All seems well.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

RESOLVED because I got fed up with Windows 11 and meanwhile switched to Linux/LMDE for my daily driver.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

1 user thanked author for this post.

Cybertooth

It’s an exaggeration, but I had to take many steps to get it functioning again.
Figure: it’s a genuine Microsoft keyboard. It even didn’t work in Linux anymore…

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

2 users thanked author for this post.

satrow, b

I just installed February’s cumulative update KB5051974 for Windows 10 22H2 – before Susan changed the MS-DEFCON, but since I skipped January’s cumulative KB5049981 because it destroyed my wireless keyboard (see my previous posts #2744490 and #2745817), I felt I should ‘close the gates’ a.s.a.p.

I am happy to confirm that February’s KB5051974 has indeed solved the USB-/DAC-related problems that I encountered after installing January’s KB5049981.

Everything’s functioning as should.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

1 user thanked author for this post.

lmacri

On February 1st I installed Cumulative January 2025 KB5049981 on my Windows 10 Pro 22H2 system, and was not happy after that:
My Microsoft (Wireless) Multimedia Keyboard did not work anymore. I tried changing the driver, reinstalled the software etc. but nothing helped. Ended up restoring my latest backup, but to my surprise that didn’t solve the problem either! Had to restore an end-of-December backup to get everything to work again.
(KB5049613 .NET 3.5 and 4.8 for Windows 10 22H2 x64 installed without problems.)

Although I haven’t seen anyone having similar problems here on Woody’s, I don’t seem to be only one encountering usb-related troubles when I search online. Most speak of audio usb-related problems, but appearantly my not-current keyboard is based on the same ancient Digital to Analog Converter.

KB5050081 is supposed to rectify these usb-problems, but it often fails to install. Many say that it does indeed fix these problems however.
But just to be sure, I will wait for February’s cumulative update to address all the above.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

1 user thanked author for this post.

JCpharm

Just installed Windows 10 Cum. Jan.2025 KB5049981. Was not happy after that:
My MS Wireless Multimedia Keyboard did not work anymore. Tried changing the driver, reinstalled the software etc. but nothing helped.
Ended up putting back a backup, but to my surprise that didn’t solve the problem either!

Had to restore an end-of-December backup to get everything to work again.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

2 users thanked author for this post.

MrToad28, Deo

Never mind, Brian. I see that Will has explained why.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

Your investigation into switching to Apple and OSX is going to be interesting, Brian.

However, don’t you think that more people are inclined to switch to Linux instead?
Not only do distros like Mint give a more Windows-like experience, people can also run it on hardware they already possess (for maybe ten years more).

 

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

2 users thanked author for this post.

Nibbled To Death By Ducks, Bill C.

I tried to upgrade from Windows 10 Pro 22H2 to Windows 11 Pro 24H2 by an “over the top” install. Only gave problems.
First by disabling genuine MS activation keys after 24 hours, and later by killing a legit manufacturer network driver (which was working fine). After I than succumbed to a plain ms driver the connection was repaired, but that again led to Defender and WuMgr not being able to connect anymore. I rest my case.

Thank you Macrium and Foxclone for bringing me back to my peaceful Win10/LMDE environment.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

I’m fed up with the whole thing and decided to do a big new year clean up and start from scratch, so I will wipe the lot and do a clean sheet install of Windows 11.

Thanks for all the help, people.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

Thank again, Paul. The activation troubles began after I put in the first genuine key, not because I later used multiple keys. That first one stayed good for days, but then all over sudden….

Yes, I’m torn now between a repair and MS. Last choice means creating a MS admin account. MS says that’s the way to solve the problem.
I only wonder whether I need to keep the MS account to keep te activation alive, because I’d rather ditch it once the activation is done.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

Thanks, but I already found the key with ShowKeyPlus which does the same as Belarc Advisor.
The problem is that all the genuine Win10 and Win11 keys I have are rejected 24 hours later.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

Sorry for the late reaction, guys. I’m in Europe and just woke up.

@Paul T It is a Fujitsu brand pc, Paul. But I did not find any key in the BIOS. All I can find in the BIOS is a UUID.
And I said already that I’ve ran the Activation Troubleshooter many times, and every time it solves the problem until 24 hours later…..

@krism It’s a Windows 11 rig, but I also have a Windows 10 key, that doesn’t stick either.

@s Thanks, Susan. I did try to activate without vpn but that didn’t help either.
Will the admin + password without vpn stick when I revert the admin account back to a local account?

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

You are totally right! I’m not familiar with the net user outcome, so that’s why I misinterpreted it.

Thanks too for the link with explanation.
I checked in Computer Management and the WDAGUtilityAccount is disabled.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

1 user thanked author for this post.

b

No, both are local accounts. I ditched all my ms accounts a while back.

I don’t know if I can change the designation and don’t know if I want to, because this WDAGUtilityAccount (Windows Defender Application Guard account) seems to give extra protection by browser isolation and other. Till now I haven’t encountered any restrictions because of it.

It is whacky however that WDAG turned itself on during the update. It was off in Windows 10.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

1 user thanked author for this post.

Elly