make sure you are on the right profile and try a different port

You click on those circles and a box pops up where you can change the color. Black = off.

but if it is an AMD issue . . . did you update your BIOS with the lastest USB fix?

Yea same issue happened with me too, there is only white for me when I click static on. I have an intel core and it doesn't work for me. Also, cancel is spelt wrong in the setup menu.

AMD build here as well and the software is giving me nothing but problems. Program closes the second I open it. 

After many days of testing the software out I've discovered some weird issues with it. First off if I unplug the x17 and run the software I'm presented with the Evga screen from the app but it's blank and the moment I plug in the mouse the app closes. 

Bear in mind that the forums are community driven. For immediate assistance it is best to contact our support team directly by submitting a support ticket or at 888-881-3842 Mon-Fri 9am-6pm PT. 
 
As for your issue. Some have reported this but we have yet to replicate it. It is likely an issue either caused by another application conflicting or Windows issue. Some have tested their same mouse in a different system without issues changing the RGB and others have tried it on a separate Windows install on the same system without issue. Make sure that your OS is fully up to date, you can provide us with your current windows build to look further into. Also if you have the EVGA Precision X1 installed make sure to disable or uninstall LED sync as it is not compatible with the Unleash RGB. We will be releasing a new application to sync EVGA lighting in the near future. 

The software does not work with Windows starting from 1903 and up. I had a spare hd and installed an older Windows 10 (1809) version and ran the software on that version of course it worked. Something is breaking the software starting with Windows 1903 and up. 

ForSerious

Wy8840
The software does not work with Windows starting from 1903 and up.

I wish that that was more helpful, but I suspect it will not be.
My Windows says 21H1 for version. OS Build: 19043.1165 and I do not have the problems mentioned in this thread.

I too have 21H1 on my main pc build and the software would not load for me. I was not about to format all of my data just to get this issue resolved so I used a spare hd lying around and used Windows 1809 and ran the software and funny enough it worked. I'm not alone on this issue and the seems to centered around FirmwareUpdate.exe as I looked in Windows Event Viewer and the error was saying FirmwareUpdate.exe could not run due to it looking for an older version of the .Net Framework. 

This was under the Summary page events in Windows Event Viewer.
 
Faulting application name: FirmwareUpdate.exe, version: 1.0.0.0, time stamp: 0xfeea13ec
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1110, time stamp: 0xc830c52d
Exception code: 0xe0434352
Fault offset: 0x0012b4b2
Faulting process id: 0x2b78
Faulting application start time: 0x01d77c380d152760
Faulting application path: C:\Program Files (x86)\EVGA\Unleash RGB\FWUpdate\FirmwareUpdate.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: d51e492c-8807-43be-9357-86bed79854f6
Faulting package full name:
Faulting package-relative application ID:
 
This is under the Administrative Events in the Event Viewer:
 
Application: FirmwareUpdate.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Management.ManagementException
at System.Management.ManagementException.ThrowWithExtendedInfo(System.Management.ManagementStatus)
at System.Management.ManagementEventWatcher.Start()
at FirmwareUpdate.ViewModels.MainWindowViewModel.initialUsbPnp()
at FirmwareUpdate.ViewModels.MainWindowViewModel..ctor(Prism.Events.IEventAggregator)
Exception Info: System.Windows.Markup.XamlParseException
at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
at System.Windows.Application.LoadComponent(System.Object, System.Uri)
at FirmwareUpdate.Views.MainWindow.InitializeComponent()
at FirmwareUpdate.Views.MainWindow..ctor()
Exception Info: System.Reflection.TargetInvocationException
at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
at System.Reflection.RuntimeConstructorInfo.Invoke(System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)
at Unity.Processors.ConstructorProcessor+<>c__DisplayClass16_0.<GetResolverDelegate>b__0(Unity.Builder.BuilderContext ByRef)
at Unity.Processors.MemberProcessor`2+<>c__DisplayClass8_0[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<GetResolver>b__0(Unity.Builder.BuilderContext ByRef)
at Unity.Processors.MemberProcessor`2+<>c__DisplayClass8_0[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<GetResolver>b__0(Unity.Builder.BuilderContext ByRef)
at Unity.Processors.MemberProcessor`2+<>c__DisplayClass8_0[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<GetResolver>b__0(Unity.Builder.BuilderContext ByRef)
at Unity.UnityContainer+<>c__DisplayClass111_0.<OptimizingFactory>b__0(Unity.Builder.BuilderContext ByRef)
at Unity.Strategies.BuildPlanStrategy.PreBuildUp(Unity.Builder.BuilderContext ByRef)
at Unity.UnityContainer+<>c.<.ctor>b__73_1(Unity.Builder.BuilderContext ByRef)
at Unity.UnityContainer.Unity.IUnityContainer.Resolve(System.Type, System.String, Unity.Resolution.ResolverOverride[])
at Unity.UnityContainerExtensions.Resolve(Unity.IUnityContainer, System.Type, Unity.Resolution.ResolverOverride[])
at Prism.Unity.Ioc.UnityContainerExtension.Resolve(System.Type)
at Prism.Ioc.IContainerProviderExtensions.Resolve[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Prism.Ioc.IContainerProvider)
at FirmwareUpdate.App.CreateShell()
at Prism.PrismApplicationBase.Initialize()
at Prism.PrismApplicationBase.InitializeInternal()
at Prism.PrismApplicationBase.OnStartup(System.Windows.StartupEventArgs)
at System.Windows.Application.<.ctor>b__1_0(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at FirmwareUpdate.App.Main()
 
 
 
Just wanted to post this for the mods as well as this was in my error log in my Event Viewer when I was getting errors with the program. I posted all issues related to the program and maybe something here could help fix the problem so mods have a look at it.

It does appear to be a Windows specific issue due to a  possible corruption in the WMI (Windows Management Instrumentation) repository. This is indeed a Windows issue and not a Unleash RBG causing this. Below are some steps to take to repair the WMI repository.
 
Rebuilding the WMI repository can result in some 3rd party products not working until their setup is re-run & their MOF re-added back to the repository. 
(You may need to reinstall some of your device's drivers and or software if affected)
 
 
Open Command prompt and "Run as administrator" 
enter: winmgmt /verifyrepository
If the repository has an issue, it will respond “repository is not consistent,” 
 
Run the command:
winmgmt /salvagerepository
 
Then execute the command to see if it now comes back as consistent-
winmgmt /verifyrepository
 
If it says that Repository is not consistent, then you need to run:
winmgmt /resetrepository
 
After that you can enter: winmgmt /verifyrepository and if all goes well then it will respond with  “repository is consistent” 
 
You may want to reinstall Unleash RGB as well as test any other devices to see if you may need to reinstall their drivers/software

Etyrnus
 
Tried the commands given.  On the verify step received "WMI repository is consistent", same after the salvage command.  Reinstalled Unleash RGB just to be on the safe side.  No change. 

Can you provide the build/version of windows you are on so we can look into it

EVGA_James

Etyrnus
 
Tried the commands given.  On the verify step received "WMI repository is consistent", same after the salvage command.  Reinstalled Unleash RGB just to be on the safe side.  No change. 

Can you provide the build/version of windows you are on so we can look into it

Update, the 1.0.10 version just released appears to have resolved the RGB issue, thank you!