Get Otto ready: the one-tap setup screen, and the Windows curl (35) / CRYPT_E_NO_REVOCATION_CHECK failure

You bought Booked Solid, installed it on Windows, and the very first screen stopped you cold. One performer described it exactly this way: upon installing BS, I ran the Let's Get Otto Ready and I get this error, and the error was this, in the small terminal area on the screen: curl: (35) schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - The revocation function was unable to check revocation for the certificate. Nothing you press moves it forward. There is a fix that takes about a minute, and it is further down this page. If your setup ran through fine and you only want to know what this screen is asking of you, skip ahead to What this screen is when it works normally.

First, what this is not

This is not your purchase, not your license, not a virus, not a corrupted download, and not something broken on your computer. Booked Solid itself installed correctly. What failed is a single download that the setup screen makes on your behalf, and it failed because of the way your network checks security certificates. When Otto setup fails on Windows at this exact point, you are looking at a network policy, not a fault in the app and not a fault in your machine.

Why it happens

The setup screen runs one command for you, in the embedded terminal you can see on screen:

curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

On Windows, curl uses the operating system's own security stack, called schannel. Before schannel trusts a secure address, it tries to reach the certificate authority's revocation server to confirm that the site's certificate has not been withdrawn. If it cannot reach that server, schannel does not shrug and carry on. It hard-fails, and curl stops rather than continue unchecked. That refusal is the CRYPT_E_NO_REVOCATION_CHECK in your error, and 0x80092012 is the same refusal written as a number. InitializeSecurityContext failed is the step it gave up on.

Three things commonly block that revocation lookup:

• A work, campus, or hotel network that filters outbound traffic.
• A VPN, especially a corporate one.
• Antivirus or security software doing TLS interception, meaning it opens and inspects encrypted traffic on its way through.

In all three cases curl is doing exactly what it was built to do. The download never starts, so the assistant never lands, so the setup screen never lets you through.

Clicking Try again will not fix this one

Almost everyone tries this first, and it is a dead end. Try again restarts the same command on the same network, so it produces the same failure, every single time. This is not an intermittent hiccup that a second attempt catches. Restarting the app, restarting Windows, reinstalling Booked Solid, and re-downloading the installer are dead ends for the same reason: the download that is failing is not part of the Booked Solid installer at all. Do not spend twenty minutes on any of it. Go straight to the fix below.

The fix: install the assistant through PowerShell instead

Here is why this works, because it is worth knowing before you paste anything. It is the same official installer, fetched a different way. PowerShell uses the .NET security stack rather than schannel, and .NET treats an unreachable revocation server as an unknown rather than a failure, so it continues. That sidesteps this whole class of error without weakening anything. It has been run on two customer machines showing exactly your error, and it resolved both.

1. Close Booked Solid completely.
2. Click Start, type PowerShell, and open it. The plain blue one is the right one. It does not need Run as administrator.
3. Paste this line exactly as it is, and press Enter: irm https://claude.ai/install.ps1 | iex
4. Let it run all the way to the end. A minute or two is normal. Leave the window alone until it gives you your prompt back.
5. Open Booked Solid again. It sees that the assistant is now present on your computer and takes you straight to the sign-in step.

In the customer's own words after doing this: No issues using PowerShell and that seems to have worked. I have it running now.

Do not switch the revocation check off

If you search that error, you will be told to re-run the same download with curl's ssl-no-revoke switch. It does make the error go away, and we are asking you not to use it. That switch works by explicitly turning off the certificate safety check on a script that is then piped straight into a shell and run. The risk is small, but it is real, and there is no reason to take it when the PowerShell route above gets you to the identical result with the check left intact.

The sign-in at the end needs a paid Claude plan

This is the next thing that stops people, so it is worth knowing before you get there. Once the assistant is installed, the setup screen asks you to sign in to Claude. That sign-in is your own Claude account, and it needs to be on a paid plan. The free Claude tier does not cover it. Claude Pro, about $20 a month, is the one we recommend and is what Otto runs on for most performers. If you run Autopilot hard every day, you may need Claude Max, about $100 a month. If you do not have a Claude account yet, the sign-in page lets you create one and pick a plan right there. You do not need an API key for any of this. The sign-in is the whole setup.

What this screen is when it works normally

Booked Solid does its thinking through an AI assistant that runs on your own computer. The Let's get Otto ready screen installs that assistant and signs it in for you: two buttons, no terminal commands, nothing technical to figure out. Once both steps are done, you never see this screen again unless something changes on your machine.

The screen appears automatically whenever the assistant is either not installed yet or not signed in. That usually means one of two moments: your very first launch on a new computer, or after something on the machine changed. Everything happens in an embedded terminal area you can watch without touching. When both checks pass, the screen steps aside on its own and you land in the app.

Step 1: install the assistant

1. Click Set this up for me.
2. The app runs the whole install for you inside the embedded terminal on this screen. You can watch it work, but there is nothing for you to type.
3. When it finishes, the screen re-checks readiness. If it does not move on by itself, click I'm ready to re-check.

Step 2: sign in to Claude

Once the assistant is installed, the screen re-titles itself One quick sign-in. Same screen, second step.

1. Click Sign in now. The sign-in starts in the embedded terminal, and your browser opens the Claude sign-in page.
2. Finish the sign-in in your browser. At the end, Claude shows you a sign-in code.
3. Copy that code, come back to Booked Solid, and paste it into the Paste your sign-in code field. If you do not see that field yet, click My browser gave me a code and it appears.
4. Click Continue. The app forwards the code to the terminal for you.
5. Click I'm signed in so the screen can re-check. When everything checks out, the screen disappears and the app opens.

Other things that go sideways on this screen

• Try again restarts the install or the sign-in from the top. It is safe to use as many times as you like, and it is worth one attempt for any error other than the curl one above.
• If the browser page never opened, click Sign in now once more.
• If you pasted the code and nothing happened, check that you copied the whole code, then paste it again and press Continue.
• If the install finished but the screen still will not step aside after clicking I'm ready, close the app and open it again. That final check runs fresh on launch.

If it still does not work

Open a ticket from this help center. While this screen is up it wraps the whole app, so nothing else in Booked Solid is reachable yet and the help center is the way in. Two things make the first reply the useful one: tell us the exact error text from the terminal area, and tell us whether you are on a work computer, a VPN, or running antivirus that inspects web traffic. That one detail is usually enough to solve it on the first pass.

One last thing, because it cost the performer who found this extra time: check your spam folder for our reply. Support answers from Booked Solid have a habit of landing there the first time, and people assume nobody wrote back.