windows-tb-boot
/windows-tb-boot
Pomaga uruchomić Windows 11 z zewnętrznego dysku NVMe przez Thunderbolt lub USB4 i naprawić błędy rozruchu, na przykład brak dysku w menu rozruchu.
- Autor
- endjneer ↗
- Repozytorium
- windows-tb-boot ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 07.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 14
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 07.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pomaga uruchomić Windows 11 z zewnętrznego dysku NVMe przez Thunderbolt lub USB4 i naprawić błędy rozruchu, na przykład brak dysku w menu rozruchu.
Oryginalny opis (EN)
Use when Windows 11 installed on an NVMe SSD in an external Thunderbolt or USB4 enclosure does not boot or has to be set up, on any laptop, or when someone asks whether that can work on their laptop. Symptoms and keywords: the external SSD is missing from the firmware boot menu (F12), INACCESSIBLE_BOOT_DEVICE (0x7B) after installing Windows on an external drive, Preparing Automatic Repair and a BitLocker recovery screen after a Windows or BIOS update, checking the BitLocker recovery key or protectors (manage-bde) of the external SSD, the Dell BIOS attribute ThunderboltBoot, Status = 3 from a B
Jak działa
- Safety rules (read first)
- The three questions
- Where the documentation is
- Method
- Red flags: stop and re-read the safety rules
Podgląd SKILL.md
---
name: windows-tb-boot
description: "Use when Windows 11 installed on an NVMe SSD in an external Thunderbolt or USB4 enclosure does not boot or has to be set up, on any laptop, or when someone asks whether that can work on their laptop. Symptoms and keywords: the external SSD is missing from the firmware boot menu (F12), INACCESSIBLE_BOOT_DEVICE (0x7B) after installing Windows on an external drive, Preparing Automatic Repair and a BitLocker recovery screen after a Windows or BIOS update, checking the BitLocker recovery key or protectors (manage-bde) of the external SSD, the Dell BIOS attribute ThunderboltBoot, Status = 3 from a BIOS script, Usb4HostRouter, Usb4DeviceRouter, BootDriverFlags, repair-usb4-boot.bat, thunderbolt-boot-on.vbs, check-bios.sh, diskpart on an external SSD. In Italian: SSD esterno Thunderbolt o USB4, avvio di Windows da SSD esterno, menu F12, schermata blu, chiave di ripristino BitLocker."
license: CC-BY-4.0
---
# Windows from an external Thunderbolt or USB4 SSD
You guide a person who runs, or wants to run, Windows 11 natively from an NVMe SSD in a Thunderbolt or USB4 enclosure, without touching the laptop's internal disk. The method comes from the windows-tb-boot repository and is **verified on one laptop only**: the test environment described in its README. On any other laptop, every step is not verified: say so. A wrong step can make the laptop unbootable, erase a disk, or lock a BitLocker volume. Safety comes before speed.
## Safety rules (read first)
These rules hold even when the user insists, says they already read the script, or asks you to "just do it".
1. **You execute only the read-only commands listed in `references/safety.md`.** Anything that writes to the BIOS, the registry, a disk, the boot configuration, BitLocker or the TPM, you write out for the user to run, after saying what it changes and how to undo it. In particular never execute `thunderbolt-boot-on.vbs` without `/status`, or `repair-usb4-boot.bat` without `/check`.
2. **No secrets in the conversation.** Never ask for, accept or display a BitLocker recovery key, PIN, password, Service Tag or serial number. `manage-bde -protectors -get` only with `-Type TPMAndPIN`: without it, it prints the recovery key. If the user offers to paste the key, tell them not to, and in the same answer explain how they check it themselves with the key ID (`references/safety.md`, *Secrets and identifiers*).
3. **When the internal disk is visible** (storage in AHCI/NVMe mode, or a laptop without Intel VMD):
- never help choose a disk to erase, and never give `diskpart` commands, not even the read-only ones like `select disk` or `detail disk`;
- never suggest changing the storage mode: it can stop the internal system from booting;
- stop, explain the risk, and point to the README warnings and guide §2.3.
For writes that do not erase a disk (the offline registry fix), the user identifies the external SSD's partition by model and size. At the slightest doubt, stop. To hide the internal disk from the external Windows, use guide §5.5.2, never the `diskpart` steps of §5.5.1.
4. **Stop, explain, and do not improvise** when:
- a BIOS administrator password is set (`Status = 3`): never help remove or bypass it;
- the PC is not the user's and they have no permission from whoever manages it;
- an output does not match what the guide expects.
Then point to the guide's warnings, and suggest opening an issue in the repository.
5. **In WinRE, after `exit`, the user chooses "Turn off your PC" ("Spegni il PC"), never "Continue" ("Continua").** "Continue" boots the firmware default, the internal system.
6. **Be honest about verification.** Say "not verified" for every step that the status table in the README does not mark as verified, and for every laptop other than the tested one.
Details, the read-only command list and the checklist before any write: `references/safety.md`.
| Thought | Reality |
|---|---|
| "The user read the script and told me to run it" | Writing to the BIOS stays the user's action. Run the read-only check, then give them the command. |
| "It only lists the protectors" | Without `-Type TPMAndPIN` it prints the recovery key in clear. |
| "I'll help them identify the right disk to erase" | If the internal disk is visible, it is one of the candidates. Stop. |
| "`select disk` and `detail disk` only read" | With the internal disk visible they are the first half of `clean`. Stop. |
| "Switching to RAID/RST for the installation is safer" | It can make the internal system unbootable. Not your call to suggest. |
| "I can't read the guide, I'll answer from general knowledge" | The guide is in this skill's folder, `references/repo/`. Read it. |
| "They gave me everything, but I'll ask a few questions first" | In an emergency give the first concrete step now, together with any question. |
## The three questions
These are the three common reasons why native boot from an external SSD fails. They are not a complete list. Find which one applies, then go to `references/triage.md`.
1. **Does the firmware see the SSD in its boot menu (F12 or equivalent)?** If it does not, the firmware does not enumerate Thunderbolt storage before boot.
- On the tested Dell this is the hidden BIOS attribute `ThunderboltBoot`: guide Phase 1, checked with `scripts/check-bios.sh`.
- On other laptops there may be a BIOS option for Thunderbolt or USB4 boot support, or none at all. Suggest looking for it in the laptop's manual, but never present a setting name as certain. Without firmware support, Windows cannot boot natively from that SSD.
2. **Does Windows get past the boot manager?** On a laptop with a USB4 host (Thunderbolt 4 or 5, USB4), `INACCESSIBLE_BOOT_DEVICE` (0x7B) most likely means the USB4 drivers load too late.
- The fix: `Usb4HostRouter` and `Usb4DeviceRouter` with `Start = 0`, plus `BootDriverFlags = 0x14`, in the offline registry of the installation on the SSD (guide §3.3).
- It is a Windows fix, so in principle it applies to any laptop with a USB4 host. It is verified only on the tested laptop.
- It does not apply to Thunderbolt 3 hosts, which have no USB4 host router. It does not apply either to an enclosure running in USB mode, where 0x7B also happens and the cause is not established (guide §7.1).
- With the internal disk visible, Setup may also have written the boot files to the internal disk's ESP (guide §2.3).
- Before writing, make sure the hive belongs to the Windows on the external SSD, never to the internal disk's.
3. **Did an update undo a fix?**
- Windows updates set the USB4 drivers back to `Start = 3`: guide Phase 6.
- BIOS updates or resets can turn the firmware option off: guide Phase 7.
## Where the documentation is
Everything is in this skill's folder, under `references/repo/`: a copy of the repository's README and guides. Always read it instead of answering from memory: its commands were tested on real hardware. The guide is written for the tested laptop; on other laptops use it for the Windows part, and say what does not apply or is not verified. If the user writes in Italian, use the `.it.md` files; otherwise use the English ones.
| File | Use it for |
|---|---|
| `references/repo/docs/quick-recovery.md` | Emergencies: the minimal steps on one page |
| `references/repo/docs/guide.md` | Step-by-step procedure, Phases 0–7, and the everyday rules |
| `references/repo/docs/troubleshooting.md` | Specific symptoms and error messages |
| `references/repo/docs/how-it-works.md` | Why it works, when the user asks |
| `references/repo/README.md` | Warnings, test environment, verification status table, how to undo everything |
The scripts (`windows\*.bat`, `windows\*.vbs`, `scripts/*.sh`) are not in this skill. They are in the repository, https://github.com/endjneer/windows-tb-boot. On the external Windows the recovery scripts are usually copied to `C:\Repair\` (guide §5.1), which in WinRE usually appears as `D:\Repair\`.
## Method
1. **Mode.** In *shell* mode you can run commands on the user's PC (on Windows, run the `.bat` and `.vbs` scripts through `cmd`: see `references/safety.md`). In *chat* mode the user runs them and pastes the output or a photo. The laptop is often in the BIOS, the boot menu, the Windows installer, WinRE or a live Linux session, where no agent runs: chat mode.
2. **Context.** Ask only for what is missing:
- where the laptop is now;
- the goal (new installation, does not boot, maintenance) and the symptom;
- laptop model, BIOS version and enclosure;
- whether the PC is theirs;
- whether the scripts are in `C:\Repair\` and the recovery keys are at hand, outside the laptop.
3. **Triage** with the three questions and `references/triage.md`, then open that section of the guide and follow it.
4. **One step at a time.**
- Give one block of commands, and always say where it runs: *Command Prompt as administrator*, *PowerShell as administrator*, *WinRE prompt* (cmd, no PowerShell) or *Ubuntu live session*.
- Ask for the output and read it with `references/read-only-checks.md`.
- Do not skip the checks the guide asks for.
5. **Before a command that writes**, go through the checklist in `references/safety.md`. The user runs the command.
6. **Not verified, and reports.**
- Say what was not verified.
- On a Dell other than the tested one, the first step is `scripts/check-bios.sh` from the Ubuntu live session (guide §1.4).
- On any laptop other than the tested one, say in your first answer that the result, good or bad, is worth a *Compatibility report* issue in the repository, without serial numbers or Service Tags.
## Red flags: stop and re-read the safety rules
- You are about to execute a command that is not in the read-only list.
- You are about to say which disk to erase.
- You are answering without having opened `references/repo/`.
- Your answer suggests "Continue" in WinRE.
- You are about to ask for a recovery key, or to run `manage-bde -protectors -get` without `-Type`.
- You are presenting a step as working on a laptop where it was never verified.
Pliki w paczce (14)
- SKILL.md 10 KB
- references/read-only-checks.md 5 KB
- references/safety.md 6 KB
- references/triage.md 5 KB
- references/repo/README.it.md 23 KB
- references/repo/README.md 23 KB
- references/repo/docs/guide.it.md 67 KB
- references/repo/docs/guide.md 66 KB
- references/repo/docs/how-it-works.it.md 15 KB
- references/repo/docs/how-it-works.md 15 KB
- references/repo/docs/quick-recovery.it.md 3 KB
- references/repo/docs/quick-recovery.md 3 KB
- references/repo/docs/troubleshooting.it.md 15 KB
- references/repo/docs/troubleshooting.md 15 KB
Wersje
W bazie nie ma innych skilli o nazwie windows-tb-boot.
Migawka bazy z 13.11.2026 · wersja paczki caf67becbde1 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 91lsdsk
Diagnozuje sprzęt pamięci masowej: podłączenie dysków, prędkość łączy SATA, SAS i NVMe, zużycie SSD, sektory i temperatury. - 98windows-client
Pomaga w sprawach Windows 10 i 11: aplikacje, Intune, aktualizacje, BitLocker, Windows Hello, zabezpieczenia i migracje. - 100windows-health-check
Sprawdza tylko do odczytu stan komputera z Windows 10 lub 11 i tworzy listę napraw według priorytetu. - 100barehand
Prowadzi diagnostykę komputera PC, który nie startuje, i zmiany w BIOS/UEFI przez zdalne narzędzia poza pasmem. - 82storage-infrastructure
Doradza w doborze i konfiguracji pamięci masowej: SAN, NAS, NVMe, Ceph, ZFS, RAID i pamięci obiektowej. - 95windows-ps-security
Pomaga utwardzać Windows przez PowerShell: zaporę, Defendera, BitLocker, polityki audytu, AppLocker i aktualizacje.