Overview
This is the environment that ends up on a technician's stick and stays there for years. It carries three preinstallation bases in one image, built from the 11, 10 and 8 lines, so the same stick handles a modern machine that needs current drivers and an old one that will not run the newer base at all. The boot menu offers all three, plus a memory testing entry and a set of loaders for the odd cases.
What distinguishes it from a plain preinstallation image is the tool set. Rather than a command prompt and a hope, you get a desktop with something like a hundred utilities organised by purpose: partitioning, imaging, data rescue, hardware diagnostics, password work, registry editing, driver extraction, network access, browsing and file management. Everything runs from memory, so the target drive can be worked on freely.
The three bases and why they matter
Machines vary more than people expect at the firmware and storage controller level. A very new laptop with a current NVMe controller needs a base with recent drivers, and a machine from a decade ago sometimes refuses to start the newer base at all for reasons that are not worth diagnosing in the field. Carrying all three means the stick works on the machine in front of you rather than the machine you expected.
Both architectures are present. The 32-bit entries exist for old hardware with limited memory and they are genuinely needed occasionally. Everything else should be booted from the 64-bit entries, which have the fuller driver set and can address enough memory to hold a working environment comfortably.
Drivers for storage, network and display are preloaded in each base, including RAID controllers, which is the usual reason a plain preinstallation image comes up to a desktop with no drives visible. If a controller is still missing, drivers can be loaded manually from a folder on the stick.
What is on it
Partitioning is covered by several tools rather than one, because they disagree in useful ways and a layout that one refuses will often be handled by another. Between them they cover resizing, moving, merging, converting table formats, rebuilding boot records and repairing the boot configuration store on both firmware types.
Imaging and cloning tools cover taking a full image before touching anything, restoring one onto bare hardware, and copying a drive directly onto a replacement. Data rescue is a separate group for the case where the file system is broken but the data is there, plus tools for reading what can still be read off a failing drive.
The rest is the technician's kit: memory testing, storage health reading, hardware inventory, offline antivirus scanning, local account password reset, offline registry editing, driver backup from an installation that no longer boots, network access with a browser for looking something up, and a file manager that is pleasant enough to work in for an hour.
Preparing the stick and working from it
Write the image to a stick of 8 GB or larger with a writer that produces a layout bootable under both firmware types. The included writer does this and can leave the remaining space as a normal partition, which is worth doing because a technician's stick that also carries drivers and installers is a stick that gets used.
Secure boot must be disabled in firmware, since the environment is unsigned. Beyond that the usual discipline applies: take an image before you repair, work on the copy where you can, and write down what you change. The tools here are powerful enough to make a recoverable situation unrecoverable if used carelessly, which is true of every tool worth carrying.
What you get
- Three preinstallation bases from the 11, 10 and 8 lines in one image
- Both 32-bit and 64-bit entries in the boot menu
- Storage, network and RAID drivers preloaded in every base
- Multiple partitioning tools that cover each other's refusals
- Imaging, restore and direct drive cloning
- Data rescue for damaged file systems and failing drives
- Local account password reset and offline registry editing
- Memory testing and storage health diagnostics
- Driver extraction from an installation that no longer boots
- Network access with a browser and a usable file manager
Inside the archive
- Strelec environment image, bootable, all three bases
- USB writer that leaves the remaining space usable
- Tool index grouped by purpose
- Additional driver folder for manual loading
- Notes on secure boot and boot menu entries
System requirements
| Firmware | UEFI or legacy BIOS, secure boot must be off |
|---|---|
| Memory | 1 GB for the 32-bit bases, 2 GB or more for 64-bit |
| Media | USB stick of 8 GB or larger, or a dual layer disc |
| Target system | Any x86 or x64 machine, installed system need not boot |
| Second drive | Recommended for holding images taken during recovery |
| Display | Any resolution the firmware reports |
Installing it
- Unpack the archive on a working machine.
- Run the included writer, choose the stick, and confirm the layout it proposes.
- Let it write, this takes a while on a slow stick.
- On the target machine, disable secure boot in firmware setup.
- Boot from the stick and choose a base from the menu, start with the 64-bit 11 entry.
- Image the target drive to a second drive before running any repair tool.
Mirrors
| Route | Region | Note | State |
|---|---|---|---|
| Direct, primary | Europe | No wait, resumable | Online |
| Direct, secondary | North America | No wait, resumable | Online |
| Torrent magnet | Global | Recommended at this size | Online |
Release history
- Driver set refreshed across all three bases for current storage controllers
- Tool index reorganised and several duplicate utilities removed
- Fixed the 32-bit base failing to start on machines reporting large memory
- Added storage health reading for newer NVMe firmware revisions
- Boot menu redrawn and the loader entries labelled more clearly
- Imaging tools updated with restore to dissimilar hardware
- Network stack fixed on adapters that were coming up without an address
Questions about this release
Why does it carry three different bases?
Because machines vary. A new laptop needs the current driver set and a very old one sometimes will not start the newer base at all. Carrying all three means the stick works on whatever is in front of you.
Will it boot under UEFI?
Yes, the written layout covers both firmware types. Secure boot has to be off, since the environment is unsigned.
Can it see my NVMe drive?
Yes, current controller drivers are preloaded. If a controller is still missing, load a driver manually from the folder on the stick.
Is the password reset limited to local accounts?
Yes. It clears or resets a local account password on an offline installation. Accounts tied to an online identity cannot be reset this way.
Can I still use the stick for files?
Yes, the writer leaves the remaining space as a normal partition.
Comments
Storage health reading picked up a failing drive before the customer lost anything. Imaged it straight from the same menu.
32-bit entry fixed on a machine with more memory than the base expected. Was the one thing failing for me.
Comments are read before they appear. If a build stops working, say so here and it gets rebuilt rather than quietly left up.
This has lived on my stick for years. The 8 base has saved me on old machines more times than I can count.