It also didn't show on wumt to me. Then forcing a check for updates under settings started to download it.
KB4051963 has been a nightmare in one of my systems. It installs fine via settings>WU (doesn't show under wumt), and everything is ok. But the problem happens when I either run Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase, use system cleanup to remove windows update files, or let the pc run it's schedule maintenance (that probably does Dism.exe /online /Cleanup-Image /StartComponentCleanup). Then Windows won' be able to boot anymore and throws a Inacessible boot device BSOD. I've found no way to solve it other than using system restore to revert to before the update. I'll try updating with the ss + cu .msu instead, to see if it turns out different. Update: It does. While installing it doesn't use that % progression in the blue logo screen, it's like older WU updates. Then after the installation, I can do a dism cleanup or run the maintenance taks, and it doesn't cause boot problems. Donno, there might be something in this hardware setup that doesn't like UUP. This is on a very recent clean 1709 installation, btw.
Updates by WU were express downloads and now, at least the CU's, on 16299.15+ they are uup downloads. ps, it didn't happen on my laptablet, it is not signed in at the release preview ring.
Weird, in the old bios system I've had problems, after downloading on the 2th December (could only get it by forcing settings>windows update>check for updates, it wouldn't show on wumt or via UsoClient.exe StartScan) and installing the CU > pressing restart button, it went to ~17% then rebooted. After this the blue logo loading screen was different, showing a % message at the bottom of the screen, and when it reached 100% it rebooted my system again. Then windows started with .98 installed. After this point, any sort of procedure like Dism.exe /online /Cleanup-Image /StartComponentCleanup, or /ResetBase, run maintenance task or disk cleanup>windows update would leave me with "inaccessible boot device" BSOD on next boot. A uefi laptop went through the exact same procedure and caused no trouble. Had to do a system restore to before update, and applying this CU via SS+CU .msu caused no problems after the optimization above. It's installation was like the old CU's, until 30% right before manual reboot, and then the remaining 100% at next log on. On another old bios system that I've only updated yesterday, the update went completely different. It also didn't show on wumt or via usoclient startscan, but after forcing a check for updates via GUI it installed like CUs used to. After pressing the button to restart it installed until 30%, then it rebooted with the regular blue logo and spinning circle, and then at log on it completed until 100%. No problems after optimization. Was this last one a WU installation and the previous (that failed on a old system) via UUP?
I dont think its because old bios. but maybe true my bios date 2014 v2.1 (no update until now) but smbios 2.8. should be used as uefi not legacy in bios setting If using 1703 windows update shows after cek(bios setting uefi/legacy) automatically, but if hit force check update.. feature update to 1709 spamming in distribution updates.. where ss+cu to 1709.98. I think it also include dynamic update If using 1709 windows update dont shows(bios setting uefi/legacy) must manual update...because dont show, check with wumpt and other tool(whd show) I've read abbodi1406 in previous post, I'm forget where the post.. in 1709 windows update different like other windows
Thanks. Guys, how can correctly reduce the size of C:\Windows\Installer? On W81 arm32 I have added new LP, all KB updates redownloaded and this folder tripled in size. I already removed formerly added LP, but the size of the folder has remained in the huge state.