Windows 10 1809 Cumulative Update
Microsoft has finally released the latest cumulative update for Windows 10 build 1809 and with it comes a huge amount of fixes for open issues.
After the problematic update releases for Windows October 2018 Update (build 1809), Microsoft has been holding back their cumulative updates for build 1809 for a longer period of time in order to work out any bugs. This is why the KB4490481 cumulative update for build 1809 was not released on March 19th with the other updates.
Microsoft also released KB4493510, “Servicing stack update for Windows 10 Version 1809: April 2, 2019”, which Microsoft suggests be installed before installing the latest KB4490481 cumulative update. If you are using Windows Update, these updates will automatically be offered to you.
The updates are also available form the Microsoft Catalog at these links:
The KB4490481 update includes a huge amount of updates, fix, and changes. The full list can be found here.
As has become the norm, this update also introduces some new issues to Windows 10. Thankfully, these issues will not be problematic for most users.
Below are the list of known issues and possible workarounds.
Symptom :After installing this update, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
- Cache size and location show zero or empty.
- Keyboard shortcuts may not work properly.
- Webpages may intermittently fail to load or render correctly.
- Issues with credential prompts.
- Issues when downloading files.
Workaround :Create unique user accounts so that two people don’t share the same user account when logging on to a Windows Server machine. Additionally, disable multiple RDP sessions for a single user account for a specific Windows Server.
Symptom : Cache size and location show zero or empty.After installing this update, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.
Workaround :Microsoft is working on a resolution and will provide an update in an upcoming release.
Symptom :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 :Right-click the URL link to open it in a new window or tab.
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, selectLocal 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.
Symptom :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 : To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:
Open an Administrator Command prompt and type the following:
Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No
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.
Set the following registry value to 0:
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 : If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen will appear at startup. This is not a common setting in non-Asian regions.
Workaround : To avoid this issue, don’t enable per font EUDC. As an alternative, you can edit the registry to mitigate this issue; for more information, see KB4496149. Microsoft is working on a resolution and will provide an update in an upcoming release.
Windows 10 version 1809 phased rollout
On a related note, Microsoft recently announced that the phased rollout of Windows 10 version 1809 has begun and you will finally start getting the new feature update automatically if your PC is compatible.