Current search for updates gives the KB4516065 (important) and KB4516048 (optional) but no KB4490628 (important). ![]() But i don't have KB4490628 installed.įor some reason, my Win updater hasn't found it as one of the updates to be installed. Now, i have Corsair iCUE 3.20.80 running and i even didn't have to import my Profile over,Ĭlick to expand.So, i went over that page and checked my installed updates if i have the prequsite KB4474419 and KB4490628 installed. You love them, care for them, buy nice things for them and they still sometimes throw a tantrum. After some 20 seconds or so (felt like forever), i saw life and JC Denton greeted me on Win log-in screen to input my psw. My heart sank at that point and i was thinking if iCUE just messed up GPU drivers or something worse happened. This time, the loss of signal to the monitor was so long that my monitor displayed "No DP signal" and went into sleep mode. Did a reboot and during OS boot-up, i almost got a heart attack since my screen went completely black.ĭuring boot-up, screen does flicker to black but it lasts only mere seconds (since i'm booting from 960 Evo M.2 NVMe SSD). Took some time before installation was complete, with prompt to reboot the PC. So, i executed 3.20.80 installation and it worked without issues. ![]() Sure enough, Corsair iCUE was gone from "Programs and Features" when i checked it. Program started to work and after about 2-3 mins, it finished and prompted "Fixed" status. Followed the on-screen instructions and selected that i have issue uninstalling Corsair iCUE. So, at least that much of my system works without issues, making issue with iCUE specific to iCUE.ĭownloaded that piece of software and executed it. Corsair Link even prompted that new version of Link is available and using built-in updater, it updated itself to 4.9.7 problem free. Software installed fine and i had no issues updating already installed software.įor uninstall test, i uninstalled Corsair Link 4.9.5 from Control Panel and then manually installed 4.9.6, again problem free. ![]() Here, i downloaded and updated my LockHunter from 3.1 to 3.2. As well as deleting all vestiges of the files it may have laid down.Ĭlick to expand.Pre-test to see if i can install/uninstall other programs (as advised in that guide above): Might just be a matter of a little editing, or find the MSI and uninstall it yourself.Īnd last resort, find every reference to it in the registry and nuke it. If you can locate the transform files *.mst you may be able to see what it is trying to do on uninstall. ![]() Might also reveal the path to the uninstaller and then you can just try running it manually. Amazing how often it came up.Ĭheck the registry here: HKLM\Software\Microsoft\CurrentVersion\Uninstall, should be a detailed list of what is in the control panel and the uninstall string it is trying to use to remove it. Usually it was a lack of LUA awareness or simply needing a fixed file and folder structure that only applied to XP. We would ask for a compatible version, for say Windows 7, they would give us a hacked together piece of garbage that half worked. I saw that a lot in my times doing OS upgrades for my company. They may have goofed on the installer, probably edited by hand rather than re-publishing it properly. That is why a re-install can fix it sometimes, it puts fresh files down and then the uninstall can happen again. Now something that can happen is that the files necessary to uninstall have been removed from a cache folder somewhere. Try a repair from the control panel if that is an option (or the installer is unavailable). Have you tried re-installing the version you have now again? Sometimes that can take care of it.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |