There has been a few reports of this versus those that did not have any issues. Its more likely a Windows isolated issue due to a  possible corruption in the WMI (Windows Management Instrumentation) repository. Below are some steps to take to repair the WMI repository. I would suggest making sure that you have Windows fully updated and the latest Windows .Net framework installed. 
 
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

Can you provide the Windows version and build number so we can look into this further
 

Apollo1321
Does the same thing for me, closes almost immediately on my daily system, my test bench on both a fresh install of windows and one win install that is just benchmarks. Tried also on a win7 laptop that just had a fresh reinstall of windows that also has zero other programs on it, yes I installed latest dotnet. Closes on all.
 
On all the machines I tried removing the firmwareupdate exe from the program folder. Then started unleash rgb, it opens and stays open with the x15 mouse showing, but cannot do ANYTHING in the program. So it seems that firmwareupdate.exe is causing the issues.
On the windows 7 laptop it says that firmwareupdate.exe has malfunctioned and stopped working.

Can you provide screen shots of the Windows build number as the error messages you are seeing

Having same issue here only with an x15.
Windows 10 Pro 21H1 19043.1202

I am having the same issue where the software closes immediately upon opening. Just got the mouse today and after browsing thru the forums it appears to me that this is an issue EVGA has not and will not take care of despite this going on since the x17 came out in February. I've tried every troubleshooting method mentioned in the forums short of reinstalling windows which is a hassle that shouldn't be necessary and appears to likely not work according to other users. I can get the program to open without crash only by changing or deleting the firmware update file, which seems to be the root of the problem, yet it is completely nonfunctional. The fact they still haven't dealt with it for over 7 months now is utterly ridiculous. I've noticed that the EVGA reps always blame windows for the issue but yet every other company has no problem creating a working program especially for an $80 mouse. My Windows version is 20H2 build# 19042.1165.

I will confirm that my full model listed on the mouse is 903-W1-17GR-KR, but I also see that the x17s on EVGA's website also list the full model with KR on the end, so it seems that this may be a dead end. At least directly. Is there something in the firmware updater that searches for a bogus model that doesn't match exactly?

zargon45
I will confirm that my full model listed on the mouse is 903-W1-17GR-KR, but I also see that the x17s on EVGA's website also list the full model with KR on the end, so it seems that this may be a dead end. At least directly. Is there something in the firmware updater that searches for a bogus model that doesn't match exactly?

I remember when I last looked into this, the error being reported back by the firmware update application was that the device could not be found, even though it clearly is pinged by the application and is aware of whether it is running or not. Can you link the part of the website you are talking about? 
 
I am not suggesting that this is an invalid version of the product, I am just suggesting the possibility that the US version of the firmware updater may not be taking certain models into consideration when determining if a compatible device is present or not.
 
@support - here is some more extended information regarding the USB live-session data if it helps your dev team at all, I find the first line interesting:
 
Device NameDescriptionDevice TypeConnectedSafe To UnplugDisabledUSB HubDrive LetterSerial NumberCreated DateLast Plug/Unplug DateVendorIDProductIDFirmware RevisionUSB ClassUSB SubClassUSB ProtocolHub / PortComputer NameVendor NameProduct NameParentId PrefixService NameService DescriptionDriver FilenameDevice ClassDevice MfgFriendly NamePowerUSB VersionDriver DescriptionDriver VersionDriver InfSectionDriver InfPathInstance IDCapabilitiesEVGA X17 Gaming MouseUSB Composite DeviceUnknownYesYesNoNo  9/19/2021 8:06:08 PM6/16/2021 6:05:21 AM3842240d0.00000000    7&29249de6& 1usbccgp@usb.inf,%GenericParent.SvcDesc%;Microsoft USB Generic Parent Driverusbccgp.sys (Standard USB Host Controller) 500 mA2.00USB Composite Device10.0.19041.488Composite.Dev.NTusb.infUSB\VID_3842&PID_240D\6&c1a2e2f&0&4Removable, SurpriseRemovalOKEVGA X17 Gaming MouseUSB Input DeviceHID (Human Interface Device)YesYesNoNo  9/19/2021 8:06:08 PM6/17/2021 5:00:58 AM3842240d0.00030102    8&1c0c126c& 0HidUsb@input.inf,%HID.SvcDesc%;Microsoft HID Class Driverhidusb.sys (Standard system devices) 500 mA2.00USB Input Device10.0.19041.868HID_Inst.NTinput.infUSB\VID_3842&PID_240D&MI_00\7&29249de6&1&0000SurpriseRemovalOKEVGA X17 Gaming MouseUSB Input DeviceHID (Human Interface Device)YesYesNoNo  9/19/2021 8:06:08 PM6/17/2021 5:00:58 AM3842240d0.00030101    8&4488627& 0HidUsb@input.inf,%HID.SvcDesc%;Microsoft HID Class Driverhidusb.sys (Standard system devices) 500 mA2.00USB Input Device10.0.19041.868HID_Inst.NTinput.infUSB\VID_3842&PID_240D&MI_01\7&29249de6&1&0001SurpriseRemovalOKEVGA X17 Gaming MouseUSB Input DeviceHID (Human Interface Device)YesYesNoNo  9/19/2021 8:06:08 PM6/17/2021 5:00:58 AM3842240d0.00030101    8&250fde02& 0HidUsb@input.inf,%HID.SvcDesc%;Microsoft HID Class Driverhidusb.sys (Standard system devices) 500 mA2.00USB Input Device10.0.19041.868HID_Inst.NTinput.infUSB\VID_3842&PID_240D&MI_02\7&29249de6&1&0002SurpriseRemovalOK

Just a quick update. I've been working with one of our users having this issue and has helped us out a lot. I think we are getting very close to the issue and hopefully I will have an updated version soon. 

If you install build 1809 of windows 10 on a device, and use that to run the EVGA Unleash RGB program, it will successfully update the firmware! You can then run the Unleash software on any build of windows, afterwards with zero issues!

can we have an update on what the progress of fixing this problem is? I have been unable to use the software for over a month since purchasing both an x17 and z15....