Blackmagic Forum

PS: The last few instances were resolved after I removed the Nvidia USB-C driver component with each GPU driver update(s) ... My GPU does not have a USB-C port so I wont miss it anyways...

Can you describe how you did that?

G0bble wrote:PS: The last few instances were resolved after I removed the Nvidia USB-C driver component with each GPU driver update(s) ... My GPU does not have a USB-C port so I wont miss it anyways...

I am extremely interested in finding out "what that is" and "how did you do it" please.

It is an option seen in Custom Install of the Driver and installed by default in Express Install mode I guess - If you already installed it you can remove it from "Add/Remove Programs"...

G0bble wrote:I is an option seen in Custom Install of the Driver and installed by default in Express Install mode I guess - If you already installed it you can remove it from "Add/Remove Programs"...

NvidiaDriverInstall.png

Thank you

Hi, I had a similar issue with Resolve 17 beta 5 getting stuck on the cut page and it would not start, the way to fix it was removing the Universe plugins from Red Giant, as soon as I did, everything worked perfectly. Hope it helps.

I'm still seeing this issue and can only solve it by rebooting.

I had a mysterious recurrence of this issue a few days back that required two warm reboots to auto-fix. Go figure ...

Could someone please post a link to a page that specifies the logs required, how to produce them, and where to upload them to? I would like to add my own sad story to this thread.

Go here:

viewtopic.php?f=21&t=90190

Scroll midway down to Logs. That explains how to create log files, both from running systems and systems that won't run.

Then scroll down near the bottom to this section: Posting on the forum / Contacting Support for DaVinci Resolve and DaVinci Resolve Studio. That explains how to provide system information and how to post all this info to the forum.

Thanks Dwaine for the info on logs. The attached "logs.zip" contains the following 3 items:

• Zip/Folder: DaVinci-Resolve-logs-20210116_151635 (from CaptureLogs.bat)
• File: DxDiag.txt (from DxDiag)
• File: 1-15-21.nfo (From Windows "System Information")

Problem statement:

1. Run Resolve Studio (v16.2.8)
2. Splash screen gets to Loading Fairlight Page and does not progress

I have tried a few things from the first few pages from this thread to no avail, until I realized how old those posts were. I do not have the Kill Switch option turned on for VPN (and am not even running the VPN when attempting to run Resolve). I did a full uninstall, then a reinstall of v16.2.8.

Thanks, Chris

PS: the instructions for obtaining the NFO for windows states to run "Windows System Information". This, for me, did not run intended app, but instead brings up the System control panel (which doesn't produce NFO files). The app you intend will come up when the following is typed "System Information" (without the "Windows" part). You might want to adjust your instructions on that.

First thing to try would be turning off Hyper-V.

If that doesn't help, send another log and NFO file with that off.

Dwaine Maggart wrote:First thing to try would be turning off Hyper-V.

If that doesn't help, send another log and NFO file with that off.

I went to turn it off to find that it's already turned off (see attached image below). Do the logs/info indicate that it's not off?

I see some info online about further disabling hyper-v components/services with powershell, but I have to ask: is this really reasonable to ask a customer to turn off operating system functionality to use Resolve? I haven't done virtualization on this box, but I have on previous computers and can see myself doing it here as well.

But I have paid for Resolve Studio, so I will try what you ask. Please just let me know what you see as still being turned on.

Chris

The logs show that a Hypervisor is active. It doesn't specify that the Hypervisor is Hyper-V, that's just the most common one that seems to be on.

And we don't know that the Hypervisor being active is the issue. But since it has been on occasion, the first troubleshooting step is to disable it, and see.

Dwaine Maggart wrote:The logs show that a Hypervisor is active. It doesn't specify that the Hypervisor is Hyper-V, that's just the most common one that seems to be on.

And we don't know that the Hypervisor being active is the issue. But since it has been on occasion, the first troubleshooting step is to disable it, and see.

I found "HV Host Services" in the Services applet and stopped the service (though it may restart at the next reboot). However, it was a little disconcerting when Windows prompted me with "Turning off HV Host Services [hypervisor] also stops the Container Manager Service."

I'm not sure how that's going to impact me in the future. However, that worked (for now, I've seen a lot of 'famous last words' in this thread) and Resolve Studio finally finished loading this time.

But I'm not happy that I have to disable a portion of the operating system to make a single app perform as it should. I trust that Blackmagic considers this a workaround and not an actual fix for the issue. Since it seems (from posts in this thread) to have continued being on issue in the v17 betas, I'm not hopeful. I hope that this message somehow makes it to management and/or dev teams.

Chris

The dev team and product management read all these posts.

Dwaine Maggart wrote:The dev team and product management read all these posts.

Thanks Dwaine,

I just came back to add: I don't have any Fairlight products and don't install those components, so it's just that much more frustrating for being a blocking issue (blocking until I learned the work-around that worked for me).

Thanks again,
Chris

Okay, well, sorry to be the latest victim of this locked up "rubbish" behavior, but I seem to be stumbling over the same boulder in the middle of my on ramp to using Resolve. And to "just wait", whatever the tech reasons under the hood, not my problem to resolve. If it is reaching out to USB devices, !!STOP!!. Unless you have one that is specifically configured. It's impractical to expect users to unplug ALL of their USB devices. In my case, in particular, where my sessions often, frequently, involve 2+ USB drives of one form factor or another, files open in half a dozen applications, etc, over the same. NOT GONNA HAPPEN. Go back to the drawing board and figure it out. Please.

I'm sorry I've got to follow up and also mention, it's been well over 30+ minutes now and STILL nothing. Frozen on the fairlight splash. I checked my task manager and it was well over 2+ GB allocated memory and releasing that memory steadily. From GOD knows WHAT before I checked just now. Sorry to be so blunt, but WTF does it need to allocate so much memory for during the splash screen?

It looks like the "Windows Defender Credential Guard" is responsible for the problems.

Disable Windows Defender Credential Guard and Davinci Resolve 16 starts without problems every time.

https://docs.microsoft.com/en-us/window ... ard-manage

Code: Select all

Delete the Windows Defender Credential Guard EFI variables by using bcdedit. From an elevated command prompt, type the following commands:
Console

mountvol X: /s
copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y
bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
mountvol X: /d

Restart the PC.


m3t4tr0n wrote:It looks like the "Windows Defender Credential Guard" is responsible for the problems.

Disable Windows Defender Credential Guard and Davinci Resolve 16 starts without problems every time.

I would not consider "is responsible for the problems" to be accurate, more like "you must cripple your security features, or CPU supported virtualization functionality, to make this video editor application work on your computer".

It's not a fix or resolution, it's a work-around, disabling something you may very well need just to get over design issues with Resolve.

PS: this work-around works for you and your particular hardware configuration, but if you dig through the history of this thread, you might find that this or similar changes did not work for others. Also, you may also find (as others did) that it may stop working for you at some point in the future.

Chris

You right. But I don't need Virtualization-based Security. I need my CPU supported virtualization functionality for third party virtualization software (eg. Virtual Box). With VBS enabled third party virtualization software works in "emulation mode".

But besides VBS, I also had to turn off secure boot to make Davinci resolve 16 work properly, and this is real security problem.

DaVinci Resolve ~ what a joke.

I installed v 16, it worked find for 2 weeks and now it takes 30 minutes to open.
I install v 17, same problem.

Why do you spend so much time and money to build such software and having this problem that cripple so many people. Can't find a solution on the internet.

I found the problem ~ my machine had 2 mounted cloud drives which were not responsive, because they were deleted previously.
But the mounting was still there. I suppose when DaVinci Resolve start, the software scan for all the drive existing on the machine and try to access them.
The OS take a while to time out and this block the software. And DaVinci does not deal with this issue well

If you can provide your NFO and logs as requested in the FAQs someone can help u set up ur system

I'm still having this fairlight hanging issue on DR17.

Surprisingly, rebooting my machine didn't fix it anymore, I had to do a subsequent complete shutdown.. On the next boot, it started as usual.
This is the second time happening in 2 days and fixed in the same way.

Why is it so hard to address this bug?

Hey guys!

Same problem over here, locking up at the Fairlight page.
I've been running the free version without ANY issues whatsoever.
Today I got my copy of Studio with the speed editor, and now I can't get into Resolve because of this problem.
NFO file attached.
But, I can't seem to be able to generate the DR log, Here's the error:



Help?

That's not an NFO file. That's a System Information File - Export .txt file. You need to do a File - Save to create a .NFO file.

For the Resolve CaptureLogs file, unzip the attached CaptureLogsOneDrive.zip file.

It unzips to CaptureLogsOneDrive.bat

Copy this file to C:\Program Files\Blackmagic Design\DaVinci Resolve

Then run the file.

I rebooted the PC and the problem went away... Haven't had it since.
I mean I also uninstalled and reinstalled everything to do with DR, but yeah!

Weird.

Thanks though!

That's usually what I do. Reboot until it works.

So I got the bug again now.

Might be because there's been a change of hardware, I installed a GoXLR today.
Or because I'm trying to open Resolve while being in a zoom call.
I'd really like to know what's causing it...

In a real world scenario you can't afford to waste time on this, you need to be using your time to work, right.

So, files.

If you disconnect the GoXLR, does Resolve launch?

Here I am with the same problem.

Additional information:
I worked with Resolve 17 Beta until yesterday evening, then I installed the Resolve STUDIO 17.1 over the existing installation. I still worked with it for some hours without a problem.
At night the last Windows 10 Update was installed.
Today when I started Resolve 17.1 Studio it crashed when the splash screen said "Loading Fairlight".
I deinstalled the Windows updates from last night with no result.
I did a lot of things I found on the internet with no result already (e.g. virus scanner and firewall are deactivated already).
I did a clean uninstall and installed version 16 - this would work, but not with my actual project databases.
As soon as I am back to my installation of 17.1 or 17.1 studio it crashes in both cases just as before.

I am in the middle of some projects (not fun projects but real business projects I need to finish soon) and after a whole day of trying I just hope to find help here - I'm tired and devastated!

I followed Dwaine's instructions for a clean reinstall.
Here you find the logfiles:
https://drive.google.com/drive/folders/ ... sp=sharing

Looking forward to hearing from you...

...update to my last post:
I did a fresh install of Windows 10 and just installed the actual graphic drivers and Google Chrome, before I installed DR Studio 17.1 - and still it crashes on "Loading Fairlight Page".

Now I don't have any idea left what to to...

New log- and NFO-files in the same GDrive folder: https://drive.google.com/drive/folders/1IDEEzRO6sj81NT_jPr8jAmqf2pmKkmle?usp=sharing

...aaaand another update:
I am using 2 monitors, connected with a docking station.
When I disconnect the docking station I can start the program. Even when I connect a single monitor to my laptop it starts. After DR is up and running, I can connect my laptop to the docking station again and it works. It seems once I passed a "special moment" of the starting progress, everything works.
But this is not a solution, it's a workaround.
Any hints what I need to do to get it working as usual (because it worked before)?

I just updated my chipset drivers today and DR 17.1 won't start anymore. I rebooted a few times and also uninstalled, re-installed DR.

Thanks

EDIT: this morning is working again

Hello again

I have installed Voicemeeter Banana last week and now DR is stuck again while loading Fairlight.

roughnecks wrote:Hello again

I have installed Voicemeeter Banana last week and now DR is stuck again while loading Fairlight.

DaVinci-Resolve-logs-042021_172546,31.zip

Any help here?
I cannot open DR anymore..

My first guess is that you have a USB device connected that is stopping Resolve from launching.

Remove all the USB devices from your system except a standard wired keyboard and mouse.

Remove any audio USB devices, including headsets.

Remove any video USB devices including web cams and USB HDMI capture dongles.

Remove any USB Bluetooth dongles.

17.1.1 was running on your system on April 2, so something you've done since then is causing an issue.

Hi,

I could do that but I haven't changed anything hw related, I have the same (usb) devices plugged in the same sockets.

Instead I just checked "Add and Remove Programs" and I installed VoiceMeeter on the 3rd of April, but I'd rather not uninstall it.

Dwaine Maggart wrote:My first guess is that you have a USB device connected that is stopping Resolve from launching.

17.1.1 was running on your system on April 2, so something you've done since then is causing an issue.

Ok, I didn't want to unplug my usb stuff and I didn't want to uninstall Voicemeeter, but in the end I did the latter about four days ago.
After the uninstall I tried booting DR any day without results, but then a few minutes ago it finally started.

Honestly I don't know what to think but I know now why it's called blackmagic design.

.. And today it's not starting anymore.

Yesterday I installed the Sound Library, launched DR and it was working fine. Today I rebooted 2 times already and it's not gonna launch, I even uninstalled the Sound Library.. No other changes were made to my system.

This is embarrassing.

I have this problem regularly and there's no rhyme or reason to it since my hardware's not changing between the times it starts and doesn't start.

What I do is if it doesn't restart after multiple reboots, I just leave it sitting at the Loading Fairlight screen. Sometimes it takes 10 minutes but it finally completes.

It sucks but that's been my usual troubleshooting steps.

pnguyen720 wrote:What I do is if it doesn't restart after multiple reboots, I just leave it sitting at the Loading Fairlight screen. Sometimes it takes 10 minutes but it finally completes.

Trying that right now; I've got nothing to lose, I guess

@pnguyen720 you're a genius! After 5 minutes it started, ahah

Better late than never.

17.2 seems to have it fixed, now I get to the Project Manager really fast even if it takes a lot longer to open a project

It's about the same time I had to wait before, to get passed on the fairlight loading page step.

Excellent news, if finally fixed. Will check it out.

Dwaine Maggart wrote:Assuming you are on a Windows system:

In a File Explorer window, go to:

C:\Program Files\Blackmagic Design\DaVinci Resolve

and run CaptureLogs

This will place a Resolve log file named similar to this on your Windows desktop: DaVinci-Resolve-logs-20181228_140434.zip (You may not see the .zip extension if your system is set to hide known extensions).


Then open Windows System Information and do a File - Save (Not a File Export), which will generate a .NFO file.

Place both those files on a file sharing site and provide links to the files here.

Hello,

I have been using Davinci Resolve 17 for a few months on my laptop without problem.
For a few days, I have encountered this issue: DR is stuck on the splash screen with the indication "Loading fairlight engine".
I read this entire post and tried all the tips mentioned but nothing works (firewall disabled, wifi disabled, virtualization disabled in BIOS, wait more than 30 minutes for DR to start, ...).

I’ve read other topics and tried:
viewtopic.php?f=21&t=144452&hilit=+loading+fairlight+engine+
viewtopic.php?f=21&t=144347&hilit=+loading+fairlight+engine+

I uninstalled all DR related components and reinstalled the latest version 17.2.2 but no improvement.

Attached are the necessary log and NFO files.

Thanks for your help.

Julien, french user.

Just installed DR 17.2.2 and am also stuck at "loading fairlight engine". Any ideas? I attached my log.

@Julien: The NFO shows a virtual graphics adapter, in addition to your Radeon iGPU.

If you open Device Manager, I think you should see the virtual graphics adapter under Display Adapters.

If you do see it there, right click it and select Disable Device.

If that doesn't help, send an updated Resolve log and NFO file with the virtual graphics adapter disabled.

@Dirk: Also need a Windows System Information .NFO file.