You fixed this warning last month. An update landed - Resolve, Windows or the driver - and the warning is greeting you again. Nothing new has broken; an update quietly reset something. Here is how to find which thing, fast.
A returning GPU warning feels like the problem was never fixed, but the pattern is well understood: three different updaters touch the GPU stack, and each can undo a piece of your fix. Resolve updates can re-run hardware detection and return the GPU settings to Auto. GPU driver updates present the card to the system as if new. And Windows Update occasionally replaces your carefully chosen Studio Driver with its own catalogue driver. The good news: your original fix still works - it just needs re-applying to whichever layer moved.
Before touching settings, answer one question: since the warning last behaved, did you update Resolve, the graphics driver, or Windows? Check Windows Update history and your driver app if you are unsure. Troubleshooting the layer that changed is three times faster than troubleshooting all of them, and reinstalling Resolve for a driver-layer reset is the classic waste of an afternoon.
Open Preferences, then System, then Memory and GPU. Updates can flip GPU Processing Mode and GPU Selection back to Auto - and Auto then re-makes the bad guess it made originally. Set the mode by hand (CUDA for NVIDIA, OpenCL for AMD on Windows, Metal on Mac), tick only your dedicated card, Save, and restart Resolve. For a large share of returning warnings, this is the entire fix, again.
Open your driver app - NVIDIA App or AMD Software - and read the installed version. If the version is older than the one you installed, or the Studio branding has vanished, Windows Update swapped your driver for its catalogue version. Reinstall the current Studio Driver from NVIDIA (or the current AMD package), restart, and the warning should clear. To slow the repeat performance, keep the driver reasonably current yourself - Windows mostly reaches in when the installed driver is very old or was flagged by a feature update.
Once it works again, take sixty seconds of insurance: note your processing mode, the GPU you tick, and the driver version in your phone or a text file. The next return - and on a machine with three updaters, there may be one - becomes a two-minute restore instead of a fresh investigation. And adopt the editor's update rhythm: update Resolve and drivers between projects, never mid-project, one at a time, so the culprit is always obvious and a deadline never depends on a same-day update behaving.
The video shows the original fix. Bookmark this page for the day an update undoes it - the re-check list above is the whole remedy.
▶️ Watch Full VideoA Resolve update can re-run its hardware detection and reset GPU Processing Mode and GPU Selection to Auto. Auto then repeats its original wrong guess. Setting the mode and card manually again, then restarting Resolve, clears the warning.
Yes - Windows Update supplies drivers from its own catalogue, and after feature updates or when it judges the installed driver unsuitable, it can install its version over yours. Checking the driver version after any big Windows update is a habit worth having on an editing machine.
You cannot freeze the three updaters, but you can make recovery instant: keep the driver current yourself, update one thing at a time between projects, and keep a note of your known-good Resolve GPU settings and driver version so any reset is a two-minute fix.