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.
Microsoft Releases Windows 10 Cumulative Update KB4476976
Microsoft released the KB4476976 cumulative update for Windows Insiders in the Release Preview ring, containing Action Center fixes for the Windows 10 Version 1809 release it pushed to customers on October 2.
On January 8, Microsoft also released new cumulative updates for Windows 10 version 1809, version 1803 and version 1709, as part of company's monthly Patch Tuesday cycle, featuring general fixes and security improvements.
The second January 2019 cumulative update is now available for Windows 10 version 1809 with fixes. Direct download links for Windows 10 KB4476976 are also available and you can use the standalone package to manually install the update.
If uninstalling the update fixes your issue, you might want to consider deferring future updates. On Windows 10 Pro, you can defer cumulative updates for up to 35 days. To do that, head to Settings > Update & Security > Windows Update > Advanced Options and scroll down and turn on the switch to pause updates.
Remember, this is for uninstalling the cumulative updates that are usually launched on Patch Tuesday each month. These include a bunch of individual updates all wrapped up in one download. If you want better control of your Windows 10 updates, check out our article on how to install specific Windows 1o updates with the help of a free app.
Every month Microsoft releases a cumulative update for Windows 10 and other supported operating systems. These updates contain improvements and fixes that will improve the quality of Windows 10. But do these updates have an impact on the performance in a VDI context? This research will compare different cumulative updates on different Windows 10 builds.
Every month Microsoft releases cumulative updates for Windows 10, Windows 10 LTSB, Windows Server 2016 & 2019. These updates are distributed with Windows updates but can also be found in the Windows Update Catalog.
The goal of this research is to show the impact of the cumulative updates on different Windows 10 builds. As over time a lot of cumulative updates are released and therefore the scope has been limited to the following builds:
Each cumulative update will be compared in the own build version, with the oldest update as the baseline. This way it shows if there is an impact with newer updates. The updates have been downloaded and installed individually on a clean Windows 10 release. As the cumulative updates include previous updates, only the latest cumulative update is installed. No additional updates for Microsoft Office 2016 have been installed.
As the changes in the cumulative updates contain fixes, improvements and security related patches it is expected there is only a minimal impact. This is very important for an enterprise environment, as big capacity changes can have a huge influence on the services.
Installing the latest updates is one of the many best practices when creating a VDI environment. Microsoft releases a new cumulative update each month for the different Windows 10 release which contains fixes, improvements and security fixes. Until today it was not clear if the cumulative updates of Windows 10 have a performance impact.
The results show there is only a minimal impact on the overall capacity when installing cumulative updates. As the capacity limit of GO-EUC lab environment is CPU related we did notice a change in storage activity for both Windows 1809 and 1803. The improvement is only noticed in reads/sec which results in a lower hit on storage resource utilization.
The following example runs the wusa.exe command to install an update (windows10.0-kb5003646-x64_ef50cfb8e8067dd27c13ae7c4150d20cb346b3bf.msu in this case) file located in the current directory. This will run the installer interactively and will prompt for input as required.
The update is already installed. You can get a list of installed updates on your computer using the wmic qfe list command or the PSWindowsUpdate PowerShell module;
This update has been replaced or a newer update has been installed that replaces this update. Information about replacing updates can be found on the KB page of the Microsoft website. Usually, this information is listed on the Package Details tab (This update has been replaced by the following updates);
The prerequisites for installing this update are not met. For example, most updates for Windows 7 require SP1 to be installed, updates for Windows 8.1 and Windows Server 2012 R2 require Update 1. You can find dependency information on the KB information page in the Microsoft Update Catalog ( ). Read all KB requirements carefully. You may have to install some other update first before installing this update;
Make sure you have downloaded the full MSU update for Windows and not the Delta update package;
If the Windows Update service does not work correctly, you can try to run the Windows Update Agent reset script or use the Windows Update Troubleshooter (Settings -> Update & Security -> Troubleshoot > Windows Update and press Run the troubleshooter);
If you received an * .msu update file from a third party, it may have been corrupted. Try to re-download the MSU update file from the Windows Update Catalog;
Check the integrity of Windows system files using the commands: Dism.exe /Online /Cleanup-Image /Restorehealth and sfc /scannow
Note that security updates for Windows are now released as cumulative updates. This means that you can install any newer monthly cumulative update for your Windows build (it contains all previous updates).
Before installing some cumulative Windows updates, you must first install the latest available Servicing Stack Update (SSU). This update can be found in the Windows Update Catalog using the following search query:
So I went to -gb/software-download/windows10 and attempted to "Update Now". I noticed the updates would get to certain percentages ie 71% or something (I don't remember the exact number) but then return to 0% then continue back up. It was bizarre. After 20 minutes or so, the updater fails with an error 0x80070522, which means the update was being performed without an Administrator account. But I WAS using an Administrator account. On three different machines I tried it on!
Now before you tell me "you always have to use a clean image" for each build update, that is NOT what Microsoft's own documentation tells you. See: -us/windows-hardware/manufacture/desktop/sysprep--system-preparation--o... - specifically: "Beginning with Windows 10, version 1607, Sysprep can be used to prepare an image that has been upgraded."
None of the cumulative updates, including KB4089848, has installed since the successful install of KB4053517. Hence, I am stuck on build 16299.125. I have tried all the fixes I can find on the web, short of using the media creation tool to do an in-place repair. Is this now the only option to get to the current build? 2ff7e9595c
Comments