> For the complete documentation index, see [llms.txt](https://www.tvrename.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.tvrename.com/help-and-support/tips-and-tricks.md).

# Tips & Tricks

### Tips from the developers <a href="#tips-from-the-developers" id="tips-from-the-developers"></a>

* Most items can be double-clicked, to do the most “useful” thing for them.
* Folders, shows, and episodes can be right-clicked for menus of appropriate actions.
* Column headers can be clicked to sort by that column.
* Folder lists support “dragging and dropping” folders from Explorer.
* You can remove items from the finding, renaming and organising lists by selecting them, and pressing “Delete” on your keyboard.
* Double-clicking the name of the **TV Shows** or **Schedule** tab does the same as its `Refresh` button, and double-clicking the **Scan** tab starts a scan.
* Changes you make are not saved unless you specifically do so. TV Rename will prompt you to save when you exit (if it needs to), unless **Auto save on Exit** is ticked in **Options>Preferences**, in which case it saves for you. If you screw something up, just exit without saving and TV Rename will forget everything you have done since the last save when it is reloaded.
* TV Rename stores all its data in XML files. For more information on what there is, and where it is, read the [Technical Guide - Configuration Files](https://www.tvrename.com/technical/logs-and-configuration.md).
* A number of TV Rename’s functions can be accessed using the command line. You can find more details [here…](https://www.tvrename.com/technical/command-line.md).
* Whatever manipulation TV Rename applies to your files, it will never change the season or episode number of a show. Even if the show and episode names get corrupted the season and episode numbers will remain unchanged. This means that the problem should be fixable after changing some settings, or adding new rules. At least, that’s the theory.

### Tips from our users <a href="#tips-from-our-users" id="tips-from-our-users"></a>

{% hint style="success" %}
**Drive keeps changing letter?**

If your media library uses removable media to store files the assigned drive letter changing each time a USB device is plugged in can be a real pain.

A small tweak in Windows settings will “fix” the drive letter for the device in question.

There are numerous internet guides for doing this, the following link will get you started:

[**Google - fix USB drive letter assignment**](https://www.google.co.uk/search?q=fix+usb+drive+letter+assignment)

***Andy B***
{% endhint %}

{% hint style="info" %}
**Can't connect to mapped network drives?**

You can change the behaviour of some earlier versions of Windows 10 regarding mapped drives. In the registry under:

**HKEY\_LOCAL\_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System**

Create a new **DWORD (32 Bit)** named **EnableLinkedConnections** and set the value to **“1”**.

Restart Windows after making the change. All applications should now see the same mappings regardless of being in User or Admin mode.

[More information from Microsoft](https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command)

***Jürgen***
{% endhint %}

{% hint style="info" %}
***Screen layout all messed up and using high DPI?***

[*https://groups.google.com/g/tvrename/c/5WjHfCwFLIU/m/9Fb5iywbDQAJ*](https://groups.google.com/g/tvrename/c/5WjHfCwFLIU/m/9Fb5iywbDQAJ)

Changing the high DPI compatibility settings for the shortcut works

<https://groups.google.com/g/tvrename/c/LV47f_md73I>

Another workaround:

[*https://groups.google.com/g/tvrename/c/oAvxJxpBW6g/m/huoHHgmIAgAJ*](https://groups.google.com/g/tvrename/c/oAvxJxpBW6g/m/huoHHgmIAgAJ)

Workarounds:

<https://github.com/TV-Rename/tvrename/issues/909#issuecomment-1153019277>

***Michael***
{% endhint %}

{% hint style="success" %}
**User Tip**

The search function of TheTVDB API is a bit flakey. I find it particularly has a problem with punctuation, but the main thing is that the API only returns exact matches, while when you do a search on the website itself you appear to get partial/fuzzy matches as well. (Mind you, there are times when searching on the web site is *worse*.) But sometimes it's worth doing a search on the website, finding the TheTVDB "code" for the show, and just entering that specifically into TVRename.

To do this, go into the details of the show and in the initial table the top line reads "TheTVDB.com Series ID". Enter the number next to this straight into the "TheTVDB code" box in TVRename, click Search, and a single result should be returned, being the show you wanted. Continue as normal from there.

When making use of the regular search function inside TVRename I find "less is more" - try searching for fewer words. Don't search for words that are acronyms, like "S.H.I.E.L.D." or "M.D.". I usually drop the " 's " (apostrophe of possession and "s") at the end of words too, as that often gets better results, or I drop the words altogether. (e.g. Is the show under "Agatha Christie's Poirot" or just under "Poirot" in the database?) Ultimately, often it's a trade-off between getting a bunch of results where you have to scroll to then find the one you want, and getting no results at all.

*-Michael*
{% endhint %}


---

# 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.tvrename.com/help-and-support/tips-and-tricks.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.
