Rescue
Stuck?
Nearly everything here is one thing gone wrong, and re-running is safe. Start with the check, read the row marked PROBLEM, fix that, run again.
First: ask your assistant
If Claude Code is already running on your machine, tell it what you are seeing, in your own words, and let it look. It can read the actual error, check the actual files, and fix most of this without you touching anything. That is the fastest route and it is the one to try before the rest of this page.
Second: run the check
This looks at your machine and prints a status table. It installs nothing, changes nothing, and sends nothing.
& ([scriptblock]::Create((irm https://learnmyos.com/get-ready.ps1))) -Doctor
PLACEHOLDER: this address is not live yet, so the line above cannot work from this draft.
Paste it into PowerShell and press Enter. You get a table like the one below, one row per thing that has to be true. Anything not marked OK is the thing to fix.
What each row means
| Row | What it is checking | If it is not OK |
|---|---|---|
| Windows version | That this is Windows 10 or 11. | MYOS is Windows only. There is no fix on a Mac or a Linux box. Mac waitlist. |
| Disk space | Enough free space on the drive to install and unpack. | Free some space and run again. Nothing is lost by re-running. |
| winget | The Windows package installer, which is how the other pieces get installed. | On an older or heavily managed machine this can be missing. The setup falls back to downloading installers directly, so this row alone is not fatal. If everything below it also failed, you are probably on a locked-down work laptop. |
| Git for Windows | Installed and reporting a version. | Claude Code runs without it, so this is a warning rather than a blocker. Your vault's own history needs it, so it is worth fixing when you can. |
| Claude Code | Installed and reporting a version. | Run the setup line again. If it installs but the row still fails, open a fresh PowerShell window and check there: Windows only gives a changed PATH to windows opened afterwards. |
| Obsidian | Installed. It is the window you read your vault through. | Run the setup line again, or install Obsidian yourself from obsidian.md and run again. |
| Claude account | That you are signed in and your plan can actually run Claude Code. It asks a real question and reads the answer. | Two causes. Signed out: sign in and run again. On the free plan: it says "free plan, needs Pro or above". Take a paid Claude plan, then run the same line again. Nothing you have done is lost. |
| Receipt line | The small helper that makes the line in your receipt email work whether you paste it into PowerShell or into Claude. | Run the setup line again to write it. If it still fails, you can always use the fallback form of the receipt line, described below. |
| Kit version | Which version of MYOS is on this machine. Only appears once a vault is installed. | Reporting "unknown" is not a fault. Tell us the value if you email us. |
| Vault size | How big your notes are, next to how big their saved history has grown. | A warning here means the history has grown out of proportion to the notes. Nothing is broken. Mention it when you write to us. |
| Script configuration | Whether this copy of the setup script was published with its support address filled in. | If this row complains, the fault is ours and not yours. Write to us. |
The common ones, before you read any codes
I typed claude and Windows says it is not recognised
Open a fresh PowerShell window and try again. Windows hands a changed PATH only to windows opened after the change, so the window that installed it can be the one window where it does not resolve.
I pasted the line and nothing happened
Check you are in PowerShell rather than Command Prompt, and that the whole line arrived in one piece. A line broken across two lines by the paste will not run. Copy it again with the copy button.
It asked whether I trust the files and I said no
Close the window, start again, and say yes. Saying no means the folder's own settings are ignored and your assistant stops to ask permission for every single file it touches. You will meet this question twice in total: once for your home folder, once for your vault.
I pasted the line from my receipt into the wrong place
Either place works. Pasted into a running Claude session it reads as an instruction. Pasted into PowerShell, a helper installed during the free setup hands it to Claude for you. If that helper is missing, use this form instead, with your own link in place of the address:
claude "Fetch <your link> and follow it exactly to install my MYOS vault."I am on a work laptop
This is the most common reason an install cannot be rescued. Corporate policy can block script execution, package installs, or the download itself. Antivirus and VPN software can quarantine or intercept the file. If you cannot get an exception from whoever manages the machine, try a personal computer, and if that is not possible, the guarantee covers you.
Install messages, and what they mean
If the install fails, it prints a line ending in a code. Find it here.
| Code | What happened | What to do |
|---|---|---|
MYOS-E-TOKEN-UNKNOWN | The link is not recognised. | Paste the line from your receipt email again, in full and unedited. If it fails a second time, write to us. |
MYOS-E-TOKEN-EXPIRED | The link is past its date. | Write to us for a fresh one. There is nothing more to pay. |
MYOS-E-TOKEN-EXHAUSTED | The link has been used too many times. | Same: write to us and we send a fresh one, no questions and nothing to pay. |
MYOS-E-DOWNLOAD | The download did not complete. | Usually a network in the way. Work laptop, VPN, or antivirus are the three suspects. Turn off the VPN, try again, and tell your assistant what you are on so it can test the connection itself. |
MYOS-E-DOWNLOAD-SHORT | The file arrived incomplete. | Run it again. |
MYOS-E-EXTRACT | Unpacking failed. | Run it again. If antivirus quarantined the file, that is the cause. |
MYOS-E-EXTRACT-INCOMPLETE | Unpacking stopped part way. | Run it again. |
MYOS-E-ZIP-SHAPE | What arrived is not a MYOS vault. | Do not retry. Write to us. |
MYOS-E-VERIFY | It installed but did not pass its own checks. | Run it again exactly as written. It saves a snapshot first, puts back anything missing, and never writes over a file that is already there. |
MYOS-E-NO-TOKEN | The install ran without your link. | The instruction block was changed before it ran. Start again from the line in your receipt email and let it run as written. |
MYOS-E-EXISTING-VAULT | There are already files where your vault goes, and this machine has no record of putting them there. | Nothing was touched. Work out what they are first: a vault you copied from another machine, or an interrupted install. If you want to keep them, keep them. If you want a clean copy, your assistant will ask you to type REPLACE, and the whole folder is moved to a dated backup beside it before anything else happens. |
MYOS-E-FORCE-UNCONFIRMED | A replacement was requested without the typed confirmation. | Type REPLACE when asked, then run again. |
MYOS-E-NO-BACKUP | A copy of your existing files could not be made, so nothing was touched. | Check free disk space and try again. Do not work around this one: it is the guard that protects what is already there. |
MYOS-E-NOT-WINDOWS | This is not a Windows machine. | MYOS is Windows only. Mac waitlist. |
MYOS-E-NO-RESULT | A report was asked for before any install had run. | Nothing to report yet. Run the install first. |
MYOS-E-NOT-SENT | A report was asked for but nothing left the machine. | Nothing was sent. Send us the install log instead. |
Checking an install without changing anything
This re-checks the vault, the files inside it and the myos command, then prints OK or FAILED. It changes nothing.
powershell -NoProfile -ExecutionPolicy Bypass -File (Join-Path $env:TEMP 'myos-install-vault.ps1') -VerifyOnlyThe log, and what to send us
Every run writes a record to %LOCALAPPDATA%\MYOS\install.log. Attach that file to your email and we can usually see the cause without a back-and-forth. It contains what the setup did on your machine. It does not contain anything from inside your vault.
A working email address and the time we aim to reply within go here. This page is the last stop for a stuck buyer, so it cannot ship without them.
If it will not run, you get your money back
Write to us and say it will not run. Give us a fair chance to help. If we still cannot get it going on your machine, you get the full US$500 back, and that holds even when the cause is your laptop, your network or your antivirus.
This sits on top of your legal rights and takes nothing away from them.