Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →choirus2.dll is a genuine legacy Steinberg VST effect plug-in, not a Windows system file. If Cubase reports that choirus2.dll is missing, restore it from the original Cubase VST installation rather than downloading a replacement DLL.
What this file actually does
choirus2.dll has the internal description VST Plug-In and belongs to the old Cubase VST product line from Steinberg Soft- und Hardware GmbH. It is an audio-effect plug-in that Cubase loads from a VST plug-in folder.
As an Amazon Associate I earn from qualifying purchases.
It is commonly associated with other old Steinberg effects, including:
Choirus.dllGrungelizer.dllStereoEcho.dllWunderVerb3.dll
Choirus2.dll and Choirus.dll are not interchangeable. They are separate plug-in files with different names and identities. Replacing one with the other may leave an old project unable to find the effect it originally used.
#1 Best Overall
- Next-Gen Music Production and Beat Maker Essential - USB-powered MIDI keyboard controller with 25 mini velocity-sensitive keys, optimized for studio or beat production, piano-style performance, synth leads, sample triggering
- Real-Time Control and Navigation - 8x assignable 360° knobs, a vibrant full-color screen and push/turn encoder for hands-on access to settings, presets, and DAW functions, without reaching for a computer
- Iconic MPC Pads with RGB Feedback - 8 velocity- and pressure-sensitive MPC pads deliver an iconic finger-drumming experience, plus dynamic visual feedback to match your performance in studio or on the go
- Studio Instrument Collection Included - A powerful VST/AU and standalone virtual suite packing 1000+ pro-grade drums, keys, synths, bass, FX from AIR, Akai Pro and Moog, plus MPK Mini IV integrated controls
- Pre-Mapped DAW Integration - Get producing in under 15 minutes with Ableton Live Lite 12, Logic Pro, FL Studio and more; comes with an expanded DAW-mapped transport section for uninterrupted workflow
The strongest available evidence identifies choirus2.dll as a 32-bit Win32 plug-in. It is not part of Windows, Microsoft Visual C++, DirectX, or .NET. Do not place it in either of these Windows folders:
C:WindowsSystem32
C:WindowsSysWOW64
The precise Cubase VST release that first included the file is not established by a current official component list. It is safely described as a legacy Cubase VST plug-in rather than assigned to a particular release without proof.
Causes and fixes at a glance
| What you see | Most likely cause | First action |
|---|---|---|
Windows says choirus2.dll was not found |
The old plug-in was removed or never installed | Restore the original Cubase VST installation |
| Cubase starts but the effect is absent | The VST folder is not being scanned | Enable VST2 and add the correct plug-in path |
| The file disappeared after security software ran | Antivirus quarantine | Check Windows Security Protection history |
| The file exists but Cubase blocks it | The 32-bit plug-in is incompatible with the host | Use a compatible legacy host or render the effect |
| The error started after moving a disk or VST folder | Cubase still points to the old location | Correct the VST2 path and rescan |
| Cubase crashes during scanning | Damaged plug-in, stale cache, or architecture conflict | Remove the bad path temporarily and test in a compatible environment |
| Windows has other missing-file errors too | Broader system corruption may be present | Run DISM and SFC after restoring the application |
Reported variants include:
- “This application failed to start because choirus2.dll was not found.”
- “The file choirus2.dll is missing or corrupted.”
- “choirus2.dll was not found.”
- “The program can’t start because choirus2.dll is missing from your computer.”
The exact wording can vary by Cubase version, Windows version, and the way the project loads the plug-in. Cubase may instead show a generic plug-in scan failure, omit the effect, or stop during startup.
Fix 1: Restore Cubase VST from the original installer
This is the safest and most likely solution when the file is genuinely missing.
Steinberg still provides unsupported legacy Cubase VST installers and updates through its official support resources. Use the original licensed installation media, Steinberg account, or official legacy download area that matches your Cubase product. Do not use a random DLL download page.
Before reinstalling
- Close Cubase and any Steinberg applications.
- Back up your Cubase projects.
- Note the VST folder used by the old installation, if you know it.
- Check whether
choirus2.dllstill exists elsewhere on the computer: - Press Windows key + E.
- Select This PC.
- In the search box, type:
text
choirus2.dll - Wait for the search to finish.
- If Windows finds the file, do not immediately copy it into a system folder. Record its complete folder path and continue with the VST scan steps below.
Reinstall the legacy product
The exact installer screens differ between Cubase generations, but the process is generally:
- Locate the original Steinberg installer or official legacy download.
- Right-click the installer and select Run as administrator.
- Choose Repair, Modify, or Install, if the installer offers those choices.
- Keep the VST plug-in component selected.
- If the installer asks for a VST folder, choose the original application plug-in folder rather than
System32orSysWOW64. - Complete the installation.
- Restart Windows.
- Open Cubase and rescan the plug-in folder.
Do not assume that installing a current Cubase release will restore every old VST component. Unsupported legacy effects may not be included in a modern installation.
How to tell whether it worked
The repair worked if:
choirus2.dllis present in the intended VST folder.- Cubase completes its plug-in scan.
- The effect appears in the VST effects list.
- The affected project opens without the missing-plug-in message.
If the file is restored but Cubase still does not list it, continue with the VST2 path and compatibility checks. A restored file is not proof that the current host can load it.
Fix 2: Check the VST2 folder and rescan it
A missing-plug-in message does not always mean the file is absent. Cubase may simply be looking in a different folder.
Rank #2
- Music Production and Beat Maker Essential -USB powered MIDI controller with 25 mini MIDI keyboard velocity-sensitive keys for studio production, virtual synthesizer control and beat production
- Total Control of your Production - Innovative 4-way thumbstick for dynamic pitch and modulation control, plus a built-in arpeggiator with adjustable resolution, range and modes
- Native Kontrol Standard (NKS) Integration - Akai Professional and Native Instruments have partnered to bring NKS support to the MPK Controller series, get ready to Kontrol straight from your MPK
- Choose Your Exclusive Complimentary NKS Bundle - Browse and control Native Instruments presets and sound libraries; select one of three curated Komplete 15 Select bundles: Beats, Band, or Electronic
- The MPC Experience - 8 backlit velocity-sensitive MPC-style MIDI beat pads with Note Repeat and Full Level for programming drums, triggering samples and controlling virtual synthesizer / DAW controls
Check the file location
- Open File Explorer.
- Browse to the folder where the original installer placed the plug-in.
- Confirm that the filename is exactly:
text
choirus2.dll - Check that Windows has not renamed it to
choirus2.dll.dll. - Keep any original preset or data folders beside the DLL or in the locations created by the installer.
Do not move the file manually until you know which VST path the project expects.
Enable VST2 in current Cubase
Cubase 14 and Cubase 15 disable VST2 scanning by default.
- Open Cubase.
- Select Studio.
- Select VST Plug-in Manager.
- Open the VST 2 section or enable VST2 support when prompted.
- Add the folder containing the original
choirus2.dll. - Start a scan or rescan from the plug-in manager.
- Close and reopen Cubase.
If the VST2 path controls are not visible, enable VST2 first. Adding a folder to a disabled VST2 subsystem will not make the plug-in appear.
Test the result
Create a temporary project and open the VST effects browser. Search for the effect by name. If Cubase reports that it is blocked or incompatible, the problem is no longer a simple missing-file problem.
Avoid adding broad locations such as the entire Windows directory or a complete drive. Use the specific folder containing the original plug-in. This reduces scan errors and prevents unrelated DLLs from being treated as audio plug-ins.
Fix 3: Check Windows Security quarantine
Antivirus software may quarantine an old plug-in after a Cubase reinstall, disk cleanup, or security-definition update.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Select Start.
- Type Windows Security.
- Open Windows Security.
- Select Virus & threat protection.
- Select Protection history.
- Look for a detection involving
choirus2.dll, the Cubase installer, or the VST folder. - Expand the detection and inspect its name, location, and action.
- Do not restore the file merely because its filename looks familiar.
A file named choirus2.dll found outside a known Steinberg installation is not automatically safe. If the file came from the original licensed Steinberg installer and the installer passes a security scan, restoration may be reasonable. If it came from an unknown download, delete it and obtain the plug-in through the original Steinberg source instead.
After restoring a known-good file:
- Restart Windows.
- Open Cubase.
- Rescan the VST2 folder.
- Check whether the effect loads.
If Windows Security repeatedly quarantines the file, stop using that copy and inspect the detection. Do not create a permanent exclusion just to force an old DLL to load.
Fix 4: Confirm the 32-bit compatibility problem
This is the most important distinction when choirus2.dll is present but still unusable.
Rank #3
- 【Free Premium Cubase LE Software Included】-Get started right away with a complimentary Cubase LE license (valued at $99) – no extra software needed. This powerful tool unlocks multi-track recording, audio/MIDI editing, VST plugin support, and access to a rich audio library. Simply register, and you’re ready to create professional music.
- 【High-Value Configuration for Every Creator】-Enjoy standout performance at an unbeatable price: 25 semi-weighted keys, 8 backlit expandable pads, 8 customizable knobs, a pitch bend wheel, modulation wheel, and an OLED display. Real-time feedback keeps you in control, making every step of your music production seamless.
- 【Flexible Controls to Fuel Creativity】-Shape your sound with ease using the built-in arpeggiator, programmable keys, and customizable knobs. Adjust rhythms, notes, and effects on the fly, tweak speed and time division, and explore endless creative possibilities. Fine-tune every detail directly in your DAW – your vision, fully realized.
- 【Dynamic Performance with Pitch & Mod Wheels】-Add expressiveness to your playing: the modulation wheel lets you craft real-time dynamics like vibrato or filter sweeps, while the pitch bend wheel (with auto-return-to-center) ensures quick, precise adjustments. Perfect for bringing virtual synthesizers to life with natural, nuanced performances.
- 【Trusted Support You Can Count On】- Choose KOKKO with confidence. We stand behind your KB-25 Mini with lifetime expert technical support, a 12-month product guarantee, Amazon’s 30-day easy return policy, and 24/7 customer service. If you run into issues – from parts concerns to usability – we’re here to help, anytime.
The plug-in is identified as a legacy 32-bit effect. A modern 64-bit Cubase installation may reject, blacklist, or fail to scan it. Current Cubase versions also cannot reactivate 32-bit plug-ins that have been placed on the blocklist. On Windows ARM, Steinberg states that 32-bit plug-ins cannot be used.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
This produces symptoms such as:
- The DLL is present, but the effect does not appear.
- Cubase reports that the plug-in is incompatible.
- Cubase crashes while scanning.
- A saved project opens with the effect missing.
- The plug-in manager shows the item as blocked.
- Enabling VST2 does not solve the problem.
What to do
- Open Cubase’s VST Plug-in Manager.
- Search for
Choirus2orchoirus2.dll. - Read the status shown by Cubase.
- If it is listed as blocked because of 32-bit incompatibility, do not keep trying to reactivate it in the current host.
- Open the project in a compatible older 32-bit Cubase environment if you have a legitimate installation and suitable Windows setup.
- If legally and technically appropriate, use a supported bridging arrangement.
- Load the project and render or export the affected track with the effect applied.
- Continue editing the rendered audio in the modern Cubase project.
A current 64-bit Cubase may be able to scan VST2 generally while still being unable to load this particular 32-bit plug-in. Those are separate issues.
Fix 5: Clear a stale plug-in path or cache problem
A corrupted Cubase user profile or stale plug-in cache can prevent discovery even when the DLL and host architecture are compatible.
First, isolate the plug-in:
- Close Cubase.
- Temporarily move
choirus2.dllinto a separate test folder outside the active VST path. - Start Cubase and confirm that it opens without scanning the file.
- Close Cubase.
- Restore the file from the original installation to the intended VST folder.
- Use the VST Plug-in Manager to rescan that specific folder.
If Cubase still crashes, remove the folder from the scan list and test the rest of the plug-ins. A crash that disappears when this folder is excluded suggests that the file, an associated support file, or its 32-bit architecture is the trigger.
Do not delete project files or randomly remove every DLL in the VST directory. Make one change at a time so you can identify the cause.
Recommended Free Tools
Fix 6: Repair or reinstall Cubase
Use this step when the original installer is available but the application or plug-in package is damaged.
- Open Settings.
- Select Apps.
- Select Installed apps.
- Search for Cubase.
- Select the three-dot menu beside the installation, if Repair or Modify is available.
- Follow the installer prompts.
- If no repair option exists, uninstall Cubase only after backing up projects, presets, and custom VST locations.
- Reinstall from the appropriate official Steinberg installer.
- Select the legacy VST component when offered.
- Reboot and rescan the plug-in folder.
Current Steinberg software is normally installed through Steinberg Download Assistant. Older Cubase VST products use their legacy installers instead. Do not expect a modern installer to restore an unsupported historical effect automatically.
If the installer itself fails, copy the installer to a local folder, right-click it, select Properties, unblock it if Windows shows an Unblock option, and run it as administrator. If the installation media is damaged, obtain a fresh copy from the official Steinberg source.
Fix 7: Repair broader Windows component corruption
SFC and DISM repair protected Windows components. They do not normally recreate a third-party Cubase VST plug-in, so use them only when Windows has additional problems such as broken built-in apps, update failures, or several unrelated missing system files.
Rank #4
- The Creative Controller: Launchkey is an all-in-one DAW controller with premium keybeds and 16 responsive FSR pads for drumming, clip launching, and more
- Seamless DAW Integration: Launchkey works with all major DAWs, offering intuitive workflows for Ableton Live, Logic, Cubase, Reason, Reaper, FL Studio, and Ardour
- Go Beyond Finger Drumming: Launchkey’s FSR drum pads with polyphonic aftertouch also serve as step sequencers, clip launchers, chord triggers, and more
- Everything in the box: Ableton Live Lite, Cubase LE, Novation Play, sounds from GForce, Klevgrand, Orchestral Tools, Native Instruments, and free Melodics lessons
- Powerful Creative Tools: Never hit a wrong note with Scale Mode, trigger lush chords from a single key or drum pad, and create and mutate wild arpeggios
Run DISM
- Select Start.
- Type Command Prompt.
- Right-click Command Prompt.
- Select Run as administrator.
- Run:
cmd
DISM /Online /Cleanup-Image /RestoreHealth - Wait for the operation to finish.
- Restart Windows.
Run System File Checker
After restarting:
- Open Command Prompt as administrator again.
- Run:
cmd
sfc /scannow - Wait until verification reaches 100 percent.
- Restart Windows if repairs were made.
- Test Cubase again.
If either command reports that it could not repair files, follow Microsoft’s repair guidance and check Windows Update. Do not expect these commands to place choirus2.dll into a VST folder.
Repeating SFC and DISM without knowing what changed can make troubleshooting circular. Outbyte PC Repair can show what it identifies during its free scan and performs repairs through the full version, but reinstalling the Cubase VST component remains the definitive fix for this application file.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix 8: Update Windows and relevant audio drivers
Drivers are not the normal cause of a missing choirus2.dll, but updating Windows and audio hardware software can help when Cubase also has audio-device crashes, blank output, or startup failures.
Check Windows Update
- Open Settings.
- Select Windows Update.
- Select Check for updates.
- Install available updates.
- Restart when required.
Check Device Manager
- Right-click Start.
- Select Device Manager.
- Expand Sound, video and game controllers.
- Right-click your audio interface or sound device.
- Select Update driver.
- Choose Search automatically for drivers.
- Restart Windows if a driver is installed.
Also check the audio-interface manufacturer’s official support page for a driver that matches your Windows architecture. Do not replace choirus2.dll with a driver DLL.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsManually hunting through many driver packages can be slow when Cubase has several audio devices installed. Outbyte Driver Updater can identify outdated drivers in its free scan, while the full version performs the driver installation; use it as an optional convenience, not as a replacement for restoring the original Cubase plug-in.
Why Visual C++, DirectX, and .NET usually do not help
choirus2.dll is a VST effect, not a Windows runtime component. Installing Visual C++ Redistributable packages, DirectX, or .NET may be appropriate for a separate error, but it will not recreate a missing plug-in or make a 32-bit VST compatible with a 64-bit host.
Only investigate a runtime dependency if:
- Cubase reports a separate runtime error.
- Other applications show the same dependency failure.
- The original Steinberg installer documents that dependency.
- Event Viewer identifies a missing runtime module.
Do not install several unrelated runtimes simply because a DLL error appeared.
Why regsvr32 does not apply
Do not normally run:
regsvr32 choirus2.dll
VST effect DLLs are loaded by the audio host from a plug-in path. They are not normally COM or ActiveX libraries that need registration. regsvr32 is intended for DLLs that expose a registration entry point such as DllRegisterServer.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteIf you run the command, Windows may report:
The module was loaded but the entry-point DllRegisterServer was not found.
That does not mean the file needs a different registration command. It means registration is not the correct repair method for this VST plug-in.
Should you copy the DLL from another computer
Copying choirus2.dll from another computer is not the preferred repair.
The other copy may have:
- A different build.
- Missing presets or support files.
- Damage that was not detected.
- An architecture unsuitable for your Cubase installation.
- A different installation path expected by the project.
If you must recover an old project, use a complete licensed Cubase VST installation or backup, not a loose DLL. After recovery, scan the file with Windows Security and verify that it came from a known Steinberg installation.
Best Value
- Mini Keys, Major Performance - 25-key MIDI controller keyboard with responsive keys to play with feel and dynamics; Enjoy expressive songwriting, composing, jamming, playing melodies, bass lines, and more
- Full Range Experience - Play every note with ease; Use the dedicated octave up and down buttons to transpose the range of your software instruments plus a sustain button for expressive performances
- Feature Packed - Use the built-in arpeggiator and clock for creative control of any of your sound sources like software instruments, synthesizers, or USB-enabled modular gear, all by one USB cable
- Customized Production - With 8 programmable preset slots you can instantly recall your mappings for DAWs, virtual instruments, and more; Create, edit, and manage all your presets from the computer
- Versatile Performance - The USB Studio MIDI controller is perfect for your songwriting, beat-making, and DJ remixes whenever you're inspired; The sleek design fits alongside your studio equipment
Never download the DLL from a random DLL website. Such files can contain malware, be the wrong architecture, have an unverified version, or simply fail because the real problem is VST2 scanning or host incompatibility.
Free tools Windows power users keep installed
One-click scans. No signup required.
When to stop restoring the plug-in
Stop attempting normal Windows repairs when all of these are true:
- The original Cubase VST installation cannot be obtained.
- The DLL is confirmed to be a legacy 32-bit plug-in.
- Your current Cubase installation is 64-bit and blocks it.
- VST2 is enabled and the correct folder is being scanned.
- The project still reports the effect as unavailable.
At that point, use a compatible legacy Cubase environment to open the project and render the affected tracks. If that is not possible, replace the effect with a current chorus plug-in and recreate the sound as closely as practical. Preserve the original project and export stems before changing plug-ins.
Frequently asked questions
Is choirus2.dll legitimate?
The filename is associated with a genuine legacy Steinberg Cubase VST effect. A file is not automatically safe merely because it has that name. Trust its provenance, not just its filename.
Is it part of Windows?
No. It is an application plug-in and should remain in a Cubase VST folder, not in System32 or SysWOW64.
What is the difference between choirus2.dll and Choirus.dll?
They are separate legacy plug-ins. Do not rename one or substitute one for the other in an old project.
Which Cubase version installed it?
It belongs to the old Cubase VST product line. The exact original release containing this file is not confirmed by a current official component manifest.
Can current Cubase load it?
It may not. The plug-in is identified as 32-bit, while modern Cubase installations are generally 64-bit and may block or reject it. Current Cubase also disables VST2 scanning by default in recent versions.
Does installing Visual C++ fix it?
Usually not. This is a VST plug-in restoration or compatibility problem, not normally a Microsoft runtime problem.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Should I use regsvr32?
No. VST effect DLLs are loaded by Cubase and are not normally registered with Windows.
What if the original installer is unavailable?
Try to recover the project in a compatible licensed legacy environment. Then render or export tracks using the old effect and continue in a supported modern host.
Why did the error appear after reinstalling Windows?
The old Cubase VST package may not have been reinstalled, the VST folder may have moved, Windows Security may have quarantined the file, or the new Cubase installation may no longer support its 32-bit architecture.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
