Turn on auto-uninstall for unused builds in ADT Hub (Windows and macOS)

Last updated on November 9, 2026

Overview​

Turn on auto-uninstall so Hub removes builds you have not used for a set number of days every Thursday, act on the Monday removal reminder, and check what Hub removed.

This guide uses AccelByte Development Toolkit (ADT) Hub on Windows. The steps are the same on macOS, apart from one removal reason noted in Troubleshooting.

Prerequisites​

Steps​

Step 1: Check your unused-days limit​

  1. In ADT Hub, click your namespace and select Application Settings.
  2. Select Downloads.
  3. In the Unused builds section, check Unused-days limit. The default is 30 days.
  4. To change it, type a whole number from 7 to 365 and press Enter. A value outside this range is not saved, and the field goes back to your current limit.

Step 2: Turn on auto-uninstall and confirm the preview​

  1. In the same section, turn on Auto-uninstall unused builds.
  2. Hub opens the Turn on auto-uninstall? preview. Read the summary, for example "6 builds (180 GB) will be removed on Thursday 5 November. You get a reminder on Monday first and can keep any of them."
  3. Check the list of builds, sorted from largest to smallest. Keep any build you still need later, from the reminder or My Builds.
  4. Click Confirm. To leave auto-uninstall off, click Cancel. Cancel schedules nothing.

After you confirm, Hub shows "Auto-uninstall is on. First removal on Thursday 5 November." The removal date is always the Thursday after the next Monday reminder. Turning auto-uninstall on never removes anything in the same week.

While auto-uninstall is on, Remind me on Monday about unused builds is greyed out and keeps its value, with the note "Replaced by the removal reminder while auto-uninstall is on".

If no build is past your limit, the preview says "No builds are past your limit. Nothing will be removed before" the first possible date. In the first 30 days after the Hub update, it says "No builds will be removed before" the first removal date after that period.

Step 3: See which builds are due for removal​

  1. Go to My Builds.
  2. Look for the Removal on Thursday 5 November tag next to a build name. Hover over it to see how long the build has been unused.
  3. To list only these builds, click Only builds due for removal above the list. A banner sums up how many builds will be removed on the next date and how much space they use.

Step 4: Act on the removal reminder​

At the start of each week, Hub sends a removal reminder, such as 3 builds will be removed on Thursday 5 November.

  1. Click the system notification, or open the notification panel and select the Activity tab.
  2. Find the removal reminder card. It lists each build with how long it has been unused and its size.
  3. For each build, choose one:
    • To keep it, click Keep build. Hub will not remove it.
    • To remove it before Thursday, select it. Then continue with Step 5.
    • To let Hub remove it on Thursday, do nothing.

You must see the reminder by the end of Monday, and at least 72 hours before removal. A reminder counts as seen when it appears in the open notification panel while the Hub window is open, or when its system notification is delivered. If you first see it later, the builds move to the next Thursday.

There is no snooze. Launching a listed build from Hub before Thursday also takes it off the list.

Step 5: Remove builds now​

  1. On the removal reminder card, select builds, or click Select all.
  2. Click Remove selected now (N), or Remove all now for every listed build.
  3. In the Remove Builds Now dialog, check the count and size. Builds that cannot be removed at this moment are listed under "These builds cannot be removed now and stay on the list:" with the reason.
  4. Click Remove now.

You can also do this from My Builds: click Only builds due for removal, tick the builds, and click Remove now in the bar above the list.

Hub removes the builds in the background and shows "Removing N build(s) in the background. You can keep using Hub." Logs and traces (Saved folder) are always kept.

Step 6: Check what Hub removed​

After a Thursday removal or Remove now, Hub sends a notice such as 2 builds were removed on Thursday 5 November, 95 GB freed. It lists each build and where its Saved folder is now.

To see every automatic removal from the last 12 months:

  1. Click View removal history on the notice, or go to My Builds and select the Removal history tab.
  2. Check the columns Build, Removed, How (Thursday removal or Remove now), Space freed, and Logs and traces (Saved folder).
  3. To open a kept Saved folder, click Open folder. If you deleted it, the row says Folder no longer exists.
  4. To find a build, type its name or version in Search.

You cannot clear the removal history. Builds you uninstall yourself are not listed.

Step 7: Turn off auto-uninstall​

  1. Go to Application Settings > Downloads.
  2. Turn off Auto-uninstall unused builds.

Every planned removal is cancelled at once and the Removal on tags disappear. An open removal reminder is marked Cancelled with "Auto-uninstall was turned off. Nothing will be removed on" that date. From the next week, you get the unused-build reminder again if Remind me on Monday about unused builds is on.

Validation​

  • Auto-uninstall unused builds is on, and Remind me on Monday about unused builds is greyed out.
  • Due builds carry a Removal on tag in My Builds.
  • After Thursday, the removed builds are gone from Installed builds and appear in Removal history with Thursday removal.
  • Each removed build's Saved folder is still in its original place. Click Open folder to check.

Troubleshooting​

  • Symptom: A removal reminder shows a Past tag and "Not removed: the reminder was shown less than 72 hours before. New date: ..." Fix: No action needed. You saw the reminder too late for this Thursday, so Hub moved the builds to the next Thursday. Other reasons you can see here are "Hub was not running on Thursday", "the reminder was not shown in time", and "Hub could not confirm which builds are in use".
  • Symptom: "N builds were not removed" notice. Fix: The notice names each build and the reason. Hub lists the build again on the next Monday and tries again that Thursday. To remove it now, fix the cause and uninstall it from My Builds.
    • "a file is in use by another program": close the program that has files open in the build folder. This reason appears only on Windows. On macOS, Hub checks only for running processes.
    • "the build folder is outside your installation folders": Hub removes only builds inside your installation folders. Uninstall this build by hand.
  • Symptom: A build was not removed and no notice says why. Fix: Builds that are running, installing, updating, or on a disconnected drive are skipped without a failure notice and tried again the next Thursday. Removal also waits until Hub has run for at least 2 minutes and has checked your followed tracks in the last 6 hours. See Build cleanup in ADT Hub.
  • Symptom: "Build name was not removed: running. It stays on Thursday's list." after Remove now. Fix: Close the build and try Remove now again, or let Hub remove it on Thursday.
  • Symptom: Lowering the limit opens a Lower the unused-days limit? preview. Fix: This is expected while auto-uninstall is on. The preview lists the builds that become due. Click Confirm to save the new limit, or Cancel to keep your current one. Raising the limit applies at once, and builds no longer past the limit are marked Cancelled in the reminder.
  • Symptom: No removal reminder in the first weeks. Fix: For 30 days after you first run this Hub version, nothing is listed or removed. My Builds shows "No builds will be removed before" the first possible date.

Next steps​

Last updated on
On this page