Dwaine Maggart wrote:Seems like SOMETHING must have changed on the system, to create such a dramatic difference in behavior.
We keep 5 good logs and 5 crash logs in a log archive. None of those show your last working state, so I guess you must have restarted the system lots of times after it was last working? All the logs are from 3-31.
The 5 crash logs all stop at the identical point. Is Resolve crashing to the desktop, or is it hanging, and you are killing it in Task Manager?
The 5 non-crash logs all appear that Resolve launched, but then almost immediately exits. Is Resolve getting to the Project Manager page half the time you've recently launched it? And If so, what happens at that point?
Based on other solutions posted in this thread, one user had a VPN causing a Resolve hang issue. You appear to have a VPN running. You might try stopping that as a test to see if it has any effect.
Another user reports that having Hyper-V enabled caused a Resolve issue. You appear to have Hyper-V enabled. You might disable that to see what effect that has.
Other users have reported USB and BlueTooth peripherals causing Resolve issues. If you have anything other than a wired USB mouse and keyboard connected, disconnect them to see what effect that has.
Hi Dwaine,
yes, that's correct. After the first time it doesn't run anymore I thought maybe it's time for a restart, then I plugged in the audio interface again, then a restart, then diabled the other audio devices, newest drivers and some other tests and after every change I started resolve to hopefully find the problem... nothing worked.
It's always the same behaviour. I start resolve, it gets to the point "Fairlight page loading" and stays there forever, no matter if waiting 30 seconds or half an hour (yes that's also something I already tested
). After clicking on the window it get's in this state and I just let Windows close it for me:
- 1.png (319.97 KiB) Viewed 36752 times
As far as I know I have no VPN running. The only thing I found was the windows setting here:
- 2.png (16.28 KiB) Viewed 36752 times
I turned off both settings, but it made no difference.
Just for completness... I have no bluetooth or similar cordless devices attached/connected.
Then I came to the virtualization. I first disabled the CPU virtualization (SVM Mode) in the bios. But this also made no difference. Then I turned off the the Hyper-V settings here:
- 3.png (24.43 KiB) Viewed 36752 times
And indeed it works now! Now VirtualBox isn't running anymore without Hyper-V, but that I have at least the possibility to turn it on and off is something I could live with.
But still a bit strange, since it was running many times with Hyper-V turned on during the last months. Could you inspect this on your development/test systems maybe? I guess I'm not the only person who has/had this problem. Maybe it can be fixed in the programming centrally for everyone. If I can help you with my system (new logs or something) please don't hesitate to get back to me.
Thanks
Marcus