Should we delete existing SQL windows registry after a full MS SQL uninstall

We have uninstall all our versions of Microsoft SQL Server 2005/2008/2012 with EE assistant (all instances were Express version).  However, we found in the windows registry  a series of entries regarding MS SQL (see below for an example).

Should we manually delete these entries?

What does EE recommend?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Éric MoreauSenior .Net ConsultantCommented:
the registry is a complex database. messing around it can cause serious issues to your computer. I wouldn't touch that!
Abhigyan SrivastavaCommented:
There is no reason for you to be bothered about deleting entries from registry unless you used SQL Express on a production server or for any other commercial activities. If that is indeed the case, you can use several tools that can clean the registry for you.

Best is CCleaner -

However manual registry cleaning is not advised unless you are very sure about what you are doing.
Vitor MontalvãoMSSQL Senior EngineerCommented:
There's a change they belong to some other previous installation that wasn't well uninstalled?
Anyway, I wouldn't bother much with those entries. Can't perform any harm now.
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

janaAuthor Commented:
Understood.  However, for some strange reason when reinstalling, the process gets halted.  This has happened to us with another apps in another pc some years ago and after removing the apps registry entries, it was a successful install.  Thus, we think that this is could be the cause of our failed installed.

We have cleaner and it's a regular this we do after any uninstall; we run both the cleaning of files and cleaning of the registry.  Yet, cleaner doesn't delete the sql entries that may have pertain to the recent uninstall process or previously to that uninstalls.

If we delete those entries that we think have no reference to any install in the pc, would that be harmful?
Abhigyan SrivastavaCommented:
I would try something else before doing that.

When you run the setup, it extracts the files in a directory. The directory name usually is a guid. Run setup and note down the name of the directory. Then stop setup, go to the directory and delete it. Then re-run setup.

I had once faced an issue while installing SQL and it helped me. Try that else we will see the registry entries.

Let me know how it goes.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
janaAuthor Commented:
Tried it, same problem.   We have had this happened in previous apps; when we deleted the registries, we then can successfully reinstall with no problem.

The purpose of placing this question is to know if we can delete all the entries we found.  We open RegEdit then just search for everything that had "SQL" in it.  After going one-by-one, we noticed that all were Microsoft SQL related (Sql 2000, 2005, 2008, 2012).

We didn't go right ahead and deleted because we tho8gh due to that its a MS product and Windows 10 is new, maybe there some sort of SQl tool related to Windows 10.

So what you think, go ahead and delete them? What else would we consider?
Abhigyan SrivastavaCommented:
Well. Go ahead and delete them. Not any harm. After deleting do run CCleaner again just for safety sake. And do take a backup of registry before deleting the keys.
janaAuthor Commented:
Good idea will do!
janaAuthor Commented:
Worked perfectly!! After SQL reinstall kool!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.