Cumulative Update KB4056892 Windows 10 v1709 Build 16299.192

Rocky · 04 Jan 2018

I decided to update manually. It took about 5 minutes total, quick and painless. No problems at all.

davidhk · 04 Jan 2018

davidhk said:

How about that.
One of my computers is getting it around 10:15 am EST.

Attachment 170851

OK, I am perplexed.

I have 4 computers, 2 tablets and 2 laptops. All of them run Windows Defender and no 3rd party AV.

Only the oldest (about 8 years old) laptop got the update from WU.
The rest are still waiting.

Well, an update and a casualty :

Yesterday, the 3rd, I used the Catalog site and manually installed 16299.192. It is a Surface 3 tablet. Still working. Thank god!
Today, the 4th, at around 10 am EST, the update showed up at my 8 yrs.+ Dell laptop. Installed without issue. Sill running perfectly. Phew!
At around 2 pm EST my 1 yr. old Acer received the update, installed and asked for restart. Restart broke the laptop. Screen stayed lit but blank. I tried but failed to go to Boot Order option (boot from DVD) for repair or image restore. Unresponsive to any key stroke. One down the drain.
Now at around 6pm my old Surface Pro1 got the update, installed and now in Restart mode. Pray and pray hard.

Adding....... Surface Pro1 is alive and kicking. 16299.192 installed.

miksi · 04 Jan 2018

Well, this is the end of the line for win10 updates on my really old notebook as after reboot I only have windows logo on black screen. No disk activity, nothing. I was able to repair win10 with F8 key pressed during reboot but new update always emerges and installs again so I deferred quality updates for some 20 days. Win10 is on the 16299.125.

Comp Cmndo · 04 Jan 2018

Rocky said:

I decided to update manually. It took about 5 minutes total, quick and painless. No problems at all.

Me, too.
If you never noticed, updating manually doesn't display exactly the same information in Settings---Update History.
It drops the "2018-01 ......" prefix.
It just says "Security Update for Windows (KB4056892)
I do notice a difference, the update history are all hot links which use a non-default browser, in my case Chrome.
Still doesn't let you copy & past the text on the screen.

Robersdog · 04 Jan 2018

Updated ok but lost Asus AI Suite3 on Z87 board and Razor Synapse took about 2 min to finally get going and now it will be interesting to see what happens on the old Asus P6T with i7-920

Bree · 04 Jan 2018

Well, I finally got my machines to see the update through Windows Update. For the 32-bit Pro system I had to run the Windows Update Troubleshooter before it would find and install it.

For the 64-bit Home system that wasn't sufficient. In the end I uninstalled the 2017-12 Cumulative update (16299.125). After the reboot a manual check in Windows Update found and installed the 2017-12 Cumulative Update again and only after rebooting from that would it find and install this one.

Interestingly, a clean install on my test machine showed the same pattern, the first check for updates found the 2017-12 CU and updated to 16299.125, only then could it find 2018-01 and update to 16299.192. There's something odd about this one.

bumboola · 04 Jan 2018

Finally came through WU after manually checking for updates several times since last night. Went quickly. Don't notice any difference in performance but I'm not a gamer nor do I run any resource intensive programs so I probably wouldn't notice that anyway. Registry key has been correct since last night so I'm not sure why it took so long, I've always gotten updates right away.

simrick · 04 Jan 2018

f14tomcat said:

That is precisely what my reg key reads, and nothing yet thru Windows Update.

Attachment 170774

Thanks TC for posting this.

I don't understand why everyone is running to the MS catalogue to download this and force-feed their systems, UNLESS, they have checked to make sure that the registry key does indeed exist on their rigs if they are using a 3rd-party AV. Otherwise, you could brick your computer. Last I checked, here is the spreadsheet of the AVs and whether they have (or will) complied.
CVE-2017-5753, CVE-2017-5715, and CVE-2017-5754 (Meltdown and Spectre) Windows antivirus patch compatibility

I checked and the key does exist on this main rig of mine, and the update came through WU.

EDIT: Okay, now that I've had a chance to read through the whole thread, I see at about page 10, people started mentioning the AV + reg key...hope no one borked their systems by jumping the gun on this one.

AMDMan2016 · 04 Jan 2018

Well with Avast installed on the systems, Windows updates was showing Machine was up to date, so I was like well reg key exists, I checked that first, then downloaded the update manually, and updated, and running fine since, Laptop I removed Avast completely, let Defender activate then got the update via Windows update, Mom's AMD based system left alone so far.

Clint · 04 Jan 2018

My laptop is a brick now. It won't even boot after restart.