dabluebery
5 discussion posts
Hello,
Fantastic product until it exploded over the weekend. I installed a Windows Update and DisplayFusion no longer works at all. At startup it crashes immediately, saying "Display Fusion has stopped working," and it doesn't come up with an answer as to why.
I uninstalled fully and reinstalled, as well as a system restore to every possible point in the past to see if I could get it to work again. But alas, nothing doing. What steps should I take to be back in business?
Thanks.
dabluebery
5 discussion posts
I should add it's a Windows 7 64 bit system.
It may be a .NET Framework issue. There are a couple of things you can try:
- Uninstall .NET Framework 4 if you have it installed, just to see if that makes any difference at all. It should work fine with .NET Framework 4, but for troubleshooting, let's try and test without it.
- At an elevated command prompt, run "sfc /scannow". This will repair Windows system files, including the .NET Framework versions that are built into Windows 7.
Thanks!
dabluebery
5 discussion posts
I uninstalled .net 4 and get the same result.
But when I restarted the computer to complete the uninstall, I got an error message at startup:
Could not load "sortbls.nlp" which is apparently a .net 2 file or whatever. I've done nothing to fix it but suspect the problems may be related. DisplayFusion still doesn't work.
Will work on the next set of instructions now.
dabluebery
5 discussion posts
I've done the "sfc / scannow" and have the following results:
The verification was 100% complete, and the windows resource protection did not find any integrity violations.
And display fusion still doesn't work with the same problem.
Ok, and if you reinstall .NET Framework 4, does that help at all?
dabluebery
5 discussion posts
I did a new Windows Update with a .net framework update bundled in and it now works fine. What should I do to prevent a problem like this in the future?
Unfortunately I don't think there's much you can do to prevent it. Sometimes the .NET Framework updates can have a minor issue that messes up certain parts of the .NET Framework, and when applications that use those parts try to access them, then they run into issues as well.
Thanks for the follow-up though, glad to hear it's working now.