AI Suite Issues after MOBO Swap

robk0304

Reputable
Sep 5, 2014
4
0
4,520
Hi,

I have recently upgraded my pc from the Z77 Sabertooth to the X99 Deluxe (yaay!)
But now I am running into compatibility issues with AI Suite!
Z77 uses AI SuiteII but because my new mobo is not compatible with the software, I am unable to uninstall it.... Also! I can't install AISuite3 :(
I have already tried everything...
- I deleted all the files from the program files,
- I tried to use the fix Asus mentioned on there ROG forum (did not work for me)
- I did system recovery to the point where things did work...

So I am a little out of options? anyone has any idea how to fix this without swapping mobo's back and forth?
 
Solution
I solved the problem :)

After alot of reading on the ROG forum, I found the hidden folder from AI Suite 3 in my program files.
There is a file in there called "lock"
This file prevents you from installing AI Suite 3 and is the reason for the error message "must reboot to finish previous installation blablabla"
So after deleting this file, I ran the "asussetup" as administrator and it installed just perfectly :)!

Thanks everyone for helping out!

parkour47

Distinguished
Jul 22, 2011
71
4
18,665
Only thing I can suggest trying (and only if you've got experience with editing the registry), is finding and deleting AI Suite II from the 'Program Data' and %appdata% folders (hidden by default) if you haven't already, and then manually removing any remnant keys.

If that doesn't work, unfortunately I'd advise the same thing as Phillip ^ pain in the arse I know, but new GPU, HDD, RAM, or peripheral would be no problem. A new motherboard almost always requires a full reinstall. Just make sure you back up your files beforehand.
 

robk0304

Reputable
Sep 5, 2014
4
0
4,520
So far ive been able to remove it completely using thirdparty software! (yaaay!!) buuuutttt I'm still unable to install the AISuit3, and yes ive already used both cleaners in Safe Mode
 

robk0304

Reputable
Sep 5, 2014
4
0
4,520
I solved the problem :)

After alot of reading on the ROG forum, I found the hidden folder from AI Suite 3 in my program files.
There is a file in there called "lock"
This file prevents you from installing AI Suite 3 and is the reason for the error message "must reboot to finish previous installation blablabla"
So after deleting this file, I ran the "asussetup" as administrator and it installed just perfectly :)!

Thanks everyone for helping out!
 
Solution

GWARslave119

Reputable
Mar 23, 2019
34
0
4,530
Ha, sorry to bring up an old topic, but I thought it was funny that someone else had a similiar issue that I had last night. What should've been a nice session of uninstalling a few programs turned into hours of me being frustrated at windows. Had an asus m5a97 r2.0 FX board and recently got an asus prime b550-plus. After coming down with the flu, what was supposed to be a 1 or 2 day system swap on my days off work turned into a week, so after moving my drives, power supply and video card to a new case, mobo, cpu and ram, I was ready to get back on my computer for sure. Used a 2 month old System Image I created when I moved windows from one drive to another, which was the first time I used that windows feature, and found it perfect for my needs. It's unfortunate that I had to use other software to restore the image 2 months ago due to no more support, so I figured I'd re-use the image again since I'm leaving 2 of my smaller ssd's (one of which has windows) in the old case that i'm giving to my friend.

Ok so to try and make a long story short (which I don't always do right lol..) the image included software for my old motherbboard obviously, including ai suite 2, which i forget why was installed cause I almost never use it. Uninstalling thru Windows proved to be a nono, windows didn't like the fact that the software was meant for an older board model, but instead of removing it from the system, it just said Wrong model for application and that's it. Can't uninstall it, and it was bugging me. So I ended up screwing up that restored windows installation by having fun trying to force remove it by deleting the program's folders (which kept regenerating itself), and finally by trying to remove the related Asus Services via registry. One of the services apparently involved handling the board's usb controller...which I assumed was for the old board. Whether it was or not, doing what I did cause my keyboard and mouse to stop working once it booted to windows, only worked in bios. And to top it off, I messed up the BCD on the usb drive that had Macrium Reflect 8 on it (Which was used to restore the windows System Image .vhdx) so my only choice ( i was about to slap my reconstructed pc at 5am when this all started at around midnight) was to install windows fresh, which I don't mind except I wasn't prepped for that. The amount of settings and programs to re-setup is a lot, I'm still not done with it all, which is why I loved the System Image idea. It's like a TWRP backup for your phone. I'm getting to the point to where I might get Macrium loaded on the usb drive and restore that image again, and try less aggressive ways to try to uninstall ai suite 2 ;p

P.S. I failed to make a long story short
 

GWARslave119

Reputable
Mar 23, 2019
34
0
4,530
Btw there didn't seem much that had to be done in getting windows migrated over and boot onto a new motherboard, as long as you're somewhat computer savvy. Macrium had winRE or similiar on the usb drive that was setup to restore a windows image, so in there, there's an option to fix windows boot errors (I don't recall the exact wording), which it did by modifiying the MBR and/or BCD (I didn't check the logs if there were any to see exactly what it did).

ALTHOUGH

During that process it's able to locate windows, but when it asks from where windows should be booting from, it doesn't show that windows install as an active partition, it only shows the usb drive with the macrium recovery software as the only valid boot source. Which me being 'why not' a lot, just went ahead and let it do it's thing. Blue screened on reboot, and a second reboot had my old windows back up and running again. I failed to realize though that it was using the usb drive to boot into windows on the ssd, which I found out after I removed the usb drive and suddenly I wasn't able to boot into windows lol. I have a feeling though that once in windows, you should be able to reconstruct the bcd from the ssd so u can boot from there normally and not needing the usb every time. Guess I won't know until I decide if I wanna go on another journey again.