Issue Title

Visual Studio 2017 crashes regularly, usually after just a minute or so, while having .NET Framework 4.8 Early Access Build 3707 installed.
After uninstalling 4.8 it worked fine again.

Version info

Provide the .NET Framework Early Access build # and your Windows version (output of winver).
.NET Framework 4.8 Early Access Build 3707
Windows 10 Version 1809 (OS Build 17763.195)

General

The following 2 events can be found in the Event Viewer after each crash.

Log Name: Application
Source: .NET Runtime
Date: 2018-12-29 23:29:14
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Windows10
Description:
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at System.Windows.Automation.Peers.ItemAutomationPeer.GetNameCore()
at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
at System.Windows.ContextLayoutManager.fireAutomationEvents()
at System.Windows.ContextLayoutManager.UpdateLayout()
at System.Windows.UIElement.UpdateLayout()
at System.Windows.Interop.HwndSource.SetLayoutSize()
at System.Windows.Interop.HwndSource.set_RootVisualInternal(System.Windows.Media.Visual)
at System.Windows.Interop.HwndSource.set_RootVisual(System.Windows.Media.Visual)
at System.Windows.Controls.Primitives.Popup.SetRootVisualToPopupRoot()
at System.Windows.Controls.Primitives.Popup.CreateWindow(Boolean)
at System.Windows.Controls.Primitives.Popup.OnIsOpenChanged(System.Windows.DependencyObject, System.Windows.DependencyPropertyChangedEventArgs)
at System.Windows.DependencyObject.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
at System.Windows.FrameworkElement.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
at System.Windows.DependencyObject.NotifyPropertyChange(System.Windows.DependencyPropertyChangedEventArgs)
at System.Windows.DependencyObject.UpdateEffectiveValue(System.Windows.EntryIndex, System.Windows.DependencyProperty, System.Windows.PropertyMetadata, System.Windows.EffectiveValueEntry, System.Windows.EffectiveValueEntry ByRef, Boolean, Boolean, System.Windows.OperationType)
at System.Windows.DependencyObject.SetValueCommon(System.Windows.DependencyProperty, System.Object, System.Windows.PropertyMetadata, Boolean, Boolean, System.Windows.OperationType, Boolean)
at System.Windows.DependencyObject.SetValue(System.Windows.DependencyProperty, System.Object)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbQuickInfoPlaceHolder.AddLightBulbControlToQuickInfo(Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbSession, Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbQuickInfoPresenterProvider, Microsoft.VisualStudio.Language.Intellisense.IAsyncQuickInfoSession)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbQuickInfoPresenter.Render()
at Microsoft.VisualStudio.Language.Intellisense.Implementation.IntellisenseSessionStack.OnSessionPresenterChanged(System.Object, System.EventArgs)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.BaseIntellisenseSession.RaisePresenterChanged()
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbSession.Recalculate()
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbSession.Start()
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbBroker.CreateSession(Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionCategorySet, Microsoft.VisualStudio.Text.Editor.ITextView, Microsoft.VisualStudio.Text.ITrackingPoint, Microsoft.VisualStudio.Text.ITrackingSpan, System.Collections.Generic.Dictionary2<Microsoft.VisualStudio.Text.SnapshotSpan,System.Collections.Generic.IEnumerable1<Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionsSource>>, Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionCategorySet, Boolean, Boolean)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbBroker.CreateSession(Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionCategorySet, Microsoft.VisualStudio.Text.Editor.ITextView, Microsoft.VisualStudio.Text.ITrackingPoint, Microsoft.VisualStudio.Text.ITrackingSpan, Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionCategorySet, Boolean, Boolean)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbBroker.CreateSession(Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionCategorySet, Microsoft.VisualStudio.Text.Editor.ITextView, Microsoft.VisualStudio.Text.ITrackingPoint, Microsoft.VisualStudio.Text.ITrackingSpan, Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionCategorySet, Boolean)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbQuickInfoPlaceHolder+<>c__DisplayClass15_0.b__0()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

Event Xml:



1026
2
0
0x80000000000000

3734
Application
Windows10



Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at System.Windows.Automation.Peers.ItemAutomationPeer.GetNameCore()
at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
at System.Windows.ContextLayoutManager.fireAutomationEvents()
at System.Windows.ContextLayoutManager.UpdateLayout()
at System.Windows.UIElement.UpdateLayout()
at System.Windows.Interop.HwndSource.SetLayoutSize()
at System.Windows.Interop.HwndSource.set_RootVisualInternal(System.Windows.Media.Visual)
at System.Windows.Interop.HwndSource.set_RootVisual(System.Windows.Media.Visual)
at System.Windows.Controls.Primitives.Popup.SetRootVisualToPopupRoot()
at System.Windows.Controls.Primitives.Popup.CreateWindow(Boolean)
at System.Windows.Controls.Primitives.Popup.OnIsOpenChanged(System.Windows.DependencyObject, System.Windows.DependencyPropertyChangedEventArgs)
at System.Windows.DependencyObject.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
at System.Windows.FrameworkElement.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
at System.Windows.DependencyObject.NotifyPropertyChange(System.Windows.DependencyPropertyChangedEventArgs)
at System.Windows.DependencyObject.UpdateEffectiveValue(System.Windows.EntryIndex, System.Windows.DependencyProperty, System.Windows.PropertyMetadata, System.Windows.EffectiveValueEntry, System.Windows.EffectiveValueEntry ByRef, Boolean, Boolean, System.Windows.OperationType)
at System.Windows.DependencyObject.SetValueCommon(System.Windows.DependencyProperty, System.Object, System.Windows.PropertyMetadata, Boolean, Boolean, System.Windows.OperationType, Boolean)
at System.Windows.DependencyObject.SetValue(System.Windows.DependencyProperty, System.Object)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbQuickInfoPlaceHolder.AddLightBulbControlToQuickInfo(Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbSession, Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbQuickInfoPresenterProvider, Microsoft.VisualStudio.Language.Intellisense.IAsyncQuickInfoSession)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbQuickInfoPresenter.Render()
at Microsoft.VisualStudio.Language.Intellisense.Implementation.IntellisenseSessionStack.OnSessionPresenterChanged(System.Object, System.EventArgs)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.BaseIntellisenseSession.RaisePresenterChanged()
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbSession.Recalculate()
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbSession.Start()
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbBroker.CreateSession(Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionCategorySet, Microsoft.VisualStudio.Text.Editor.ITextView, Microsoft.VisualStudio.Text.ITrackingPoint, Microsoft.VisualStudio.Text.ITrackingSpan, System.Collections.Generic.Dictionary2<Microsoft.VisualStudio.Text.SnapshotSpan,System.Collections.Generic.IEnumerable1<Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionsSource>>, Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionCategorySet, Boolean, Boolean)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbBroker.CreateSession(Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionCategorySet, Microsoft.VisualStudio.Text.Editor.ITextView, Microsoft.VisualStudio.Text.ITrackingPoint, Microsoft.VisualStudio.Text.ITrackingSpan, Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionCategorySet, Boolean, Boolean)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbBroker.CreateSession(Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionCategorySet, Microsoft.VisualStudio.Text.Editor.ITextView, Microsoft.VisualStudio.Text.ITrackingPoint, Microsoft.VisualStudio.Text.ITrackingSpan, Microsoft.VisualStudio.Language.Intellisense.ISuggestedActionCategorySet, Boolean)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.LightBulbQuickInfoPlaceHolder+<>c__DisplayClass15_0.<CreateMouseTrackingLightBulbSession>b__0()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

Log Name: Application
Source: Application Error
Date: 2018-12-29 23:29:15
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Windows10
Description:
Faulting application name: devenv.exe, version: 15.8.28010.2036, time stamp: 0x5ba2ae3b
Faulting module name: PresentationFramework.ni.dll, version: 4.8.3707.0, time stamp: 0x5c07a66b
Exception code: 0xc0000005
Fault offset: 0x00d360e1
Faulting process id: 0x77c
Faulting application start time: 0x01d49fef5c8742f9
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe
Faulting module path: C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\b4e6bf52e3735075487c2f59a919f6a9\PresentationFramework.ni.dll
Report Id: eff9785d-3793-4534-9deb-3cf7d80caf73
Faulting package full name:
Faulting package-relative application ID:
Event Xml:



1000
2
100
0x80000000000000

3735
Application
Windows10



devenv.exe
15.8.28010.2036
5ba2ae3b
PresentationFramework.ni.dll
4.8.3707.0
5c07a66b
c0000005
00d360e1
77c
01d49fef5c8742f9
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\b4e6bf52e3735075487c2f59a919f6a9\PresentationFramework.ni.dll
eff9785d-3793-4534-9deb-3cf7d80caf73

MSIL that ran correctly with earlier .NET framework fails due to 64-bit JIT optimizations in 4.7.2 preview build

Version Info

.NET 4.7.2 Preview Build 3052, Windows 10 1703 (OS Build 15063:909)

Description

This looks like a regression in the 64-bit jitter. The attached x.il can be used to repro by running ilasm x.il and running x.exe. The correct output should be 'Pass', but will show 'Fail'. If you use the /32BitPreferred arg to ilasm (or corflags) the output will correctly show 'Pass'. Running in 64-bit mode on earlier .NET framework versions (including 4.7) will show 'Pass'. Disabling RyuJit by either COMPLUS_UseLegacyJit=1 or COMPLUS_JitMinOpts=1 will also result in 'Pass'.

x.txt

We ran into a nasty bug on Windows Server 2019 and I can't find any KB articles on it. It's really easy to replicate.

1. Install Windows Server 2019 Standard with Desktop Experience from an ISO.

2. Install Failover Cluster Services.

3. Create new cluster, on the 4th screen, add the current server name. This is what it shows:
   

4. Install .NET 4.8 from an offline installer. (KB4486153) and reboot.

5. Go back to the same screen of the same Create Cluster Wizard and now it looks different:
   

cluster services broken afte.NET 4.8 is installed - unable to put in a 3-digit IP

Now we are unable to type in a 3 digit IP in any of the octet fields. It accepts a maximum of two characters. This has been replicated by others. See full description here: https://social.technet.microsoft.com/Forums/windowsserver/en-US/a563b4e2-67d0-4f96-a10e-5136bc86521b/failover-cluster-manager-bug-on-server-2019-after-net-48-installed-unable-to-type-more-than-two

I don't see SHA3 anywhere in .NET Framework 4.7.2 with the list of hashes. Will built-in support for SHA3 be added at some point, possibly with .NET Framework 4.8?

Issue Title

Environment.SetEnvironmentVariable() messing up system variables and registry keys

Version info

.NET Framework Early Access build 3745 (it applies to all .Net Framework versions until now)
Windows Version 10.0.17763.379

General

If you use Environment.SetEnvironmentVariable() to change PATH environment variable it will lead to the expansion of its content (any %var% contained in PATH variable will get replaced with its content), and the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\Path type will be changed from REG_EXPAND_SZ to REG_SZ.

What is worse, if you are running a 32-bit application on a 64-bit OS, expansions for system variables such as %CommonProgramFiles%, %COMSPEC%, %PROCESSOR_ARCHITECTURE%, or %ProgramFiles%, will be incorrect due to WOW64 redirection so if you had for example %ProgramFiles%\7-Zip in your PATH that will be expanded to C:\Program Files (x86)\7-Zip instead of C:\Program Files\7-Zip.

Finally, given that ComSpec, PSModulePath, and windir registry keys are also by default REG_EXPAND_SZ, if this function is used to change any of them it will mess them up as well.

Actual behavior:

1. Registry key type is changed
2. Variable contents are expanded

Expected behavior

1. Registry key type is preserved
2. Variable contents are not expanded

Early Access ID

N/A

Hi,

How do I build with this early access of .NET ?

I just downloaded the early access of .NET 4.7.2 to see if it would correct this bug I had since the release notes mention many things about HttpClient.

I changed the .csproj to put <TargetFrameworkVersion>v4.7.2</TargetFrameworkVersion> and executed the following MSBuild:

"C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\MSBuild.exe" /toolsversion:15.0 /nologo

but I receive this error:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1124,5):
error MSB3644: The reference assemblies for framework ".NETFramework,Version=v4.7.2" were not found.
To resolve this, install the SDK or Targeting Pack for this framework version [...]

Or is it just changing the app's .config file to put the following?

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <startup> 
        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7.2"/>
    </startup>
</configuration>

Thanks.

ISSUE: In a master/detail scenario using ADO data, changing the primary key of a master item cleared the display of the corresponding details, with no way to display them thereafter. This is fixed by default for apps targeting .NET Framework 4.7.2, and for all apps that set the app-context switch Switch.System.Windows.Data.DoNotUseFollowParentWhenBindingToADODataRelation to false. [457740, PresentationFramework.dll, Bug]

When I build and run directly under VS2015, the bug remainds, the corresponding details are still cleared.

On the other hand, if I run the application targeting .NET Framework 4.7.2 directly from the Windows operating system, the bug does not happen and the display of the corresponding details is updated correctly.

Would it be possible to fix the problem when running throught Visual Studio?

Thanks for you reply

Raymond

Issue Title

When a WPF UserControl has a reference to the Form hosting (using ElementHost) and the UserControl tries to close the Form from a keystroke it will cause a NullReferenceException.

Version info

.Net Framework 4.8 (Version: 4.8.03761)
Windows 10 Pro Version 1809 (OS Build 17763.503)

Also reproducible on Windows 10 Pro 1803 (OS Build 17134.765)

General

After installing .NET 4.8 and testing our Excel COM add-in (upgraded from .NET 4.0) with it I found that there is a bug related to a WPF UserControl being hosted in a WinForm using ElementHost. I first thought the behavior may be related to being a COM add-in rather than a desktop application, but I was able to recreate the bug with a desktop application (example solution to recreate bug is attached).

Scenario to Cause Bug
The below code creates a Form that has a ElementHost and shows the form:

Dim newForm As FormHostingWPF = New FormHostingWPF()
newForm.InitializeForm()
newForm.Show()

In FormHostingWPF.vb the InitializeForm() will create the WPF UserControl and set it to the Forms ElementHost.Child

Friend Sub InitializeForm()
    Dim wpfControl As New WPFChild()
    wpfControl.Form = Me ' The control has a reference to Form so it can close it on button click

    ElementHost1.Child = wpfControl
End Sub

In WPFChild there is a Button and the click event is wired up to close the form hosting it. code below:

Private Sub Button_Click(sender As Object, e As Windows.RoutedEventArgs)
    If Me.Form IsNot Nothing Then Me.Form.Close()
End Sub

When you press 'Tab' to give the button focus and press 'Enter' key to click the button (which closes the Form) the program will crash. Here is the stack trace from the exception:

System.NullReferenceException
  HResult=0x80004003
  Message=Object reference not set to an instance of an object.
  Source=WindowsFormsIntegration
  StackTrace:
   at System.Windows.Forms.Integration.ElementHost.ProcessCmdKey(Message& msg, Keys keyData)
   at System.Windows.Forms.Control.PreProcessMessage(Message& msg)
   at System.Windows.Forms.Control.PreProcessControlMessageInternal(Control target, Message& msg)
   at System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg)
   at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FPreTranslateMessage(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
   at RecreateElementHostProcessCmdKeyBug.My.MyApplication.Main(String[] Args) in :line 81

NOTE: This exception is not thrown when using ShowDialog() e.g...

Using newForm As FormHostingWPF = New FormHostingWPF()
    newForm.InitializeForm()
    newForm.ShowDialog()
End Using

I was hoping to upgrade our application to .NET 4.8, but this bug is preventing us from committing to .NET 4.8. Is there any possible work around to this?

Attached Solution To Recreate Bug: RecreateElementHostProcessCmdKeyBug.zip
I also reported the issue on this repo: microsoft/dotnet#1041

UPDATE
After further testing on my part I found that after installing .NET 4.8 runtime on another computer and installing and older version of our Excel add-in (built using .NET 4.0) I am still receiving the NullReferenceException bug when trying to close the Form from the WPF UserControl. Any help would be appreciated.

Version info

Windows 10 Pro: Version 1709 (OS Build 16299.248)

General

This is with respect to the early access build 3052 installer: The installer didn't require or suggest to restart the OS after it finished. However, to resolve the ServicePoint default settings issue, a restart is required.

Suggestion: Add a checkbox etc. to the final page of the installer flow that triggers a restart of the OS. Or put a message on that page that a restart is required to complete the setup.

Early Access ID

N/A.

Please provide feedback on .NET Framework 4.7.1 Early Access Build 2538

.NET Framework 4.7.1 Early Access Build 2538 is available for download and testing.

Please give the build a try and provide us with feedback, either positive or otherwise. You can comment on this issue or create new issues for bugs that you find.

Thanks for helping to make the next release of the .NET Framework better.

Issue .net framework 4.8

Provide a descriptive title.

Version info:

.Net framework 4.8 Version 3621
Windows 10 Version 1803 (Build 17686.1003)
Home Insider Preview

Provide the .NET Framework Early Access build # and your Windows version (output of winver).

General

Unable to install on this version of Windows 10 OS
States: Newer or Higher Version installed!

Last .NetFramwork installed:

Microsoft .Net Framework 4.7 SDK 4.7.03062
Microsoft .Net Framework 4.7 Targeting Pack 4.7.03062
Microsoft .Net Framework 4.7 Targeting Pack (ENU) 4.7.03062

Visual Studio Enterprice 2017 15.7.27703.2000
Visual Studio Enterprice 2017 Preview 15.8.27729.1

Microsoft .Net Core SDK - 2.0.2 (x64)

Is there a new version coming?

Issue Title

Blue/Green Screen of Death when moving some WPF windows between multiple monitors with different DPIs

Version info

• Windows version 1903 (18362.53), but I've also had it happen in previous versions (I think at least as far back as 1709)
• .NET version 4.8.03752

General

The following is a way to reproduce the issue fairly consistently, but there may be other ways to repro it.

1. Use the attached project with a simple WPF window.
   WpfApp1.zip

The keys appear to be:

• PerMonitorV2 in the app.manifest
• Use the SizeToContent property on the window

2. Setup monitor DPIs as follows
   

3. Move a WPF window in a circle in the intersection between the three monitors to trigger DPI changes.

Results:
Blue/Green Screen of Death. It appears to be a stack overflow caused by an infinite loop of DPI change and repositioning. Not sure if there's a good way to mitigate this at the application level?

The following is the call stack for the Kernel memory.dmp:

# Child-SP          RetAddr           Call Site
00 ffffe101`1accaf48 fffff800`803ce469 nt!KeBugCheckEx
01 ffffe101`1accaf50 fffff800`803c92bf nt!KiBugCheckDispatch+0x69
02 ffffe101`1accb090 fffffeaa`25dcc764 nt!KiDoubleFaultAbort+0x2bf
03 fffffb82`cc67f000 fffffeaa`25dcc5aa win32kbase!EtwTraceAcquiredExclusiveUserCrit+0x24
04 fffffb82`cc67f190 fffffeaa`25b50c9f win32kbase!EnterCrit+0xea
05 fffffb82`cc67f2b0 fffffeaa`25af0cb5 win32kfull!LeaveEnterCrit::~LeaveEnterCrit+0x17
06 fffffb82`cc67f2e0 fffffeaa`25aa75c1 win32kfull!SfnINOUTNCCALCSIZE+0x235
07 fffffb82`cc67f4d0 fffffeaa`25aa6de1 win32kfull!xxxHkCallHook+0x261
08 fffffb82`cc67f5f0 fffffeaa`25aa4f93 win32kfull!xxxCallHook2+0x331
09 fffffb82`cc67f840 fffffeaa`25a432ca win32kfull!xxxSendTransformableMessageTimeout+0x3c3
0a fffffb82`cc67f990 fffffeaa`25a421c6 win32kfull!xxxCalcValidRects+0x726
0b fffffb82`cc67fb20 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x236
0c fffffb82`cc67fc00 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
0d fffffb82`cc67fc90 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
0e fffffb82`cc67fd10 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
0f fffffb82`cc67fd80 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
10 fffffb82`cc67fe30 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
11 fffffb82`cc67fe70 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
12 fffffb82`cc67ff20 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
13 fffffb82`cc680000 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
14 fffffb82`cc680090 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
15 fffffb82`cc680110 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
16 fffffb82`cc680180 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
17 fffffb82`cc680230 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
18 fffffb82`cc680270 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
19 fffffb82`cc680320 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
1a fffffb82`cc680400 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
1b fffffb82`cc680490 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
1c fffffb82`cc680510 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
1d fffffb82`cc680580 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
1e fffffb82`cc680630 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
1f fffffb82`cc680670 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
20 fffffb82`cc680720 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
21 fffffb82`cc680800 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
22 fffffb82`cc680890 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
23 fffffb82`cc680910 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
24 fffffb82`cc680980 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
25 fffffb82`cc680a30 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
26 fffffb82`cc680a70 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
27 fffffb82`cc680b20 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
28 fffffb82`cc680c00 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
29 fffffb82`cc680c90 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
2a fffffb82`cc680d10 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
2b fffffb82`cc680d80 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
2c fffffb82`cc680e30 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
2d fffffb82`cc680e70 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
2e fffffb82`cc680f20 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
2f fffffb82`cc681000 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
30 fffffb82`cc681090 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
31 fffffb82`cc681110 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
32 fffffb82`cc681180 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
33 fffffb82`cc681230 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
34 fffffb82`cc681270 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
35 fffffb82`cc681320 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
36 fffffb82`cc681400 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
37 fffffb82`cc681490 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
38 fffffb82`cc681510 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
39 fffffb82`cc681580 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
3a fffffb82`cc681630 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
3b fffffb82`cc681670 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
3c fffffb82`cc681720 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
3d fffffb82`cc681800 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
3e fffffb82`cc681890 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
3f fffffb82`cc681910 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
40 fffffb82`cc681980 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
41 fffffb82`cc681a30 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
42 fffffb82`cc681a70 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
43 fffffb82`cc681b20 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
44 fffffb82`cc681c00 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
45 fffffb82`cc681c90 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
46 fffffb82`cc681d10 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
47 fffffb82`cc681d80 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
48 fffffb82`cc681e30 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
49 fffffb82`cc681e70 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
4a fffffb82`cc681f20 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
4b fffffb82`cc682000 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
4c fffffb82`cc682090 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
4d fffffb82`cc682110 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
4e fffffb82`cc682180 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
4f fffffb82`cc682230 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
50 fffffb82`cc682270 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
51 fffffb82`cc682320 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
52 fffffb82`cc682400 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
53 fffffb82`cc682490 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
54 fffffb82`cc682510 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
55 fffffb82`cc682580 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
56 fffffb82`cc682630 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
57 fffffb82`cc682670 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
58 fffffb82`cc682720 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
59 fffffb82`cc682800 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
5a fffffb82`cc682890 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
5b fffffb82`cc682910 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
5c fffffb82`cc682980 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
5d fffffb82`cc682a30 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
5e fffffb82`cc682a70 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
5f fffffb82`cc682b20 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
60 fffffb82`cc682c00 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
61 fffffb82`cc682c90 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
62 fffffb82`cc682d10 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
63 fffffb82`cc682d80 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
64 fffffb82`cc682e30 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
65 fffffb82`cc682e70 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
66 fffffb82`cc682f20 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
67 fffffb82`cc683000 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
68 fffffb82`cc683090 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
69 fffffb82`cc683110 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
6a fffffb82`cc683180 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
6b fffffb82`cc683230 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
6c fffffb82`cc683270 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
6d fffffb82`cc683320 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
6e fffffb82`cc683400 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
6f fffffb82`cc683490 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
70 fffffb82`cc683510 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
71 fffffb82`cc683580 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
72 fffffb82`cc683630 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
73 fffffb82`cc683670 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
74 fffffb82`cc683720 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
75 fffffb82`cc683800 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
76 fffffb82`cc683890 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
77 fffffb82`cc683910 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
78 fffffb82`cc683980 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
79 fffffb82`cc683a30 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
7a fffffb82`cc683a70 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
7b fffffb82`cc683b20 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
7c fffffb82`cc683c00 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
7d fffffb82`cc683c90 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
7e fffffb82`cc683d10 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
7f fffffb82`cc683d80 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
80 fffffb82`cc683e30 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
81 fffffb82`cc683e70 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
82 fffffb82`cc683f20 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
83 fffffb82`cc684000 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
84 fffffb82`cc684090 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
85 fffffb82`cc684110 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
86 fffffb82`cc684180 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
87 fffffb82`cc684230 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
88 fffffb82`cc684270 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
89 fffffb82`cc684320 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
8a fffffb82`cc684400 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
8b fffffb82`cc684490 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
8c fffffb82`cc684510 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
8d fffffb82`cc684580 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
8e fffffb82`cc684630 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
8f fffffb82`cc684670 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
90 fffffb82`cc684720 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
91 fffffb82`cc684800 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
92 fffffb82`cc684890 fffffeaa`25b2285a win32kfull!xxxSetWindowPos+0x85
93 fffffb82`cc684910 fffffeaa`25a3d086 win32kfull!xxxSendDpiChangedMessageToTopLevelWindow+0xa2
94 fffffb82`cc684980 fffffeaa`25a3ef37 win32kfull!xxxSendDpiChangedMsgs+0x12a
95 fffffb82`cc684a30 fffffeaa`25b714ae win32kfull!xxxNotifyMonitorChanged+0x7b
96 fffffb82`cc684a70 fffffeaa`25a42315 win32kfull!xxxSendChangedMsgs+0x12dc42
97 fffffb82`cc684b20 fffffeaa`25a40faf win32kfull!xxxEndDeferWindowPosEx+0x385
98 fffffb82`cc684c00 fffffeaa`25a40db5 win32kfull!xxxSetWindowPosAndBand+0xc3
99 fffffb82`cc684c90 fffffeaa`25a3f674 win32kfull!xxxSetWindowPos+0x85
9a fffffb82`cc684d10 fffff800`803cde98 win32kfull!NtUserSetWindowPos+0x254
9b fffffb82`cc684dd0 00007ff8`97d51524 nt!KiSystemServiceCopyEnd+0x28
9c 0000002c`fd5591d8 00000000`00000000 0x00007ff8`97d51524

The following is !analyze -v output for the Kernel memory.dmp

WinDbg Analysis on memory.dmp file

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffe1011accb090
Arg3: fffffb82cc67f000
Arg4: fffffeaa25dcc764

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  LENOVO

SYSTEM_PRODUCT_NAME:  243852U

SYSTEM_SKU:  LENOVO_MT_2438

SYSTEM_VERSION:  ThinkPad W530

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  G5ET99WW (2.59 )

BIOS_DATE:  05/15/2014

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  243852U

BASEBOARD_VERSION:  0B98401 Pro

DUMP_TYPE:  1

BUGCHECK_P1: 8

BUGCHECK_P2: ffffe1011accb090

BUGCHECK_P3: fffffb82cc67f000

BUGCHECK_P4: fffffeaa25dcc764

BUGCHECK_STR:  0x7f_8

TRAP_FRAME:  ffffe1011accb090 -- (.trap 0xffffe1011accb090)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff32d4b35500a4 rbx=0000000000000000 rcx=ffffe1011acc0180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffffeaa25dcc764 rsp=fffffb82cc67f000 rbp=fffffb82cc67f100
 r8=ffffb60b71d05810  r9=0000000000000001 r10=fffff80080302b90
r11=fffffb82cc67f120 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
win32kbase!EtwTraceAcquiredExclusiveUserCrit+0x24:
fffffeaa`25dcc764 e8b78c2900      call    fffffeaa`26065420
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: a86

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 20'00000000 (cache) 20'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  Snagit32.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  TSC-1507

ANALYSIS_SESSION_TIME:  04-19-2019 13:38:33.0480

ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

STACK_OVERFLOW: Stack Limit: fffffb82cc67f000. Use (kF) and (!stackusage) to investigate stack usage.

STACKUSAGE_FUNCTION: The function at address 0xfffffeaa25a42315 was blamed for the stack overflow. It is using 4480 bytes of stack total in 20 instances (likely recursion).

FOLLOWUP_IP: 
win32kfull!xxxEndDeferWindowPosEx+385
fffffeaa`25a42315 8386b0040000ff  add     dword ptr [rsi+4B0h],0FFFFFFFFh

STACK_COMMAND:  .trap 0xffffe1011accb090 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  9aa938da11b16da9b9463cfb8cb27d8d8c38444a

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  3905e3dd60d8f66afe4afe19e49fe95be254315f

THREAD_SHA1_HASH_MOD:  4729be0e17939d880c198515f5416c5bafd43429

FAULT_INSTR_CODE:  4b08683

SYMBOL_STACK_INDEX:  f

SYMBOL_NAME:  win32kfull!xxxEndDeferWindowPosEx+385

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  42b41a6

BUCKET_ID_FUNC_OFFSET:  385

FAILURE_BUCKET_ID:  0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxEndDeferWindowPosEx

BUCKET_ID:  0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxEndDeferWindowPosEx

PRIMARY_PROBLEM_CLASS:  0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxEndDeferWindowPosEx

TARGET_TIME:  2019-04-18T14:46:30.000Z

OSBUILD:  18362

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  22f9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7f_8_stack_usage_recursion_win32kfull!xxxenddeferwindowposex

FAILURE_ID_HASH:  {8ef82beb-6fe8-24d2-0fa4-d9e255d04436}

Followup:     MachineOwner
---------

Early Access ID

N/A

Issue Title

Provide a descriptive title.

Version info

Provide the .NET Framework Early Access build # and your Windows version (output of winver).

General

Provide details on the problem you are experiencing, including step by step instructions to reproduce the issue.

Please provide a code sample for your issue if it is relevant, either inline, link to a gist (or similar) or as a zipped attachment.

For UI problems please provide screenshots inline or as a zipped attachment.

Early Access ID

Some users have been given a .NET Framework Early Access ID. Please provide the ID if you have one.

Version info

Windows 10 Pro: Version 1709 (OS Build 16299.248)

General

This is with respect to the early access build 3052 installer: Given how impossible it is to remove a .NET Framework version from Windows, it would be beneficial to automatically create a system restore point prior to installing a new framework version, in case a bug requires the customer to go back to the previous build.

Early Access ID

N/A

Issue Title: Youtube Subtitle/Closed Caption

Provide a descriptive title: I'm using the latest build of firefox in a 1803 enterprise version of operating system build 17134.407 64-bit in an MSI motherboard, intel cpu clocked at 3.9 GHz 7th Gen i3-7100

Version info : December release version 3694

Provide the .NET Framework Early Access build # and your Windows version (output of winver):
.net framework version 3694 Developer pack, # version 1803 (OS build 17134.407)

General:

Showing the subtitles/closed caption in youtube is impossible unless you try to show it at the instant the video appears in the latest version of mozilla firefox browser.

Provide details on the problem you are experiencing, including step by step instructions to reproduce the issue:
Just try clicking on the subtitles/closed caption in youtube . It will not appear and there is no red line below the cc option of the video if the video has already played several seconds ago in full screen.

Please provide a code sample for your issue if it is relevant, either inline, link to a gist (or similar) or as a zipped attachment:
None

For UI problems please provide screenshots inline or as a zipped attachment:
None

Early Access ID:

???

Some users have been given a .NET Framework Early Access ID. Please provide the ID if you have one.

Version info

.NET Framework 4.7.1 build 2538
Windows 8.1 (6.3.9600) (VM)
Windows 10 1703 (15063.540)

General

Provide details on the problem you are experiencing, including step by step instructions to reproduce the issue.

Upon updating a staging server to .Net Framework 4.7 from Windows Update, I noticed that my IdentityServer3 based application stopped working when trying to get a desktop product to sign in with the Hybrid flow. Long story short, when @Html.AntiForgeryToken exists in the Razor view, cookies added with owinContext.Response.Cookies.Append will not be sent to the browser because MVC/System.Web is also adding cookies for the anti forgery token. This problem continues to exist in .Net Framework 4.7.1 preview.

This issue has come up before, on Stack OverFlow and some have made work arounds, but they mainly deal with CookieAuthentication middleware, which could also be solved by SystemWebCookieManager. These resolutions did not work for just owinContext.Response.Cookies.Append combined with MVC adding its own cookies, such as with @Html.AntiForgeryToken.

Attached is a zip file containing a .Net 4.6.2 compiled MVC 5 application that adds Owin, has a simple HomeController that tries setting an Owin cookie and then sees if it worked on the POST.

SimpleOwinCookieBugRepro.zip

1. On a machine running .Net Framework 4.7.x (including 4.7.0 and this preview), make sure that Index.cshtml has a call to @Html.AntiForgeryToken() and it is not commented out.
2. The routing is set so that the Action EatCookies is the "home" page, but otherwise make sure that's the first page you land on.
3. You'll get redirected to /Home/Index, observe if the JavaScript was able to read out the Owin Test cookie, the HTML will tell you.
4. The cookie should be missing according to the JavaScript, but hit the submit button anyway.
5. Observe that the server could not find the response cookie.
6. Stop the application, and make sure that Index.cshtml has @Html.AntiForgeryToken() commented out.
7. Rerun the app, but this time the JavaScript should see the cookie, the POST will send the cookie, and the server will be able to read it.

1. On a machine running .Net Framework 4.6.x, repeat the steps above, but the cookie will work whether or not @Html.AntiForgeryToken() is commented out.

If this isn't fixed, I either have to stay on .Net Framework 4.6.2 for the foreseeable future, or port my application. Asp.Net Core and IdentityServer4. The port would be a good idea, but I have no idea when I'll be able to.

Hi, I hope to send this request at the right place
In all previous versions of .NET Framework, if we want to display a Persian calendar (Calendar Control), only the name of some months is translated, It's actually the same as the Gregorian calendar (Only the name of the moon has been translated)
Fortunately, in Windows 10, we can fully use the Persian calendar, We can also use it in UWP apps But we can not use in wpf
If possible, please consider this item and add it in the next version
tnx

VisualStyleState return weird number

It looks like there is a issue with latest .Net or Windows causing Application.VisualStyleState return weird number when SavefileDialog is used.

Version info

OS: 1809 (Build 18267.1001)
NET: 4.8.03667(According register)

General

When open a SavefileDialog (In System.Windows.Forms) as a dialog cause controller in background to repaint. This controller is using VisualStyleRenderer when painting but now the Constructor for VisualStyleRenderer is throwing "System.InvalidOperationException Visual Styles-related operation resulted in an error because visual styles are currently disabled in the client area.". When check VisualStyleState in Application class after VS2017 pause the application for me it return 11 as a value. Not sure if this is NET faulty or the new 1809. If i check VisualStyleState after application is started it returns VisualStyleState.ClientAndNonClientAreasEnabled.

Issue Title

System.NullReferenceException in System.Windows.Automation.Peers.ExpanderAutomationPeer.GetChildrenCore() when Switch.UseLegacyAccessibilityFeatures=false in AppContextSwitchOverrides.

Version info

Windows 10 x64 Version 1703 (Build 16257.1)
‎.‎NET Framework 4.7 or later (Build 4.7.02542)

Windows 10 x64 Version 1703 (Build 16251.1002)
‎.‎NET Framework 4.7 or later (Build 4.7.02531)

General

We are noticing this exception when using a ListBox containing a virtualized grouped list of items. It occurs intermittently when an ObservableCollection backing a ListCollectionView which is bound to the ListBox is cleared.

Telemetry is indicating it is only occuring on Insider builds running preview versions of .NET 4.7.1.

The following stack trace is produced:
System.NullReferenceException: Object reference not set to an instance of an object.
at System.Windows.Automation.Peers.ExpanderAutomationPeer.GetChildrenCore()
at System.Windows.Automation.Peers.AutomationPeer.EnsureChildren()
at System.Windows.Automation.Peers.AutomationPeer.UpdateChildrenInternal(Int32 invalidateLimit)
at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
at System.Windows.Automation.Peers.AutomationPeer.UpdatePeer(Object arg)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Issue Title

System.NullReferenceException in .net 4.8 AutomationPeer

Version info

.net 4.8 build 3694
os 17763.195

General

VS crashes when mouse hovers over Editor and opens certain QuickInfo popups.
Not all popups crash VS, such that you can see a few quick info sessions before crashing.
For example, hovering over namespace or using was fine. Hovering over type or a number caused crash

Steps to reproduce:

Install .net 4.8
Open any code file (I tested .cs and .xaml)
Either use Windows Magnifier or remote to the target computer
Hover mouse over a type or a number
After QuickInfo opens, VS crashes

Here, I hovered over "1.0"

Object reference not set to an instance of an object.
   at System.Windows.Automation.Peers.ItemAutomationPeer.GetNameCore()

See the internal bug: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/756115 which contains link to the crash dump

Issue Title:

Savefiledilaog.ShowDialog() is failing on Windows Server Core RS4. It requires COMDLg32.dll.

Provide a descriptive title:
Savefiledilaog.ShowDialog() is failing on Windows Server Core RS4. It requires COMDLg32.dll.

Version info

Window sServer Core RS4 (Build #17101)

General

Savefiledilaog.ShowDialog() is failing. It requires COMDLg32.dll.

Unable to paste the error dialog. Error dialog text is:

"Creating an instance of the COM componennt with CLSID form the class factoryfailed due to following error: 80040111 Classfactory cannot supply requested class. (Exception from HRESULT 0x80040111 (CLASS_E_CLASSNOTAVAILABLE)"

If I try to register DLL it throws error :-
"The module comdlg32.dll was loaded but the entry point DLLRegisterServer waqs not found."

Early Access ID

Some users have been given a .NET Framework Early Access ID. Please provide the ID if you have one.

Since updating .NET Framework 4.7.2, I have begun receiving this error anytime I run an EF query that joins against a table-valued function that takes in a scalar parameter.

Message: The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 2 (""): Data type 0x00 is unknown.

Stack Trace: at System.Data.SqlClient.SqlCommand.<>c.b__180_0(Task1 result) at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke() at System.Threading.Tasks.Task.Execute() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.d__c.MoveNext()

I verified that the same code executes without a problem on another computer using Windows 10 1709 with .NET 4.7.1. I updated the computer to .NET 4.7.2 with no other change, and I started getting the error above. Code causing the error:

var query = from fs in db.ViewWithInformation
            join e in db.GetEventsForPerson(personnelId) on fs.Event_Id equals e.Event_Id
            where !fs.Is_Deleted
            select fs;
return await query.ToArrayAsync();

If I remove the join against db.GetEventsForPerson, the query runs. The SQL generated by the EF query above runs fine in SSMS.

Another person with the same issues: dotnet/ef6#537

Version info

.NET 4.7.2 (461814)
Version 1709 (OS Build 16299.371)
Provide the .NET Framework Early Access build # and your Windows version (output of winver).

Issue Title

missing fix from coreclr: Fiber-friendly Vectored Exception Handling #20746

Version info

4.8 3745 (downloaded from msdn 4/16/19)
Server 2008 R2

General

The fix for fiber-friendly Vectored Exception Handling seems to be missing (c.f. dotnet/coreclr#20746)

Thus, if clr is loaded on a fiber that get deleted then the clr crashes the process on the next exception (ANY exception, not only managed exceptions)

Issue Title

Setup cannot continue as the package does not apply to this operating system. Please refer to this page for more information about the supported operating systems.

Version info

.NET Framework 4.8 Early Build
Windows 7 6.1 (Build 7601, Service Pack 1)

General

I have attach the log file from collect.exe

vslogs.zip

I see that the change log is somewhat here: https://blogs.msdn.microsoft.com/dotnet/2018/02/05/announcing-net-framework-4-7-2-early-access-build-3052/ would it be possible to post it here first so we can also check it for mistakes as well as get an idea of what's coming sooner / not have to rely on actively checking blogs.

Issue Title

System.Windows.Forms.ListView HideSelection Default Value Incorrect

Version info

.NET 4.8 Build 3646
Windows 10 1803 (17134.345)

General

The default value for ListView.HideSelection is specified as True, and designer generated code omits the property set when HideSelection is set to True in the designer properties window. However it appears that HideSelection is actually defaulting to False. So unless you manually set the property to True after InitializeComponent(), or add the set line to the Designer code, HideSelection is always False.

Here are screenshots showing the designer property setting and the actual value and behavior of the ListView control. In each shot I've clicked on an item, followed by a click on the button to cause the ListView to lose focus.
HideSelection_Caps.zip

It's a minor issue, but there may be other controls/properties affected.

Merge ObjectIdGenerator fix from .NET Core to Desktop

We are hitting the issue
https://github.com/dotnet/corefx/issues/24902
with regular .NET Framework now. It would be good to merge the fixes done there back
to the full .NET Framework or as quick fix at least increase the fixed hash values to support at
least 30 million objects in the serialized data.

Issue Title

When using System.Web.Caching you'll get the following error. To install IIS would solve the problem, but that's not an actionable solution for us as too many systems are affected.

Fehler beim Initialisieren der systemeigenen, für den Webarbeitsprozess externen Konfigurationsunterstützung (HRESULT=0x80040154).
"nnativerd.dll" muss sich in "%windir%\system32\inetsrv" befinden.

in english something like:

Unable to initialize the native configuration support external to the web worker process (HRESULT=0x80040154). nativerd.dll must be in %windir%\system32\inetsrv.

Version info

.Net Framework 4.8 (Version: 4.8.03761 / Release: 528049)
Windows 10 Release 1809 (Build 17763.475)
but also reproduceable with current Windows 10 Release 1903 and its included Framework 4.8

General

This bug is going to crash our software product which is running on some zillions of systems. Please help us with this severe impact on our company and provide a bugfix as soon as possible.

Everything worked fine until .Net Framework 4.7.2.

My team leader wrote few lines of C# code to make the trouble reproduceable (precondition: IIS is NOT installed):

`
using System;
using System.Web.Caching;

namespace ConsoleApplication36
{
class Program
{
static void Main(string[] args)
{
try {
Cache _cache = new Cache();
_cache.Add("test", "test", null, DateTime.MaxValue,TimeSpan.FromDays(1),CacheItemPriority.Normal, null );

        } catch (Exception ex) {
            Console.Out.WriteLine(ex.Message);
        }
    }
}

}
`

Early Access ID

Use of INITBLK and CPBLK MSIL instructions can cause compatibility issues when running under .NET 4.7.2 preview

Version Info

.NET 4.7.2 Preview Build 3052, Windows 10 1703 (OS Build 15063:909)

Description

The attached IL fragment can be used for a repro. Issue occurs only in 64-bit and when the IL is compiled using ilasm and the /debug (or /debug=impl) flags. Note, compiling with /debug=opt does not trigger a problem. The issue seems related to the use of the MSIL INITBLK and CPBLK instructions and specifically when data length is 2, 4 or 8 bytes. The attached example only uses CPBLK - I can supply other examples if necessary.

x1mod.txt

Issue Title

Moving a WPF window upwards gets stuck and stops updating

Version info

.NET version: 4.8.03752
Windows version: 1903 (18356.16)

General

1. Create a new basic WPF project targeting .NET 4.7.2 (or 4.6, doesn't seem to matter).
2. Run the app.
3. Try to move the application window up

Code:
WpfApp1.zip

Expected results:

• Application window moves with cursor when moving it upwards

Actual results:

• Application window doesn't move with cursor when moving it upwards. It only moves after releasing the mouse. Moving it in other directions works fine. Other non-WPF windows on the system (i.e. Explorer) move fine. Moves fine in Windows 10 1809 with .NET 4.7.2.

In the release notes of .NET Framework 4.7.1 build 2538 there are several items related to touch or stylus.
So, i gave it a try to check whether it solves the WPF/Tablet errors.
Unfortunately the error(s) already reported by me and others are still there, at least 1 error:

When I click fast randomly with the pen on the ComboBox, click on the items... after 5 or 10 minutes the control stops working.
Then I can open the ComboBox, can click on an item, the item gets highlighted, but nothing happens: The ComboBox does not close and no click event gets fired.
The same error happens with a ContextMenu. And when the error occurs then all ComboBoxes and all menus does not work anymore. It occurs when i click with the pen or with my finger, the mouse works fine even when the controls are no more usable with pen or finger.

In normal usage, this happens about 5 times per working day in my app, very annoying for my users. You may need some patience to get the error reproduced, maybe it takes you more than 10 minutes... but it DOES happen.

I have made a test app with one ComboBox and one button with a ContextMenu, you can re-produce the error with it. No code needed to get the error, only XAML:

<Window x:Class="MainWindow"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        xmlns:local="clr-namespace:DotNet47ComboBoxAndMenuError"
        mc:Ignorable="d"
        Title="" Height="900" Width="715" WindowStartupLocation="Manual" WindowState="Maximized">
    <Grid>
        <WrapPanel>
            <ComboBox FontSize="16" Width="150">
                <ComboBoxItem>ComboBoxItem 1</ComboBoxItem>
                <ComboBoxItem>ComboBoxItem 2</ComboBoxItem>
                <ComboBoxItem>ComboBoxItem 3</ComboBoxItem>
                <ComboBoxItem>ComboBoxItem 4</ComboBoxItem>
                <ComboBoxItem>ComboBoxItem 5</ComboBoxItem>
                <ComboBoxItem>ComboBoxItem 6</ComboBoxItem>
                <ComboBoxItem>ComboBoxItem 7</ComboBoxItem>
                <ComboBoxItem>ComboBoxItem 8</ComboBoxItem>
                <ComboBoxItem>ComboBoxItem 9</ComboBoxItem>
            </ComboBox>
            <Button x:Name="btnMenu" Content="MENU" FontSize="16" Margin="100,0,0,0">
                <Button.ContextMenu>
                    <ContextMenu>
                        <MenuItem Header="MenuItem 1"></MenuItem>
                        <MenuItem Header="MenuItem 2"></MenuItem>
                        <MenuItem Header="MenuItem 3"></MenuItem>
                        <MenuItem Header="MenuItem 4"></MenuItem>
                        <MenuItem Header="MenuItem 5"></MenuItem>
                        <MenuItem Header="MenuItem 6"></MenuItem>
                        <MenuItem Header="MenuItem 7"></MenuItem>
                        <MenuItem Header="MenuItem 8"></MenuItem>
                        <MenuItem Header="MenuItem 9"></MenuItem>
                    </ContextMenu>
                </Button.ContextMenu>
            </Button>
        </WrapPanel>
    </Grid>
</Window>

My users also report that occasionally clicking on buttons does nothing in dialog windows.
I have not tried to re-produce this with the preview.

And the app occasionally crashes, for ex:

Exception Info: System.IndexOutOfRangeException
   at System.Collections.Generic.Dictionary`2[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Insert(System.__Canon, System.__Canon, Boolean)
   at System.Windows.Input.StylusWisp.WispLogic.CoalesceAndQueueStylusEvent(System.Windows.Input.RawStylusInputReport)
   at System.Windows.Input.PenContext.FirePackets(Int32, Int32[], Int32)
   at System.Windows.Input.PenThreadWorker.FlushCache(Boolean)
   at System.Windows.Input.PenThreadWorker.FireEvent(System.Windows.Input.PenContext, Int32, Int32, Int32, Int32, IntPtr)
   at System.Windows.Input.PenThreadWorker.ThreadProc()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()`

other example crash info:

Exception Info: System.ArgumentNullException
   at System.Collections.Generic.Dictionary`2[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].FindEntry(System.__Canon)
   at System.Collections.Generic.Dictionary`2[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].TryGetValue(System.__Canon, System.__Canon ByRef)
   at System.Windows.Input.StylusLogic.ProcessInputReport(System.Windows.Input.RawStylusInputReport)
   at System.Windows.Input.PenContext.FirePenOutOfRange(Int32, Int32)
   at System.Windows.Input.PenThreadWorker.ThreadProc()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

These crashes happen about every second day. I have not tried to re-produce this with the preview.

Please see also this error posts from others:
WPF touch application (partially) freezes on .NET Framework 4.7
"Stylus Input" threads hanging leading to non-responsive WPF-App
.NET 4.7 - WPF - Touch Enabled Devices Crash Applications

My desperate tries to get this fixed:
WPF - ComboBox and Menu events malfunction on tablets with Windows 10 Creators Update, .NET 4.7, or KB4034658 installed
.NET 4.7 - WPF - Application crashes occasionaly - Tablet (Surface 3 and 4)
.NET 4.7 - WPF - ComboBox and ContextMenu click events not fired - Pen does not work reliable with tablets
WPF .NET app crashes, ComboBox and Menu events not fired on Tablets with Windows 10 Creators Update, .NET 4.7 or KB4034658

Sorry for beeing probably a little too aggressive in my others posts, but i am so frustrated.
I "wasted" so much time on this error until now, without any success.

Version info

Windows 10, Version 1607 (OS Build 14393.1715)
2017-09 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4038782)
.NET Framework 4.7.1 build 2539

General

When enabling Per-DPI awareness and High DPI Auto Resizing with "DpiAwareness" value="PerMonitorV2" and "EnableWindowsFormsHighDpiAutoResizing" value="true" via app.config, rescaling does not seem to occur on VB Windows Forms projects when a form is moved between monitors with different DPI scaling levels or when changing it in settings. Additionally, DPI changed events are not called. This seems to work fine, however, for C# projects. I can get it to partially work with WPF projects that contain Windows Forms - forms rescale automatically only when they visible (if a form is hidden, and then shown on a screen with a different DPI scaling level, it will scale according to the DPI level used the last time it was shown or when the app was opened if the form has never been shown). Also, Forms components inside a WindowsFormsHost do not rescale. I have not tried WPF with a C# project yet. I have tried targeting .Net 4.7, 4.7.1, 4.7.2 and .NET Framework 4.8 Early Access build 3646. I have also tried with Windows 10 added in the compatibility section of the manifest and with dpiaware set to "true/PM" and dpiawareness set to "permonitorv2,permonitor".

Shown in the screenshot is a VB form launched at a DPI scaling level of 100%, I then changed it to 175%. In the follow screenshot, I did the same but with a C# project. The C# form scales correctly while the VB form does not scale at all.

Version info

I have tried targeting .Net 4.7, 4.7.1, 4.7.2 and .NET Framework 4.8 Early Access build 3646 running Windows 10 October Update.

64-Bit JIT Optimization bug

This looks to be an issue with 64-bit JIT optimizations. It is present in 4.7 as well as 4.8 Preview

Version Info

Present in .NET 4.7 (or at least as of recent updates) as well as .NET 4.8 Preview. Worked in 4.6.

Description

Compile the attached .il file contained in the attached .zip with ilasm and run. There should be two lines ok 'OK', instead there is only one. Usual workarounds apply, such as COMPLUS_JitMinOpts=1, compile with /debug or target x86. Additionally, I attached a C# sample. Whilst the C# example will produce the correct results it will fail if you run ildasm on the .exe and re-assemble using ilasm.

JITBug.zip

It was added to coreclr in Jan 2017 and now lives in corefx repo.

Unfortunately that's one of the classes that people can't just copy-paste to their programs to get the new features, because it relies on DependentHandle which is private to a particular runtime.

Issue Title

On some Windows 10 systems that have been upgraded from a previous Windows 10 version to April 2018 Update (Version 1803), trying to initialize a X509Certificate2 throws an Access denied error.

Version info

.NET Framework 4.7.2 on Windows 10 Pro, April 2018 Update (Version 1803) Build 17134.48, x64, German

General

Hi, sorry if this is the wrong place to report this, but I wanted to make sure you are aware of it, as this is really a strange problem (and I haven't yet found other reports of this issue).

The issue is that on some Windows 10 machines (Pro, German, x64) that have been upgraded from a previous Windows 10 version (1511, 1607, 1703) to Windows 10 April 2018 Update (Version 1803) (e.g. using an ISO image downloaded with Media Creation Tool), some certificate operations like loading a X509Certificate2 throws an Access denied exception unless you run the program as administrator.

Please see the following program:

using System;
using System.Security.Cryptography.X509Certificates;

namespace ReproWin10AprilUpdateCertificateError
{
    class Program
    {
        static void Main(string[] args)
        {
            try {
                var bytes = Convert.FromBase64String("MIIKmwIBAzCCClsGCSqGSIb3DQEHAaCCCkwEggpIMIIKRDCCBg0GCSqGSIb3DQEHAaCCBf4EggX6MIIF9jCCBfIGCyqGSIb3DQEMCgECoIIE/jCCBPowHAYKKoZIhvcNAQwBAzAOBAgCQl7XdyiGFAICB9AEggTYyJcvgH6yuk8ytypN6Fo/WXIq+PqBmqK0SBc4/0kCCZXTZSqsvk5INk/gECYdl4/UgsgBaeZEEMMWJFi+m4eSiiexDmL6Ico7Zx2BuWaYP0MofQmgJ9wKRtAVSVEMkiaLPZLYnlLXjD42j6KkYeHfcy2boc3dD5CHXT5wtF5h+iNuQifLcIPFO+XQhnmwl4bW6xr8WyOjG8vP06ePkgfJrJCOHN52h4487X0d6JuuwJEnzQbE+uBI8SDlfriaynvUTgUdGceiKeX1htGsSSGl7U0rGUX3be1yoNnG94W6a23eNQz+0gTH6oG+0DzjjDJtPQ7HQ4QoLlXQ5ZnTdFh48qo26Ngawli/0xP8FyL7hE45uacTd0V415g4ihu7wYPOfPpiYS1Q2p7e5Hg1JKh/rImw+efHimeVcBjm2Ki2acHbYQ17GCuVBYmdnUElE2rfOhu+2vo1quQJj3z7SEBbtPxfgrNQf2DqQw7Zu8/DAkt9Kwr5Kcg+3AKi9kpI/GI3St02j5TFtz04Yx7dXNoBfvFSYjH6AQaVcLzFylY/rw845AMqXpwLSf0BcxmkvRR/l2t8ahlLV+7tovf2TJG7an8k41k1amzgOcGnciFVeXG9ZFBDbaNELesudF371tbw0rVf0mgmpbpbTHgejPW13vd+rgOcXMzg2jDMULokJSR1QKeeqSxYyjitM1j5ke0WjA3H+x6XoRcFXoBzzxPft9OLndR8+b9BcYgbmQHCY3s191Yy90/UfT09Qw9VaiPMS1XprZk2JY24IBFLPgNQF+k0FE69SF8iJEXOjslSibo4WzBFpJnKgpBLeGiPGMKiK1L3CRb82gKveAZMt/ONwSHlZpeNFylY09sYD/vpVZtXx+bKnHyjCUf2WsRL+htHPkd8epYqN7gNQEGYWbbsSV82IFatRo7sGPphHi7IwQ3z/OGL3jvQen0xNTJu80NLtjTXdRGMqvIPDVlG/zGKoWCiIWvUcKESKpndFtsF9DIPYNcf1HUvgimJv0Tz2La1q5y8XwRERgL/y88Svq0NthpTSAkLp1YjVAn31RNdvtT4l0CKvIYmGwvOIlbtod5wrepE42J6YhfgzcghNjqlKA8HCnrpwXZX8KJxoTzlWr/8h0LB5r3msKOO2320PPr2G+ZmMUDrX95qeFBlLrmZI+xxe6G5rlxr/3dIsA5hREcPLwtvNcrQGGHvcCCNMweQqswh6FmdXETxEy1c8f3R0AeInImFTjtxMa0ta1JGjPPK1aMjJXmz1yOpHOiDdfO4990wIMBxNZ67UrBgJLWkocBJauz9rKTMx0+LOLuYwEBrogjS+Y+kxfIZfcbevtXB4IWHKhGUXxej6y+leIJH6IaeH9wWJ563W1DsTDe+z46il45T/zYUJ87/XE+CIWKiIrWAeSPtK+3b5wEh4tODfwnQMOlGDAL3ymGjOt6qae8evK3d/cyB8f4aRtD+VlqamkoC73PLK50BstThM7+sQdNvDCtMirnwAyEEYmBxIrg18PLGVb1eLxmkFGJi5tQrNg5FrXuAi4ABXXOjMa8Q1Cm+WMTFP8RMjTj+2vKNzr183L3kNzOCU8K+pua7ErLuDW/qW2DCgXLGO4XcGHA4C8G7ChwW4Volv4jFTfOKgxzCvjRKrSduRTGB4DANBgkrBgEEAYI3EQIxADATBgkqhkiG9w0BCRUxBgQEAQAAADBbBgkqhkiG9w0BCRQxTh5MAHsAOABEAEIANAAwADUAQQA5AC0AMwBBADQAQQAtADQAMwA5AEYALQA4AEMANAA2AC0AOQAzADUANQBBADEANwA3AEYAQwA4ADkAfTBdBgkrBgEEAYI3EQExUB5OAE0AaQBjAHIAbwBzAG8AZgB0ACAAUwB0AHIAbwBuAGcAIABDAHIAeQBwAHQAbwBnAHIAYQBwAGgAaQBjACAAUAByAG8AdgBpAGQAZQByMIIELwYJKoZIhvcNAQcBoIIEIASCBBwwggQYMIIEFAYLKoZIhvcNAQwKAQOgggPLMIIDxwYKKoZIhvcNAQkWAaCCA7cEggOzMIIDrzCCApegAwIBAgIQVAl0PYSjMr9NAYefsCdr4TANBgkqhkiG9w0BAQUFADAzMR8wHQYKCZImiZPyLGQBGRYPREVTS1RPUC0yVUdHR082MRAwDgYDVQQDEwdDb0RhQml4MCAXDTE4MDUyODE3NDAxMVoYDzIwNjgwNTI4MTc0MDExWjAzMR8wHQYKCZImiZPyLGQBGRYPREVTS1RPUC0yVUdHR082MRAwDgYDVQQDEwdDb0RhQml4MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtYYWFHspvQAsB8aaq2qaJC3a2kEc05LlF7deVk1221mApMX/XKChRQ4IBTTbrZWzdFxBu9ivS6kPonZOT1KW1zJ4wctF97xgee+hEUL8rP6doEHVSiNhEcSPlL+zEqXxYuVB2TKosSeUMJmKkymDhwiiKuSZha+5+h8FiFUoffCJ3vR1xelTRVT0rZQAS6i5ZTnNcGrx3xP7jUzd8uITn5yABbAnt/Qh/OWXFsDAgwId3VUn9OFWFepIVJZJACMvsRd5c1bSaiMGIGDjBHEXqFnzxL2zvO+ukgM7qbqkDR67bJVWOtkR4GLHarO2qdA00zA7wUR8OVGNBJJKFr6M8QIDAQABo4G8MIG5MB0GA1UdDgQWBBT8J0h/E9+OHoLzpnjxCH5L4m3L6jAfBgNVHSMEGDAWgBT8J0h/E9+OHoLzpnjxCH5L4m3L6jAMBgNVHRMBAf8EAjAAMA4GA1UdDwEB/wQEAwIC9DAgBgNVHSUBAf8EFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwNwYDVR0RBDAwLoYbdXJuOkRFU0tUT1AtMlVHR0dPNjpDb0RhQml4gg9ERVNLVE9QLTJVR0dHTzYwDQYJKoZIhvcNAQEFBQADggEBADq8dZBJ97hK0Uol+VJCCyKWu7cFozmYi8s7IS3+B+xhVQhVMVPtlSm9BPXq1ykKtdA1XiLgxFN1XXU9TgdvhMRTIelHOJs5sBBNxfa5rh36UwGEj3sYxbB2gSpNFVlVt9yf+u98g3AwE2gMnkUyK4ZJK8NqucumF4nlVsak6mvQluNreZPZO/dy2yHAUjAehilz0jvUdxRkE+CJiGWH/YlKegjIUKn3ZV+HYg0x58F02KOK1GawJENj7Ib4mcJvR0+r+WIDhwTPbkK3C4O3KwxYVkSIXK5HLe3O4kpjE+EVGfr2S+VY/0HaWh+rqyd+0Mu9y5nnoZJOh9pDUBpqwVExNjATBgkqhkiG9w0BCRUxBgQEAQAAADAfBgkqhkiG9w0BCRQxEh4QAEMAbwBEAGEAQgBpAHgAADA3MB8wBwYFKw4DAhoEFOcW1YBC5chQA0GL63/6KDdX8+3CBBQzl31+DTyiDorXhXVvnc0GAL3YJA==");
                var cert = new X509Certificate2(bytes, "");
                Console.WriteLine(cert.Thumbprint);
            }
            catch (Exception ex) {
                Console.WriteLine(ex.ToString());
            }

            Console.ReadKey();
        }
    }
}

The program loads an X509Certificate2 using the given bytes and then writes the fingerprint. If you compile this program e.g. for .NET Framework 4.6 and run it, it should print this output:

9D5C16B3695ACEF3F820F45DCF4D72745A922855

However, on Windows 10 April 2018 Update machines that exhibit this problem, it prints the following exception ("Zugriff verweigert" means "Access denied"):

System.Security.Cryptography.CryptographicException: Zugriff verweigert

   bei System.Security.Cryptography.CryptographicException.ThrowCryptographicException(Int32 hr)
   bei System.Security.Cryptography.X509Certificates.X509Utils._LoadCertFromBlob(Byte[] rawData, IntPtr password, UInt32 dwFlags, Boolean persistKeySet, SafeCertContextHandle& pCertCtx)
   bei System.Security.Cryptography.X509Certificates.X509Certificate.LoadCertificateFromBlob(Byte[] rawData, Object password, X509KeyStorageFlags keyStorageFlags)
   bei System.Security.Cryptography.X509Certificates.X509Certificate2..ctor(Byte[] rawData, String password)
   bei ReproWin10AprilUpdateCertificateError.Program.Main()

• This problem only occurs on some machines that have been upgraded from a previous Windows 10 version (like 1511, 1607, 1703) to Windows 10 April 2018 Update (1803).
  
  When running the program on the previous Windows 10 version before doing the upgrade, it works correctly.
  
  Also, when doing a clean reinstall of Windows 10 April 2018 Update, it works correctly.
  
  
• When running the program as administrator, it will also work correctly. Only when running the program normally without elevation, it will throw the error.

This issue has an impact for us as we are developing software that needs to interact with certificates, and a customer that has upgraded to the April 2018 update now report this problem. Also, I could reproduce this problem on two VMware virtual machines that have been upgraded from Version 1511 and from version 1703 to 1803.

Is there anything I can do to help diagnosing the issue?

Edit: I cannot reproduce this issue when using the english (en-us) version of Windows 10, but I can reliably reproduce it using the german version, using ISO images that can be downloaded with the Media Creation Tool:

• Boot from Windows 10 Version 1703 (Build 15063) ISO image (German, x64) and install Windows 10 Pro (without a Product Key)
• Set up for personal use, select offline user account; when asked for Cortana select "No"
• When message "Your PC has an update waiting" appears, click "Not now" ("Jetzt nicht")
• After setup is finished, copy the "ReproWin10AprilUpdateCertificateError.exe" on the machine and run it, to ensure it works correctly. Do NOT install other software like VM tools.
• Now, insert Version 1803 (Build 17134) ISO image (German, x64)
• Run setup.exe from the DVD drive
• On the first page asking for updates, select "Not right now" ("Nicht jetzt"), then continue using default options ("Keep personal files and apps"/"Persönliche Dateien und Apps behalten") to install Windows 10 Version 1803
• After the upgrade finishes, when asked for privacy options, select the 2nd option for each.
• After the setup is finished, you can now reproduce the problem when running the EXE.
• You can now also install an english (US) display language in Windows; the issue will still be reproducible.

Thank you!

The Visual Studio developer community forums indicate this bug is resolved in an early .NET Framework 4.8 build. https://developercommunity.visualstudio.com/content/problem/223410/vector2-incorrectly-populated-from-stack-floats-in.html

But the release notes don't back up this claim. Are the release notes inclusive of all changes in these builds? Or just a curated list?

Issue Title

Installer tells me that the Preview cannot not be installed on the current OS.

Version info

Provide the .NET Framework Early Access build # and your Windows version (output of winver).
winver: 10.0.15063

General

Simply start the installer. I have attached the log.
Microsoft_.NET_Framework_4.7.1_Preview_Developer_Pack_20171006232354.log

Version info

.NET Framework 4.7.1 Developer Pack build 2539
Windows Server 2016 Version 1607 (OS Build 14393.1715)

General

Consider the following small program that simply creates a TransactionScope, prints Transaction.Current, calls a method in another AppDomain (that takes a while to execute) and then prints Transaction.Current upon return.

using System;
using System.Linq;
using System.Runtime.Remoting.Lifetime;
using System.Threading;
using System.Transactions;

namespace TransactionScopeFlowTest
{
   class Program
   {
	  static void Main(string[] args)
	  {
		 // These times are just to generate the error faster. Normally the initial lease is 5 minutes, meaning the method call
		 // would have to take 5 minutes to occur, so we speed it up here for demonstration purposes.
		 LifetimeServices.LeaseManagerPollTime = TimeSpan.FromSeconds(1);
		 LifetimeServices.LeaseTime = TimeSpan.FromSeconds(1);
		 LifetimeServices.RenewOnCallTime = TimeSpan.FromSeconds(1);

		 AppDomain domain = AppDomain.CreateDomain("Temp", null, AppDomain.CurrentDomain.SetupInformation);

		 using (TransactionScope scope = new TransactionScope(TransactionScopeAsyncFlowOption.Enabled))
		 {
                        // This will print a valid transaction ID
			Console.WriteLine($"Transaction Before Call = {Transaction.Current?.TransactionInformation?.LocalIdentifier?.ToString() ?? "<null>"}");

                        // We make a remoting call to the other domain, that does nothing but wait a bit.
			domain.DoCallBack(AppDomainCallback);

                        // And now when we return the transaction is null!?
			Console.WriteLine($"Transaction After Call = {Transaction.Current?.TransactionInformation?.LocalIdentifier?.ToString() ?? "<null>"}");
			scope.Complete();
		 }

		 AppDomain.Unload(domain);
	  }

	  public static void AppDomainCallback()
	  {
		 Thread.Sleep(3000);
	  }
   }
}

Quite unexpectedly, the program generates the following output:

Transaction Before Call = 1f980219-2583-4796-8d6d-256a6f100698:1
Transaction After Call = <null>

The expected behavior is for the cross-domain call to have no effect on the ambient transaction in the main app-domain.

If we change the TransactionScopeAsyncFlowOption in the ctor of TransactionScope to TransactionScopeAsyncFlowOption.Suppress, then the Transaction remains after the call.

This behavior exists in .NET 4.7 as well.

Issue Title

Windows update removed .NET 4.8 but preview installer still thinks 4.8 is installed

Version info

.NET 4.8 preview - unkown
Windows 1809 (OS Build 17763.107)

General

I've searched my installed programs and features and can't find 4.8, but I can find 4.7. And when I try to install the new preview build I get a ".NET Framework 4.8 Preview or a later update is already installed on this computer." error. I've been trying to install .NET 4.8 v3621

I've recently noticed a huge number of crashes and hangs in an application, reported by different users which have some kind of stylus or touch input, just after they installed the windows update KB4058258.

Reading this early access release notes, I noticed a lot of improvements on behavior of stylus and touch devices that would seem to solve the problem, but even after installing it, the problem remains.

bug seems related to:
https://github.com/Microsoft/dotnet/blob/master/releases/net471/KnownIssues/481090-WPF%20Touch%20generates%20NullReferenceException%20in%20ProcessInputReport.md

more info:
https://developercommunity.visualstudio.com/content/problem/205823/exception-after-kb4058258-with-wacom-tablets-1.html

My question is if this bug will really be addressed in the final version of 4.7.2 or if there is any way of working it around.

Thanks in advance.

Issue Title

A NullReferenceException originating from a when expression in a catch block results in an AccessViolation, error code: 0xc0000005

Version info

.NET framework version: 4.8.03752
Windows version: 1903 (OS Build 18362.592)

General

Here are the steps to reproduce:

1. Create a new C# console app using .NET framework 4.8
2. In project properties => Build, uncheck "Prefer 32-bit" flag
3. Copy the following code inside the Main method

static void Main(string[] args)
{
	string message = null;

	try
	{
		throw new InvalidOperationException();
	}
	catch when (message.Contains("sd"))
	{

	}
}

4. Start debugging

I get the following exception:

Managed Debugging Assistant 'FatalExecutionEngineError'
Message=Managed Debugging Assistant 'FatalExecutionEngineError' : 'The runtime has encountered a fatal error. The address of the error was at 0xff87bee8, on thread 0x7774. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.'

Running the program in release crashes it and adds the following entries in event viewer, note that I've named my project "AccessViolation"

Error:

Application: AccessViolation.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFFFF87BEE8 (00007FFFFF520000) with exit code c0000005.

Error:

Faulting application name: AccessViolation.exe, version: 1.0.0.0, time stamp: 0xbf0b9487
Faulting module name: clr.dll, version: 4.8.4075.0, time stamp: 0x5dd8a55e
Exception code: 0xc0000005
Fault offset: 0x000000000035bee8
Faulting process id: 0x9e8
Faulting application start time: 0x01d5e356ec098930
Faulting application path: C:\Users\aakarshit.dhingra\source\repos\AccessViolation\AccessViolation\bin\Release\AccessViolation.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 152a4ee5-0483-472b-a6f3-5c630233d430
Faulting package full name:
Faulting package-relative application ID:

Information:

Fault bucket 1536708727133926912, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: AccessViolation.exe
P2: 1.0.0.0
P3: bf0b9487
P4: clr.dll
P5: 4.8.4075.0
P6: 5dd8a55e
P7: c0000005
P8: 000000000035bee8
P9:
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2971.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A0E.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AEA.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AF9.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B29.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_AccessViolation._c328f20dc34ba6ad6a6cca0c429b68b5ca99c53_193c7b63_a8d7ff7b-9ec5-4742-8e1f-b4b4d662cbfa

Analysis symbol:
Rechecking for solution: 0
Report Id: 152a4ee5-0483-472b-a6f3-5c630233d430
Report Status: 268435456
Hashed bucket: 204b39c255f772ebf5537c720c0f7600
Cab Guid: 0

Early Access ID

Don't have one

Version info

.NET Framework 4.7.1 build 2539
Windows 10 v1703 (OS Build 15063.608)

General

When I run the installer I receive a Setup Failed message which states the Preview Developer pack is not support on my operating system. Build 2538 installed without issue.

Relevant line from the installer log:

Setting string variable 'OSBuildNumber' to value '15063'

and

Error 0x81f40001: Bundle condition evaluated to false: ((VersionNT = v6.1 AND ServicePackLevel >= 1) OR       (VersionNT = v6.2 AND NOT (OSInstallationType = "Client")) OR       (VersionNT = v6.3) OR       (VersionNT = v10.0 AND (OSBuildNumber > 15063 OR OSBuildNumber = 14393 ) ) OR       (VersionNT > v10.0))

HEllo

https://developercommunity.visualstudio.com/content/problem/1087456/stringsreplace-bug.html#

HEllo

I found a bug in Fmk 4.8 + VS2019 + Win10x64:

dim y as string = “Ólga”

y.Replace( “Ó”, “O”)

Produce “Overload resolution failed because no accessible ‘Replace’ accepts this number of arguments.”
Same with:

Strings.Replace( y, “Ó”, “O”,1,1, CompareMethod.Binary)

Ins asp.net vb page

Thx

Issue Title

SelectionHighlight in FlowDocumentScrollViewer obscures text in .NET 4.7.2 with
<AppContextSwitchOverrides value="Switch.System.Windows.Controls.Text.UseAdornerForTextboxSelectionRendering=false;" />

Version info

.NET 4.7.03052
Windows 10.16299.214

General

See attached sample and screen shots.

FlowDocumentDemoIssue [12-02-2018 00-45].zip

Text obscured with UseAdornerForTextboxSelectionRendering=false

Text shown as expected with UseAdornerForTextboxSelectionRendering=true

Version info

Microsoft Windows Version 1709 (OS Build 16299.19)

.NET Framework Release (from registry: 461308)

General

First of all please forgive me I am not attaching full repro. I have lost entire day after upgrading to Fall Creators Update to track down this issue and I am way too tired to create at the moment proper reproduction, however I am creating this issue now (even without full repro), because it might somehow affect rollout of Fall Creators Update.

My scenario:
Lib1 - library targeting .NET Standard 2.0
It has an interface that has a member that returns a ValueTuple (more precisely: Task<(T1 F1, T2 F2)>).

App1 - Service Fabric application (I have not tried to isolate this to a different kind of application yet) targeting .NET Framework 4.6.1
Inside this app I implement aforementioned interface from Lib1).

UPDATE: It works for simple console applications as well - see the second post.

This application compiles and runs correctly on Windows 10 Creators Update.
This application fails on Windows 10 Fall Creators Update with TypeLoadException Method 'XXX' in type 'YYY' from assembly 'ZZZ' does not have an implementation.

I have lost a lot of time because I was also updating Service Fabric today and was sure it was rather related to some issues in new project system etc. However at last I have downgraded Service Fabric to previous version and the issue kept occurring. On my second machine with Windows 10 Creators Update everything works as expected.

I have noticed somewhere that Fall Creators Update is shipped with .NET 4.7.1 which has a potentially breaking change in ValueTuple implementation.

Finally I decided to try to change the .NET framework version in App1 to .NET 4.7 and everything started to work correctly.