Jump to content

Microsoft release new Cumulative Update for Windows 10 October 2018 Update (changelog)


The AchieVer

Recommended Posts

The AchieVer

Microsoft release new Cumulative Update for Windows 10 October 2018 Update (changelog)

Microsoft has released a new Cumulative Update for Windows 10 189, taking the OS to build 17763.475.

 

KB4495667 is an optional update being tested on seekers, and should be part of Patch Tuesday next week if there are no issues.

The update contains the following fixes and improvements:

 

 

  • Allows the built-in Administrator account to run Microsoft Office setup after downloading the installer in Microsoft Edge.
  • Addresses an issue that causes Internet Explorer Automation to fail in certain instances.
  • Addresses an issue that may prevent Custom URI Schemes for Application Protocol handlers from starting the corresponding application for local intranet and trusted sites on Internet Explorer.
  • Addresses an issue that prevents certain apps from launching when you set folder redirection for the Roaming AppData folder to a network path.
  • Addresses an issue in Gdi32full.dll that causes an application to stop responding.
  • Addresses an issue that may cause the UI to stop responding for several seconds when scrolling in windows that have many child windows.
  • Addresses an issue that may cause a touch screen to stop working after restart.
  • Enables a touch keyboard to support new Japanese Era characters. For more information, see KB4469068.
  • Addresses an issue that causes ShellExperienceHost.exe to stop working when the start date for the Japanese Era is not on the first day of the month. For more information, see KB4469068.
  • Addresses an issue that prevents the CALDATETIME structure from handling more than four Japanese Eras. For more information, see KB4469068.
  • Updates the NLS registry to support the new Japanese Era. For more information, see KB4469068.
  • Addresses an issue that causes the DateTimePicker to display the date incorrectly in the Japanese date format. For more information, see KB4469068.
  • Addresses an issue that causes the Date and Time Settings control to cache old Eras and prevents the control from refreshing when the time enters the new Japanese Era. For more information, see KB4469068.
  • Updates fonts to support the new Japanese Era. For more information, see KB4469068.
  • Addresses an issue that prevents an input method editor (IME) from supporting the new Japanese Era character. For more information, see KB4469068.
  • Addresses an issue that causes the Clock and Calendar flyout control to display the day of the week incorrectly mapped to a date in the month of the new Japanese Era. For more information, see KB4469068.
  • Adds alternative fonts for the new Japanese Era fonts. For more information, see KB4469068.
  • Enables Text-To-Speech (TTS) functionality to support new Japanese Era characters. For more information, see KB4469068.
  • Allows existing devices that are managed by Configuration Manager to be enrolled in Microsoft Intune using Co-management without any user interaction. It does not require an active user to be logged in, and there are no Multi Factor Authentication (MFA) prompts. This update also allows the Co-managed mobile device management (MDM) enrollment to use the device credential it received when the device is enabled to join Hybrid Azure Active Directory (AADJ).
  • Improves access to detailed troubleshooting and diagnostic logs from managed devices, such as business PCs, when using a PC cloud management service. PC cloud management services include Microsoft Intune or other Mobile Device Management (MDM) providers for Windows.
  • Addresses an issue that may allow a user to continue logging on to an account using a smart card after disabling the account.
  • Addresses an issue that prevents access to enterprise resources when using Kerberos with Windows Hello for Business (WHfB) credentials. This causes users to receive multiple prompts to provide their credentials.
  • Addresses an issue that occasionally causes a PostScript printer to use the wrong font.
  • Addresses an issue that causes Lightweight Directory Access Protocol (LDAP) client applications to stop responding for at least 30 seconds when many LDAP queries are requested through multiple connections. This occurs because of a race condition in wldap32.dll. You must install this update on the LDAP client that calls wldap32.dll.
  • Addresses an issue that causes a roaming profile user to lose customized Start menu settings after upgrading the operating system (OS). After installing this update, administrators must enable the UseProfilePathMinorExtensionVersion registry setting described in KB4493782 for roaming user profiles (RUP). This key allows you to create a new RUP for an upgraded OS and prevents the loss of a custom Start menu. The RUP must be stored locally, and you must restart the device to enable the feature.
  • Addresses an issue that causes connection requests to the Remote Desktop Session Host (RDSH) servers in the deployment to fail. This issue occurs because of a deadlock in the Connection Broker.
  • Addresses an issue that may prevent Cluster Aware Update from restarting nodes when a cluster’s credentials are reset. Cluster Aware Update must restart nodes after installing an update. The error is the following:”Failed to restart “NODENAME”: (ClusterUpdateException) Failed to restart “NODENAME”: (Win32Exception) The user name or password is incorrect.”
  • Addresses a gradual memory leak in LSASS.exe on systems that have cached logon enabled. This issue mainly affects servers that process many interactive logon requests, such as web servers.
  • Addresses an issue that may cause a Lightweight Directory Access Protocol (LDAP) query to return incorrect results. This occurs if a filter clause contains an attribute that has a syntax of Large Integer type and the filter uses the rule, LDAP_MATCHING_RULE_BIT_AND. For example, a simple filter, such as “msExchRoleAssignmentFlags:1.2.840.113556.1.4.803:=51539607552” may return no matches when it should.
  • Addresses an issue that prevents Print Workflow Applications from launching for Point and Print.
  • Addresses an issue that may prevent Universal Windows Platform (UWP) apps from receiving keyboard input when its user interface thread becomes too busy. This issue occurs when the UWP app has an embedded WebView control.

It also has the following known issues:

Symptom Workaround
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension. To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:

 

Option 1:
Open an Administrator Command prompt and type the following:

Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No

Option 2:
Use the Windows Deployment Services UI.

  1. Open Windows Deployment Services from Windows Administrative Tools.
  2. Expand Servers and right-click a WDS server.
  3. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.

Option 3:
Set the following registry value to 0:

“HKLM\System\CurrentControlSet \Services\WDSServer\ Providers\WDSTFTP\ EnableVariableWindowExtension”.

Restart the WDSServer service after disabling the Variable Window Extension.

Microsoft is working on a resolution and will provide an update in an upcoming release.

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.

Microsoft and ArcaBit have identified an issue on devices with ArcaBit antivirus software installed that may cause the system to become unresponsive upon restart after installing this update. Microsoft has temporarily blocked devices from receiving this update if ArcaBit antivirus software is installed.

 

ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.

Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) may fail after installing this update. Microsoft is working on a resolution and will provide an update in an upcoming release.
When attempting to print from Microsoft Edge or other Universal Windows Platform (UWP) applications you may receive the error, “Your printer has experienced an unexpected configuration problem. 0x80070007e.” You can use another browser, such as Internet Explorer to print your documents.

 

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.

 

The optional update can be installed by simply Checking for Updates on Settings or you can manually download it here.

 

 

Source

 

Link to comment
Share on other sites


  • Replies 4
  • Views 908
  • Created
  • Last Reply

Could somebody tell me: Is the latest Win10 1809 cumulative update, KB 4495667, forced or optional?

There’s a kind of unwritten rule that the first cumulative update each month gets pushed onto Win10 machines, and the second is an “optional” update — meaning you have to intentionally click on “Check for updates” (or download and install it) in order to get it going.

 

That’s considered acceptable behavior because the second updates are, traditionally, non-security updates. There’s no urgency in installing them. You only get bit if you’re a sucker, er, seeker and click Check for updates.

 

When the latest Win10 1809 cumulative update, KB 4495667, rolled out yesterday, it included the standard first-Tuesday admonition:

Install this update

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

I thought it was odd at the time, and fretted about warning people with an AskWoody Alert. Then shortly after the KB article appeared, @abbodi86 eased my fears and said it was for seekers only. I checked the KB article and it had been modified to say:

Install this update

To download and install this update, go to Settings > Update & Security > Windows Update and select Check for updates.

… which is the common “optional” non-security patch warning. That’s what the KB article says at the moment. Somebody slipped in a change to the KB article without mentioning it. Happens all the time. Since Google doesn’t cache KB articles, there was no way for me to verify the before-and-after contents.

 

But then Susan Bradley got hit.

 

 

The behavior Susan saw corresponds to the first version of the KB article, not the second version. Susan’s in California and doesn’t work with Japanese-era dating. Understand that this is the “second second” Win10 1809 cumulative update for April — it’s the latest patch for Win10 1809, not the stopgap issued on May 1, KB 4501835.

 

So which is it, Microsoft? Will the KB 4495667 patch get pushed onto Win10 1809 machines that aren’t actively blocking patches? Or did somebody screw up big time?

 

Again?

 

Source: Could somebody tell me: Is the latest Win10 1809 cumulative update, KB 4495667, forced or optional? (AskWoody)

Link to comment
Share on other sites


6 hours ago, Karlston said:

Could somebody tell me: Is the latest Win10 1809 cumulative update, KB 4495667, forced or optional?

 

Tonight, when I was to turn off Windows 10, I found the option to restart with update. "Aborted"  the turn off and went to Windows Update, to find effectively this same note, telling me that cumulative update, KB 4495667 was there, pending restart. So, well, I let it to be installled and had no issue but I never checked for it. It was there, Microsoft pushed it! Presume I can unistall it .  Well, wait and see... But definitively, it was not optional!

Link to comment
Share on other sites


Well, Microsoft needs to testing bug with Native English language before release to Japan because it is easier to read complaints in English than Japanese. 

Link to comment
Share on other sites


The AchieVer

Windows 10 Build 17763.475 is now available, download offline installers

 
Windows 10 Start Menu

 

The first May 2019 cumulative update is rolling out to Windows 10 October 2018 Update devices with a new series of bug fixes. Direct download links for Windows 10 KB4495667 have been published on Microsoft Update Catalog and you can use them for manual installation.

 

Windows 10 Build 17763.475 doesn’t come with any new features, but instead, it includes a bunch of fixes and performance improvements. On Windows 10 October 2018 Update PCs, the update is labelled as KB4495667 and will bump the build version to 17763.475.

 

If you check for updates on Windows Updates pages, the update will appear as “2019-04 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4495667)”. You can also download the msu files for compatible PCs and update your devices manually.

KB4495667 Download Links for Windows 10

Windows 10 KB4495667 Direct Download Links: 32-bit (x86) and 64-bit.

KB4495667 Windows 10 Build 17763.475 Full Changelog

The cumulative update for Windows 10 allows the users with a built-in Administrator account to run Microsoft Office setup after users download the installer from Microsoft Edge. It also addresses an issue associated with Internet Explorer where the browser’s automation fail in certain instances.

 

The update also addresses an issue that may cause the Windows 10’s user interface to stop responding for several seconds if you scroll in windows that have many child windows. Another bug where touch screen may not work after system reboot has been addressed in the latest release.

 

There are several fixes included in today’s release but most of the changes are aimed at enterprises. For instance, Microsoft has addressed an issue where users could continue logging on to an account using a smart card after disabling the account.

 

Microsoft is also fixing an issue where the UWP apps may not receive keyboard input when the user interface is too busy. As per the changelog, this problem was experienced when the UWP app featured an embedded WebView control.

 

 

 

Source

Link to comment
Share on other sites


Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...