Cumulative Update KB4483234 Windows 10 v1803 Build 17134.472 - Dec. 19 Win Update

December 19, 2018 - KB4483234 (OS Build 17134.472)

Applies to: Windows 10 version 1803

---

Note
Because of minimal operations during the holidays and upcoming Western new year, there won’t be any preview releases for the month of December 2018. Monthly servicing will resume with the January 2019 security releases.

Improvements and fixes

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Security update to Internet Explorer.

If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.

For more information about the resolved security vulnerability, please refer to the Security Update Guide.

Known issues in this update

Symptom	Workaround
After you install the August Preview of Quality Rollup or September 11, 2018 .NET Framework update, instantiation of SqlConnection can throw an exception. For more information about this issue, see the following article in the Microsoft Knowledge Base: 4470809 SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.	Microsoft is working on a resolution and will provide an update in an upcoming release.
After installing this update, some users cannot pin a web link on the Start menu or the taskbar.	Microsoft is working on a resolution and will provide an update in an upcoming release.
After installing KB4467682, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the Group Policy “Minimum Password Length” is configured with greater than 14 characters.	Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters. Microsoft is working on a resolution and will provide an update in an upcoming release.

How to get this update

Deployment Notes
For customers using Windows Update offline scan file, Wsusscn2.cab, no new December scan cab will be issued. You will need to download the December 2018 WSUS scan cab and then manually download this KB from Microsoft Update Catalog to deploy. An updated scan file that includes this KB will be available in the next security release in January 2019.
A Delta package for this update will not be available. Customers using Delta package updates need to apply the Full Update. Customers who do not apply the Full update, and only the December Delta package update from December 11, 2018 will experience an update failure when installing the January Delta Update. The January Full update will install correctly.

Before installing this update

Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest cumulative update (LCU). SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU and applying Microsoft security fixes. For more information, see Servicing stack updates.

If you are using Windows Update, the latest SSU (KB4477137) will be offered to you automatically. To get the stand-alone package for the latest SSU, go to the Microsoft Update Catalog.

Install this update

This update will be downloaded and installed automatically from Windows Update.

To get the stand-alone package for this update, go to the Microsoft Update Catalog website.

File information

For a list of the files that are provided in this update, download the file information for cumulative update 4483234.

Source: https://support.microsoft.com/en-us/help/4483234


Direct download links for KB4483234 MSU file from Microsoft Update Catalog:

Download KB4483234 MSU for Windows 10 v1803 32-bit (x86) - 446.5 MB

Download KB4483234 MSU for Windows 10 v1803 64-bit (x64) - 798.6 MB

   Tip

How to Find Windows 10 Version Number

How to Find Windows 10 Build Number

Downloaded installed and working ok

Dirk Gently said:

An 800MB update to fix a problem with Internet Exploder? WTF?

No thanks.

jamis said:

I find it ironic that Google found the exploit and vulnerability and notified MS about it.

More and more, find myself asking how did I get into this "Windows" operation trap?
The only operating system I knew was Windows. So, I should be a "loyal" Windows fan. Sadly I am not.
I am at the breaking point threshold about this never-ending-updates fiasco.
Why would any "normal" home user be burdened with this ?
Business people, maybe.
Home users, why bother ?