Undeleteable Registry Entries

Topic

New Reply

My OS is Win 7 Pro 32 bit.

I installed the free version of LogMeIn, and subsequently decided to uninstall it. Several registry entries remained, and I cannot delete them. If I try to delete an entry in the right pane of regedit I am told “Unable to delete all registry values”. If I try to delete entries in the left pane I am told “Error while deleting key”. I tried to get help from LogMeIn support, but their reply was “The legacy ones cannot be removed, as they are there to prevent people from misusing the trial of Pro2.” I have gone back to LogMeIn support, pointing out that I installed the free version of their program, not the the trial of Pro2, and asking again how I can delete the remaining reg entries, but am not holding my breath for a reply.

Can anyone tell me how to delete the unwanted reg entries?

Help would be appreciated.

Thanks and regards,
Roy

Reply | Quote

Replies

You could try highlighting the entry then clicking on Edit -> Permissions, and see what is set there, changing to taste…

BATcher

Plethora means a lot to me.

Reply | Quote

You might try Revo Uninstaller I don’t know if it will pick it up because you have already tried to uninstall, but if it doesn’t reinstall and then uninstall with Revo

Reply | Quote

My OS is Win 7 Pro 32 bit.

Can anyone tell me how to delete the unwanted reg entries?

Roy,
Hello…. You need to set yourself as the “Owner” When you run “regedit” right click on the “parent” key and select properties > then advanced…Then click on the Owner tab and set yourself as the “big dog” …you probably see trusted installer , restricted , system , etc . when finished “OK” out and now back at the first screen, give yourself full control click on “yourself”…then tick “allow” in the “full control” box … If there are children keys involved you have to start with the last one , and work your way up the chain with this procedure. When finished you then can delete them starting at the last in the chain.Be careful when deleting “reg entries” you should have a backup handy or use the “Export ” function and save the original key until you know that it worked. Regards Fred

Reply | Quote

System restore to a time before you installed it and they will be gone.

Reply | Quote

If it will not work with the above suggestions…
Run a potent registry cleaning utility and look for specific references the those files you wish to delete. Ignore all others.

Reply | Quote

Thanks for all the suggestions.

I tried to edit permissions and to change Owner but every time I clicked apply/ok I was told unable to set permissions/access denied.

I also tried installing Revo Uninstaller, then reinstalling LogMeIn and then uninstalling LogMeIn with Revo, but the legacy reg entries for LogMeIn are still there.

With regard to System Restore, unfortunately the restore points I have don’t go back far enough.

Regarding Clint’s suggestion, I used the Registry Find option in jv16 Power Tools to find the LogMeIn entries, but when I selected all of them and clicked delete was told they could not be deleted because Windows kernel said access denied.

Does anyone have any other suggestions?

Please advise.

Thanks,
Roy

PS, I also tried regedit in Safe Mode, but it made no difference. When I rebooted I was given the option to either log on to LogMeIn or to Roy. (The first time this has happened.). I logged in to Roy, and then deleted the LogMeIn User Account and files (which I didn’t know existed), and tried again to delete the unwanted reg entries, without success.

I have a recent System Image, but assume if I used that the LogMeIn reg entries would be recreated.

Reply | Quote

I tried to edit permissions and to change Owner but every time I clicked apply/ok I was told unable to set permissions/access denied.
Does anyone have any other suggestions?

Roy ,
Hello… When you Click on the registry entry… and expand them, did you start on the last entry ? (to take ownership ) I have never had this “take ownership” tactic fail . I know that the sequence that you do things is quite “picky” and if not done correctly it won’t work. Regards Fred

Reply | Quote

Fred,

Hello, yes I did start on the last entry.

I tried again to delete the entries using jv16 Power Tools, and their error message reads:

[15:39:18 – Error]: Failed to remove “HKEY_LOCAL_MACHINESYSTEMControlSet001EnumRootDISPLAY000 : DeviceDesc”! Windows core returned the following error: “Access denied or invalid key (PT)”
[15:39:18 – Error]: Failed to remove “HKEY_LOCAL_MACHINESYSTEMControlSet001EnumRootDISPLAY000 : Mfg”! Windows core returned the following error: “Access denied or invalid key (PT)”
[15:39:18 – Error]: Failed to remove “HKEY_LOCAL_MACHINESYSTEMControlSet001EnumRootDISPLAY000 : HardwareID”! Windows core returned the following error: “Access denied or invalid key (PT)”
[15:39:19 – Error]: Failed to remove “HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumRootDISPLAY000 : DeviceDesc”! Windows core returned the following error: “Access denied or invalid key (PT)”
[15:39:19 – Error]: Failed to remove “HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumRootDISPLAY000 : Mfg”! Windows core returned the following error: “Access denied or invalid key (PT)”
[15:39:19 – Error]: Failed to remove “HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumRootDISPLAY000 : HardwareID”! Windows core returned the following error: “Access denied or invalid key (PT)”

I don’t know what else to try, but hope someone does.

Regards,
Roy

Reply | Quote

Hello, yes I did start on the last entry.

I don’t know what else to try, but hope someone does.

Roy ,
Hello… is there only one entry for the program ? there might be other entries in other “hives” that you would need to remove first.. that are preventing you from removal… I have one more trick it’s called Total uninstall 5… more about that one latter Regards Fred

PS: jv-16 will not remove keys that don’t have the proper ownership. And i agree with Clint..that there is something “leftover” see this thread about removal of “leftovers” http://bro.ws/780052L

Reply | Quote

My OS is Win 7 Pro 32 bit.

I installed the free version of LogMeIn, and subsequently decided to uninstall it. Several registry entries remained, and I cannot delete them. If I try to delete an entry in the right pane of regedit I am told “Unable to delete all registry values”. If I try to delete entries in the left pane I am told “Error while deleting key”. I tried to get help from LogMeIn support, but their reply was “The legacy ones cannot be removed, as they are there to prevent people from misusing the trial of Pro2.” I have gone back to LogMeIn support, pointing out that I installed the free version of their program, not the the trial of Pro2, and asking again how I can delete the remaining reg entries, but am not holding my breath for a reply.

Can anyone tell me how to delete the unwanted reg entries?

Help would be appreciated.

Thanks and regards,
Roy

It would appear that the software program “LogMeIn” was not uninstalled properly. Look for a process or service that specifically belongs to this program and disable/delete it.
You may find it advantageous to do so from safemode.
for deleting services: sc delete “servicename”.
If that does not work, reintsall the program and look over it’s product spec sheet for removal instrunction located on it’s manufacturer/programer website, them proceed to uninstall.
I do not know anything about this program. If the application shares functionality with your browser you will need to see if it has a browser addon component to remove.

LogMeIn Community

CLiNT

Reply | Quote

Hello Clint and Fred,

I tried the sc delete LogMeIn command, but no service was found, and there were no items in Services or Task Manager relating to it, and nothing in browser addons for IE or Firefox.

Fred, with regard to the registry entries, I assume I am right in thinking that in regedit, if I first highlight Computer and then search for the program name, then when entries are found and I have dealt with those, click find next and keep to this routine until regedit says finished checking the registry, that all hives will be searched.

I installed Total Uninstall 5, and that got rid of some, but not all, of the reg entries. However, I used regedit again, and went through the take ownership routine again.When I clicked permissions on the last entry, at first I was told unable to open permissions, access denied. When I right clicked the same entry again and selected permissions I was told something to the effect that I could not view the current permissions but that I could edit permissions! I then clicked Advanced, changed Owner to Administrators, and then gave Administrators full control, and clicked apply and ok. I then right clicked the last reg entry and clicked delete, but at first was told Access Denied! However, after a second or so a sub-key of what previously appeared to be the last key appeared. (I had previously clicked expand on the key I originally thought was the last one, but no sub-key appeared). I went through the same procedure with this sub-key, and was finally able to delete it, and then to delete the parent key. I had to do the foregoing for every remaining key, and finally managed to delete all of them.

I used regedit to search for entries for the program again, as a final check, and I am pleased to say none were found.

Thanks to everyone who contributed to this subject.

Best regards,
Roy

Reply | Quote

.When I clicked permissions on the last entry, at first I was told unable to open permissions, access denied. When I right clicked the same entry again and selected permissions I was told something to the effect that I could not view the current permissions but that I could edit permissions! I then clicked Advanced, changed Owner to Administrators, and then gave Administrators full control, and clicked apply and ok. I then right clicked the last reg entry and clicked delete, but at first was told Access Denied! However, after a second or so a sub-key of what previously appeared to be the last key appeared. (I had previously clicked expand on the key I originally thought was the last one, but no sub-key appeared). I went through the same procedure with this sub-key, and was finally able to delete it, and then to delete the parent key. I had to do the foregoing for every remaining key, and finally managed to delete all of them.

Roy,
Hello…. I’m glad that you prevailed, and probably that you have found out that deleting things, in that land of “OZ” is most times not as easy as it may sound … But be happy in that you have learned another “puzzle piece” Like i have said that deleting things and taking ownership of the registry…. is very “picky” about how it’s done. This “taking ownership” thing is a large pain, and i wish that there was a way to set myself as the “owner” , trusted installer” , and “system” once and for all …with every folder , file , and registry entry, with a couple of commands ….Until that time we will have to slug through and “by shear force of will and determination” take complete ownership of our own PC’s. ….even if we end up sometimes shooting our-self in the foot occasionally…. “trashing” our own system. But after all it’s our PC …right ? Regards Fred

PS: don’t let anyone stop you with the “sky is falling ” argument messing with the registry…. as long as you have a backup that is.

Reply | Quote

It has been my experience in dealing with stubborn registry entries via Regedit, that it works best to logon as a member of the Administrators Group, open MMC, expand Users in Users and Groups, and enable the default Administrator.

Logoff and then logon as the default Adminsitrator, and run Regedit from that account. I have found that the default Administrator has a few more permissions than created accounts in the Administrators Group. I have never experienced a change of ownership failure of any registry entry using the default Administrator account.

Also, I would advise a number of individual searches for the same item or item type; they don’t all show up on the first round. I have used as many as seven or eight searches for the same string before finding and manipulating all the entries I was after. I don’t stop searching until I get three searches in succession that don’t turn up any items in the search string.

That’s three empty searches after the seven or eight successful searches.

Once your registry editing is complete, logoff the default Administrator, logon as a member of the Administrators Group and disable the default Administrator account through MMC.

Also, I say once again that I recommend against using any registry cleaner for any reason at any time. A thousand successes will not make up for one catastrophic failure.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Hello bbearren and Fred,

Fred I agree 100% with your sentiments, and bbearren thanks for the information.

All of the help given to me in this thread is greatly appreciated.

Best regards,
Roy

Reply | Quote

Take Ownership Batchfile Command
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT*shellrunas]
@=”Take Ownership”
“NoWorkingDirectory”=””

[HKEY_CLASSES_ROOT*shellrunascommand]
@=”cmd.exe /c takeown /f “%1” && icacls “%1″ /grant administrators:F”
“IsolatedCommand”=”cmd.exe /c takeown /f “%1” && icacls “%1″ /grant administrators:F”

[HKEY_CLASSES_ROOTDirectoryshellrunas]
@=”Take Ownership”
“NoWorkingDirectory”=””

[HKEY_CLASSES_ROOTDirectoryshellrunascommand]
@=”cmd.exe /c takeown /f “%1” /r /d y && icacls “%1″ /grant administrators:F /t”
“IsolatedCommand”=”cmd.exe /c takeown /f “%1” /r /d y && icacls “%1″ /grant administrators:F /t”

Use the above in a batchfile to take ownership.
Reference thread: Windows 7 Tweaks by veegertx
Integrates into explorer like so..

Reply | Quote

Take Ownership Batchfile Command
Windows Registry Editor Version 5.00

Use the above in a batchfile to take ownership.
Reference thread: Windows 7 Tweaks by veegertx
Integrates into explorer like so..

Clint,
Hello… and thank you for the information… …One question, and then i hope we (if you are willing) can start a new thread so you could explain just how to proceed with doing this , as i have no idea ( the whole batch file thing ) here’s the question…
After doing this procedure is this result the same as having the “take ownership” (right click context menu) as provided by many of the various “tweaks” …WinBubble etc….. If so that does not set “ownership” of everything … just the folder you are clicking on I’m looking to set myself as owner over the whole PC “OS” permanently, …so you don’t have to keep jumping through these hoops. Regards Fred

Reply | Quote

Not an all encompassing “take ownership” of the PC on the whole, just a means to access a file or folder when in need without the
inconvenience of jumping through administrative and security hoops.

A correction to my previous post; The above commands are actually a registry script. In order to use it, copy
and paste it to note pad, name it “InstallTakeOwnership.reg”. Make certain you have file extentions visible.
It will set itself up as a right click option in Windows Explorer as seen in the above photo.

Reply | Quote

A footnote to my previous posts.

LogMeIn replied to my complaint about the leftover registry entries, as follows:

“It is not possible to install LogMeIn Free on a computer. Every time you add a new computer to your account, it is automatically given a trial of Pro2. Even if you were to revert that trial to Free before the Pro2 trial was expired, the registry entries still remain intact to prevent continual re-installation of the software for trial use purposes.

After the trial of Pro2 expired on that computer, it would have then automatically reverted to Free on its own.

We cannot provide any further assistance in altering the computer’s registry. Many companies utilize this same practice for the same purpose and I can assure you it will not be slowing your computer down, besides maybe a few milliseconds when booting it up.”

My reply was as follows:

“Just to let you know I finally managed to delete the remaining registry entries.

The fact that many companies utilise the same practice as yours in altering computer registries does not make it right. It is my computer, nobody elses.”

I don’t suppose for a moment LogMeIn will change their methods, but at least I registered my protest and learned from the experience.

Regards to all,
Roy

Reply | Quote

My reply was as follows:

“Just to let you know I finally managed to delete the remaining registry entries.

The fact that many companies utilise the same practice as yours in altering computer registries does not make it right. It is my computer, nobody elses.”

I don’t suppose for a moment LogMeIn will change their methods, but at least I registered my protest and learned from the experience.

Roy,
Hello…In the words of my “gran-daughter” “Way Cool” Regards Fred

Reply | Quote

Be advised that there are a number of registry entries that, if owned by Administrators or Administrator, will cause numerous difficulties down the road.

It has been my experience that when ownership must be assumed in order to alter a registry entry, the best practice is to revert the ownership to System after the editing is complete.

I have not yet found a way to revert ownership to TrustedInstaller, but System ownership (so far) appears to allow those affected registry entries to continue to operate normally.

I also do not know for certain precisely which keys or how many have this susceptibility, but I do know that there are quite a few.

Drive images can undo lots of “Oops!” moments.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

I’m just gad I don’t have the “disease.” Out of sight, out of mind for me (I know, tisk tisk). I process so much information daily and waste so much time playing games and video and audio media on computers already, I would go insane if I were also concerned with the small, trifling and trivial.

Reply | Quote

I’m just gad I don’t have the “disease.” Out of sight, out of mind for me (I know, tisk tisk). I process so much information daily and waste so much time playing games and video and audio media on computers already, I would go insane if I were also concerned with the small, trifling and trivial.

Curious, then, that you would take the time to offer this irrelevance on a “Windows Secrets” board in an “Undeleteable Registry Entries” thread. On my system, LogMeIn created nearly 300 registry entries. That’s not “small” or “trivial” to me!

The trial/free user gets no clue of the depth at which LMI intertwines itself with the system. Even after uninstallation, a number of its drivers continue to run, as do its services — putting an extra and unauthorized load on the user’s system.

I have been on the trail of uninstalling “LogMeIn” and its junk leftovers from my registry for several days now. In fact, I posted a method the other day about how to solve this problem. However, my solution is neither simple nor complete.

I wanted to thank the posters here for contributing their insights and experiences. Fred offered some excellent ideas, several of which I will pursue shortly, in an effort to post an accurate and comprehensive way to clean up the mess that “LogMeIn” leaves behind. Since it chooses to put itself into keys such as HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumRootDISPLAY, it may have to be handled as though one were trying to excise a driver. So the best option might wind up being a driver-uninstaller script. Sheesh!

I will never buy anything from this company.

Reply | Quote

Perhaps I should have said, doesn’t bother me, 3000 extra enties wouldn’t bother me, 30,000….perhaps a little…so sorry for that. I literally wouldn’t know, cuz I never look. I put the priority on just processing the heck out of tens to more than a hundred gigabytes of information every day. Now if THAT process were to get compromised…then I’m bothered plenty of O’plenty!

Reply | Quote