The difference between a toolkit and a junk drawer is a layout decided once and never improvised again. This is a folder system that survives years of updates, new tools and tired midnight repairs.
Open most technicians' repair sticks and you will find the same archaeology: New folder (2), three versions of the same tool, an ISO named final_FINAL2.iso, and nothing findable while a customer waits. The tools were never the problem — the layout was. This page gives a folder structure, naming rules and two small habits that keep a custom toolkit as tidy in year three as on day one.
Your memory under pressure works by task: the disk is clicking, the password is lost, the files must come off. So the top level of Tools is jobs — Disk, Recovery, Backup, Network — and each tool lives inside its job folder. When two tools do the same job, they sit side by side and the weaker one gets deleted at the next update, not hidden in another corner.
This one rule prevents the classic failure: five partition tools scattered across the stick because each arrived in a different month. Jobs are stable; tool fashions change. Organise by the stable thing.
Every file name answers three questions: what, which version, when. DiskHealth_v2.4_2026-09 tells you everything; tool_new.exe tells you nothing. Apply the same pattern to ISOs — Win11_25H2_English.iso beats windows.iso the first time two versions share the stick.
Keep names short, English, and free of spaces and special characters. WinPE command lines, boot menus and older firmware all handle plain names predictably. If a tool's own folder name is a mess of version strings, rename the folder to the job pattern and note the real version in the changelog.
00_README.txt sits at the root and sorts first in every listing. Five lines are enough: what this stick is, its version and build date, what changed last, where the master copy lives, and your phone number if the stick is found in a customer's office. CHANGELOG.txt gets one line per change — date, what was added, removed or updated — written at the moment of the change, never later from memory.
These two files feel like paperwork on day one. By month six they are the difference between knowing your toolkit and guessing at it — and they are what makes sharing the stick with a teammate safe, because the stick explains itself.
Repairs mean temporarily holding other people's data — documents copied off a dying drive, a backup before a reinstall. Give that data exactly one home: a Customer folder, with a subfolder per job named by date and machine. Nothing customer-related ever lands in Tools, ISO or the root.
And the rule that makes it safe: the Customer folder is emptied after every completed job, once the data is confirmed back with its owner. A repair stick that accumulates strangers' documents is a privacy accident waiting for a lost pocket. One folder, emptied every time — simple enough to never skip.
Watch the video to see a real working layout in action, then set yours up the same evening.
▶️ Watch Full VideoFolders on the stick are easier to update — swap one tool without rebuilding the image. Inside the WIM they are available even if the stick's file system is browsed or partially damaged, but every change costs a rebuild. Most custom builds mix both: the repair shell inside the WIM, the tool folders outside it.
The collapse always starts with one lazy drop into the root 'just for now'. The fix is a two-minute rule: nothing lands on the stick without its job folder and a changelog line, and the quarterly update includes ten minutes of deleting orphans. Small discipline, applied every time, beats a yearly spring clean.
Yes — the layout describes the data side of the stick, which is identical either way. On Ventoy the ISO folder becomes the star, since images boot by simply sitting there. Keep the VTOYEFI partition untouched whatever layout you use; Ventoy owns that part.