Blackmagic Forum

After leaving Resolve alone for a couple of months, I decided to try using it again to practice some color grading. On the first startup, it got to the "loading fairlight page" step, and then stopped. Eventually it would stop responding and I would have to close it manually. Here are the steps I have tried:

1. Uninstall Resolve and Reinstall with newest (16.2.3)

2. Revert back to 16.0

3. Try installing on C: drive instead

4. Completely disable firewall to see if ports were the problem

5. Uninstall possibly problematic programs: VPN, Native Instruments, all torrent applications

6. Try multiple different nVidia drivers

7. Disable Hyper-V

8. Make sure it is running with the dGPU (nVidia Optimus)

9. Every solution I could find on this forum

10. Many more that I cannot remember right now

Everything listed above has not fixed the problem. I have also used procmon to try to see if there are any other possible conflicts with networking. None found.

System information:
i9-9880h
GTX 1650
64gb DDR4

Resolve (NOT Studio)

Windows Version 2004 (OS Build 20150.1000)

Cannot get to the resolve about menu for version info. I have tried the newest possible installer and the ones for 16.1 and 16.0.

All Needed Files:
https://drive (dot) google (dot) com/drive/folders/1_0pL-yZQvit9Om_HXuM914dtCEliIivF?usp=sharing

Couple things come to mind for me. May be extreme, but I have high confidence that it would work.

1. Always install applications to their default location.
2. Leave My Documents in it's default location.
3. An edit system should be dedicate to editing. Nothing extraneous installed. No email, office, games, etc. Perform non-editing tasks on another machine.
4. Use a 1000 or 2000 series nVidia GPU with the most recent Studio driver.
5. Don't use USB audio.

I'm also speculating that you didn't have item 3 in place when you started, and I have to wonder if instead of removing things, it would be better to perform a Clean Install of Windows.

I had the exact same problem when I first started using Resolve.
The problem was fixed by updating my video drivers.
The 'latest/greatest' game driver can often cause problems with Resolve,
and yours may have been updated by you or Windows update since you last used the software.
As Jim mentions, try the Nvidia studio drivers - they are heavily tested to work with software like Resolve.

The issue is he is using the latest windows insider build just like me. The problem is OS related. That version of windows doesn't like resolve for some reason. Hopefully they will fix it soon, for now revert to the windows before this one and you wont have any issues.

Mac* user here experiencing same problem.

I'm running macOS High Sierra 10.13.6. Actually an OSx86 / Hackintosh (I can see your eyes rolling) with NVIDIA GeForce GTX 1080 Ti GPU and 3.7GHz coffee lake processor.

DaVinci Resolve Studio 16.2.5 from the Apple App Store hangs at splash screen "Loading Fairlight page" indefinitely.

Application crash log provided as a .md text doc.

###
P.S.:
- Did the crash log upload correctly?
- Tried upgrading OS to Catalina to get around this bug:
- - This resulted in GPU incompatibility. So now I just bought a new AMD GPU and am selling my 1080 at half price...for more than the price of the new AMD one

I took a look at my own logs and noticed several things trying to load from c:\programdata this is NOT a good practice to do ProgramData is typically used while installing a program or for very minor things like determining if the software has already been installed on a system, it should never contain any data that the program requires to run.

This may explain several things from most forums on this issue:

Why installing an older working version of the software fails (because the program component causing the issue is in c:\programdata and is newer so wasn't overwritten)

Why some systems get the issue at different times (ProgramData can be cleared or overwritten at random points depending on software installed)

So maybe try uninstalling resolve, then delete or rename it's folder in c:\programdata, reinstall and see what happens.

Regards,
Damien

Slipoch wrote:I took a look at my own logs and noticed several things trying to load from c:\programdata this is NOT a good practice to do ProgramData is typically used while installing a program or for very minor things like determining if the software has already been installed on a system, it should never contain any data that the program requires to run.

This may explain several things from most forums on this issue:

Why installing an older working version of the software fails (because the program component causing the issue is in c:\programdata and is newer so wasn't overwritten)

Why some systems get the issue at different times (ProgramData can be cleared or overwritten at random points depending on software installed)

So maybe try uninstalling resolve, then delete or rename it's folder in c:\programdata, reinstall and see what happens.

Regards,
Damien

I've been facing these issues (OP) with Fairlight Locking and not completing DRS opening. Previously (BTW-Not in any BETA Programs with any products) I troubleshot from the beginning: MB BIO, AMD Processor and Chipset. Nvidia, and my dog's license. I still had the same lockup. As SPILOK advised, I deleted, not renamed, "ProgramData" and reinstalled DRS current and it has worked flawlessly. HOWEVER, I did not have a Localdb backup and all those were erased or somehow trashed on the reinstallation. My only word of warning would be backup your LocalDiskdb.

Test the SLIPOK procedure before you reinstall your localbd project, etc. WHY? Because if the SLIPOK process produces a completely functioning DRS (or free) and then there are issues after you reinstall your db then you know it is something specific in your db or a specific or possibly a number of Projects within the db giving you the problem.

Thank you SLIPOK!!!!

I used the CaptureLogs.bat script in the Resolve install directory to discover Resolve needed a port. Using another network monitoring tool, found that Resolve was attempting to listen on port 5432 which was in use by the VMWare Player. I uninstalled VMWare player and now Resolve works.

A few afterthoughts and experiences; my machine would "hang" at Fairlight (even with b17) for reason unknown. Sometime it would hang for what seemed forever considering the hardware I'm using, then one night I just sat and closed my eyes. After some period of time it had moved passed Fairlight and continue with a normal and fully operational tool (DRS). I'd use it a bit shut it down, restart the app and it started quite normally. Since then I have regularly performed the following with almost no more Fairlight issues. If I did then I'd do the following...

After a clean install of DRS, I'd go to C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve - open the Troubleshooter for the executable and give it "Additional Permissions" continue through the test and saved the Compatibility menu. Then I'd go back into the troubleshooter for "Resolve.exe" and perform an OS test letting Win10 pick the version, typically starts with Win 8 - work with DRS for a bit, if no hitches save the config.

After that "*Circus*" I've not had issues with Fairlight when in startup of DRS I would just continue my work.

*IF* I did (have an issue) I'd go here C:\Program Files\Blackmagic Design FOLDER and make sure the permissions for System, Admin, and Admins had complete operational read, write, execute, and the rest, never Special Permissions. And that all FOLDER and Subfolders inherited the permissions.

I don't know if any of that makes for good user practices or not, but I can say I typically have no issues after the very last "Hail Mary Pass".