Microsoft released Windows cumulative updates last week to several versions of the operating system, including the October 2018 Update. This particular version has proven to be nothing but a huge mess for the Windows maker and it seems version 1809 isn’t done creating chaos. Even the latest update has apparently brought in some issues with it.
Microsoft has now updated the list of known issues that arrived with last week’s Patch Tuesday update. Build 17763.437 (KB4493509) released on April 9 brought with it a number of security fixes and improvements. The update is also carrying at least 4 known issues, Microsoft writes. Here are all of them and their possible workarounds:
Symptom
Workaround
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.
Right-click the URL link to open it in a new window or tab.
Or
Enable Protected Mode in Internet Explorer for local intranet and trusted sites.
- Go to Tools Internet options Security.
- Within Select a zone to view or change security settings, select Local intranet and then select Enable Protected Mode.
- Select Trusted sites and then select Enable Protected Mode.
- Select OK.
You must restart the browser after making these changes.
Microsoft is working on a resolution and will provide an update in an upcoming release.
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.
- 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:
“HKLMSystemCurrentControlSetServicesWDSServerProvidersWDSTFTPEnableVariableWindowExtension”.
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.
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.
We are presently investigating this issue with ArcaBit and will provide an update when available.
For more information, see the Arcabit support article
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.
It appears that version 1809 isn’t the only one having to deal with issues. Except for the ArcaBit problem, the other three issues also plague Windows 10 version 1803 (the April 2018 Update).
Latest update blocked for some Windows 7 and 8.1 users
Apart from the Windows 10 issues, the latest April Patch Tuesday update has also introduced problems to Windows 7 and Windows 8.1 for Sophos, Avast, and other antivirus users. “Microsoft and Avast have identified an issue on devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software after you install this update and restart,” the company says. “Devices may become unresponsive at the login or Welcome screen. Additionally, you may be unable to log in or log in after an extended period of time.”
The Windows maker has also implemented a block on the April updates for Avira users on Windows 7 and Windows 8.1 and Sophos is also affected.
Microsoft has temporarily blocked devices from receiving this update if the Sophos Endpoint is installed until a solution is available.
You can find more about the workarounds over here for Windows 7 and here for Windows 8.1. Some of the problems won’t be fixed until the next update so it is recommended to read all the known issues in detail before you go ahead to install the latest updates on your machines.
