Skip to content

Conversation

Copy link

Copilot AI commented Jan 26, 2026

The issue request was to concisely document, for v2.5.0+, how users can force NVIDIA or AMD selection when the app reports both driver types (e.g., AMD iGPU + NVIDIA dGPU). This PR adds a short troubleshooting section describing the shortcut flags needed to bypass the ambiguous-driver prompt.

  • Documentation
    • Added a “Troubleshooting (v2.5.0+)” section with concise guidance for forcing GPU type via shortcut arguments when the ambiguous-driver error appears.

Example usage:

C:\WHATEVER\vibranceGUI\vibranceGUI.exe --force-nvidia
Original prompt

Hi all,

can you please take a look at this new beta version i have built based on this

To force a GPU type in that new version, do the following:

Create a shortcut of the vibranceGUI.exe file (right click -> create shortcut)
Go to the shortcut properties (right click, properties)
Add the following at the END of the Target field:
for NVIDIA: --force-nvidia
for AMD GPU: --force-amd
Make sure to add a space ( ) in between the path to the .exe file and the argument, so for example it looks like this:
C:\WHATEVER\vibranceGUI\vibranceGUI.exe --force-nvidia
It would be great if you can let me know if this also works after you reboot your pc.
By the way, this version also includes a lot of bug fixes and performance improvements in comparison to that version above from 2019.

update the readme to explain how to do the above if you encounter the following error when using for example a amd cpu with an igpu and a dedicated nvidia gpu, be concise, follow pattern already there, explain its for version 2.5.0+: Both NVIDIA and AMD graphic drivers have been found on
your system. This can happen when you recently switched
your graphic card and did not uninstall the old drivers. Make
sure to uninstall unused graphic drivers to keep your system
safe and stable. Use the program "Display Driver Uninstaller"
to uninstall your old drivers!

In case you want to do it manually: The related files are
located in your Windows folder and are called "nvapi.dll"
(NVIDIA) and "atiadlxx.dll" (AMD) and "atiadlxy.dll" (AMD). You
are free to rename/delete the files that you no longer need
but proceed with caution!

Press Yes to open "Display Driver Uninstaller" download
website in your Browser now.
Press No to quit vibranceGUI.

Name the new branch something appropriate then make a pr back to the original vibracegui repo


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Co-authored-by: harisonw <87620631+harisonw@users.noreply.github.com>
Copilot AI changed the title [WIP] Update README to explain GPU type shortcut creation Document forced GPU selection flags for ambiguous driver detection Jan 26, 2026
Copilot AI requested a review from harisonw January 26, 2026 23:46
@harisonw harisonw marked this pull request as ready for review January 27, 2026 00:09
Copilot AI review requested due to automatic review settings January 27, 2026 00:09
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds documentation to help users resolve the "Both NVIDIA and AMD graphic drivers have been found" error by providing concise instructions on how to force GPU selection using command-line flags in version 2.5.0+.

Changes:

  • Added a new "Troubleshooting (v2.5.0+)" section to README.md with instructions for forcing GPU type selection via shortcut arguments

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@harisonw harisonw merged commit 289ac4a into master Jan 27, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants