The error message “The specified account already exists” during installation usually occurs on Windows when a program’s previous installation was not fully removed or its registry entries remain active. This is a Windows Installer (MSI) Error Code 1316, commonly seen when reinstalling or upgrading software such as Epic Games Launcher, Autodesk applications, or others.
Common Causes
A previous version of the program is still partially present in the system registry.
The Windows Installer registry has duplicate user entries created by the app’s first installation.
Corrupted installation or uninstallation processes, which prevent a clean reinstall.
Step-by-Step Fix
Use Microsoft’s “Program Install and Uninstall Troubleshooter”
This official tool can automatically detect and remove leftover registry keys that block installation.
Download from Microsoft Support: https://support.microsoft.com/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed.
Manually uninstall remnants
Open Programs and Features in Control Panel.
If the app is still listed but can’t be uninstalled, use Revo Uninstaller to force remove it.
Delete related folders under C:\Program Files or C:\Program Files (x86).
Clean Windows Installer and Registry
Run Command Prompt (Admin) and execute:
sfc /scannow
This checks and repairs missing system components.
Optionally, run:
net user administrator /active:yes
Then log in as Administrator, reinstall the software, and disable it again with
net user administrator /active:no
Install the latest version
After cleaning, download and install the latest version of the software directly from its official site to avoid outdated or corrupt installation bundles.
Summary
This issue is not related to user accounts, but rather Windows Installer entries referring to earlier program setups. Using Microsoft’s uninstall fix tool and cleaning old installation traces usually resolves it fully.
Where can I download a clean version of Cubase 14? I’ll try uninstalling Cubase. Your site offers versions starting from 14.0.5, if I understand correctly.
I downloaded the “Program Install and Uninstall Troubleshooter”, and uninstalled Cubase 14. By the way, uninstalling directly from “Add Remove Programs” kept giving me those errors that a file was missing. After that I ran the Download Assistant and installed Cubase 14.0.40.
I did just that. I reinstalled Cubase and restarted the computer and MediaBay now behaves =) …not entirely according to my wishes, but that’s another discussion.
I feel you and its frustrating! However, I’m sure Steinberg does its fair share of tests before shipping their software. The problem usually lies in the thousands of drivers, shared libraries, system configurations and their squared number of versions out there sitting on millions of computers. Its impossible to predict and test all these use cases. For each product you install, some libraries, drivers and configurations may by updated or modified by that product, which former version or setting was relied upon by another product. This in turn adds to the potential instability of your system. I would cut Steinberg some slack in this case.
Yes you make a good point if this didn’t happen nearly every update, but I don’t work for Steinberg, nor am I an apologist for them. I am a customer, my money is the slack. They receive it, and I expect the product to be close to flawless.
I can’t understand though why the same problems don’t occur to nearly the same degree with other software updates, thinking of things like Microsoft Word and Excel, Adobe, etc.
Or even updates to operating systems (Windows, e.g.), or browsers.
These updates come and go without “breaking” things as frequently as it seems Cubase features are broken with each update historically. “Why is that?”, I ask myself.
Regarding other sequencers (Reaper, Studio One, etc.) - I don’t use any of them often enough to have an opinion, but the impression I get from reading comments is that they don’t have the problems with their updates Cubase does.
Maybe, as I’ve read in these pages, it comes down to Cubase being much older, and therefore containing a lot of old code that’s hard to reprogram or possibly even identify that also interacts with the new features and other changes introduced with new Cubase versions. Or not!