EVGATech_JamesL
try deleting the unleash folder from AppData\Local\EVGA_Co.,_Ltd and C:\Users\James\AppData\Roaming\EVGA.
 
Its likely going to be some issue within Windows. I had provided the update to some users before it went live and none of them had any issues. 

Now I get four entries in Event Viewer - Window Logs : Applications
 
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: FirmwareUpdate.exe
P2: 1.0.0.0
P3: 8310b159
P4: System.Management
P5: 4.8.4084.0
P6: 5dda3e36
P7: 8c
P8: 3f
P9: System.Management.Management
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF056.tmp.WERInternalMetadata.xml
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FirmwareUpdate.e_5a15bfceca31dbd58c5c2ff222267dee488858c_e38cddd4_6eaa9ce7-d656-4180-a37a-097827950002
Analysis symbol:
Rechecking for solution: 0
Report Id: a63741f8-08c9-4399-b1be-4b9aab4194b7
Report Status: 100
Hashed bucket:
 
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: FirmwareUpdate.exe
P2: 1.0.0.0
P3: 8310b159
P4: System.Management
P5: 4.8.4084.0
P6: 5dda3e36
P7: 8c
P8: 3f
P9: System.Management.Management
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER99D5.tmp.WERInternalMetadata.xml
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FirmwareUpdate.e_5a15bfceca31dbd58c5c2ff222267dee488858c_e38cddd4_2455fd6d-40c3-4602-87ba-d34c46304892
Analysis symbol:
Rechecking for solution: 0
Report Id: d640b2fd-d447-48d1-bfe2-ecd50b720e1a
Report Status: 100
Hashed bucket:
Cab Guid: 0
 
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: FirmwareUpdate.exe
P2: 1.0.0.0
P3: 8310b159
P4: System.Management
P5: 4.8.4084.0
P6: 5dda3e36
P7: 8c
P8: 3f
P9: System.Management.Management
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A3F.tmp.WERInternalMetadata.xml
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FirmwareUpdate.e_5a15bfceca31dbd58c5c2ff222267dee488858c_e38cddd4_22a713a6-5b24-4938-b4f5-474daa54a3f2
Analysis symbol:
Rechecking for solution: 0
Report Id: 4c8bda3a-ce6a-46b0-853d-1cd92c52f7d2
Report Status: 100
Hashed bucket:
 
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: FirmwareUpdate.exe
P2: 1.0.0.0
P3: 8310b159
P4: System.Management
P5: 4.8.4084.0
P6: 5dda3e36
P7: 8c
P8: 3f
P9: System.Management.Management
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9016.tmp.WERInternalMetadata.xml
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FirmwareUpdate.e_5a15bfceca31dbd58c5c2ff222267dee488858c_e38cddd4_a8fd431f-6a9b-4d61-8944-9695e5b62029
Analysis symbol:
Rechecking for solution: 0
Report Id: 0074dbf2-766d-40cf-b76f-d1d5b894bae8
Report Status: 100
Hashed bucket:
 
 
 
 
Event Viewer: Custom Views : Administrative Events. 
 
Faulting application name: FirmwareUpdate.exe, version: 1.0.0.0, time stamp: 0xe189ed58
Faulting module name: KERNELBASE.dll, version: 10.0.19041.804, time stamp: 0xb610d74d
Exception code: 0xe0434352
Fault offset: 0x0012a8b2
Faulting process id: 0x3290
Faulting application start time: 0x01d70c95564cff06
Faulting application path: C:\Program Files (x86)\EVGA\Unleash RGB\FWUpdate\FirmwareUpdate.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: d8b700db-6b7e-4eea-ad5e-c39ffbb39a84
Faulting package full name:
Faulting package-relative application ID:
 
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()
 

HoWxCoRe23
theres nothing in the release notes that said it addressed issues with the "x17", so it looks like us folks will have to wait even longer for a fix, i have the latest .NET runtime, uninstalled all evga software and reinstalled with still the same issues, no errors in sfc/scannow ran a couple disms the issue still persists

I have an X17 and a Z20 and it won't work for either, plugged in together or one at a time.

If the software isn't compatiable' or conflicting with x&y software, it shouldn't be up to the end user to figure it out. That's great that it's working for you , but as for me until the x17 and unleash rgb software , I haven't had such issues with any apps or games.

So I reinstalled windows and the software now works, thought I'd share the great news.

I just installed Unleash 1.0.5.0 and it would not load. I ran FirmwareUpdateX20Fake.exe and now it will open. On the Z20 I can only change options on the General Settings tab. On the X17 all options are greyed out.

EVGA_James

liquid0124
I just installed Unleash 1.0.5.0 and it would not load. I ran FirmwareUpdateX20Fake.exe and now it will open. On the Z20 I can only change options on the General Settings tab. On the X17 all options are greyed out.

Its likely some software or windows conflict has was mentioned to HoWxCoRe23. After he had reinstalled windows and installed Unleash everything ran accordingly. I may suggest uninstalling Unleash RGB then manually deleting the Unleash folders in C:\Program Files (x86)\EVGA, AppData\Local\EVGA_Co.,_Ltd and C:\Users\James\AppData\Roaming\EVGA. If you have LED Sync installed from the Precision X1 installer I would suggest uninstalling that as well. Then reboot and reinstall Unleash RGB

I finally solved my issue. I work  a a lot of  60 hour work weeks and don't have a lot of time to troubleshoot. I did a clean install of windows onto a flash drive, then installed EVGA unleash v. 1.0.5 . When I opened it up, it wanted to update my mouse driver. I did that. Then selected the keyboard tab and it wanted to update that driver. I did that and all options were working for the keyboard and the mouse. I restarted my computer into my regular windows install (on an M2 drive) and Unleash now works properly. (I don't have Precision installed, I set my 3070 up  prior and had uninstalled it during my troubleshooting.) So in conclusion, I believe that for some reason there was an issue properly updating the bios on my mouse and keyboard.

I have the same issue. Had to reinstall and everything is now working ok.

I already RMA'd mine, got a replacement...and now the audio jack is dying. It still doesn't open unleash either

I gave up on this product, I don't like sending back something with essentially a camera (TOF sensor) staring at me all day and the cost for shipping is almost half the cost of just buying one on sale at newegg right now brand new.

Worst EVGA product I've ever owned, but I got my 3090 24GB queue email the next day so it was also the best $100 I ever wasted lmao.

I have 4 Hard drives all running a separate OS either Windows 7 or 10, and I've had 2 keyboards.

I'd have to disagree on this one, I mean no offense to EVGA but if I had to take a guess I would say its either the KB is not compatible with older Mobo (I have an MSI Z270 Gaming M7) for some unique reason, it has a power issue (again maybe on certain hardware), or its just plain out a major design flaw right out of the box with the middle wire box.

Its either one of those scenarios or they sent me the same Keyboard back when I returned mine originally, because I only believe is so much circumstance....and I should have beat the odds on this one by a long shot.

All my OS and my Mobo BIOS can detect it, but can not load unleash, regardless of which ports I use on the motherboard or on my case headers...which are running a Pioneer External 3.0 BDR an Oculus Touch, etc without issue and my headers are running tons of Corsait ARGB products off a ComPro in a non argb setup. Certainly not lacking in power.

Sorry EVGA, love ya...but this is one product that should have been left off the market. Too many issues.

I had this same problem. With an x20, I navigated to C:\Program Files (x86)\EVGA\Unleash RGB\FWUpdate\X20Wired\ and ran FirmwareUpdateX20Fake.exe as admin. It did the firmware update and I was good to go. Finally.