DF start in task manager but close after few secondes with no error message

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

PHILIPPE B GAUTHIER

2 discussion posts

I installed a new software yesterday and after the restart windows asked, DF stopped working. When I look at task manager, DisplayFusionService is running, but if I kill it I can't reopen it. When I click to open any of these :
DisplayFusion
DisplayFusionCommand
DisplayFusionHookAppWinXXXX(5032, 5064, 6032, 6064)
DisplayFusionService
DisplayFusionSettings

they all do the same thing, they start up on task manager and after a few secondes they close. I tried to follow this tread
http://www.displayfusion.com/Discussions/View/not-working-in-windows-7-ultimate/?ID=4074608e-dc7e-4a0e-9d5f-02298272c3c3
try to reintall, try windows restore point, try to get a debug log but didnt work. I then did windows update, all witout success.

I'm now stuck to solve it.

My system is Windows Vista Premium Family Edition 64 bit, have 2 NVidia video card (I read somewhere in tread that it could be that but I didnt find the services mentionned on that tread), ererything is up to date, DF 7.1.
It stopped working after installation of Proteus 8 demo

Thank you
Phil

Apr 8, 2015 • #1

That usually indicates a .NET Framework issue. There are a few more things you can try:

Run the following at a command prompt: sfc /scannow
Check for Windows Updates, and install any .NET Framework updates available

Failing the above, try the following:

Install the .NET Framework 4 if you don't have it already: http://www.microsoft.com/en-ca/download/details.aspx?id=30653
Extract the attached ZIP file to a temporary folder on your drive
Copy the files from the temporary folder into the C:\Program Files (x86)\DisplayFusion folder, overwriting the existing files
Try launching DisplayFusion

Hope that helps!

Apr 8, 2015 (modified Jul 29, 2022) • #2

PHILIPPE B GAUTHIER

2 discussion posts

Everything failled to make it work until I reinstall Framework 4.5. Now all works like a charm.

Thank you
Phil

Apr 8, 2015 • #3

No problem, glad to hear it! Did you also have to use the manifest files I attached, or was simply re-installing .NET Framework 4.5 enough to fix it?

Apr 9, 2015 • #4