Uninstall a Service in Vista, Repair Adobe CS3 and Clean Up the Registry

I totally messed things up with a botched uninstall of Adobe CS3. Basically, all I was trying to do was get rid of the absurd and unnecessary Version Cue Server, which absolutely should not be installed, and Version Cue, which should not be a default option. I was hoping it might help my group manage collaboration on InDesign documents, but it is not appropriate for what we want (I want real concurrent versioning for Word or InDesign, but I don’t think it’s possible). So anyway, I got stuck in this thing where I had some parts of CS3 removed, which was causing other parts to fail, but I could neither repair the installation nor remove the apps. So I was stuck. What follows is what I did step-by-step to get unstuck. [Update: please help others. I created this blog after figuring this out because I wanted to put the information somewhere. As it turns out, even though this is just a nothing blog with no traffic, this page actually gets a bit of traffic from frustrated folks so I would like to improve it if possible. If this works for you, I would appreciate it if you would leave a brief comment on anything that was unclear. If it doesn't work for you, I would really appreciate it if you would leave a comment saying where you got stuck. Thanks.]

So I eventually found out that you need to download a special program to clean up the detritus left by CS3. So first

  • Go get the Windows Installer Cleanup Utility (scroll down that page for the actual download link).
  • Then get the AdobeCS3Clean Script. In theory this utility is for cleaning up the beta distro to install the full package, but it cleaned tons of stuff off my system. Run it a couple of times until it doesn’t seem to do anything more.

This is a simple non-GUI tool that runs in a shell window. In theory, based on the options given, there are two levels on this cleanup utility, but in fact, there are four. I found out about this from CrucialLimit.com blog post on running the CS3 cleanup script and he got it from Adobe support. Dave (CrucialLimit) ran at level 3. I tried that and some stuff was left, so I thought, “Well, everything is hosed, might as well go nuclear” so I ran it at level 4.

Annoyingly, the Version Cue service was still running. Get rid of that damn it! Frankly, I did not want to just disable it, I wanted to kill it forever.You can do this by editing the registry, but (full disclosure), I think that’s how I got to the sorry state I’m in, though I did do a system backup and restore, so in theory my registry is back where it was before I mucked with it. Anyway, it turns out this is absolutely simple. So often, Windows is like Linux, only you just don’t know it, which is to say that there are command tools for everything if you know where to look. In this case, it’s a simple little tool named “sc.exe”. Simple

  • Open a command prompt
  • type sc delete “Adobe Version Cue CS3″ and the nasty virus, er Version Cue, is finally gone. Note the quotes. Without them, you’ll get an error.

Now you’re almost done. If you want to try to get rid of as much Registry detritus as possible, download the Eusing Free Registry Cleaner. I’ve run it many times without it every causing any problems. I’m not sure it’s ever truly fixed anything either, but it does delete tons of registry keys with no seeming ill effects. In this case, it finds tons of Adob-related keys left over. Make sure to run it twice and to check that you have the latest version.

Finally, believe or not, you might still have some stuff left over and CCleaner is another registry cleanup and repair tool (choose “Issues”) and also does disk cleanup and handles uninstall functios using other option. A pretty handy little tool and also free.

So now you should have

  • most CS3 files removed
  • CS3 services totally uninstalled
  • most registry keys deleted
  • weird file assocation issues fixed.

So were pretty much at a clean slate. Restart and see if you can install!

4 comments ↓

#1 Leo on 12.07.07 at 4:22 am

Thanks, the Adobe CS3 suite was totally removed from Windows XP finally.

#2 Tom on 12.07.07 at 12:33 pm

Glad to hear it. I think there’s something wrong with a piece of software when the uninstall process requires you to download a cleaner from the software maker, another cleaner from the OS maker and you still find cruft to clean out when you run a *fourth* party registry cleaner. It’s frankly just ridiculous.

That said, CS3 is a fine software package (although, I got it for free through work, I can’t imagine ever paying full price for that).

#3 Jakob on 12.12.07 at 6:35 pm

Can“t you just use CCleaner then?

#4 Tom on 12.12.07 at 8:41 pm

Jakob… if only! In fact, though, no you can’t. CS3 is far too devious for that (do I need to reiterate that I *like* CS3 except for this issue? I’m not trying to rant about it). Ok, that’s out of the way.

You definitely need to run the Adobe cleaner/Windows Installer Cleanup Utility. If you just ran CCleaner before that, it would still see CS3 as a valid application (just like you Add/Remove Programs interface and your CS3 Installer/Repair/Uninstaller wizard does). You literally cannot uninstall it without this tool, so it’s not cruft that you can clean up with a registry tool. It’s an application and, thankfully, CCleaner is much too cautious to go blowing away your valid (or semi-valid) apps.

Now if you mean beyond that whether you need to run both Eusing and CCleaner, the answer is that you don’t need to run either one, in theory. Everything was fine after running the Adobe Cleaner. In theory, I could have re-installed then, but I just wanted to get as close as possible to a clean slate, so I decided to just have at it with the cruft cleaners.

Why not just use one? I’ve tested this a few times. If I run one then the other, I always find more stuff. It doesn’t matter which one you run first. They’re both excellent apps that do a great job (especially for free), but neither one of them seems to nail 100% of the cruft.

I suppose if I ran a third cruft cleaner, maybe it would find even more, but of course there’s a point where it becomes ridiculous, so I decided to declare victory and be done.

Leave a Comment

Powered by WP Hashcash