SharePoint Document Issues

How to Fix Cannot Remove a SharePoint App from Site Contents

Rana GarciaRana Garcia Nov 4, 2026 870 views

Question details

The user is unable to delete a specific SharePoint app from Site Contents using either the web interface or PowerShell, while standard built-in apps can be removed without any problems.

How to Fix Cannot Remove a SharePoint App from Site Contents
Product
Microsoft SharePoint
Device & OS
not provided
Scenario
Attempting to uninstall or clean up an application from a SharePoint site collection.
Observed behavior
The application remains listed in Site Contents even after PowerShell removal commands are executed, and attempting to delete it through the web interface yields an error message.
Before you start

Ensure you have Site Collection Administrator permissions and verify whether the problematic app is a custom deployment or a third-party application.

Solution 1Recommended

Identify the App Type and Gather Error Details

Determine if the affected app is a third-party application and collect specific error outputs to isolate the removal failure.

Built-in apps generally remove cleanly. When a specific app fails to uninstall, it is often due to third-party dependencies, custom deployment states, or specific permission requirements.

1
Verify app origin

Navigate to your Site Contents and check the app details to see if it is a custom or third-party add-in. Test if a standard built-in app can be removed normally to isolate the issue to this specific app.

2
Attempt web interface removal

Try to remove the app through the SharePoint web interface. If a failure screen appears, take note of the exact error message and any correlation IDs provided.

3
Run PowerShell removal

Execute your SharePoint PowerShell removal script once more. Capture the exact red error output in the console, as it often contains specific clues about orphaned components.

Identify the App Type and Gather Error Details
Permissions Check: Ensure that your user account has Site Collection Administrator privileges, as standard owner permissions might not be sufficient for removing deeply integrated third-party apps.
Free Microsoft Office alternative

Looking for a Hassle-Free Office Suite? Try WPS Office

While managing SharePoint apps can require deep technical troubleshooting, your daily document tasks should be straightforward. WPS Office provides a lightweight, highly compatible, and completely free alternative to Microsoft Office for creating, editing, and sharing documents.

  1. 1. Download the installer: Visit the official WPS Office website and click the free download button.
  2. 2. Install the software: Run the downloaded setup file and follow the straightforward on-screen instructions to install WPS Office on your device.
  3. 3. Open your documents: Launch WPS Office and instantly open your existing .docx, .xlsx, or .pptx files with perfect formatting preservation.
Fully compatible with Microsoft Word, Excel, and PowerPoint formatsLightweight design ensures fast installation and smooth performanceFree to use with an intuitive, familiar user interfaceBuilt-in PDF tools for seamless document conversion and editing
microsoft office alternative - wps office

Frequently Asked Questions

Why do built-in SharePoint apps uninstall fine, but third-party apps fail?

Third-party apps often deploy custom actions, web parts, or remote event receivers that integrate deeply with the site. If any of these components are locked or fail to unregister during the removal process, the entire uninstallation will fail, whereas built-in apps handle cleanup natively.

How can I forcefully remove a stubborn SharePoint app using PowerShell?

If standard PowerShell cmdlets fail, SharePoint administrators often use PnP PowerShell. You can use the 'Uninstall-PnPApp' cmdlet to uninstall the app from the site, followed by 'Remove-PnPApp' to delete it completely from the app catalog.

Where can I find the Correlation ID logs for the removal error?

If you receive a 'Sorry, something went wrong' error with a Correlation ID on the web interface, a SharePoint administrator can use the 'Merge-SPLogFile' PowerShell cmdlet or the ULS Viewer tool on the SharePoint server to search for that specific ID and uncover the exact cause.