battlebox — audit of the br user profile

2026-07-30 · internal · question asked: is there anything worth preserving before we delete it?

Short answer: no. The profile is 46.9 GB, of which ~45 GB is cache and re-downloadable installers. There is no unique source code, no documents, and no SSH private keys.

Exactly one thing is unique to this machine: a ~7-line defensive try/catch in one C# file. Everything else is either already on Bitbucket or reproducible.

Context: this was a developer account, last actual logon 2023-05-16. We're reclaiming space on battlebox's C: drive, which was down to 1.5 GB free.

What's in the profile

LocationSizeContents
AppData\Local40 GBGoogle Drive cache 29.9 GB (stale since Feb 2023) + NVIDIA 7.2 GB (incl. a single 6.8 GB log file) + NuGet 1.1 GB. All cache. delete
Downloads6.0 GBSee below — the only real content.
source\repos0Completely empty. No code. delete
Documents21 MB827 files, all vendor samples — .NET Reactor SDK test apps, IISExpress config, VS Visualizers. delete
Desktop, OneDrive, Pictures/Videos/Music0Empty (a Teams shortcut and desktop.ini files). delete
.ssh395 Bknown_hosts only — no private keys. No credential exposure. delete

The only content worth discussing

sartorius.assettools (3.6 GB) — a git working copy. It is already safe:

Only two files carry real changes:

Other files in Downloads (~1.6 GB): some 2022 Revit models (Zürich FireBIM) and a set of FBX/NWC exports of a customer transport-system model at several detail levels. These look like project data that should already exist in the project archive on Drive — this is the only thing I could not verify from the machine itself. Worth one check before deleting. The remaining ~600 MB is installers (TeamViewer, TortoiseGit, dotPeek, Google Drive, etc.), all re-downloadable.

Recommendation

  1. Save one patch file (a few KB) for the FileController.cs change:
    git diff -w -- .../FileController.cs > D:\archive\br-sartorius-filecontroller.patch
  2. Confirm the Revit and FBX files (~1.6 GB) exist in the project archive on Drive.
  3. Delete the rest — about 45 GB.

Unrelated to disk space The br Windows account is still enabled, with the password last set in March 2022, on an account unused since May 2023. Worth disabling regardless of what we do with the files.

Two OneDrive scheduled tasks registered under this account still touch the registry hive daily, which makes the profile look active at a glance. It isn't — no processes run under it.