TinyTask Not Working: Causes and Fixes

This is the most common failure by a wide margin, and it is not a bug.

The program replays screen positions. It recorded that you clicked a point. It did not record that you clicked a Save button, because nothing in the recording knows what a button is.

So anything that moves what is on screen breaks the macro. Four things do that.

A window in a different position. The most common cause of all. Maximise the window before recording, and maximise it before playing.

A different screen resolution. Everything moves proportionally, so every click misses.

Display scaling. Laptops with external monitors are the classic case, because the two screens usually scale differently. Docking and undocking changes it underneath you. The Windows 11 page covers this properly.

The application itself changed. An update moved a menu, a sidebar collapsed, a notification appeared at the top. The macro still aims where things used to be.

The fix is technique, not settings. Record with windows maximised, start from a known state, and use keyboard steps instead of clicks wherever the task allows. Keys do not depend on position at all. That single habit solves more macro problems than everything else on this page combined, and it is covered in the how to use TinyTask guide.

If everything works except one program, this is almost certainly privileges.

Windows will not allow a normal program to send input into a program running as administrator. It is a deliberate security boundary. Your macro is not failing, it is being blocked.

Right-click the program and run it as administrator too. Both sides then sit at the same level and input flows normally.

A compiled macro faces the same rule, so a standalone file may work for you and fail for a colleague whose setup differs. The Windows 11 page has the detail.

Something else has claimed that key, nine times out of ten.

Each hotkey has a small set of options, and the alternatives to the default are all keys other software wants. One of them opens developer tools in every browser. One is claimed by Windows itself. Pick a different option from the menu and try again.

On a laptop there is a second cause. If your function keys default to media controls, the program never sees the press unless you hold the function modifier. Most laptops have a firmware setting to swap that.

The third possibility is that the program cannot save your choice at all, which is the next section. Everything about hotkeys, including which options exist, is on the hotkeys page.

The program cannot write its settings file.

Preferences are stored in a small file beside the executable. If it cannot create or update that file, your settings apply while the program is open and vanish when it closes.

Two causes, and both are about where you put the file.

It is in a protected folder. Program Files is the usual one. Windows blocks ordinary programs from writing there. Move the executable into your documents, your desktop, or a USB drive.

You are running it from inside a compressed archive. Opening the download and double-clicking straight from the archive viewer means there is no real folder to write to. Extract it first.

More on what that file holds is on the settings file page.

There is nothing in memory.

Play stays disabled until you have recorded something or opened a saved recording. Pressing the compile button in that state raises a dialog telling you the same thing.

This also catches people after they close and reopen the program. Recordings are not remembered between sessions. Whatever was in memory is gone, and you need to open the saved file again.

You pressed the record hotkey expecting it to pause.

There is no pause. That key is a toggle: it starts a recording, and it ends one. Press it midway through and you have finished the recording, not paused it. Everything after that point was never captured.

There is no way around this. If you make a mistake halfway through a long macro, record it again from the start.

Usually speed, sometimes state.

Too fast. At high speed the clicks arrive before menus, dialogs and pages are ready, so they land on whatever was underneath. Drop to normal speed and try again. If it works, timing was the cause. The playback speed page explains what each setting does.

Something only happens once. A confirmation dialog that appears the first time and not the second. A login already completed. A field already filled. The macro still clicks where that thing used to be.

The screen did not start where it should. Playback begins from wherever you happen to be, not from wherever you were when you recorded.

You are probably double-clicking it in Windows.

The program does not register its own file type. Windows hands the file to whichever other application has claimed that extension, and that application cannot read it. On our test machine a media player owned it, which is why saved macros can appear with an unrelated icon.

Open recordings with the Open button in the program. Always. The rec files page has the full explanation.

You stopped the recording by clicking Rec with the mouse.

That journey to the toolbar was recorded, because everything before you pressed stop is part of the macro. Use the record hotkey to stop instead. The keypress itself is deliberately excluded from the recording, so nothing is added.

That happens with this category of software, and it is worth understanding rather than working around.

A program that captures keystrokes and injects input resembles a keylogger to a behavioural scanner. The resemblance is unavoidable in a macro tool.

Do not add an exclusion on our say-so. Verify the file instead. The safety page shows the command that confirms whether your copy is identical to the published one. If it matches, you know what you have. If it does not, your scanner was right to be suspicious.

These come up constantly and none of them can be solved with this program. Knowing that now saves you hours.

It cannot make decisions. No conditions, no branching, no checking whether the last step worked.

It cannot wait for something to appear. It waits for the time you recorded, not for the screen.

It cannot find things visually. No image matching, no text recognition, no way to locate a moved button.

It cannot be edited. No timeline, no step list. A wrong macro gets recorded again. The downloads labelled as an editor version are a different vendor's product entirely, as the with editor page shows.

It cannot pause, in either direction. Not during recording and not during playback. Stopping playback is covered on the stop playback page.

It cannot schedule itself, and it has no awareness of multiple monitors beyond raw coordinates.

If your task needs any of these, you have outgrown a recorder. That is not a failure on your part, and continuing to fight it is the expensive option. The alternatives page sets out what to move to.