Microsoft .NET Framework 4.8
This update for Windows 8.1, RT 8.1, and Server 2012 R2 includes a fix to an issue introduced in the October 15th Cumulative update. See the Quality and reliability improvements section for more details. Before you install this update, see the Prerequisites and Restart requirement sections.
- All updates for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2 require that update KB 2919355 is installed. We recommend that you install update KB 2919355 on your Windows 8.1-based, Windows RT 8.1-based, or Windows Server 2012 R2-based computer so that you receive updates in the future.
- If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.
Quality and reliability improvements
Address an issue where ClickOnce applications and applications creating the default AppDomain with a restricted permission set may observe application launch or application runtime failures, or unexpected behaviors. The observable issue was the System.AppDomainSetup.TargetFrameworkName is null, leading to any quirks enabling reverting back to .NET Framework 4.0 behaviors.
1 Common Language Runtime (CLR)
Known Issues in this update:
There are no known issues with this update, however, this update resolves a previous known issue. This patch includes improvements to resolve a known issue discussed in KB4519567 that occurs after applying the October Preview of Quality Rollup for .NET Framework 4.8. To resolve this issue, install update for .NET Framework 4.8 for Windows 8.1, RT 8.1, and Server 2012 R2 KB4533004.
How to obtain and install the update
Windows 8.1, Windows RT 8.1 and Windows Server 2012 R2
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
Additional file information