Fix: mkdir C:\WINDOWS\system32\openshorts\output: Access is denied
Your first video free up to 60 minutes, then 20 free minutes a month, no credit card.
The fix: your OpenShorts folder is inside C:\Windows\system32. Clone it into your user folder and start it from there:
cd $HOME
git clone https://github.com/mutonby/openshorts.git
cd openshorts
docker compose up --buildIndependent guide, not affiliated with OpenShorts. Checked on November 18, 2026 against docker-compose.yml on mutonby/openshorts main and issue #163.
What the error looks like
The images build, then the backend container fails to start:
✔ Image openshorts-backend Built
✔ Image openshorts-frontend Built
✔ Image openshorts-renderer Built
✘ service:backend:1 Error response from daemon: mkdir C:\WINDOWS\system32\openshorts\output: Access ...
Error response from daemon: mkdir C:\WINDOWS\system32\openshorts\output: Access is denied.
Why it happens
The backend and renderer both mount ./output from the project folder (see docker-compose.yml), and Docker creates
that folder if it is missing. A PowerShell or Command Prompt window opened as Administrator starts in C:\Windows\system32,
so a git clone typed straight away puts the project there. Docker then tries to create
C:\WINDOWS\system32\openshorts\output, and Windows refuses. The person who opened issue #163 traced it to the same thing:
they had cloned from a PowerShell window that was sitting in system32.
The fix, step by step
- Open a normal PowerShell window (not "Run as administrator"), or type
cd $HOMEto move to your user folder. Check withpwd: it should show something likeC:\Users\you. - Clone the repository there:
git clone https://github.com/mutonby/openshorts.git, thencd openshorts. - Start it:
docker compose up --build, then openhttp://localhost:5175. - Optional clean-up: delete the old
C:\Windows\system32\openshortsfolder from an Administrator window.
Next errors you may hit
On the current main branch, the renderer container may then crash-loop with export 'Interactive' was not found in 'remotion'. That one is a version mismatch in the repository and has its own fix. For the full setup, see the OpenShorts install guide.
Would rather not run Docker at all? AIClipMaker.org is a hosted build of the same engine, and your first video is free.
FAQ
- Why is Docker trying to create a folder in C:\WINDOWS\system32?
- Because the openshorts folder is there. docker-compose.yml mounts ./output, a path relative to the project folder, so if the repository was cloned into C:\Windows\system32, the output folder lands there too. Windows protects system32, so Docker is refused.
- How did my clone end up in system32?
- PowerShell or Command Prompt opened as Administrator starts in C:\Windows\system32. Running git clone straight away puts the repository there. The person who reported this on GitHub found the same thing.
- Should I just run Docker as Administrator?
- No. Move the project to a folder you own, such as your user folder. Keeping it in system32 will keep causing problems.
- What do I do with the copy in system32?
- Nothing is running from it, so you can delete C:\Windows\system32\openshorts. Deleting it needs an Administrator window; double-check the path before you do.