Cumulative Update KB4516077 Windows 10 v1809 Build 17763.774 - Sept.24 Win Update

    Cumulative Update KB4516077 Windows 10 v1809 Build 17763.774 - Sept.24

    Cumulative Update KB4516077 Windows 10 v1809 Build 17763.774 - Sept.24

    Category: Win Update
    Last Updated: 01 Oct 2019 at 17:16

    September 24, 2019 - KB4516077 (OS Build 17763.774)

    Applies to: Windows 10 version 1809, Windows Server version 1809, Windows Server 2019 all versions

    Note Follow @WindowsUpdate to find out when new content is published to the release information dashboard.

    Starting with update KB4497934, we are introducing functionality that allows you to decide when to install a feature update. You control when you get a feature update while simultaneously keeping your devices up to date. Feature updates that are available for eligible devices will appear in a separate module on the Windows Update page (Settings > Update & Security > Windows Update). If you would like to get an available update right away, select Download and install now. To find out more about this feature, please go to this blog.
    When Windows 10 devices are at, or within several months of reaching, end of service, Windows Update will begin to automatically initiate a feature update. This keeps those devices supported and receiving the monthly updates that are critical to device security and ecosystem health.


    ePub support ending in Microsoft Edge
    Microsoft Edge will end support for e-books that use the .epub file extension over the next several months. For more information, see Download an ePub app to keep reading e-books.


    For more information about the various types of Windows updates, such as critical, security, driver, service packs, and so on, please see the following article.

    Highlights

    • Allows Microsoft Edge to print PDF documents that contain landscape and portrait-oriented pages together correctly.
    • Updates an issue that doesn't provide a cursor when you select a text input box using touch.
    • Updates an issue that prevents some minimized windows from being restored, closed, or maximized.
    • Updates an issue that prevents the Save and Save As options in Microsoft Office 2010 applications from working when high contrast mode is on.
    • Updates an issue with incorrect folder and file properties in File Explorer.
    • Updates an issue that causes vertical fonts to be larger when printing to a PostScript printer.
    • Updates an issue that prevents Microsoft Narrator from opening.
    • Updates an issue that occasionally prevents you from changing the display brightness after resuming from Sleep or Hibernation when using certain graphics drivers.
    • Updates an issue that causes icons in message box dialogs to appear too large when you choose scaling options in Display settings.
    • Updates an issue that may cause the Calculator app to close unexpectedly if you select any available Converter option.
    • Updates an issue that causes excessive CPU usage when you switch applications or hover over the Taskbar.
    • Updates an issue that causes a dim display after waking from Sleep.

    Improvements and fixes

    This non-security update includes quality improvements. Key changes include:

    • Addresses an issue that prevents the discovery of remote systems associated with a user from working properly.
    • Addresses an issue that prevents Microsoft Narrator from opening when the User Account Controls setting is disabled on the Standard User account.
    • Addresses an issue to enable Microsoft Edge to print PDF documents that contain landscape and portrait-oriented pages correctly.
    • Addresses an issue that occasionally prevents users from changing the display brightness after resuming from Sleep or Hibernation when using certain graphics drivers.
    • Addresses an issue with MSCTF.dll that causes an application to stop working.
    • Addresses an issue that prevents some minimized windows from interacting, and you cannot restore, close, or maximize them when a system is running with a custom shell.
    • Addresses an issue that fails to provide a cursor when you select a text input element using touch.
    • Addresses an issue that causes icons in message box dialogs to appear too large when you choose scaling options in Display settings. For more information, see Using Dialog Boxes and Display Scaling in Windows 10.
    • Addresses an issue that prevents the Save and Save As options in Microsoft Office 2010 applications from working when high contrast mode is on.
    • Addresses an issue that causes File Explorer to report the number or the size of files and folders incorrectly when they use long paths.
    • Addresses an issue that causes unnecessary restart requests on servers.
    • Addresses an issue with diagnostic data processing during the Windows Out of Box Experience (OOBE) sequence.
    • Configures Windows 10 Enterprise for Virtual Desktops (EVD) editions in Azure Active Directory (Azure AD) licensing mode by default. Users who connect to EVD editions must have an EVD license.
    • Addresses an issue that prevents an App-V application from opening and displays a network failure error. This issue occurs under certain circumstances, such as when a system's battery is low or there is an unexpected power failure.
    • Addresses an issue that prevents a web browser from connecting securely to Windows Server. This occurs when using a client authentication certificate, such as a SHA512-based certificate, and the web browser does not support a signature algorithm that matches the certificate.
    • Addresses an issue that may cause the Local Security Authority Subsystem Service (LSASS) to stop working with an “0xc0000005” error.
    • Addresses an issue that prevents the BitLocker recovery key from being successfully backed up to Azure Active Directory.
    • Addresses an issue that leads to excessive memory utilization in Microsoft Defender Advanced Threat Protection (ATP).
    • Addresses a possible compatibility issue when Microsoft Defender Advanced Threat Protection (ATP) accesses case-sensitive Server Message Block (SMB) shares.
    • Addresses a rare issue that occurs when the mssecflt.sys driver takes too much space on the kernel stack. This results in the error, "STOP 0x7F: UNEXPECTED_KERNEL_MODE_TRAP", and Parameter 1 is set to “EXCEPTION_DOUBLE_FAULT.”
    • Improves the detection accuracy of Microsoft Defender ATP Threat & Vulnerability Management.
    • Addresses an issue that gives a Windows Hello for Business user two certificates for authentication during certificate renewal instead of one certificate.
    • Addresses an issue that causes the lsass.exe service to stop working, which causes the system to shut down. This occurs when migrating Data Protection API (DPAPI) credentials using dpapimig.exe with the -domain option.
    • Addresses an issue that may cause Direct Access servers to use a large amount of non-paged pool memory (pooltag: NDnd).
    • Addresses an issue that causes vertical fonts to be larger when printing to a PostScript printer.
    • Addresses an issue that prevents Windows from sending a shutdown notification to a Non-Volatile Memory Express (NVMe) drive when the driver unloads using Disable Device in Device Manager.
    • Addresses an issue that prevents you from running the Active Directory Diagnostics Data Collector Set from the Performance Monitor for Domain Controllers. This causes the Data Collector Set name to appear empty. Running the Active Directory Diagnostics Data Collector Set returns the error, “The system cannot find the file specified.” Event ID 1023 is logged with the source as Perflib and the following messages:
      • “Windows cannot load the extensible counter DLL “C:\Windows\system32\ntdsperf.dll.”
      • “The specified module could not be found.”

    • Addresses an issue in GetFinalPathNameByHandleW() that prevents Favorites from opening in Internet Explorer 11. This occurs when Favorites are redirected and offline in a client-side caching scenario with enhanced protected mode compatibility (EPM) enabled.
    • Addresses an issue in which the product description of Windows Server 2019 was incorrect when queried using slmgr /dlv.
    • Addresses an issue that may cause authentication to fail for certificate-based authentication when the certificate authentication includes a cname as part of the pre-authentication request.
    • Addresses a Lightweight Directory Access Protocol (LDAP) runtime issue for Domain Controller Locator-style LDAP requests. The error is, “Error retrieving RootDSE attributes, data 8, v4563.”
    • Addresses an issue that causes LDAP queries that contain LDAP_MATCHING_RULE_IN_CHAIN (memberof:1.2.840.113556.1.4.1941) to intermittently fail on Windows Server 2019 domain controllers. However, these queries do not fail on domain controllers running previous versions of Windows Server.
    • Addresses an issue that causes group membership changes in Active Directory groups to fail. This occurs if the Lightweight Directory Access Protocol (LDAP) client uses the Security Identifier (SID) Distinguished Name (DN) syntax after installing previous versions of NTDSAI.DLL. In this scenario, an issue with the LdapPermissiveModify (LDAP_SERVER_PERMISSIVE_MODIFY_OID) control causes Active Directory to incorrectly return a “SUCCESS” status even though the group membership change did not occur.
    • Addresses an issue in which the Set-AdfsSslCertificate script is successful. However, it throws an exception during resource cleanup because the target server-side endpoint is no longer there.
    • Addresses an issue that causes File Explorer to show a regular file icon for files marked with FILE_ATTRIBUTE_OFFLINE instead of the expected placeholder icon.
    • Addresses an issue that may cause the Calculator app to close unexpectedly if you select any available Converter option.
    • Addresses an issue that causes excessive central processing unit (CPU) usage when users switch applications or hover over the Taskbar.
    • Addresses an issue with applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent. They 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 solution also resolves this issue for all the updates on or before June 18, 2019.
    • Addresses an issue with the Origin request header behavior in Internet Explorer when you make cross-origin resource sharing (CORS) requests that use redirected resources in internal subnets.
    • Addresses an issue that causes the display’s maximum brightness to appear as 50% or less after completing the out-of-box experience (OOBE) and then waking from Sleep.
    • Allows auditing of security events for clients managed by mobile device management (MDM) for security monitoring and incident response activities.
    • Addresses an issue that prevents Microsoft App-V from handling a parameter of the CreateProcess API properly, which prevents the virtual process from opening.
    • [ADDED 10/1] Addresses an issue that causes a device to stop working when opening files from a network drive that has client-side caching enabled. This issue may occur when the device has certain third-party antivirus products installed and the drive is backed by a server that is not a Microsoft Server Message Block (SMB) server. The error code is, “0x27 RDR_FILE_SYSTEM.”
    • [ADDED 10/1] Addresses an issue that may cause a Hyper-V virtual machine and a Hyper-V host to lose network connectivity because of an inconsistency in the media access control (MAC) address learning process. As a result, the Hyper-V virtual switch drops packets.

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

    Windows Update Improvements
    Microsoft has released an update directly to the Windows Update client to improve reliability. Any device running Windows 10 configured to receive updates automatically from Windows Update, including Enterprise and Pro editions, will be offered the latest Windows 10 feature update based on device compatibility and Windows Update for Business deferral policy. This doesn't apply to long-term servicing editions.


    Known issues in this update

    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."
    1. Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10.
    2. 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:

    1. Go to the Settings app > Recovery.
    2. Select Get Started under the Reset this PC recovery option.
    3. 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.
    After installing this update, Windows Mixed Reality Portal users may intermittently receive a “15-5” error code. In some cases, Windows Mixed Reality Portal may report that the headset is sleeping and pressing “Wake up” may appear to produce no action. To mitigate the issue, use the following steps:

    1. Close the Windows Mixed Reality Portal, if it is running.
    2. Open Task Manager by selecting the Start button and typing “task manager”.
    3. In Task Manager, under the Processes tab, right-click Windows Explorer and select Restart.
    4. Open the Windows Mixed Reality Portal.

    We are working on a resolution and will provide an update in an upcoming release.
    Some Input Method Editor (IME) may become unresponsive or may have high CPU usage. Affected IMEs include Chinese Simplified (ChsIME.EXE) and Chinese Traditional (ChtIME.EXE) with Changjie/Quick keyboard. Due to security related changes in this update, this issue may occur when the Touch Keyboard and Handwriting Panel Service is not configured to its default startup type of Manual. To resolve the issue, perform the following steps:

    1. Select the Start button and type “services”.
    2. Open the Services app and locate Touch Keyboard and Handwriting Panel Service.
    3. Double-click Touch Keyboard and Handwriting Panel Service and select Properties.
    4. Locate Startup type: and change it to Manual.
    5. Select OK.

    The TabletInputService service is now in the default configuration and IME should work as expected.

    How to get this update

    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. For more information, see Servicing stack updates.

    If you are using Windows Update, the latest SSU (KB4512577) will be offered to you automatically. To get the standalone package for the latest SSU, search for it in the Microsoft Update Catalog.

    Install this update

    Release Channel Available Next Step
    Windows Update or Microsoft Update Yes Go to Settings > Update & Security > Windows Update and select Check for updates.
    Microsoft Update Catalog Yes To get the standalone package for this update, go to the Microsoft Update Catalog website.
    Windows Server Update Services (WSUS) No You can import this update into WSUS manually. See the Microsoft Update Catalog for instructions.

    File information

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


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


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

    Download KB4516077 MSU for Windows 10 v1809 32-bit (x86) - 126.0 MB

    Download KB4516077 MSU for Windows 10 v1809 64-bit (x64) - 271.5 MB

    Download KB4516077 MSU for Windows 10 v1809 ARM64 - 297.5 MB

    How to Find Windows 10 Version Number

    How to Find Windows 10 Build Number

    Known issues and notifications for Windows 10 version 1809 and Windows Server 2019 - Windows Release Information | Microsoft Docs

    Resolved issues for Windows 10 version 1809 and Windows Server 2019 - Windows Release Information | Microsoft Docs

    Brink's Avatar Posted By: Brink
    24 Sep 2019


  1. Posts : 2,557
    Windows 10 pro x64-bit
       #1

    My, my... It seems that I am the only one still on 1809 on my production machine. It also seems that my almost flawless period using this build is over, because after installing this update, MS Edge couldn't be launched, which was one of the main reasons why I rolled back from 1903 to 1809.

    The update installed OK, but I had to use MS Edge Chromium Beta to reach tenforums. Normally, MS Edge stable version is my default browser.

    Cumulative Update KB4516077 Windows 10 v1809 Build 17763.774 - Sept.24-winver-after-installing-kb4516077.png

    This is something of a big mystery to me. Why on earth every time an update is installed, it has to break something else?. Definitely MS has to do a better job than that. I don't even know yet what else is broken. I might as well advance to 1903 since I am not to roll back to 1803.

    - - - Updated - - -

    Now I understand why I cannot launch Edge, it is because this folder "Microsoft.MicrosoftEdge_8wekyb3d8bbwe" is missing from the following path: C:\Users\%username%\AppData\Local\Packages. How can that be, it was there before the update. BTW, Repair & Reset cannot fix the issue. Tx MS!
      My Computers


  2. Posts : 509
    Windows10 Home 64 bit v. 21H1 bld. 19043.1620
       #2

    I hold my breath every time a CU comes up for installation. I do a lot more System Saves this year than previous years. Will run another one tonight since this CU hit today. Fortunately, I don't run Edge Anything, so I haven't been hit with IronZorge's issue. MS was complaining about CCleaner tying up their resouces, guess they need them for update problem determination.
      My Computer


  3. Posts : 2,557
    Windows 10 pro x64-bit
       #3

    jamis said:
    I hold my breath every time a CU comes up for installation. I do a lot more System Saves this year than previous years. Will run another one tonight since this CU hit today. Fortunately, I don't run Edge Anything, so I haven't been hit with IronZorge's issue. MS was complaining about CCleaner tying up their resouces, guess they need them for update problem determination.
    I really don't know what to make of it. Even using @Brink's tutorial to Reinstall and re-register Microsoft Edge doesn't help. That is really what always rubs me the wrong way with MS, the fact of not being able to fix something that was working fine before installing an update. BTW, I don't use CCleaner anymore after the debacle once it has become Avast's proprietary tool.

    It is like I have to accept and use Edge Chromium Beta, which in all likelihood, would soon be the stable version.
      My Computers


  4. Posts : 61,837
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #4

    IronZorg89 said:
    I really don't know what to make of it. Even using @Brink's tutorial to Reinstall and re-register Microsoft Edge doesn't help. That is really what always rubs me the wrong way with MS, the fact of not being able to fix something that was working fine before installing an update. BTW, I don't use CCleaner anymore after the debacle once it has become Avast's proprietary tool.

    It is like I have to accept and use Edge Chromium Beta, which in all likelihood, would soon be the stable version.

    Hey mate,

    Did you also try to reset the "Microsoft Edge" app?

    Reset App in Windows 10
      My Computers


  5. Posts : 2,557
    Windows 10 pro x64-bit
       #5

    Brink said:
    Hey mate,

    Did you also try to reset the "Microsoft Edge" app?

    Reset App in Windows 10
    Tx Shawn, I am going to try and post back...

    EDIT: Just realize I have done that already as mentioned in post #1 and it didn't work. Same thing for "Repair". I think the root cause of the problem is the missing folder mentioned in the edit part of the same post (#1). Nothing to do with your tutorial.

    - - - Updated - - -

    This is what I get using the command-line for "All users":

    PS C:\WINDOWS\system32> Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml” -Verbose}VERBOSE: Performing the operation "Register package" on target "C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AppXManifest.xml".Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF6, Package could not be registered.error 0x80070050: Windows cannot register the package because of an internal error or low memory.NOTE: For additional information, look for [ActivityId] abc6dc4f-73dc-0001-0c30-c7abdc73d501 in the Event Log or use the command line Get-AppPackageLog -ActivityID abc6dc4f-73dc-0001-0c30-c7abdc73d501At line:1 char:68+ ... | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.I ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : WriteError: (C:\Windows\Syst...ppXManifest.xml:String) [Add-AppxPackage], IOException + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand VERBOSE: Operation completed for: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AppXManifest.xmlVERBOSE: Performing the operation "Register package" on target "C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AppXManifest.xml".Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF6, Package could not be registered.error 0x80070050: Windows cannot register the package because of an internal error or low memory.NOTE: For additional information, look for [ActivityId] abc6dc4f-73dc-0001-3130-c7abdc73d501 in the Event Log or use the command line Get-AppPackageLog -ActivityID abc6dc4f-73dc-0001-3130-c7abdc73d501At line:1 char:68+ ... | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.I ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : WriteError: (C:\Windows\Syst...ppXManifest.xml:String) [Add-AppxPackage], IOException + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand VERBOSE: Operation completed for: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AppXManifest.xml
    The one for single user didn't run at all:

    Cumulative Update KB4516077 Windows 10 v1809 Build 17763.774 - Sept.24-ps-single-user-account-only.png

    EDIT: A better representation of the screenshot in "quote" above:
    Cumulative Update KB4516077 Windows 10 v1809 Build 17763.774 - Sept.24-ps-all-users.png
      My Computers


  6. Posts : 61,837
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #6

    UPDATE 10/1:

    New items added to Improvements and Fixes. See first post for more details.
      My Computers


  7. Posts : 2,557
    Windows 10 pro x64-bit
       #7

    BTW, Regarding my issue in post # 5, I uninstalled the update and Micorsoft Edge is back to working normally again. After that, I paused Updates in Update & Security settings for both CUs & FUs. I will think of what to do once 19H2 is officially out for the general public. All I can say is that those MS's bugs are causing me a lot of downtime.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:20.
Find Us




Windows 10 Forums