Replies

@Anonymous 10:40 a.m. and 11.33.

I noticed that too on a family member’s computer who also isn’t getting the update. It appeared to change itself after fetching a Windows Defender update, but it’s hard to believe that would have anything to do with it. Do you run Windows Defender or have a 3rd party AV?

anonymous wrote:

I only know that, in the past, that WaaSAssessment “CURRENT” value has always been consistent with the currently installed Windows 10 build. In this case, however, it seems to have got pushed ahead of the actual update installation on some machines somehow. One wonders if that value might then be read by “Check for Updates” resulting in no subsequent offer of the update that it “thinks” has been installed already. But obviously at this point I’m just guessing. — Arvy

I suspect this is the exactly the case. I decided to bite the bullet and download & install the update from the catalogue. It installed quickly & smoothly and all seems well. *exhales*

I had a play with my father’s laptop earlier to see if I could get to the bottom of it. He hadn’t turned the computer on in a few days. I noticed the registry key “CURRENT” changed from .286 (the correct number) to .319 after Windows Defender updated (ONLY WD, no others) but surely that can’t be the cuplrit? Though I do find it interesting that the only computer I had trouble with of the three Win 10 laptops I own, was the one running Windows Defender. All others have Avast and Windows Defender completely turned off (i.e. no periodic limited scanning). Anyway Dad’s laptop couldn’t find the update either, so I installed from the catalogue on his too.

Woah, the plot thickens. I definitely cannot explain or make sense of that, but I’ve just checked my Win 10 Pro machine that is refusing to fetch this update, and my registry entry is the same as your’s. The key “CURRENT” key says 10.17134.319, and the other two you mention also say .285.

I’ve just compared it with one of my Win 10 Home machines that did get the update and CURRENT is .319 and the other two are also .285.

I do see a difference in the the key above CURRENT though. In the NON-updated machine 10.0.17134.SB is 10.0.17134.165, and on the updated machine it is 10.0.17134.1. I haven’t looked for other differences, but I too am thoroughly perplexed why my current version is showing as .319 in the registry when I have not received the update, and in my Settings app under System > About > it shows 17134.286!

Can anyone shed some light on the availability of any of yesterday’s patches, based on:

Sure! I manually checked for and received updates on my two Win 10 Home machines yesterday (at 5.30am & 10.30am NZ time), but I am not receiving KB 4458469 on my third laptop, and have been trying since 4pm yesterday (it is now 5pm the next day).

Details of the problematic machine: Win 10 Pro 1803. 17134.286, SAC (T), and I have been checking manually MANY times over last 25hrs. I have the required SSU installed (4456655), updates are not paused or deferred, and the machine is fully up-to-date otherwise. The software set-up is the same on all 3 computers, the only difference being I have a 3rd party AV on the two that updated, and just Windows Defender on the Pro machine. I have not enabled the option in “Delivery Optimisation” (in the advanced WU options) to allow updates from other machines (local or otherwise).

I suspect they have pulled it…. I’m not keen to download the standalone installer in case there’s a valid reason I’m not being offered it.

EDIT html to text – content may not appear as intended