Difference between .NET 4.8.0 and 4.8.1

Question

We've found that our program breaks when a machine is updated from .NET 4.8.0 to .NET 4.8.1. Nothing else has changed on the machine. The program is set to target .NET 4.7.2. I know MS isn't going to trouble-shoot our program. But what they can do it give us detailed information about the differences between .NET 4.8.0 and 4.8.1 since that is the only thing that changed on the machine. All I can find online are very generic statements that don't help at the technical level. Can anyone help with providing these types of details?

Based on the Q&A Assist's feedback, here are some details of the issue, in case it helps:

• The error is "A new guard page for the stack cannot be created."
• The Event viewer shows:

Faulting module name: clr.dll, version: 4.8.9195.0, time stamp: 0x64e9259c
Exception code: 0xc00000fd
Fault offset: 0x004593ca
Faulting process id: 0x85c
Faulting application start time: 0x01da0db6be29ee79
Faulting application path: <the EXE being run>
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: 99b804be-c16c-445c-9a5c-4db3a32148b3
Faulting package full name:
Faulting package-relative application ID:

I'm also curious why updating to .NET 4.8.1 would break a program targeted for .NET 4.7.2. Any insight here would be appreciated.

Thank you.

Answer 1

this is a stack overflow error and is typically an application bug (often a recursive error). a stack trace can help.

Answer 2

Hi @Matt Bond , Welcome to Microsoft Q&A,

Try to use Microsoft .NET Framework Repair Tool.

You can also try the following scenarios to see if it works:

1. First, press "win+r" to open the run, and enter regedit to open the registry editor.
2. Then locate in turn:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionExplorerShellExecuteHooks，

Delete AEB6717E-7E19-11d0-97EE-00C04FD91972 on the right.

3. Press "win+r" again to open the run, and enter cmd to open the command prompt.
4. Enter the code in the open command prompt window: for %i in (%windir%system32*.dll) do regsvr32.exe /s %i Press enter to see the effect.

Note: The solution involves a registry, so it is recommended that you export the registry information for backup before the operation.

You also have the option to go back to a previous version to avoid the programs you need not working.

Best Regards,

Jiale

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.