> For the complete documentation index, see [llms.txt](https://www.locksmith.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.locksmith.guide/faqs/more/locksmith-is-not-uninstalling-correctly.md).

# Locksmith is not uninstalling correctly!

What to do when you're having issues uninstalling Locksmith from your theme

Locksmith was designed to integrate into your theme automatically, and pull out automatically as well. Our basic guide to removing Locksmith is here:

{% content-ref url="/pages/bJ5D1IwU7bA8WCPZ7hJ0" %}
[Removing Locksmith](/basics/removing-locksmith.md)
{% endcontent-ref %}

It *can't*, however, automatically remove custom code that's added to your shop theme, to support [manual locking](/keys/more/manual-mode.md) (e.g. for hiding price or add-to-cart buttons).

Because of this, Locksmith will NOT run an uninstallation if it detects custom manual locking code in your theme. If this is affecting you, you'll see this warning in the app, letting you know exactly which theme files contain the detected code:

![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/5ddd799f2c7d3a7e9ae472fc/images/5e1cee9a04286364bc93d593/5e1cee295cdd8.png)

## How to fix this

If they're handy, contact the person who added the manual locking code to the theme, have them remove it, and return to Locksmith's "Help" area to run the removal one more time.

Or, do not hesitate to get in touch with us via email at **<team@uselocksmith.com>** and we'll help you with this as soon as we can!

## Related article:

{% content-ref url="/pages/FWdEXn2S5usZKN7OOBvI" %}
[Locksmith isn't installing correctly!](/faqs/more/locksmith-isnt-installing-correctly.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.locksmith.guide/faqs/more/locksmith-is-not-uninstalling-correctly.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.