- Posts: 5
- Joined: Thu Dec 17, 2020 3:48 pm
- Real Name: Andrew Hearn
Solved! Eventually I solved this by unmapping a network drive that was being unresponsive.
Edit: a bit more info - I tried all sorts to fix this - in the end I noticed that if I left Resolve long enough (~15 or 20 minutes) then it would eventually load.
It seems like a bug in Resolve tried to look at all drives on the machine but does not time-out very quickly - and because my mapped network drive was unresponsive it blocked Resolve from loading.