I go to ManageFeatures.aspx and I see bunch of features that don't belong there and they are not in the 14 hive's feature folders. I go to the backend database and look in alldocs, features, and featuretracking tables and don't see them. Now, where do they came from and how do I get rid of them?

Have you upgraded to SharePoint 2010 recently? Also, which Features are they? Custom-added ones?
–
James LoveJul 25 '11 at 16:31

Yes, migration was performed long before I came on board. Trying to clean these up before SP1. And I could not find the old features anywhere. The old developer is gone and took knowledge with him.
–
Robert HalfJul 25 '11 at 16:47

James, get-spfeature is same as looking inside the content database. thoese features dont show up using get-spfeature but they are listed on the managefeature page.
–
Robert HalfJul 25 '11 at 17:14

It it be part of a solution on a site collection?
–
Robert HalfJul 25 '11 at 18:29

Delete from dbo.solutions Now all the junks from sp2007 are gone. what a pia (pain in a air)
–
Robert HalfJul 25 '11 at 18:50

1

Have you contact Microsoft about this solution yet? Directly editing the content database renders your environment completely unsupportable by Microsoft, and is highly discouraged in any and all circumstances.
–
James LoveJul 25 '11 at 22:04

Assuming they these "orphaned features" are active, you can click the deactivate button and note the featureid in the querystring. With that you should be able to use STSADM deactivatefeature and/or uninstallfeature with the force option to remove them.

Hello Rob, Actually, they are not activated so not found when I do get-spfeature. However, if i activate them i get an item created in feature table with brand new guid n everything. i can also de-activate them.
–
Robert HalfJul 25 '11 at 18:10

Delete from dbo.solutions Now all the junks from sp2007 are gone. what a pia (pain in a air)
–
Robert HalfJul 25 '11 at 19:09

Just curious, did you try STSADM uninstallfeature once you had the feature GUID? Assuming that worked/would have worked it would be a preferred solution over directly deleting rows from the database.
–
Rob D'OriaJul 25 '11 at 19:21