As the title says something with displayfusion is causing uwp apps to crash. When looking in the windows event log an error is presented that says DisplayFusion is the culprit.
As I do not know how to fix this and this problem is blocking me from using something as essential as the calculator, I would very much like to know how to fix this problem.
AppModel-Runtime:
Error message:
App Microsoft.WindowsCalculator_10.1804.11545.0_x64__8wekyb3d8bbwe was terminated with error 0xC000047E because of an issue with Windows binary \Device\HarddiskVolume5\Program Files (x86)\DisplayFusion\Hooks\AppHook64_97990F36-D5FE-410E-BE35-7D60F158D2C7.dll. This could be because the binary is unsigned, contains an untrusted signature, or has been corrupted or tampered with. Refresh your PC to fix this issue.
In the DisplayFusion Settings > Advanced Settings window, if you enable the "Disable Application Hooks" option and restart DisplayFusion, does that make any difference?
If not, could you also try enabling the "Disable Shell Hooks" option?
In the DisplayFusion Settings > Advanced Settings window, if you enable the "Disable Application Hooks" option and restart DisplayFusion, does that make any difference?
If not, could you also try enabling the "Disable Shell Hooks" option?
Disabling the Application Hook works, but unfortunately also disables window-snapping, which is a very awesome feature. Some other very useful features which gets disabled but it not mentioned in the warning message is the "Wrap mouse cursor around left/right monitor edges" and "Prevent mouse cursor from snagging on unaligned monitor edges". It might be worth updating the warning message, when disabling the application hooks, to include a couple of more features which gets disabled, or possible link to a webpage where it is described what happens should the user disable the application hooks.
Since this problem seems to stem from some .dll files I would verymuch like to know if there is a way to fix the files so I can enable the application hooks again.
When looking at the error message displayed it looks like something with Displayfusion corrupting the file.
Quote:
... the binary is unsigned, contains an untrusted signature, or has been corrupted or tampered with.
Edit: Add other disabled features and reformulated the last part
Is this on a company computer? I believe that when Application/Device Guard is enabled, Windows will forcefully terminate UWP apps if they get a DLL injected.
Ok, you might need to check with your IT staff to see if they can add our code signing certificate to the allowed list for device guard then. There isn't anything we can do from our end to resolve this, aside from disabling the hooks, which as you noticed comes with some reduced functionality
