Windows 10: Advisory on July 2018 .NET Framework Updates

Brink · Jul 21, 2018

The July 2018 Security and Quality Rollup updates for .NET Framework was released earlier this month. We have received multiple customer reports of applications that fail to start or don’t run correctly after installing the July 2018 update. These reports are specific to applications that initialize a COM component and run with restricted permissions. You can reach out to Microsoft Support to get help.

We have stopped distributing the .NET Framework July 2018 updates on Windows Update and are actively working on fixing and re-shipping this month’s updates. If you installed the July 2018 update and have not yet seen any negative behavior, we recommend that you leave your systems as-is but closely monitor them and ensure that you apply upcoming .NET Framework updates.

As a team, we regret that this release was shipped with this flaw. This release was tested using our regular and extensive testing process. We discovered while investigating this issue that we have a test hole for the specific combination of COM activation and restricted permissions, including impersonation. We will be mitigating that gap going forward. Again, we are sorry for any inconvenience that this product flaw has caused.

We will continue to update this post and dotnet/announcement #74 as we have new information.

Technical Context

The .NET Framework runtime uses the process token to determine whether the process is being run within an elevated context. These system calls can fail if the required process inspection permissions are not present. This causes an “access denied” error.

Workaround

Temporarily uninstall the July 2018 Security and Quality Rollup updates for .NET Framework to restore functionality until a new update has been released to correct this problem.

Symptoms

A COM component fails to load because of “access denied,” “class not registered,” or “internal failure occurred for unknown reasons” errors.

The most commonly reported failure results in the following error message:

Exception type: System.UnauthorizedAccessException
Message: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Sharepoint

When users browse to a SharePoint site they may see the following HTTP 403 message:

"The Web Site declined to show this webpage"

The SharePoint ULS Logs will contain a message like the following:

w3wp.exe (0x1894) 0x0B94 SharePoint Foundation General 0000 High UnauthorizedAccessException for the request. 403 Forbidden will be returned. Error=An error occurred creating the configuration section handler for system.serviceModel/extensions: Could not load file or assembly <AssemblySignature> or one of its dependencies. Access is denied. (C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Config\machine.config line 180)

w3wp.exe (0x1894) 0x0B94 SharePoint Foundation General b6p2 VerboseEx Sending HTTP response 403:403 FORBIDDEN.

w3wp.exe (0x1894) 0x0B94 SharePoint Foundation General 8nca Verbose Application error when access /, Error=Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

When crawling a people content source, the request may fail with the following entry logged to the SharePoint ULS Log:

mssearch.exe (0x118C) 0x203C SharePoint Server Search Crawler:Gatherer Plugin cd11 Warning The start address sps3s://<URLtoSite> cannot be crawled. Context: Application 'Search_Service_Application', Catalog 'Portal_Content' Details: Class not registered (0x80040154)

IIS Hosted Classic ASP calling CreateObject for .NET COM objects may receive error "ActiveX component can't create object"

.NET Application creates instance of .NET COM application within an Impersonation Context may receive error "0x80040154 (REGDB_E_CLASSNOTREG)"

BizTalk Server Administration Console

BizTalk Server Administration Console fails to launch properly with the following errors:

An internal failure occurred for unknown reasons. (WinMgmt)

Program Location:

at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

at System.Management.ManagementObject.Get()

at Microsoft.BizTalk.SnapIn.Framework.WmiProvider.SelectInstance

Use the following guidance as a workaround:

Add “NETWORK SERVICE” to the local Administrators group.

IIS with Classic ASP

IIS Hosted Classic ASP calling CreateObject for .NET COM objects may receive the following error: “ActiveX component can’t create object”. Use the following guidance as a workaround.

If your web site uses Anonymous Authentication, change the Web Site Anonymous Authentication credentials to use the “Application pool identity”

If your site uses Basic Authentication, log into the application once as the application pool identity and then create an instance of the .NET COM component. All subsequent activations for that .NET COM component should succeed, for any user.

.NET applications using COM and impersonation

.NET Applications that creates instances of .NET COM application within an Impersonation Context may receive the following error: “0x80040154 (REGDB_E_CLASSNOTREG)”. Use the following guidance as a workaround.

Create an instance of the .NET COM component prior to the impersonation context call. Later impersonated create instance calls should work as expected.

Run the .NET Application in the context of the impersonated user

Avoid using Impersonation when creating the .NET COM object

Click to expand...

Source: Advisory on July 2018 .NET Framework Updates | .NET Blog

:)

Brink · Jul 21, 2018

.NET Framework July 2017 Cumulative Quality Update for Windows 10

Today, we are releasing a new Cumulative Quality Update for the .NET Framework. It is specific to Windows 10 build 1703 (Creators Update).

Previously released security and quality updates are included in this release, including the July 2017 Security and Quality Rollup, the July 2017 Preview of Quality Rollup and the June 2017 Cumulative Quality Update for Windows 10.

Note: This release is considered a July release even though it is being released in August.

Quality and Reliability

The following improvements are included in this release. Most changes are for the .NET Framework 4.7. .NET Framework 3.5 changes are called out specifically.

ASP.NET

.NET Session State throttles change requests when several requests for the same session object arrive on the server, with .NET Framework 3.5 [447143].

CLR

CRWLock::StaticAcquireWriterLock() never returns if Int32.MaxValue number of ReaderWriterLock objects are created, with .NET Framework 3.5 [242568].

Dynamic method compilation may fail due to out of memory if memory for the code is not available near its precode [394998].

Memory leak in AppDomain::m_clsidHashMap [431586].

EETypeHashTable lookups can deadlock with GC during comparison with unrestored persisted TypeHandles [435006]

Data

SqlConnection object memory leak [444016].

System.Data.SqlClient: Errors due to undersized prelogin packet data buffer [445492].

Performance improvements in Entity Framework [445511].

Management

Reboot method of Win32_OperatingSystem has Privilege not held exception, with .NET Framework 3.5 and 4.7 [441904].

Windows forms

MdiWindowListItem remove MDI from list after closing cancellation [396476].

Excessive object creation in a performance-critical code-path leading to performance regressions and/or displaying empty UI and/or exhausting GDI+ handles [452048].

Windows Presentation Foundation (WPF)

NullReferenceException thrown from PresentationFramework.dll during SpellCheck operations after SpellCheck.CustomDictionaries.Clear() is called programmatically [432174].

XML

Incorrect Validation logic is applied when handling the <xsd:whiteSpace value=”collapse”/> directive in System.Xml [227903, 440921, 440932]

Getting the Update

The July 2017 Cumulative Quality Update is available via Windows Update, Windows Server Update Services and Microsoft Update Catalog.

Docker Images

The .NET Framework Docker images have not been updated for this release.

Downloading KBs from Microsoft Update Catalog

You can download patches from the table below. See .NET Framework Monthly Rollups Explained for an explanation on how to use this table to download patches from Microsoft Update Catalog.

Product Version Cumulative Quality Update KB Windows 10 Creators Update Catalog
4032188 .NET Framework 4.7 4032188 .NET Framework 3.5 4032188
Click to expand...

Source: .NET Framework July 2017 Cumulative Quality Update for Windows 10 | .NET Blog

Waseemulla S · Jul 21, 2018

Microsoft .NET Framework, Unhandled exception

Hi,

Welcome to Microsoft Community.

I suggest you to un-check and recheck .Net framework 3.5 and .Net framework 4.6 advance series from Windows features.

Try the following steps:

Press Windows + R keys to open Run command.

Type Appwiz.cpl and select "turn Windows feature on or off" from the left

Uncheck .Net framework 3.5 and .Net framework 4.6 advance series.

Restart the computer

Repeat step 1 and 2 and check .Net framework 3.5 and .Net framework 4.6 advance series.

Restart the computer.

Regards,

Brink · Jul 21, 2018

.NET Framework May 2018 Preview of Quality Rollup

Today, we are releasing the May 2018 Preview of Quality Rollup.

Quality and Reliability

This release contains the following quality and reliability improvements.

CLR

Resolves an issue in WindowsIdentity.Impersonate where handles were not being explicitly cleaned up. [581052]

Resolves an issue in deserialization when using a collection, for example, ConcurrentDictionary by ignoring casing. [524135]

Removes case where floating-point overflow occurs in the thread pool’s hill climbing algorithm. [568704]

Resolves instances of high CPU usage with background garbage collection. This can be observed with the following two functions on the stack: clr!*gc_heap::bgc_thread_function, ntoskrnl!KiPageFault. Most of the CPU time is spent in the ntoskrnl!ExpWaitForSpinLockExclusiveAndAcquire function. This change updates background garbage collection to use the CLR implementation of write watch instead of the one in Windows. [574027]

Networking

Fixed a problem with connection limit when using HttpClient to send requests to loopback addresses. [539851]

WPF

A crash can occur during shutdown of an application that hosts WPF content in a separate AppDomain. (A notable example of this is an Office application hosting a VSTO add-in that uses WPF.) [543980]

Addresses an issue that caused XAML Browser Applications (XBAP’s) targeting .NET 3.5 to sometimes be loaded using .NET 4.x runtime incorrectly. [555344]

A WPF application can crash due to a NullReferenceException if a Binding (or MultiBinding) used in a DataTrigger (or MultiDataTrigger) belonging to a Style (or Template, or ThemeStyle) reports a new value, but whose host element gets GC’d in a very narrow window of time during the reporting process. [562000]

A WPF application can crash due to a spurious ElementNotAvailableException. [555225]
This can arise if:

Change TreeView.IsEnabled

Remove an item X from the collection

Re-insert the same item X back into the collection

Remove one of X’s subitems Y from its collection
(Step 4 can happen any time relative to steps 2 and 3, as long as it’s after step 1. Steps 2-4 must occur before the asynchronous call to UpdatePeer, posted by step 1; this will happen if steps 1-4 all occur in the same button-click handler.)

Note: Additional information on these improvements is not available. The VSTS bug number provided with each improvement is a unique ID that you can give Microsoft Customer Support, include in StackOverflow comments or use in web searches.

Getting the Update

The Preview of Quality Rollup is available via Windows Update, Windows Server Update Services, and Microsoft Update Catalog.

Microsoft Update Catalog

You can get the update via the Microsoft Update Catalog.

Product Version Preview of Quality Rollup KB Windows 8.1
Windows RT 8.1
Windows Server 2012 R2 Catalog
4103473 .NET Framework 3.5 4095875 .NET Framework 4.5.2 4098974 .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.1 4098972 Windows Server 2012 Catalog
4098968 .NET Framework 3.5 4095872 .NET Framework 4.5.2 4098975 .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.1 4098971 Windows 7
Windows Server 2008 R2 Catalog
4103472 .NET Framework 3.5.1 4095874 .NET Framework 4.5.2 4098976 .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.1 4096234 Windows Server 2008 Catalog
4103474 .NET Framework 2.0, 3.0 4095873 .NET Framework 4.5.2 4098976 .NET Framework 4.6 4096234
Click to expand...

Read more: .NET Framework May 2018 Preview of Quality Rollup | .NET Blog

Windows 10: Advisory on July 2018 .NET Framework Updates

Advisory on July 2018 .NET Framework Updates

Advisory on July 2018 .NET Framework Updates

Advisory on July 2018 .NET Framework Updates

Advisory on July 2018 .NET Framework Updates - Similar Threads - Advisory July 2018

July 2023 windows 10 22H2 updates issues with .net framework

July 2023 windows 10 22H2 updates issues with .net framework

July 2023 windows 10 22H2 updates issues with .net framework

.NET Framework Update

.NET Framework Cumulative Updates for Windows 10 October 2018 Update

.NET Framework July 2018 Update available

.NET Framework July 2017 Preview of Quality Rollup

.NET Framework July 2017 Security and Quality Rollup

.NET Framework July 2017 Cumulative Quality Update for Windows 10

Users found this page by searching for:

KB4098972

kb4098971