KB2267602 Windows Defender Update -- Is installing never > 0% Normal

Is it normal for KB2267602 Windows Defender Update to never show more than 0% installed?
Never see more than 0% or any confirmation that install completed.

Do others see it just sit at 0% and then acts like its done -- where you can click to check for updates again?
I see % increase for other updates, but KB2267602 updates never other than 0%.

Hi g33, Welcome to 10F!

You'll see different kinds of behavior, but that's normal. I had one this morning when I took a look at updates, it went from pending D/L to D/Ling, then pending install, to installing, to what you saw, installing - 0%, then Done an it disappeared, rechecked for updates and finally finished telling me I'm up-to-date.

All my progress indicators showed 0%

• If you want or need to check the updates installed refer to this tutorial: Update Security Intelligence Definition for Windows Defender Antivirus It'll show you how to get to updates and when there click on View update history.

• To find Defender's versions see; Find Windows Defender Antivirus Version in Windows 10

g33 said:

Do others see it just sit at 0% and then acts like its done -- where you can click to check for updates again?
I see % increase for other updates, but KB2267602 updates never other than 0%.

Let's see... I see it, and if there's one there's others.

Usually the WDU (Windows Defender Update) is in a 2,3,5,7MB range where a CU (cumulative update) or a FU (feature update) may start in that range of sizes, but they normally start at 250MB and can go as high as 600MB to 700_800MB? and more. So...

The WDU doesn't take as long as the CU or FU to D/L. And my best guess would be that the algorithm Microsoft designed to keep track of the percentage gain just can't keep up with the quickness of a smaller D/L and install, and, need to back it down. But, that's my theory and Microsoft is keeping mum on the subject, you know how close they keep their cards to their chest...
The reason the 1909FU went so well is it was small and only acted as a switch for the 1903FU to turn the part of its update and morph into 1909.

Bare with me here; I'm taking literary license with those D/L figures, they can vary a lot. Microsoft Update Catalog

g33 said:

where you can click to check for updates again?

I have disabled auto-updates and been using the following VBScript command to update Windows Defender automatically at six-hour intervals.

Createobject("wscript.shell").Run("""%ProgramFiles%\Windows Defender\MpCmdRun.exe"" ""-SignatureUpdate"""), 0

g33 said:

Never see more than 0% or any confirmation that install completed.

Perhaps the following CMD command will show something else.

"%ProgramFiles%\Windows Defender\MpCmdRun.exe" "-SignatureUpdate"

g33 said:

Never see more than 0% or any confirmation that install completed.

See below:

Wow, that's quick! Don't, blink.

But hey! Matt! Your method looks to be if one needs to install security updates from the catalog or at the least a check for security updates, which are in the WUCatalog? Was there a time stamp for the CMD? Start? - Finish?

Can you explain?

If the original poster (OP) Is okay with letting microsoft run the updating, that's okay with me. He was just curious about the progress indicator and how it works, we all know that windows update is notorious for bad readings. I remember earlier OS versions that were as or just as bad with accurate readings and I still believe the indicator works best with larger files, and even then it jumps around.

I think signature updates have nothing to do with https://www.catalog.update.microsoft.com/.

I stand corrected.

Anak said:

Was there a time stamp for the CMD? Start? - Finish?

Can you explain?

I cannot explain why there were no timestamps for "started" and "finished", as I am no CMD guru.