Help

1. Create an account here on your phone.
2. On your gaming PC, open this website and press Download. Windows will warn you about the file because it is not signed by a company yet: choose More info, then Run anyway.
3. Put the file somewhere permanent (not your Downloads folder) and double-click it. A QueueUp icon appears by the clock.
4. It shows a six character code. Type that code into this website on your phone. That links the two.
5. Stop the PC going to sleep. On the PC: Settings, System, Power, set "When plugged in, put my device to sleep after" to Never. This one matters more than it sounds: a sleeping PC cannot join anything and QueueUp cannot wake it, so a join scheduled for hours later is simply missed. Letting the screen turn off is fine.

That is it. QueueUp starts with Windows from then on and keeps itself up to date. It checks the sleep setting too, and says so on your dashboard if it would cause trouble.

Smart App Control is a newer Windows 11 feature, stricter than the usual "Windows protected your PC" warning, and it treats anything not signed by a known publisher with suspicion. New Windows 11 laptops often have it on.

It behaves in one of two ways. Often it shows its message and lets you carry on anyway: click through it and QueueUp starts normally. On some PCs it refuses outright, with no way past. If that happens, turn it off:

1. Open Windows Security from the Start menu.
2. App & browser control, then Smart App Control settings.
3. Set it to Off.

Since the April 2026 Windows update you can switch it back on afterwards. On a PC missing that update, turning it off is permanent unless Windows is reinstalled, so update Windows first if you would rather keep it.

Why does this happen? Signing an app costs a few hundred pounds a year, and QueueUp has not bought that yet. It is honestly the next thing on the list.

Four things, and nothing else: it starts Rust through Steam the same way clicking a link does, it reads the game's own log file to see what is happening, it checks whether the game is running, and it can close the game the way you would.

It never touches the game's files or memory, and never presses keys for you. Rust runs Easy Anti-Cheat and QueueUp is built to stay well clear of it.

No. QueueUp never asks for it, never stores it, and has no way to use it. Steam stays signed in on your own PC exactly as it is now.

Yes. QueueUp does the waiting on your PC, so the PC has to be awake and signed in to Windows, with Steam running. Turn off sleep in Windows power settings, or it will nod off and miss the wipe.

Work down this list:

1. Is the QueueUp icon by the clock? Click the small ^ arrow next to the clock: Windows hides new icons there. No icon means QueueUp is not running. Double-click the QueueUp file to start it.
2. Is the PC actually awake? A sleeping PC looks identical to a switched-off one from here.
3. Is the PC online? Open any website on it.
4. Right-click the QueueUp icon and check it does not say "Stopped". If it does, quit it and start it again.

The dot on your dashboard goes green within a few seconds of QueueUp starting.

Connecting can genuinely take a couple of minutes: Rust and Easy Anti-Cheat are slow to start, and the map has to load.

If it sits there much longer:

• Look at the PC. If Rust is showing an error or a Steam window, that is your answer.
• If Rust is not running at all, Steam may be mid-update. Your phone says so when that is happening.
• Cancel the join and tap Join again. If it happens twice, save a problem report.

Normal, especially on force wipe day: Rust ships an update with the wipe and Steam has to download several gigabytes. QueueUp waits for it and connects as soon as it finishes. There is nothing to do.

Two things make it quicker, both worth doing the night before: in Steam, right-click Rust, Properties, Updates, set Always keep this game updated; and leave Steam running, because a closed Steam downloads nothing.

This one needs you at the PC: waiting will not fix it. Open Steam and look at Downloads. Usually it is one of:

• the download was paused, so press resume;
• Steam is in offline mode (Steam menu, then Go Online);
• the drive is full. Rust wipes need several gigabytes free.

QueueUp carries on by itself once the download moves again.

Sign in to Steam on the PC and start the join again. QueueUp tries a couple of times before saying this, so a Steam that was merely restarting will have sorted itself out already.

If Rust crashed, QueueUp relaunches it and rejoins the queue for you. That is deliberate, and your phone says "Rust closed unexpectedly".

If you closed Rust, QueueUp takes that as a cancel and stops. It does not reopen a game a person just closed. If it did reopen after you closed it, something is wrong: send a problem report.

It should never do that. Once you are in a server the job is finished and QueueUp leaves the game completely alone, including if you quit the QueueUp icon. If this happened, send a problem report from the tray icon: that is a bug and worth knowing about immediately.

Because nothing outside the game knows it. Rust does not write your queue position to its log, and it does not publish it anywhere else either. QueueUp used to show a number worked out from how long the server's whole queue was, and it was misleading: that is the length of the line, not your place in it, so it could sit unchanged for an hour while you were steadily moving up.

So the screen now says simply that you are in the queue. When you get through it changes to loading into the server, then "You're in", and those are real: they come from the game's own log.

Leaving the server, or backing out of the queue, stops the join. So does closing Rust. QueueUp reads that from the game's log and finishes the join as cancelled, and it will not relaunch the game or pull you back into the server you just left.

If the app kept showing the join running for more than a minute after you left, that is worth reporting: send a problem report from the tray icon. The exact wording Rust uses when you disconnect varies between builds, and the report contains the lines needed to fix it.

That came from the server, not from QueueUp: usually a password, a whitelist, or a ban. Check you can join that server by hand before trying again.

QueueUp retries a bounded number of times, waiting longer each time, then stops rather than hammering a server forever. Look at the timeline on the join screen: the reason it gave up is in there. Fix that, then tap Join again.

The live screen refreshes itself every couple of seconds while a join is running. If it has frozen, pull down to refresh the page. If the whole site fails to load, the relay may be restarting: wait a minute and try again.

Go to Schedule, pick your server and the wipe time, and tick Wait for the wipe. QueueUp then watches that server, and the moment it returns from its wipe restart your PC starts connecting, without waiting for the clock.

Set it earlier than you think you need to. With that ticked, your PC will not touch the server until it has actually wiped, so being early costs you nothing and being late costs you the wipe.

Times are in your phone's local time. If you are travelling, set it in the time zone you are actually in and it will be right.

That is it working. On wipe day the server that is up at your scheduled time is the old one. Joining it would only get you kicked a few minutes later when the wipe restarts it, and then the force wipe update has to download before you can get back in.

So QueueUp waits for the server to go down for its restart and goes into the new one instead.

It joins straight away. Rust servers publish when they started, so QueueUp can see that the server in front of it came up twenty minutes ago and is already the new one. The timeline will say This server has already wiped when that happens.

If a server does not publish its age, QueueUp waits for a restart as usual, and after a couple of hours joins anyway rather than waiting all night. That goes on the timeline too.

Nothing goes wrong, as long as Wait for the wipe is ticked. Your PC watches the old server without joining it and goes in when the new one answers.

Without it ticked, joining early means joining the server that is about to wipe. Leave it ticked on wipe day.

The join is saved and starts the moment your PC comes back. Nothing is lost. The timeline on the join will say the PC was offline.

QueueUp starts again with Windows, reconnects, picks the job back up and requeues by itself. You lose your place in the queue, because the game did, but nothing needs doing at your end.

Settings, then Change password. It asks for your current one.

Doing it signs out anything else that is signed in to your account, which is how you throw off a PC or a phone you no longer trust. You stay signed in where you changed it.

Forgotten it instead? Get a reset link by email. It lasts an hour and works once.

One account, one PC. In Settings, press Unlink next to the PC you have now, then set up the new one the usual way.

Unlinking stops any join running on that PC and cancels joins scheduled for it, so do not do it on wipe morning.

Settings, then Delete my account. It asks for your password and for you to type DELETE.

Nothing is deleted straight away. Your account is set to be deleted in seven days, and we email you to say so. Nothing stops working in the meantime: your PC, your schedules and your saved servers all carry on as normal.

On the day, everything goes at once: your PC link, every join and its timeline, your schedules, your saved servers, and anything you have sent us. After that we cannot get it back for you.

If a subscription is running, cancel it first under Subscription on the same page. Otherwise your card would keep being charged with no account left to cancel from.

Sign in. Every screen carries a bar saying when your account goes, with a Keep my account button. Press it and the deletion is cancelled completely, with nothing lost. It works any time before the day.

If you got the email and did not ask for it, somebody else is in your account. Press Keep my account, then change your password, which signs out whoever else is signed in.