It runs, and here is why that is not obvious
The program is old. Its build date, shown in the app under Prefs and then About TinyTask, predates Windows 11 by years.
It is also a 32-bit application. Windows 11 ships only in 64-bit form, which sounds like it should be a problem and is not. Windows 11 runs 32-bit applications without any intervention from you. This one is a plain Windows program using long-standing input functions that have not changed.
That screenshot is TinyTask on Windows 11. Same toolbar, same behaviour, nothing missing.
Display scaling is the real problem
This is the cause of most Windows 11 complaints about this program, and it is not really about Windows 11 at all.
A macro replays screen positions. It clicks a point, not a button. Windows display scaling changes where everything on screen sits, so a macro recorded at one scaling setting aims at the wrong places at another.
You meet this in three situations, and modern machines make all three common.
A laptop with an external monitor. The two screens usually have different scaling. A macro recorded on one misses on the other.
A high resolution laptop screen. Windows applies scaling by default on those, and any change to it moves every target.
Docking and undocking. The layout changes underneath your macros without you doing anything at all.
The fix is not a setting inside the program, because there isn't one. Record the macro on the display you intend to run it on, with scaling left alone, and it will be reliable. If you must move between displays, prefer keyboard steps to clicks, because keys do not depend on screen position.
Administrator rights, the second real problem
If a macro works everywhere except one particular application, this is almost certainly why.
Windows will not let a normal program send input into a program running as administrator. That is a security boundary and it is doing its job. Your macro is not broken. It is being blocked.
The fix is to run this program as administrator too. Right-click the executable and choose to run it that way. Both sides then sit at the same level and input flows normally.
Two things worth knowing. You will get a prompt each time unless you set the file to always run elevated in its properties. And a compiled macro carries the same limitation, so a standalone file handed to somebody else may hit the same wall on their machine. Compiled files are covered on the compile to EXE page.
The taskbar moved, and your old macros know it
Windows 11 centred the taskbar. Anything you recorded on an older version of Windows that clicks the Start button, a pinned application, or the notification area is now clicking empty space.
There is nothing to fix here. Record those macros again on Windows 11. It takes less time than diagnosing it.
The same goes for anything that clicks a window control, a right-click menu entry, or a settings panel, because those moved as well.
SmartScreen and security software
Windows may warn you when you first run the file. It may also say nothing at all.
We could not reproduce a warning on our own test machine, downloading fresh and running the program. SmartScreen decides case by case using reputation signals nobody outside Microsoft can see, so neither outcome tells you anything about the file.
Security software is a different matter, and a flag there is worth understanding rather than ignoring. A program that sends synthetic mouse and keyboard input resembles, behaviourally, things you would not want running. That resemblance is not evidence.
What settles it is the file itself. The download page publishes a checksum, and comparing yours against it takes a minute. The safety page shows the command. If it matches, you have the genuine file whatever your scanner thinks. If it does not, you have a different file and you should delete it.
What does not need doing
A few pieces of advice circulate that are worth ignoring.
Compatibility mode. We have seen no evidence that it changes anything here, and setting it because a program is old is a habit rather than a fix.
Installing anything first. There is no runtime to install and no framework to add. It is one file. It does not need installing at all, as the portable page explains.
Disabling your antivirus. Never a fix, and a genuinely bad idea. Verify the file instead.
When it is not Windows 11's fault
If a macro misbehaves and none of the above applies, the cause is usually in the macro rather than the operating system.
Windows that open in different positions. Dialogs that appear the first time and not the second. Applications that respond more slowly than they did when you recorded. All of those break a fixed sequence of clicks, on any version of Windows.
The full list of causes, including the ones with no fix, is on the not working page. If you are new to the program, the how to use TinyTask guide covers recording in a way that avoids most of them.
Frequently asked questions
No. It runs without compatibility settings and without any installation, and nothing in it needed changing for Windows 11.
No. Windows 11 runs 32-bit applications normally. You do not need to do anything to allow it.
Almost always display scaling. A macro replays fixed screen positions, and scaling moves everything on screen. Record it on the display you intend to run it on.
That program is probably running as administrator, and Windows blocks input from a lower-privileged program into a higher-privileged one. Run this one as administrator too.
The interface moved. The taskbar is centred and several menus and controls are in different places, so a recording that clicked them is now clicking nothing. Record those macros again.
Only when the application you are automating runs that way. For ordinary use it is unnecessary.
We have not tested it, so we are not going to claim it either way. This answer will be replaced once someone with that hardware has actually tried it.