Installing Video Unique Booster: requirements and rights
Video Unique Booster is installed with a normal installer. By default the app is installed to the %LOCALAPPDATA%\Programs\Video Unique Booster folder. Installing does not need administrator rights. But the app asks for them at every start. Projects, settings and the log are kept in the app folder.
What the computer needs
| What | Requirement |
|---|---|
| Windows | Windows 10 version 1809 or newer, Windows 11, Windows Server 2019, 2022 or 2025 |
| Bitness | 64-bit only |
| Free space | at least 2 GB |
| Rights | administrator at every start of the app |
| Internet | needed all the time |
The minimum Windows version is set not by the app itself but by the interface library it is built on. The app does not check its minimum Windows version. It will not warn you about a failure either.
Windows Server and VPS with Windows
The app works on Windows Server 2019, 2022 and 2025. This also applies to rented servers with Windows: VPS, VDS and dedicated ones. The app does not work on a server with Linux, for example Ubuntu or Debian. It is installed the same way as on a regular computer. The trial period can also be taken on a server.
A server does not need a graphics card. Without one, the processor encodes the video. The app works out by itself how many videos the server creates at the same time and shows it in the "Check before start" window.
You connect to the server with Remote Desktop (RDP). You can connect from any computer, including a Mac.
Windows Server 2016 does not fit: its kernel is older than Windows 10 version 1809.
Check the bitness before installing. On 32-bit Windows the installer finishes without errors, but the app will not start afterwards. There will be no warning. We have not tested Windows for ARM processors.
Right after installation the folder takes about 736 MB. The installer itself is another 222 MB. After that the folder takes up more and more space: projects and logs pile up next to the app. So 2 GB is a requirement with a margin, not the minimum needed.
The app has no separate requirement for RAM. It works out by itself how many videos your device creates at the same time and shows a warning in the "Check before start" window. If memory runs short during work, the app stops starting new threads.
Nothing needs to be installed in addition. The Visual C++ libraries come with the app. A separate .NET is not needed either: it is needed only to show the processor temperature, and it is part of Windows 10 and 11.
Is the internet needed
Yes, all the time. There are two reasons.
The first is the license. Without an internet connection the main window will not open.
The second is video creation itself. Without a network not a single copy is created. This is also true for the "Local" mode: your processor does the computing, but a connection is still needed.
How to install the app
- Download the installer from videouniquebooster.com. The file name contains the version number, for example
vub_1.11.0_setup.exe. - Run this file. The installer supports Russian, English and Ukrainian. You choose the language at the first step.
- Read the license agreement and confirm that you agree.
- Keep the folder the installer suggested, or set your own. By default it is
%LOCALAPPDATA%\Programs\Video Unique Booster. - To get an icon on the desktop, check the box in the installer window. It is unchecked by default. The app always creates an icon in the "Start" menu.
- Press the install button and wait for the installation to finish.
After installation the app has to be activated. How to do this is described on the Activation page.
Please download the installer only from videouniquebooster.com. Video Unique Booster support never asks you to send the license key, an account password or a cookie file.
Why administrator rights are needed at every start
The requirement for administrator rights is written into the executable file itself. Windows shows an elevation request at every start. Without confirmation the app window will not appear.
The rights are needed for the app to work, not for convenience. Without them part of the app's work is impossible. One noticeable example is the processor temperature sensor: without administrator rights the temperature is not read. The app shows a dash instead of a value, and the overheating pause and notification stop working.
This requirement cannot be removed.
Where the app is installed and where your data is kept
Video Unique Booster keeps its files next to the executable file. It does not write them to system folders.
| What it is | Where it is |
|---|---|
| The app itself | %LOCALAPPDATA%\Programs\Video Unique Booster |
| The list of projects and their settings | the projects file in the app folder |
| General app settings | the globalsettings file in the app folder |
| The log | the logs folder, the app.log file in the app folder |
| Reports on hangs and crashes | the logs\hangs folder in the app folder |
| Device state during work | logs\resource_monitor.txt, if the "Log device state to a file during video creation" setting is on |
The size of the log is limited. The app.log file grows up to 5 MB. After that the app saves it as the previous one and creates a new one. At any time it keeps the current file and three previous ones.
Sometimes the app folder is closed for writing. Then the app keeps the log in a backup folder: %TEMP%\TekoSoftware\logs\app.log. This happens when the app is installed in Program Files.
Created videos are not saved to the app folder. The app saves them where you said. The path is set by the "Folder to save videos to" setting in the project itself.
ClipSave saves downloaded videos to the "ClipSave" subfolder inside the same folder. While no folder is set in the project, the "ClipSave" subfolder appears next to the app.
What happens to your data on update and removal
When a new version is installed over the old one, your files stay in place. The installer writes only the files of the app itself to disk. Your files are unknown to the installer, so it does not touch them.
- Projects stay. This is the
projectsfile. - General settings stay. This is the
globalsettingsfile. - Logs in the
logsfolder stay. - The activation key stays: you do not need to enter it again.
There is also a reverse effect. The installer does not delete files of past versions. They stay in the folder. So over time the folder takes more space than right after installation.
Removing the app through "Add or remove programs" does not touch projects either. The uninstaller removes only what it installed itself. The app folder stays on disk together with projects, settings and logs. You will not see a message about this: for the uninstaller the work is fully done.
This leads to one warning. If you delete the app folder entirely - by hand, not through "Add or remove programs" - the projects are deleted with it. They are inside this folder. Please copy the projects file to another place before deleting the folder. What exactly to copy and how to bring the copy back: where your files are kept.
Which video formats can be imported
The "Import video" button accepts 13 formats:
mp4, mov, mkv, avi, webm, m4v, wmv, flv, mpg, mpeg, ts, m2ts, 3gp.
Sometimes a media file is needed, not just a video. Then audio formats are added to the list:
mp3, wav, flac, aac, m4a, ogg, opus, wma.
Nothing needs to be installed in addition. The video processing module comes with the app. It is installed together with the app.
What affects the speed of video creation
The speed depends on the settings and on the state of your device. Three settings have the strongest effect. These are "File compression" in the "Performance" section, "Number of local threads" in the "Export" section and the limit of logical processors per thread.
"Number of local threads" in the "Export" section. This is the number of videos the app creates at the same time on your device's processor. By default it takes half of your device's logical processors, but no more than 5. On a device with 8 logical processors this is 4. With 4 logical processors, 2. With 10 or more, 5. The more threads, the higher the processor load.
"Limit logical processors per thread". The setting is needed if you work in other resource-hungry apps at the same time. Video Unique Booster creates videos in the background meanwhile. Under the switch is the "Maximum logical processors per thread" field. An example from the hint in the app. The processor has 10 logical processors. 2 threads are set. Logical processors per thread: 3. Then the app takes at most 6 logical processors. The limit lowers the load. Together with the load, the speed drops too.
Project complexity. The counter is in the project window. It shows the sum of the complexity of all the settings you turned on. The higher the complexity, the lower the speed of video creation. You can click the counter. A table opens. It shows which setting loads the system the most.
Device state. While resource monitoring is on, the app measures the state of the device. It watches the processor, RAM and disk:
- the processor has heated up to 85 °C or more - the app stops starting new local threads. It continues when the processor cools down to 65 °C. Threads that are already running keep working;
- the disk is 95% full or more - the app shows a warning. From 99% it stops handing out new tasks. This applies to both the device and the cloud: there is nowhere to save the finished file. Threads that are already running keep working.
Part of the work can be moved from your device to the cloud. The difference between the two modes is covered on the Video creation on the device and in the cloud page.
Can I open two app windows
No. The projects file is shared by all running copies of the app. So a second start shows the "The app is already running" window.
Sometimes no window is visible, but the app still does not start. This means the first copy is still running. Please close it through Task Manager. Then start the app again.
How to collect a detailed log for support
Next to the executable file there is debug.cmd. It starts Video Unique Booster with a detailed log.
- Open the app folder.
- Run
debug.cmdinstead of the normal icon. - Repeat what did not work right.
- Send the
logs\app.logfile from the app folder to support.
A normal start also keeps a log, but without the details.
Frequently asked questions
Are administrator rights needed for installation?
No. The installer works with normal rights. The rights are needed by the app itself at start.
Why does the app not start from the command line?
The executable file has the administrator rights requirement written into it. Rights are not elevated from the command line. A direct start ends with error 740 "The requested operation requires elevation". Please start the app with its icon.
How do I move project settings to another computer?
Right-click the project card. The menu has the "Save settings to file" item. It saves the settings as a .csv table or a .json file. On the other computer the same file is read by the "Load settings from file" item. Both items are unavailable while the project is open in a tab.
Where do I see the installed version number?
In the "About the app" window. Press the menu button at the top of the main window - the icon with three bars. Choose the "About the app" item. The window has the "App version" line and a button that copies the number.
The number is nowhere else in the app windows. Not in the window title, not on the splash screen at start.
Do not confuse it with another number. At the bottom of the "Sources" section there is the label "Video download module: version ...". This is the version of the external download module, not the version of the app. It is written as a date, for example 2026.07.30.
The app also writes the version number as the first line of the logs\app.log log.
How do I update to a new version?
The app checks for updates by itself. What to do if an update does not appear or does not install is described on the Updates page.
What do I do if the window turns white and Windows shows "Not Responding"?
This is a separate case with its own page. Please open the App is not responding page.