KB4524244 Security update for Windows 10 - February 11
-
I am not having any issues but decided to uninstall this update. This is what pushed me to uninstall KB4524244. Since it seems the one way to know if this update can create problems is by doing a Reset, and in my case, it might take years before doing one, it seemed like uninstalling was the reasonable thing to do. Otherwise, I would be pondering about whether I should have or not uninstalled it, forever and ever. 
Uninstalling was fast, and well.
Bo
-
My thinking was the same as bo elam and I uninstalled it from my HP Pavillion even though it had been on here 3 days with no problems. Better safe than sorry.
- - - Updated - - -
Even though I uninstalled and did a restart the update still shows in my update history. Is this normal?
-
Even though I uninstalled and did a restart the update still shows in my update history. Is this normal?
Yes, that's normal. Where you ll see the update gone is in the list of Installed Updates in Control panel.

Bo
-
-
-
" You use UEFI in legacy mode. "...............dont understand , MOBO is an ASUS Z97-K with latest Bios-update from 2015 ( !)
Im sure its a Legacy Bios ..........
btw ; should you restore to 10 Februari , to get rid of it....??
Both of my Z97 units are running 64 Bit UEFI not Legacy mode?
Last edited by Brink; 16 Feb 2020 at 21:56.
Reason: removed duplicate posts
-
-
Yes, that's normal. Where you ll see the update gone is in the list of Installed Updates in Control panel.
Bo
Hi Bo,
Man, I opened a can of worms. While I believe what you say is true I'm not so sure.
I have three machines; Two laptops that are in my system specs and one recently upgraded from 7 to 10 desktop, and even though they were running well with KB4524244 I decided to err on the side of caution and uninstalled 4244 on all three. The CP applet showed 4244 as uninstalled on all three but it remained listed in all three of 10's OS Settings\Update applet.
Here's where the can of worms comes in.
I checked my dsktp this morning and thought
I wonder if 4244 shows in an ELV CMD prompt and it did then I checked in PS and it was there to, so taking this one step further I used these CMDs to check and then uninstall 4244 using the CMD and PS prompts:
Code:
These two work to check in the CMD prompt:
wmic qfe list
wmic qfe | find “4524244”
This one only works to check for PS:
Get-Hotfix
This one works to uninstall in both CMD and PS prompts:
wusa /uninstall /KB:4524244
The uninstall CMD for CMD prompt removed 4244 and when I checked CMD with 'list' 4244 wasn't there when I used 'find' I was returned to the blinking prompt.
When I used uninstall in PS it returned a small pop-up saying 4244 wasn't installed on this computer. Okay. But then I went back to 10's OS Settings\Update applet and it was still listed.
So I'm thinking; Somewhere in the bowels / registry? of 10's update file there's a '1' letting Windows Updates know when it visits the next time to fix the old 4244 that 4244 was on my machine at one time. I just hope the new update still runs the uninstaller to clean everything up before it installs the new 4244 and then there should be a new date listed for 4244 in the Settings\Update applet.
For now I'm going to let sleeping dogs lie and wait for the 'new' 4244 to come down the pike and see what happens, I have two laptops that I haven't and won't use the prompts to uninstall 4244 and one test machine dsktp for comparison.
p.s. That's my story and I'm sticking to it, I have pix's but this post is long enough without adding them in, but available on request...
-
I used your info in CMD and PS and the update in question was not present. With my limited knowledge I don't usually mess round with CMD and PS but with your explicit instructions everything went perfect.
Thanks, you guys are the best.
-
You're welcome, did you use the elevated versions of both CMD and PS?
You jogged my ambition, when I get back from runnin' errands I'll do a check on the two laptops to see if the 4244's are there and if they are I'll let 'em be and then see what happens after the new replacement, I'll let you know how it goes.
-
You're welcome, did you use the elevated versions of both CMD and PS?
If you mean "Run As Admin" I did on the PS but not on the CMD.
I found the update in the registry under: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\CatalogsToUninstall.
-
" CatalogsToUninstall."...............Im missing this key !
Something wrong about this ?