DaVinci Resolve Frozen on Splash Screen: Every Real Fix

Is it actually frozen, or just slow?

Worth ruling out before you change anything, because forcing a quit on an app that was thirty seconds from finishing wastes more time than it saves.

Resolve does real work behind that splash screen, and some of it legitimately takes longer than you'd expect. The first launch after any update rebuilds internal indexes. A large project library, dozens or hundreds of projects across multiple databases, takes longer to enumerate than three test projects on a fresh install. A network-attached database adds round-trip latency the splash screen has to wait out. None of that is a freeze. It's just slower than the five seconds you're used to.

The test is activity, not time. Open Task Manager on Windows or Activity Monitor on Mac, find the Resolve process, and watch its CPU, disk, and GPU columns for thirty seconds. If numbers are moving, even a little, it's working. If everything reads flat, at or near zero, with the status text unchanged, that's frozen, not busy.

A splash screen with moving disk or CPU activity underneath it is working, not frozen, no matter how long the same words have been on screen. Give it a genuine two to three minutes on a first launch after any update before you assume something's wrong.

Is your GPU driver the problem?

Start here. It's the single most common cause across every breakdown of this issue, and it costs you nothing to check first.

Resolve initializes a GPU context, CUDA on Nvidia, OpenCL or Metal depending on platform, extremely early in its launch sequence, well before the interface appears. If that initialization hangs instead of failing cleanly with an error, the splash screen just sits there, because the next step in the sequence is waiting on a handshake that's never going to complete. One troubleshooting guide puts the fix bluntly: "If Resolve crashes on startup, start with OFX plugins, GPU drivers, and corrupted preferences," per Vagon's guide to DaVinci Resolve crashes and fixes, and the same order applies to a freeze that never quite becomes a crash.

The fix is a clean driver install, not a routine update:

1. Note your exact GPU model and current driver version before you start.
2. Download the newest driver directly from NVIDIA, AMD, or Intel's own site, not through Windows Update and not through a laptop manufacturer's utility, both of which lag behind and sometimes repackage drivers in ways that leave old files behind.
3. Run a clean install if the installer offers one. On Nvidia, choose the Studio driver over Game Ready when given the option, since Resolve 21's own requirements name the Studio branch specifically.
4. Reboot fully before relaunching Resolve. A driver swap that doesn't survive a restart hasn't actually taken effect yet.

A driver installed through Windows Update is not the same driver as one installed straight from the manufacturer, even when the version number looks identical. Windows Update packages and schedules driver changes on its own, silently, which is exactly the kind of surprise that turns a machine that launched fine on Friday into one frozen on its own splash screen Monday morning with nothing you touched yourself.

If the freeze started right after a driver update specifically, and a fresh install of the newest driver doesn't fix it, rolling back one version is a legitimate next step, not a last resort. Our AMD GPU not detected guide covers the deeper driver troubleshooting path, including the AMD-specific cleanup utility, in more depth than fits here.

Are DaVinci Resolve Control Panels installed without the hardware?

This one catches people who installed everything Blackmagic offered during setup, thinking more software couldn't hurt.

DaVinci Resolve Control Panels is a separate driver package that lets Resolve talk to physical Blackmagic hardware, the Speed Editor, the Micro Color Panel, the full Advanced Panel. Install that software and never plug in the actual panel, and Resolve's startup sequence scans for a device that isn't there. One breakdown of the issue explains exactly why that scan can stall the whole launch: "When you launch Resolve, it looks for the control panel device, which doesn't exist, and because of this, Resolve won't open," per beginnersapproach.com's fix list.

Check whether you actually have this installed:

• Windows: Settings > Apps > Apps & features, search "Control Panels" or "Blackmagic," and remove it if you don't own a physical panel.
• Mac: Check /Applications for a DaVinci Resolve Control Panels Setup or similar package, and use its own uninstaller if present, or the general uninstall approach covered in MacPaw's guide to uninstalling DaVinci Resolve on Mac.

If you do own a panel and this is the cause, the fix flips: confirm the panel is actually connected and powered before launching Resolve, try a different USB port or cable, and only remove the software if you've genuinely stopped using the hardware.

Software that scans for hardware you don't own is a startup hang waiting to happen, and it's one of the easiest causes on this whole list to rule out. Two minutes in Apps & features tells you definitively whether this is your problem or not.

Did Fairlight or a new audio device cause the hang?

If the status text specifically says "Loading Fairlight" or "Loading Audio Plugins" and stops right there, this is your lead, not a coincidence.

Fairlight, Resolve's audio page, initializes every audio device Windows or macOS currently sees, your speakers, a USB interface, a Bluetooth headset, a virtual audio driver from a conferencing app, during startup. A device that's misbehaving, was just plugged in for the first time, or is running a driver with a known conflict can make that initialization hang indefinitely instead of timing out. This is documented across multiple Resolve versions and platforms, not a one-off: users have reported the exact freeze on the "Loading Fairlight Page" stage going back several major releases, with fixes ranging from disconnecting a newly added audio interface to closing background apps that grab the audio subsystem, like Discord, before relaunching.

Work through this in order if Fairlight is where you're stuck:

1. Unplug any audio device you added recently, a new interface, headset, or capture card, and relaunch.
2. Close background apps known to interact with system audio, video call software and voice chat apps chief among them, then relaunch.
3. Check for a pending update to your audio interface's own driver, separate from your GPU driver entirely.
4. As a temporary test, switch your OS's default audio output to a basic built-in device before launching Resolve, to see whether the hang follows the device or stays with Resolve.

A splash screen that specifically freezes on "Loading Fairlight" is naming its own bottleneck, not being vague about it. That's a rarer cause than a GPU driver, but it's also one of the fastest to confirm, since unplugging one USB device and relaunching costs you thirty seconds.

Is antivirus or Windows Defender blocking Resolve?

Security software doesn't usually announce that it's the problem. It just quietly refuses to let Resolve do something, and the splash screen sits there waiting for a green light that never comes.

The mechanism is straightforward once you see it named: "Security software can block Resolve from writing preferences, loading GPU libraries, scanning plugins, or accessing the project database," per techbloat.com's DaVinci Resolve troubleshooting guide. Windows' own Microsoft Defender is a documented case of this specifically, with a Blackmagic Forum thread on Microsoft Defender blocking DaVinci Resolve describing the app appearing "suspended" in Task Manager with high antimalware service activity right before it drops out entirely. Windows' Controlled Folder Access, a separate ransomware-protection feature from Defender's real-time scanning, adds its own version of the same block if Resolve hasn't been explicitly allowed to write into folders it protects.

1. Open Windows Security > Virus & threat protection > Manage settings, and temporarily turn off Real-time protection, then try launching Resolve.
2. If that fixes it, don't leave protection off. Instead add an exclusion for the DaVinci Resolve installation folder and your cache/project database locations, then re-enable real-time protection.
3. Check Controlled Folder Access under the same Virus & threat protection settings, and either allow DaVinci Resolve as an app explicitly or confirm your cache and project folders aren't inside a protected location.
4. If you run third-party antivirus alongside or instead of Defender, temporarily disable it fully, not just real-time scanning, since some suites intercept more aggressively than Defender does.
5. Check for an active VPN and disconnect it as a test. A Blackmagic Forum thread on Resolve hanging at the splash screen specifically traces one case to a VPN blocking the project window from ever appearing, with the freeze clearing the moment the VPN was disabled.

Security software doing exactly what it's designed to do, blocking an unfamiliar write or network request, looks identical to a genuine freeze from the outside. Testing with protection briefly off is the fastest way to tell whether you're fighting Resolve or fighting your own antivirus.

Are Windows runtime components missing or corrupted?

This cause is less common than a driver or a security block, but it's worth knowing about because no amount of Resolve-specific troubleshooting fixes it. The problem isn't in Resolve at all.

Resolve depends on Microsoft's Visual C++ runtime libraries being present and healthy underneath it. Per one breakdown of this exact failure mode, "Resolve and its supporting services use Microsoft Visual C++ runtime libraries. Even if they already appear installed, repairing them can replace missing DLLs and fix broken registry entries," according to techbloat.com's guide. If a Windows update, a botched uninstall of another app, or disk corruption damaged one of those runtime files, Resolve can hang at the exact point where it tries to call into that library, with no error dialog naming the actual culprit.

1. Open Control Panel > Programs and Features, find every "Microsoft Visual C++ 2015-2022 Redistributable" entry, and use the Repair option on each rather than uninstalling first.
2. If repair isn't offered, uninstall and reinstall the current x64 and x86 redistributables directly from Microsoft's own site, not a third-party mirror.
3. Run sfc /scannow from an elevated Command Prompt to check for and repair corrupted core Windows files.
4. Follow it with DISM /Online /Cleanup-Image /RestoreHealth if System File Checker reports problems it couldn't fix on its own.
5. Reboot and try launching Resolve again.

This is a lower-probability cause than the driver or security fixes above, so it's worth trying after those, not instead of them. But if you've worked through the more common causes and nothing changed, this is the next place to look before a full reinstall.

Is a leftover Resolve process blocking the launch?

Sometimes the fix has nothing to do with drivers, security, or corruption. It's that DaVinci Resolve is already technically running, just invisibly, and your new launch is colliding with the ghost of the last one.

This happens most often after a previous crash or a forced shutdown that didn't fully release the process. You double-click the icon, the splash screen appears, and it sits there because a second copy of Resolve is trying to claim resources, ports, or files the first, still-running copy already holds.

1. Open Task Manager (Windows) and click the Details tab, or Activity Monitor (Mac) and search for Resolve.
2. Look for any entry named Resolve.exe, DaVinci Resolve, or similar, including ones showing 0% CPU that look idle rather than stuck.
3. Right-click and End Task (Windows) or select and Force Quit (Mac) on every instance you find, not just the newest one.
4. Wait about ten seconds for Windows or macOS to fully release the process, then launch Resolve fresh, once, and let the splash screen run its course without clicking the icon again.

Clicking the desktop icon repeatedly while the splash screen sits there is one of the most common ways people accidentally create this exact problem for themselves. Each click can spawn another launch attempt on top of the one already stuck, so by the time you check Task Manager there might be two or three Resolve processes fighting over the same startup checks instead of one.

Launching DaVinci Resolve a second time while the first launch is still stuck doesn't speed anything up, it usually multiplies the problem. One clean launch, from a fully quit state, beats five impatient double-clicks every time.

Is license or activation checking the thing that's actually stuck?

If your status text reads "Checking Licenses" specifically, and nothing else, you're looking at a narrower problem than a generic freeze, and it's often tangled up with hardware you wouldn't expect.

This exact symptom has a long history on Blackmagic's own community, and it's rarely about your license being invalid. It's about the check itself hanging on the way to a dongle or an activation server. A Creative COW forum thread on Resolve stuck at 'Checking Licenses' during startup shows how far the actual cause can be from anything license-related. Forum member Kelly Chen traced their own version of this freeze to a completely unrelated piece of hardware, a CalDigit USB 3 dock, describing the eventual fix: "Contacted Caldigit, and they suggested I do a Repair disk permission using disk utility and presto, Davinci loads up. Now I have best of both worlds." Another poster in the same thread, Pepijn Klijs, reported a related symptom on a Hackintosh setup, where "Resolve seems to see the dongle after a fresh boot, but if I quit resolve and open it again, my licence/dongle seems to be gone," pointing at a kernel extension conflict rather than anything wrong with the license itself.

The pattern across that whole thread: a USB dongle detection check can get blocked by an unrelated USB device, driver, or docking station sitting on the same bus, and the splash screen has no way to tell you that, since as far as Resolve knows, it's still waiting for a normal answer.

1. If you're on a dongle-based Studio license, unplug the dongle, plug it directly into the computer rather than through a hub or dock, and relaunch.
2. Disconnect other USB peripherals temporarily, especially docks, hubs, and external drives, then reconnect them one at a time once Resolve launches cleanly, to isolate which one was conflicting.
3. On Windows, check Device Manager for any USB controller showing a warning icon, since a flaky USB driver can block dongle detection the same way it blocked Kelly Chen's CalDigit setup.
4. If you're on an activation key rather than a dongle, and you're behind a corporate network, domain controller, or an active proxy, that network path can stall the online activation check specifically. Try tethering to a phone hotspot as a test, or disable the proxy temporarily.
5. If none of that clears it and you suspect the license itself, not just the check, is the actual problem, our license already in use guide covers activation conflicts and the automatic recovery process in full.

A splash screen stuck on "Checking Licenses" is often a USB or network problem wearing a licensing costume. Rule out the hardware and the network path before you assume anything is wrong with the key or dongle itself.

Is a corrupted preferences file or cache the cause?

If you've ruled out drivers, control panels, security software, and a stuck license check, and the freeze is consistent, same stage, every single launch, this is next.

Resolve reads its preferences file early in the startup sequence, before the interface exists to show you anything went wrong. A single corrupted value in that file, often left behind by a previous crash mid-write, can stall the read entirely instead of failing with an error you could act on.

The fix doesn't touch your projects, since preferences and your project database live in completely separate places on disk.

1. Fully quit Resolve and confirm no process remains, using the Task Manager or Activity Monitor check from earlier.
2. On Windows, navigate to C:\Users\[YourUsername]\AppData\Roaming\Blackmagic Design, find the DaVinci Resolve folder, and rename it to DaVinci Resolve.orig rather than deleting it outright, so you can restore it if this wasn't the cause.
3. On Mac, press Command+Shift+. to reveal hidden files in Finder, navigate to ~/Library/Preferences/Blackmagic Design, and rename the DaVinci Resolve folder the same way.
4. Launch Resolve. It creates a fresh folder with default preferences automatically, and this is the moment a corrupted-preferences freeze clears.
5. If the freeze persists after a clean preferences folder, per one Blackmagic Forum thread on the fix for a stuck splash screen, the next step is renaming the equivalent folder under C:\ProgramData\Blackmagic Design on Windows as well, since some settings live at the system level rather than the user level, then reinstalling the current version over the top.

Renaming the preferences folder does not touch a single project file, because Resolve stores your edits in an entirely separate database, not inside the settings it's failing to read. That separation is exactly why this fix is safe to try even when you're not sure preferences are the actual cause. Worst case, you've reset your interface layout and recent files list, both of which rebuild themselves in seconds.

What's different about a splash screen freeze on Mac?

The causes above mostly apply on both platforms, but Mac adds a few of its own, tied to how macOS handles permissions and app signing.

macOS runs a Gatekeeper signature check on Resolve at launch, not just at install. A system update, especially a major macOS version bump, can invalidate that check for an app that worked fine the day before, and the splash screen stalls waiting on a verification that's failing silently rather than throwing the familiar "app is damaged" dialog you'd see at install time.

Full Disk Access is the other Mac-specific trap. Since Catalina, Apple requires explicit permission before an app can freely read and write across your drives, and Resolve genuinely needs that access for its cache, project database, and media. If that permission was revoked, by a fresh macOS install, by resetting privacy settings, or by never being granted in the first place on a new drive, Resolve's startup checks that touch disk can hang waiting on a permission prompt that's sometimes rendered behind the splash screen itself rather than in front of it, invisible until you Command-Tab away and back.

1. Open System Settings > Privacy & Security > Full Disk Access, and confirm DaVinci Resolve is listed and its toggle is on. If it's missing, click the plus button and add it manually from /Applications.
2. Command-Tab through your open windows before assuming the freeze is real. A permission dialog rendered behind the splash screen is easy to miss and will sit there indefinitely until you click it.
3. Open Console (in /Applications/Utilities) and check Diagnostic Reports for a fresh crash or hang report naming Resolve, since macOS's own crash reporter is sometimes more specific than Resolve's internal log about which component stalled.
4. If Gatekeeper is the suspect, right-click the DaVinci Resolve app in Finder, choose Open, and confirm through the dialog macOS shows, since this forces a fresh signature check outside the normal double-click launch path.
5. As a last resort specific to Mac, create a new, temporary admin user account and try launching Resolve there. If it launches cleanly in a fresh account, the problem lives in your account's own caches or permissions, not the Resolve installation itself, which narrows the cleanup dramatically.

Remember too that DaVinci Resolve 21 requires an Apple Silicon Mac running macOS 15 Sequoia or later, per DaVinci Resolve Club's breakdown of Resolve 21's system requirements. If you're troubleshooting a splash screen freeze on an Intel Mac, stop. That machine can't run Resolve 21 at all, and no permission fix or preferences reset changes that. DaVinci Resolve 20 is the newest version available on Intel hardware.

A frozen splash screen on Mac hides behind the same logo as Windows, but the actual blockage is more often a permission macOS is silently waiting on than a driver. Check Full Disk Access and hidden dialog windows before you spend time on anything else Mac-specific.

Could a third-party OFX plugin or LUT pack be the trigger?

Resolve scans its plugin folders during startup, before you've opened anything, to register every effect and LUT so they're available the moment a project loads. A plugin that's incompatible with your current Resolve version, one built for Resolve 19 and never updated for 21, can hang that scan instead of failing gracefully past it.

This is a genuinely common cause right after a major version upgrade specifically, since plugins that worked fine on the previous release don't automatically stay compatible.

1. Move everything out of the shared OFX plugins folder temporarily: C:\Program Files\Common Files\OFX\Plugins on Windows, /Library/OFX/Plugins on Mac.
2. Also check for third-party LUT packs installed into Resolve's LUT folder, since a malformed .cube file can occasionally stall the same scan.
3. Relaunch Resolve with both folders empty. If the splash screen clears, a plugin or LUT was your problem.
4. Move items back in small batches, relaunching between each batch, until the freeze returns. Whatever you just reintroduced is the culprit.
5. Check the plugin vendor's site for a Resolve 21-compatible build before giving up on it entirely. Many plugin makers ship compatibility updates within weeks of a major Resolve release.

This is the same isolation method covered for mid-session crashes in our DaVinci Resolve keeps crashing guide, just applied one step earlier in the app's lifecycle, before a project is even involved.

Which splash screen text tells you which fix to try?

If Resolve's status line changed before it froze, that text is a direct pointer, not decoration. Match what you saw to the row below.

The table is a shortcut, not a verdict. If your symptom matches two rows, or the status text is one you haven't seen listed here, work through the full order below instead of guessing between them.

What's the right order to troubleshoot this from scratch?

Work through these eight steps in order and stop the moment the splash screen clears:

1. Confirm it's genuinely frozen, not slow, using Task Manager or Activity Monitor's activity graphs.
2. End every leftover Resolve process before attempting a fresh, single launch.
3. Update your GPU driver directly from NVIDIA, AMD, or Intel, with a clean install, then restart the machine.
4. Remove DaVinci Resolve Control Panels software if you don't own a physical panel.
5. Temporarily disable antivirus real-time protection and any active VPN, then relaunch as a test.
6. Rename the DaVinci Resolve preferences folder to force a clean rebuild.
7. Pull third-party OFX plugins and LUT packs out of their folders temporarily.
8. On Mac specifically, confirm Full Disk Access is granted and check for a hidden permission dialog behind the splash screen.

If you've worked through all eight and the freeze is still identical, every time, on the exact same machine, that points toward either a genuinely damaged installation or a runtime component issue on Windows, both covered in the next section.

What if none of this works and you need a clean reinstall?

A full, clean reinstall is the actual fix for a genuinely corrupted installation, not the default fix for everything above. Reach for it after the eight steps, not before them, since most splash-screen freezes clear well before you get here.

1. Uninstall DaVinci Resolve through Apps & Features (Windows) or the app's own uninstaller and by dragging it to Trash (Mac). MacPaw's guide to uninstalling DaVinci Resolve covers the Mac-specific leftover locations worth checking afterward.
2. On Windows, manually check C:\Program Files\Blackmagic Design, C:\ProgramData\Blackmagic Design, and C:\Users\[YourUsername]\AppData\Roaming\Blackmagic Design for anything the uninstaller left behind, and delete those folders. On Mac, check ~/Library/Application Support/Blackmagic Design, ~/Library/Preferences/Blackmagic Design, and ~/Library/Caches/Blackmagic Design.
3. Reboot before reinstalling, to release any file locks the old installation left behind.
4. Download a completely fresh installer from Blackmagic's own support and downloads page, not a cached copy from your Downloads folder that might itself be the source of a corrupted install.
5. Install and launch once, letting the splash screen run its full course without touching anything else on the machine at the same time.

Your project database survives this entire process untouched, since it lives outside every folder listed above. A clean reinstall costs you nothing project-wise, only the time it takes to redo any preference customization you'd built up.

If a clean reinstall genuinely doesn't fix it, that's the point to contact Blackmagic support directly rather than keep guessing. Run the CaptureLogs utility from inside the DaVinci Resolve program folder to generate diagnostic logs, and send those along with your exact GPU model, driver version, and OS build through Blackmagic's support page. A genuinely rare hardware or firmware-level incompatibility is the remaining explanation once every software-side fix above has failed, and Blackmagic's own engineers can see patterns in your logs that no amount of local troubleshooting will surface.

How do you stop this from happening again?

A handful of habits keep this problem rare instead of recurring every few weeks.

• Install GPU drivers manually, from the manufacturer, on your own schedule. Never let a driver update land automatically the week before a deadline. If Resolve is working, that's not the week to accept whatever Windows Update or an auto-updater wants to push.
• Add DaVinci Resolve to your antivirus exclusions once, proactively, rather than discovering the block mid-launch on a day you needed to work fast.
• Skip installing Control Panels software until you actually own the hardware. It costs nothing to install it later, the moment you unbox a Speed Editor, instead of carrying a dormant scan that can freeze every launch until then.
• Don't double-click the app repeatedly if the splash screen seems slow. Give it two full minutes, checking Task Manager or Activity Monitor for activity, before you conclude it's actually stuck and force-quit it.
• Keep one known-good GPU driver installer on disk. If a fresh release ever causes this exact freeze, having last month's installer already downloaded turns a rollback into a five-minute fix instead of a hunt through a manufacturer's archive at the worst possible time.
• Update plugins alongside Resolve itself, not months later, especially right after a major version release when compatibility gaps are most common.

None of this makes DaVinci Resolve immune to an occasional bad driver release or a Windows update that changes something without asking. It makes the failure boring and fast to diagnose instead of a mystery that eats your whole morning.

The verdict

A frozen DaVinci Resolve splash screen is Resolve stuck partway through its own startup checklist, not a dead application and not a damaged project. A GPU driver problem is the most likely single cause, followed by a stuck license check, security software, and corrupted preferences, in roughly that order of likelihood. Work through the eight-step order above rather than reaching straight for a reinstall, since most of these clear at the driver or preferences step, long before you'd need to touch the installation itself.

DaVinci Resolve 21 shipped two stability patches, 21.0.1 and 21.0.2, within eight days of each other after launch, per RedShark News' coverage of the 21.0.2 update and Newsshooter's report on the same release, a reminder that a brand-new major version genuinely does ship faster than it gets battle-tested against every driver and hardware combination in the wild. If you're still on the original 21.0 release and this is a new problem, installing the current point release before anything else is a fair first move, not a stall tactic.

Once the splash screen clears and you're actually inside Resolve, the harder problem is usually the next one, a menu you don't recognize, a control a tutorial from two versions ago doesn't match anymore. TryUncle is a paid AI tutor for DaVinci Resolve on macOS, and its assistant, Uncle, watches your screen and points at the exact control you're missing on the Edit, Color, or Fusion page. It's not a launch-troubleshooting tool, so it won't touch your GPU driver or your preferences folder, but if that same kind of confusion follows you past the splash screen, check TryUncle for the current founder-pricing rate before deciding if it fits your workflow.