New
#1
and KB4522742 for 1909
Cumulative Update KB4522742 .NET Framework 3.5, 4.8 Windows 10 Oct. 24
October 24, 2019 - KB4522741 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1903 and Windows Server 1903 RTM
Applies to: .NET Framework
Version: .NET Framework 3.5 and 4.8
Summary
This article describes the Cumulative Updates for 3.5 and 4.8 for Windows 10 Version 1903 and Windows Server 1903 RTM.
Additional information about this update
Prerequisites
To apply this update, you must have .NET Framework 3.5 and 4.8 installed.
The following articles contain additional information about this update as it relates to individual product versions.
- 4519573 Description of the Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8 for Windows 10 Version 1903 and Windows Server 1903 RTM and Windows 10, version 1909 and Windows Server, version 1909 (KB4519573)
Source: https://support.microsoft.com/en-us/help/4522741
See also: https://devblogs.microsoft.com/dotne...-version-1909/
Direct download links for KB4522741 MSU file from Microsoft Update Catalog:
Download KB4522741 MSU for Windows 10 v1903 and v1909 32-bit (x86) - 34.8 MB
Download KB4522741 MSU for Windows 10 v1903 and v1909 64-bit (x64) - 62.1 MB
and KB4522742 for 1909
Cumulative Update KB4522742 .NET Framework 3.5, 4.8 Windows 10 Oct. 24
2019-10 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1903 for x64 (KB4522741)
I've just installed this update on a W10 Pro desktop and it's broken all my Office 365 programs, none of them would start, removing the update didn't solve the problem so I have had to restore a Macrium image from yesterday to get Office 365 working again!
Further info:- a second attempt at installing this update has worked successfully so I don't know why there was a problem on the first attempt!
Last edited by Sheltieuk; 25 Oct 2019 at 04:55. Reason: Update
This update was causing service host problems. Was causing high CPU, ram, and HDD usage. As well as health monitor was hogging resources. Seems that the .449 update seemed to fixed that though.