R
RAJU.MSC.MATHEMATICS
On 01-05-2019, Microsoft released another windows CLU update KB4501835 build no 17763.439 to windows 10 v1809 and to windows server 2019(1809).
I am sharing the direct download links form www.catalog.update.microsoft.com
for windows 10 v1809 clu kb4501835 64bit os
for windows 10 v1809 clu kb4501835 32bit os
for server 2019(1809) clu kb4501835 64bit os
Improvements and fixes
- 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.
- Addresses an issue in Unified Write Filter (UWF) that prevents Hibernate Once/Resume Many (HORM) from working as expected on Unified Extensible Firmware Interface (UEFI) systems.
If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.
Known issues in this update
Symptom 1
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.
Workaround 1
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.
Open Windows Deployment Services from Windows Administrative Tools.
Expand Servers and right-click a WDS server.
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.
Symptom 2
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.
Workaround 2
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.
Symptom 3
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.
Workaround 3
Microsoft has temporarily blocked devices from receiving this update if ArcaBit antivirus softwareis installed.
ArcaBit has released an update to address this issue. For more information, see the Arcabit support article.
Symptom 4
After installing this update, Custom URI Schemes for Application Protocol handlers may not start the corresponding application for local intranet and trusted sites on Internet Explorer.
Workaround 4
This issue is resolved in KB4495667.
Symptom 5
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."
Workaround 5
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.
Symptom 6
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Workaround 6
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.
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 (KB4493510) will be offered to you automatically. To get the standalone package for the latest SSU, go to the Microsoft Update Catalog.
sources are taken from
www.catalog.update.microsoft.com
my windows does not detected this update , so I skipped this update and updated next update KB4495667
Thanks for reading my post, if you found this as useful means, then give me UPVOTES.
Continue reading...