Jump to content

technochitlin

Members
  • Posts

    16
  • Joined

Reputation

10 Good
  1. I was getting the same error, and after trying this fix https://help.corsair.com/hc/en-us/articles/15664228575373-How-to-Resolve-Failed-to-install-required-modules-due-to-some-error-with-iCUE-5?_gl=1*1ej5j1v*_gcl_au*ODkwNzA0ODAyLjE2ODQxNjQ4MjA I still got the same error, with this in my Installer log: 2023-05-24_08:42:51 Checking user locale: en-US. 2023-05-24_08:42:51 Setting user preffered language: en-US. 2023-05-24_08:42:53 Product code found, but key cannot be found in registry 2023-05-24_08:42:54 Opening file: C:\ProgramData\Corsair\iCUE5 Initial Installer\manager\cuepkg.zip.sha2 2023-05-24_08:42:54 Opening file: C:\ProgramData\Corsair\iCUE5 Initial Installer\manager\cuepkg.zip 2023-05-24_08:42:54 Using bootstrap package from repo: https://www3.corsair.com/software/CUE_V5/public/modules/windows/installerpackage/cuepkg.zip 2023-05-24_08:42:56 Package manager failed: "C:\ProgramData\Corsair\iCUE5 Initial Installer\manager\cuepkg.exe" --installdir="C:\ProgramData\Corsair\iCUE5 Initial Installer\packages" install icue-installer code: 1 out: Warning: A working directory is not restricted, aborting. The Package Manager log says this: 2023-05-24 08:42:55.420 I cuepkg.init: Non-standard path used for init operation: "C:/ProgramData/Corsair/iCUE5 Initial Installer/packages" I uninstalled iCue4 and retried, rebooting each time, still ste same error- so I reinstalled 4 and will wait until you release an update that works for me. This is similar to the craziness that went on going from 3 to 4. I figured ya'll would have learned by now.
  2. I probably should have included this- the install log file: 2023-05-13_13:39:49 Checking user locale: en-US. 2023-05-13_13:39:49 Setting user preffered language: en-US. 2023-05-13_13:39:53 Product code found, but key cannot be found in registry 2023-05-13_13:39:54 Opening file: C:\ProgramData\Corsair\iCUE5 Initial Installer\manager\cuepkg.zip.sha2 2023-05-13_13:39:54 Opening file: C:\ProgramData\Corsair\iCUE5 Initial Installer\manager\cuepkg.zip 2023-05-13_13:39:54 Using bootstrap package from repo: https://www3.corsair.com/software/CUE_V5/public/modules/windows/installerpackage/cuepkg.zip 2023-05-13_13:39:56 Package manager failed: "C:\ProgramData\Corsair\iCUE5 Initial Installer\manager\cuepkg.exe" --installdir="C:\ProgramData\Corsair\iCUE5 Initial Installer\packages" install icue-installer code: 1 out: Warning: A working directory is not restricted, aborting.
  3. Same problem here- the installer tries to download some files and throws this error- "CORSAIR iCUE Installer was unable to complete the installation: Failed to install required modules due to some error." Some error?
  4. They are "looking into it". I sent them my log files. I get the distinct impression I am bothering them with my problem.
  5. I fairly religiously export all my profiles, but when I try to import them to an earlier version of iCue I get the error "The profile selected is from a newer version of ICUE and cannot be Imported." So I would have to re-create them from scratch. I think in the future I'll just make a copy of my exported profiles folder before updating iCue. That does not solve my present problem though.
  6. Yes, the Commander came back on 3.32.80, but I'd rather have usable profiles so I went back to 3.34.170, even though the lights on my computer are only red now since it doesn't see the Commander. I'm assuming you meant RE-CREATE all the profiles, not re-import them, as iCue won't let me do that.
  7. Just got a detailed email from Corsair on how to roll back to 3.32.80 - but I already tried that, it will not load my profiles which were all updated by 3.34.170! So I am back to square one- surely they know this is an issue. At least tell me how to modify my profiles so the earlier version can once again load them!
  8. Just got a detailed email from Corsair on how to roll back to 3.32.80 - but I already tried that, it will not load my profiles which were all updated by 3.34.17! So I am back to square one- surely they know this is an issue. At least tell me how to modify my profiles so the earlier version can once again load them!
  9. Both 3.34.161 and 3.34.170 do not recognize my Commander Pro. If roll back to 3.32.80 iCue sees my Commander Pro, but now none of my scripts work as they have been "updated". I have around 50 scripts, and really don't wish to recreate all of them, so can you please release some fixed software that will both read my scripts AND see the Commander Pro?
  10. Both 3.34.161 and 3.34.170 do not recognize my Commander Pro. If roll back to 3.32.80 iCue sees my Commander Pro, but now none of my scripts work as they have been "updated". I have around 50 scripts, and really don't wish to recreate all of them, so can you please release some fixed software that will both read my scripts AND see the Commander Pro?
  11. Excellent! That fixed my problem as well- the Corsair techs should add that to their list of fixes... Thank you very much!
  12. I have reported this before. When I try to install 3.22.74 or 3.21.88 I get an error; the install stops, rolls back, and I am left with no iCue software at all. I can install 3.20.80 with no problem, so I go back to that. http://https//imgur.com/JqKv2qm I have completely uninstalled 3.20 using Rivo Uninstaller and rebooted before attempting to install the new software, with no luck. Please help! I have attached msi.log and two screenshots [EDIT] I also did another uninstall following the procedure listed on the Support Ticket web page, which deleted all my setups (a warning would have been nice). Still cannot install either 3.21 or 3.22 msi.log
  13. When I try to install 3.21.88, it errors out trying to find C:/ProgramData/Corsair/qt55.dll; it then quits and I am left with no install at all. I reinstalled 3.20, but I see I'm not the only one who has this problem- is there a fix on the way?
×
×
  • Create New...