The licence
A patch, plain and simple
xstub answers BimmerUtility's licence check the way the programme expects, so it accepts the licence and keeps running. The rest of the application behaves exactly as it normally would.
Windows · licence patch
xstub is a patch for BimmerUtility. It answers the licence check the way the programme expects, so BimmerUtility accepts it and keeps running. The patch is applied when you start it and undone when you close it, so your machine is left as it was.
For BimmerUtility (bimmerutility.com) · perpetual licence · one machine
Why it exists
xstub is a patch for BimmerUtility. It answers the licence check the way BimmerUtility expects, so the programme accepts it and keeps running. The rest of the application behaves exactly as it normally would.
The licence
xstub answers BimmerUtility's licence check the way the programme expects, so it accepts the licence and keeps running. The rest of the application behaves exactly as it normally would.
One machine
The licence is checked against the server from time to time, which is what lets a revoked key stop working. Between checks the tool runs without a network at all.
Windows 10 / 11
xstub needs an elevated process to patch the licence check. It declares that up front, so Windows shows a UAC prompt instead of failing halfway through with a permission error.
What happens on start
The order matters - xstub sets up what it needs on this machine so it can reach BimmerUtility's licence check, then patches it. Everything it set up is undone when it exits, so your machine is left exactly as it was.
Verify the xstub key first. This is separate from BimmerUtility's own licence — the stub itself must be licensed.
xstub sets up what it needs on this machine so the patch can be applied.
xstub applies the patch to BimmerUtility's licence check.
xstub locates the point where BimmerUtility asks whether the licence is still valid.
xstub answers the licence check the way BimmerUtility expects, so the programme accepts it and keeps running.
When xstub exits, everything it set up is undone, so your machine is left exactly as it was.
Your machine is not left modified
When xstub exits, everything it set up is undone, so your machine is left exactly as it was. If the process is killed outright, starting xstub again cleans up what the previous run left behind.
Getting started
The key binds to this machine on first activation and is stored in %ProgramData%\xstub\license.json. After that, starting xstub takes no arguments at all — and double-clicking the exe works too, because it asks for a key at the prompt when it cannot find one.
Windows raises a UAC prompt on launch: xstub needs an elevated process to patch the licence check.
C:\> xstub --activate XSTB-4H7K-9QM2-VNXR-8TWD-P5JC ok licence bound to this machine ok environment ready ok licence check patched C:\> xstub patch applied — BimmerUtility accepts the licence running — launch BimmerUtility as usual press Ctrl+C to stop and roll back
Your licence
No subscription and no renewal. The licence is checked against the server from time to time — which is what lets a revoked or refunded key stop working — but between checks the tool runs without a network at all.
One machine, bound on first activation
The binding is a hash of Windows' own machine id. It does not change when you reinstall the tool, and it is not transferable by hand — moving a licence goes through support.
Signed activation tokens, verified offline
The server signs your activation with ECDSA P-256; the build ships only the public half, so it can check a token but never mint one. Tokens last about two weeks before the server is consulted again.
Keep your key — it cannot be shown again
Only a hash of it is stored, so nobody can read it back to you, including us. The bot shows a masked form; the full key is delivered once, when you buy.
Kept working from the server side
How the patch behaves is maintained on the licence server, not baked into the exe. It can be adjusted for your build without shipping you a new download.
Licence card
example — this is what /key shows in the bot
Buying
There is no checkout form and no account to create. The bot is the whole storefront: it quotes the amount, gives you an address and a memo, watches the chain, and sends the key the moment the transfer confirms.
Tap Buy
You get a receiving address, the exact amount, and a memo that belongs to your order alone.
Send USD-T on TON
Attach the memo as the transfer comment — that is how your payment is matched to you. Send from a normal wallet; some exchanges strip comments on withdrawal.
The key arrives on its own
A worker watches for the transfer. No need to press anything, though there is an "I have paid" button if you would rather nudge it.
Download whenever
Ask the bot for a link any time you need the build again.
Perpetual licence
One machine. No subscription, no renewal.
Payments settle on chain and are final. Refunds are arranged by hand through payment support, not automatically.
Before you buy
No. xstub patches BimmerUtility's licence check, so the programme accepts the licence it is given and keeps running. There is nothing extra to set up.
xstub needs to be able to patch BimmerUtility's licence check, which requires an elevated process. The exe declares that up front, so Windows shows a UAC prompt instead of failing halfway through with a permission error.
Not by yourself — the key binds to the first machine it is activated on and stays there. A real move (new laptop, reinstalled machine) is a support request: write to payment support in the bot and it is handled by hand.
It keeps working. Activation needs the server once; after that the signed token is valid for about two weeks and xstub starts and runs entirely offline. When the token expires the server has to be reached again for a fresh one.
A disposable guest gets a new machine id each time, which would otherwise look like a new machine to the licence. Set XSTUB_MACHINE_ID to a stable value and ask support to allow it for your licence — without that permission a supplied id is refused, since one value set on twenty machines would make one licence serve all of them.
Then it cannot be matched automatically — the comment is the only thing tying a transfer to your order. It is not lost: write to payment support with the transaction and it is reconciled by hand. Sending from an exchange is the usual cause, as some strip the comment on withdrawal.
No. The build is Windows x64 only and needs an elevated process.
The server keeps only a hash of it, so it genuinely cannot be printed again — not by the bot and not by an operator reading the database. The bot can show you a masked form to confirm which licence is yours, and support can issue a replacement against your purchase.
BimmerUtility keeps behaving exactly as it normally would. Buy the licence in Telegram and you will have the build in a couple of minutes.
Buy in Telegram 10 USDTFor BimmerUtility · Windows 10 / 11 x64 · Administrator required