ums.dll is a Microsoft DLL described as SQL User Mode Scheduler DLL, usually associated with legacy SQL Server components rather than Windows itself. If ums.dll is missing, not found, or cannot be loaded, repair the specific SQL Server instance or older application that originally installed it instead of downloading a replacement file.
What ums.dll is and where it belongs
Historical SQL Server installation inventories place ums.dll in a path similar to:
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Tech-Shop-pro Compatible with install Key Included USB For Windows 11 Home OEM Version 64 bit.... | $48.00 | Buy on Amazon |
C:Program FilesMicrosoft SQL ServerMSSQLBinnums.dll
It is not normally a Windows component stored in C:WindowsSystem32 or C:WindowsSysWOW64. It is also not a Visual C++ Redistributable, DirectX, or .NET file.
The file is associated especially with SQL Server 7.0 and SQL Server 2000-era binaries. Historical inventories list Microsoft as the publisher and show 32-bit SQL Server versions, including 2000.080.0194.00 and 2000.080.0382.00. Those records describe old installations, not a current Windows system requirement.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Do not confuse ums.dll with the Windows User-Mode Scheduling API. Microsoft documents that API separately and states that it is unavailable on Windows 11. That does not make ums.dll a modern Windows system file.
Version and location guide
| What you find | What it usually means |
|---|---|
ums.dll under a SQL Server MSSQLBinn folder |
A legacy SQL Server installation or instance owns the file |
ums.dll under an old application’s folder |
The application may have bundled or privately used SQL Server components |
No copy of ums.dll |
The installation may be incomplete, removed, quarantined, or damaged |
A copy in System32 or SysWOW64 |
Do not assume it is legitimate; verify its publisher, path, and owning program |
| A 32-bit historical file | It must match the application and SQL Server release that expect it |
A program may request the file even when SQL Server itself is not visible. An old accounting package, database utility, installer, or business application may have installed SQL Server privately or depend on a local SQL Server component.
What the error message means
You may see messages such as:
- “The program can’t start because ums.dll is missing from your computer.”
- “There was a problem starting ums.dll.”
- “Error loading ums.dll. The specified module could not be found.”
- “The code execution cannot proceed because ums.dll was not found.”
- “ums.dll is either not designed to run on Windows or it contains an error.”
These are reported variants, not conclusive diagnoses. “The specified module could not be found” can mean that ums.dll is absent, but it can also mean that a dependency required by the DLL is missing or incompatible.
The “not designed to run on Windows” wording can indicate a damaged file, the wrong architecture, an incompatible SQL Server build, or a dependency problem. It does not prove that ums.dll itself is the only damaged component.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Step 1: Identify the program that is failing
Before replacing anything, identify the executable that displays the error.
- Close the error message and note when it appears.
- Start the affected program again.
- If the error appears during startup, write down the program name and version shown in its title bar or shortcut.
- Right-click the program’s shortcut and select Properties.
- On the Shortcut tab, read the Target path.
- Note whether the path points to an old application, a SQL Server tool, a setup program, or a scheduled task.
- Open Settings → Apps → Installed apps on Windows 11, or Settings → Apps → Apps & features on Windows 10.
- Search for the program and for Microsoft SQL Server.
- For older installations, open Control Panel → Programs → Programs and Features and look for SQL Server entries.
If the message appears without opening a program, check startup entries:
- Press
Ctrl+Shift+Esc. - Select Startup apps.
- Disable only entries you recognize as belonging to the failing legacy program.
- Restart Windows and check whether the message returns.
For a deeper check, open Event Viewer:
- Press
Win+R. - Type
eventvwr.mscand press Enter. - Open Windows Logs → Application.
- Look for an error at the time of the failure.
- Record the application name, faulting module, and full path.
You can also search for the file from an elevated Command Prompt:
where /r C: ums.dll
A legitimate copy should normally be inside the original SQL Server or trusted application directory. A copy found in an unexpected folder should be treated cautiously.
Step 2: Repair the owning SQL Server installation
Repair is the safest primary fix when the failing program depends on SQL Server.
- Open Settings → Apps → Installed apps.
- Search for SQL Server.
- Select the matching SQL Server entry and choose Modify, if available.
- Allow SQL Server Setup to load.
- Choose Maintenance.
- Select Repair.
- Select the affected instance when Setup asks which instance to repair.
- Provide the matching installation media if requested.
- Complete the repair and restart Windows.
- Launch the original program again.
On older Windows versions, use Control Panel → Programs and Features, select the matching SQL Server installation, and choose Change to start Setup.
Microsoft documents that SQL Server repair can replace missing or corrupt files, registry entries, and configuration values. Use installation media that matches the installed edition and release. Do not assume a current SQL Server installer can repair SQL Server 7.0 or SQL Server 2000.
For supported current SQL Server releases, Microsoft documents command-line repair in a form similar to:
setup.exe /q /ACTION=Repair /INSTANCENAME=<instancename>
The exact options are version-dependent. Do not apply this command unchanged to a legacy SQL Server installation.
If repair is unavailable:
- Back up databases and record the instance name and configuration.
- Obtain the original installation media.
- Run the SQL Server uninstall process for the affected component.
- Restart Windows if prompted.
- Reinstall the matching SQL Server component.
- Reinstall or repair the application that depends on it.
- Test the application before deleting any old database files.
If Setup reports missing installer-cache files or cannot locate its source, do not copy files into the Windows Installer cache manually. Use valid matching media and follow Microsoft’s guidance for recovering a missing SQL Server installer cache.
Step 3: Repair the older application
If the program installed SQL Server privately, repairing SQL Server alone may not restore the correct files or configuration.
- Open Settings → Apps → Installed apps.
- Find the application that produces the error.
- Select its menu and choose Advanced options, if available.
- Select Repair and wait for it to finish.
- If no repair option exists, choose Modify from Control Panel.
- If the application has its own installer, run that installer from the original vendor media.
- Choose Repair, Modify, or the database prerequisite option when offered.
- Restart Windows and test the program.
If the application was copied from another computer rather than installed, reinstall it from its original trusted media. Copying only the program folder often omits SQL Server services, registry entries, dependencies, and the correct MSSQLBinn path.
Step 4: Check antivirus quarantine
Security software may have removed or quarantined a damaged or suspicious copy.
- Open Windows Security.
- Select Virus & threat protection.
- Select Protection history.
- Look for an event involving
ums.dll. - Expand the event and inspect the detected path and threat details.
- Do not restore the file merely because an application says it is missing.
- If the file came from a trusted, correctly installed SQL Server directory and the detection is confirmed as a false positive, restore it only after verifying the installation and updating Defender.
- If the file was in an unusual directory, leave it quarantined and scan the computer.
If Defender repeatedly flags the file, update security intelligence, run a full scan, and obtain a clean copy through the original Microsoft or application installer. Do not create an exclusion simply to suppress the warning.
For suspected malware:
- Open Windows Security → Virus & threat protection.
- Select Scan options.
- Run Full scan.
- If the problem suggests active malware, select Microsoft Defender Offline scan and follow the restart instructions.
Step 5: Check Windows components with DISM and SFC
SFC and DISM normally repair Windows components, not third-party SQL Server DLLs. Use them if the error began after broader system corruption, failed Windows servicing, or multiple unrelated Windows errors.
Rank #2
- Video Link to instructions and Free support VIA Amazon
- Great Support fast responce
- 15 plus years of experiance
- Key is included
- Open Start and type
cmd. - Right-click Command Prompt.
- Select Run as administrator.
- Run this command and wait for it to finish:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Then run:
sfc /scannow
- Restart Windows.
- Test the affected application.
DISM repairs the Windows image, while SFC checks protected Windows resources. If both commands complete successfully but the application still reports ums.dll, return to the SQL Server or application repair steps.
Crashes, 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 minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Repeatedly running SFC and DISM without identifying the owning application usually will not restore a missing SQL Server file. Outbyte PC Repair can reduce the manual work of checking for system problems and showing what needs attention, but its free scan does not replace repairing the original SQL Server installation; repairs are performed by the full version.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Step 6: Check architecture, dependencies, and drivers
Historical ums.dll listings are 32-bit. A 32-bit application on 64-bit Windows may need the 32-bit SQL Server component in the application’s expected directory. Installing or copying a 64-bit substitute is not a valid fix.
Check the following:
- the application’s architecture;
- the SQL Server edition and release;
- whether the application expects a local or named SQL Server instance;
- whether the file is in the expected
MSSQLBinndirectory; - whether the error began after installing a different SQL Server release;
- whether the file’s dependencies are missing.
Do not move the file between System32, SysWOW64, and an application folder to experiment. If the DLL exists but still will not load, inspect the application’s logs and SQL Server Setup logs for the missing dependency or incompatible entry point.
Drivers are not a normal source of ums.dll, but update-related corruption can cause wider application failures. To check them:
Recommended Free Tools
- Right-click Start and select Device Manager.
- Expand categories related to storage, chipset, display, and network hardware.
- Right-click a device and select Properties.
- Open the Driver tab and record the provider and version.
- Use Update driver only when a suitable driver is available through Windows Update or the hardware manufacturer.
- Restart Windows and test the application.
Outbyte Driver Updater can show which drivers may be stale instead of making you check many devices manually; its free scan identifies issues, while driver installation is handled by the full version. Driver updating remains secondary here, and reinstalling the application or matching SQL Server component is the definitive fix for an application-owned ums.dll.
What not to do
Do not download a random ums.dll
Unverified DLL download sites can provide malware, the wrong SQL Server build, or the wrong architecture. Even a clean file may not fix the missing dependency, registry configuration, SQL Server service, or application search path.
Use the original Microsoft SQL Server installation media or the original application installer instead. Microsoft’s SQL Server repair guidance explains the supported repair approach.
Do not copy it into System32
ums.dll is not normally a Windows system file. Copying it into System32 or SysWOW64 can cause the wrong program to load the wrong build and makes later diagnosis harder.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A controlled recovery may use the exact file from matching trusted installation media, placed back in the original SQL Server Binn directory. Verify the location and product before doing so.
Do not run regsvr32 as a general repair
regsvr32 applies to DLLs that provide the COM self-registration function DllRegisterServer. There is no verified evidence that ums.dll is a self-registering COM component.
Running:
regsvr32 ums.dll
is therefore unlikely to help and may return an error stating that DllRegisterServer was not found. Registration does not restore missing dependencies or repair a SQL Server installation.
If the error remains
Record these details before contacting the application vendor or planning a legacy migration:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- the exact error text;
- the executable that displays it;
- the executable’s full path;
- every location where
ums.dllwas found; - the SQL Server edition, instance name, and release;
- whether the application is 32-bit or 64-bit;
- antivirus Protection History results;
- SQL Server Setup and application log messages;
- the Windows version.
If the program is old enough to require SQL Server 7.0 or 2000-era components, it may not be compatible with current Windows security or runtime behavior. Use the vendor’s supported replacement or migration path. If continued operation is unavoidable, isolate the legacy environment rather than weakening Windows security or mixing DLLs from unrelated installations.
FAQ
Is ums.dll part of Windows 10 or Windows 11?
It is not normally a standard Windows system file. It is historically associated with legacy SQL Server installations and applications that used them.
Is ums.dll a Visual C++ or DirectX file?
No verified evidence identifies it as a Visual C++, DirectX, or .NET runtime component. Installing unrelated runtimes is not the primary remedy.
Should I register ums.dll?
No. regsvr32 is intended for self-registering DLLs, and ums.dll has not been established as one.
Free tools Windows power users keep installed
One-click scans. No signup required.
Can I copy ums.dll from another computer?
Only in a controlled recovery using the exact matching SQL Server build from trusted installation media. Copying a file from another computer can create architecture, dependency, and version problems.
Why does an application request it when SQL Server is not installed?
The application may have bundled an old SQL Server component, may expect a private SQL Server installation, or may have been incompletely copied or removed. Identify and repair the application as well as any SQL Server prerequisite.
What if the file exists but still will not load?
Check dependencies, architecture, SQL Server release, antivirus activity, and the application’s logs. The message can indicate a missing dependency or incompatible file rather than a missing ums.dll itself.
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.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems
