Cumulative Update KB4511553 Windows 10 v1809 Build 17763.678 - Aug. 13 Win Update

IronZorg89 · 14 Aug 2019

Just finished installing it on my production machine and everything seems to be working fine so far:

Cumulative Update KB4511553 Windows 10 v1809 Build 17763.678 - Aug. 13-winver-after-installing-kb4511553.png

jamis · 14 Aug 2019

My system auto updated with this CUM last night. No issues.

johnpd · 14 Aug 2019

One strange thing I noticed is that the list of Installed Updates in "Control Panel" > "Programs and Features" was messed up. The list did not show the normal columns. It showed only "Name", "Date Modified", "Type", and "Size" which are the normal columns for File Explorer. It also lost the update categories. I was able to restore the normal columns but not sure about how to get the categories although I would rather be without them anyway.

JohnD

babyblue · 14 Aug 2019

johnpd said:

not sure about how to get the categories

Try right-clicking on that page and selecting "Group by" and then "Program"

johnpd · 15 Aug 2019

babyblue said:

Try right-clicking on that page and selecting "Group by" and then "Program"

Thanks, that worked. I don't know how everything got reset.
JohnD

Brink · 15 Aug 2019

UPDATE 8/14:

New known issue added. See first post for more details.

Brink · 16 Aug 2019

UPDATE 8/16:

Known issues updated. See first post for more details.

rseiler · 17 Aug 2019

17763.720 just came out. It's a "non-security" update, though notable for fixing the VB issue introduced in 17763.678, among a slew of other things. It is not installed automatically, you have to seek it.

If someone skipped (or uninstalled) .678 and went right to .720, despite it being a higher version number, is the higher build in this instance in fact cumulative? That is, the "non-security" .720 update would include what was in .678? I always thought that it does include it, despite being called "non-security." Likewise, next month's Patch Tuesday "security" update includes this month's "non-security" update--it just doesn't say that it does.

But I'm no longer sure.

If non-security updates really do include the latest security updates, then it would avoid a weird situation where a cautious person, who usually waits a week or two before diving in, could in effect be bypassing "security" updates on a regular basis by only installing non-security updates.

Bree · 17 Aug 2019

rseiler said:

17763.720 just came out....

A Saturday is an unusual day for one of these....

It's a "non-security" update, though notable for fixing the VB issue introduced in 17763.678, among a slew of other things. It is not installed automatically, you have to seek it.

Here: https://support.microsoft.com/help/4512534

...is the higher build in this instance in fact cumulative? That is, the "non-security" .720 update would include what was in .678? I always thought that it does include it, despite being called "non-security."

Yes, in the case of these C/D updates "non-securty" means no new security updates. It will include all previous security fixes.

...updates are published on the second Tuesday of each month, known as the “B” release (“B” refers to the second week in the month), and are the only regular monthly releases that include both new security fixes and previously released security and non-security fixes.

Windows 10 monthly security and quality updates overview

Symptom	Workaround
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.	Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."	Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note: If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.	To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally. We are working on a resolution and will provide an update in an upcoming release.
Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM) may fail to start with the error "Status: 0xc0000001, Info: A required device isn't connected or can't be accessed" after installing this update on a WDS server.	For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data, often 50 or 100 entries. When requesting additional pages you may receive the error, “1359: an internal error occurred.” This issue occurs in this update and in all the updates before June 18, 2019.	We are working on a resolution and will provide an update in an upcoming release.
[UPDATED 8/17] After installing this update, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an "invalid procedure call error."	This issue is resolved in KB4512534, which is an optional update. It is available on the following release channels: Microsoft Update Catalog. Windows Update. Microsoft Update. Windows Server Update Services (WSUS). As with any optional update, you will need to Check for updates to receive and install KB4512534. For instructions, see Update Windows 10. Note Windows Update for Business customers should apply the update using the Microsoft Update Catalog or Windows Server Update Services (WSUS).

Release Channel	Available	Next Step
Windows Update and Microsoft Update	Yes	None. This update will be downloaded and installed automatically from Windows Update.
Microsoft Update Catalog	Yes	To get the standalone package for this update, go to the Microsoft Update Catalog.
Windows Server Update Services (WSUS)	Yes	This update will automatically synchronize with WSUS if you configure Products and Classifications as follows: Product: Windows 10 Classification: Security Updates