Found a missing feature ID=’xxxx’ during SharePoint 2010 upgrade

There are many tools out there to detect and remove/delete any feature references in your content database when you face ‘Found a missing feature ID=’XXXX’ during SharePoint ugrade . This can be done directly in SQL database – which is not suggested ofcourse.

When i am trying to mount and upgrade a MOSS 2007 content database to SharePoint 2010 web application, pre upgrade check complained about some of the missing features and also their references in content database.

Clean way of upgrading was to get rid of those missing feature references from content db or install those features if they are still being utilized in your SP 2010 environment.

Incase if you are looking to get rid of them, use the following STSADM commands


 Unistall a feature using Id

Browse to C:\Program Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN in command prompt and then

                     STSADM -o uninstallfeature -id “xxxxxxxx”

If the feature is not installed in the farm any more, it throws an error message saying

Feature with Id ‘xxxxxxxx’ is not installed in this farm. The feature was not uninstalled.

In this case, feature can be deactivated using below command


 Deactivate a feature using Id

Browse to C:\Program Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN in command prompt and then

                     STSADM -o deactivatefeature -id “xxxxxxxx” -force

Note: You may need to use -force attribute to deactivate the feature since it is not currently installed.

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Disable feedback surveys in Power Platform

If you have worked in Microsoft 365 PowerApps or Power Automate, you might be familiar with feedback survey which pops up quite often. Microsoft wants your feedback on how likely are your to recommend Power Automate to a friend or colleague? Well, I ran into a conversation in twitter about this survey. Apparently I learnt […]

Read More

Error handling in Azure PowerShell Runbooks

Error handling in Azure PowerShell Runbooks should be handled carefully if not the runbook with continue to Completed state even if there is an Error in the script. Unlike exception, Runbook execution will continue after  an Error  by default. Windows PowerShell has multiple streams of output. Runbooks in Azure work differently in each of these […]

Read More

SharePoint Designer cannot display the item

You run into ‘SharePoint Designer cannot display the item’ error when you are trying to edit an existing workflow setup in Designer quite often when there is a windows update or update to .NET framework installed in your computer. In some cases it may also not allow you to create new workflows. Resolution: Clearing Designer […]

Read More