Ever since a couple months ago DisplayFusion crashes on startup and after launch. It starts for a couple seconds and then immediately crashes. It is fully up-to-date and I don't have any antivirus software installed. I'm on the latest build of Windows 11. I tried uninstalling/reinstalling, disabling application hooks, and changing startup type to Automatic instead of Automatic (Delayed Start). I've attached the log files, it crashed at 8:05PM.

Sorry there's no crash file for DisplayFusion there.

I don't know if this helps but here are the errors from Event Viewer:

Application: DisplayFusion.exe
CoreCLR Version: 7.0.423.11508
.NET Version: 7.0.4
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack:
at BFClientTools.BFNativeMethods.ShellExecuteEx(SHELLEXECUTEINFO ByRef)
at BFClientTools.BFNativeMethods.ShellExecuteEx(SHELLEXECUTEINFO ByRef)
at BFClientTools.BFProcessHelpers.
(System.String, System.String, System.String, ShellExecuteVerbEnum, ShowWindowEnum)
at DisplayFusion.DFHookManager.
(Boolean, System.String, System.String, System.String)
at DisplayFusion.DFHookManager+.
()
at .+
.
()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

Faulting application name: DisplayFusion.exe, version: 10.0.0.0, time stamp: 0x641de100
Faulting module name: coreclr.dll, version: 7.0.423.11508, time stamp: 0x63ed7a18
Exception code: 0xc0000005
Fault offset: 0x00000000001ca906
Faulting process id: 0x0x4C98
Faulting application start time: 0x0x1D972F6ED0EF0B0
Faulting application path: C:\Program Files\DisplayFusion\DisplayFusion.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.4\coreclr.dll
Report Id: 89641340-c3a7-4ceb-b63a-be88cc255aa7
Faulting package full name:
Faulting package-relative application ID:

It hasn't let me reply with an attachment (says server maintenence) so I sent the crash dump to the support email. Thanks!

Hello, I believe I have the same issue across the current release and some betas for the past 4 months or so. I have the same exact errors shown in event viewer and there are crash dumps available but they're all larger than 400MB. Is there any update to this or something I can do?

Edit, I copied some of the text from windbg after having it analyze the dump, hopefully it's helpful.

Hi, I tried using the upload several times over the past two days but unfortunately after I hit "upload" I get redirected to a 502 error page. I'll try again tomorrow.

In my case, the issue was a conflict with ExplorerPatcher which is to customize Windows 11.

That would make sense, I happen to use explorer patcher too. I was hoping just not using overlapping features would be enough to solve any potential issues, but I guess explorer patcher changes something DF relies on? Besides taskbar options (which I don't use in either) and the option for the classic context menu in win11, I don't know of any other overlapping features.

Now that I think about it, I was having other problems with explorerpatcher after a recent windows update and after reinstalling it and disabling the shell-extension option in it seems to have resolved that, and (un?)coincidentally DF hasn't crashed since then either (knock on wood). Hopefully I can upload the dump file soon and it'll confirm what the problem is.

Unfortunately it still doesn't seem to work, I get a 502 error in firefox and I tried edge which seemed to work at first but eventually it seemed to time out and send me to a different edge-internal error page. I just uploaded it to gdrive and I'll put the share link in a protected text attachment.

I also have the same problem with the crashs at the startup (on Win11), also using ExplorerPatcher together with DisplayFusion. Good thing to know that that was the cause!

The following seems work for now (in the Properties for ExplorerPatcher):

• Deactivated "Enable symbols download" in "Advanced"
• Deactivated "Register as shell extension" in "File explorer"

Of course, this is very anecdotical and it is very well possible that only one of the settings caused the problem. But at least for now, it seems, I can keep using the Win10 style start menu together with DisplayFusion, which is great!
If the startup crash thing still happens, I'll try to update this comment.

EDIT1: Ok, so the "symbols download" seems irrelevant (activated it back and still works), therefore I striked it out.