Excess Posted June 22, 2017 Share Posted June 22, 2017 Good day, I own a K65 RGB and after running it via CUE 1 for a long time, I today realized: there's 2.14.67 (CUE 1 doesn't tell you when checking for updates, that CUE 2 is available). Operating system: Win 10 - deinstalled CUE 1 - downloaded CorsairUtilityEngineSetup_2.14.67_release.msi via official corsair-website and tried to install it - errormessage, immediately after clicking "install": System cannot open the device or file specified. http://www.bilder-upload.eu/thumb/eadd68-1498095608.jpg - reinstalled CUE 1 without difficulties (also a .msi file), deinstalled it via Revo Uninstaller, ran a registry cleaner, removed temp files, tried various languages, tried various directories, manually added keys in registry to run .msi-files as admin, deactivated Avira Antivirus, tried windows secure mode (no .msi-installation possible), several reboots, several new downloads of the installationfile, some hours of research via google - nothing worked Installation log: MSI (s) (44:CC) [03:12:32:589]: Running installation inside multi-package transaction D:\Downloads\CorsairUtilityEngineSetup_2.14.67_release.msi MSI (s) (44:CC) [03:12:32:589]: Grabbed execution mutex. MSI (s) (44:3C) [03:12:32:590]: Resetting cached policy values MSI (s) (44:3C) [03:12:32:590]: Machine policy value 'Debug' is 0 MSI (s) (44:3C) [03:12:32:590]: ******* RunEngine: ******* Product: D:\Downloads\CorsairUtilityEngineSetup_2.14.67_release.msi ******* Action: ******* CommandLine: ********** MSI (s) (44:3C) [03:12:32:590]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (44:3C) [03:12:32:595]: Note: 1: 2203 2: C:\WINDOWS\Installer\inprogressinstallinfo.ipi 3: -2147287038 MSI (s) (44:3C) [03:12:32:596]: SRSetRestorePoint skipped for this transaction. MSI (s) (44:3C) [03:12:32:597]: Note: 1: 1309 2: 5 3: D:\Downloads\CorsairUtilityEngineSetup_2.14.67_release.msi MSI (s) (44:CC) [03:13:32:295]: I/O on thread 5868 could not be cancelled. Error: 1168 MSI (s) (44:CC) [03:13:32:295]: I/O on thread 6864 could not be cancelled. Error: 1168 MSI (s) (44:CC) [03:13:32:295]: I/O on thread 12156 could not be cancelled. Error: 1168 MSI (s) (44:CC) [03:13:32:295]: I/O on thread 9192 could not be cancelled. Error: 1168 MSI (s) (44:CC) [03:13:32:295]: I/O on thread 6924 could not be cancelled. Error: 1168 MSI (s) (44:CC) [03:13:32:295]: I/O on thread 1852 could not be cancelled. Error: 1168 MSI (s) (44:3C) [03:13:32:296]: MainEngineThread is returning 110 MSI (s) (44:CC) [03:13:32:296]: No System Restore sequence number for this installation. === Verbose logging started: 22.06.2017 03:12:32 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\Users\User\APPDATA\LOCAL\TEMP\MSI13165\InstallerGui.exe === MSI © (6C:CC) [03:12:32:586]: Resetting cached policy values MSI © (6C:CC) [03:12:32:586]: Machine policy value 'Debug' is 0 MSI © (6C:CC) [03:12:32:586]: ******* RunEngine: ******* Product: D:\Downloads\CorsairUtilityEngineSetup_2.14.67_release.msi ******* Action: ******* CommandLine: ********** MSI © (6C:CC) [03:12:32:586]: Client-side and UI is none or basic: Running entire install on the server. MSI © (6C:CC) [03:12:32:586]: Grabbed execution mutex. MSI © (6C:CC) [03:12:32:587]: Cloaking enabled. MSI © (6C:CC) [03:12:32:587]: Attempting to enable all disabled privileges before calling Install on Server MSI © (6C:CC) [03:12:32:587]: Incrementing counter to disable shutdown. Counter after increment: 0 Das System kann das angegebene Gerät oder die angegebene Datei nicht öffnen. [that's German for System cannot open the device or file specified.] MSI © (6C:CC) [03:13:32:300]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI © (6C:CC) [03:13:32:301]: MainEngineThread is returning 110 === Verbose logging stopped: 22.06.2017 03:13:32 === What did I miss? :-) Many thanks! Link to comment Share on other sites More sharing options...
Toasted Posted July 2, 2017 Share Posted July 2, 2017 Try an older CUE version and see whether the error still persists. http://forum.corsair.com/v3/showthread.php?t=138472 Link to comment Share on other sites More sharing options...
Corsair Employee Corsair James Posted July 7, 2017 Corsair Employee Share Posted July 7, 2017 Also try 2.15 as we updated it yesterday. Link to comment Share on other sites More sharing options...
Excess Posted July 10, 2017 Author Share Posted July 10, 2017 sorry, I was out of the country (and will be again for a few weeks, but well it doesn't hurry :-) ) Tried to install 2.4.66, 2.8.70, 2.10.71, 2.12.66 and 2.15.83. Unfortunately, the error remains the same. Link to comment Share on other sites More sharing options...
Corsair Employee Corsair James Posted July 10, 2017 Corsair Employee Share Posted July 10, 2017 See if you can try this in safe mode: http://support.eset.com/kb2098/?locale=en_US Then install the SW. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.