ntdsbsrv.dll Missing: Safe Windows Repair and Recovery Steps

ntdsbsrv.dll may trigger messages such as “This application failed to start because ntdsbsrv.dll was not found” or “The program can’t start because ntdsbsrv.dll is missing from your computer.” On a normal Windows PC, this is not usually a game DLL problem and should not be fixed by downloading a replacement from a random DLL site.

Which fix applies to you

Use this quick decision list before changing anything:

• Windows 10 or Windows 11 workstation: Start with Windows Update, then run DISM and SFC. A regular consumer PC may not need this directory-services component at all, so confirm which process is reporting the error.
• The error names lsass.exe: Treat it as a Windows security and directory-services problem. Do not copy a DLL manually or restart repeatedly without checking the system state.
• The error names dsamain.exe, AD LDS, or a directory-services instance: Use the server-specific path in this guide. The machine may have an incomplete, damaged, or outdated AD LDS installation.
• A domain controller: Stop before replacing files. Repair Windows servicing and the AD DS role through supported administration procedures.
• The error appears only in an unrelated application folder: Suspect a bad application installation, an unauthorized DLL copy, or a missing dependency rather than a missing Windows component.
• Windows Security quarantined the file: Do not restore it automatically. Verify the path and Microsoft signature first.
• The error says “The specified module could not be found”: The named DLL may exist while one of its dependencies is missing.
• The problem began after an update, cleanup, malware removal, or disk failure: Check Windows Update history, Protection History, Event Viewer, and disk health before attempting manual file replacement.

What is ntdsbsrv.dll

ntdsbsrv.dll is a genuine Microsoft Windows directory-services component. Microsoft documentation identifies it as the DS Backup Restore component loaded by lsass.exe, with a role in backing up and restoring the directory database on a domain controller. It is associated with Active Directory Domain Services, or AD DS, and Active Directory Lightweight Directory Services, or AD LDS.

It is not a Visual C++ runtime, DirectX component, .NET library, graphics driver, or game-specific runtime. If a game or desktop program displays the error, that does not prove the game requires this DLL directly. The program may be launching a Windows process, using a damaged system component, or reporting a missing dependency indirectly.

Microsoft’s servicing documentation places the file in the Windows directory-services core-files component and documents it on older Windows and Windows Server releases. That does not prove that the same filename is installed on every Windows 10 or Windows 11 edition. Its absence by itself is not proof that your computer is damaged.

On a system that uses the component, the expected copy belongs in the Windows system directories, commonly %windir%System32. Do not assume that every copy found elsewhere is legitimate. A copy in an application directory, Downloads folder, temporary directory, or user-writable location deserves extra scrutiny.

Microsoft has not identified an official standalone ntdsbsrv.dll redistributable. The supported sources are Windows Update, the Windows component store, an applicable cumulative update, an AD DS or AD LDS role installation, or matching Windows repair media.

Check the error before repairing Windows

Identify the failing process

Read the complete error window instead of focusing only on the filename. Note whether it names:

• lsass.exe
• dsamain.exe
• an AD LDS instance
• a Windows service
• a game or desktop application
• an installer or updater

Then open Event Viewer:

1. Press Win + X.
2. Select Event Viewer.
3. Expand Windows Logs and select Application.
4. Also check System and, on a server, the relevant Directory Service logs.
5. Look for entries at the same time as the error.
6. Record the event source, process name, error code, and whether the failure happened during startup, an update, or an AD operation.

An Event Viewer entry alone does not always mean a program failed to start. Confirm that there is an actual launch failure before changing system files.

Locate copies of the file

Open Command Prompt as administrator:

1. Open Start.
2. Type cmd.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Approve the User Account Control prompt.
6. Run:

where /r "%windir%" ntdsbsrv.dll

This searches beneath the Windows directory. A result in a Windows component directory is more plausible than a result in an application folder, but location alone does not prove authenticity.

Check the Microsoft signature

In PowerShell, run:

Get-AuthenticodeSignature "$env:windirSystem32ntdsbsrv.dll"

A valid Microsoft signature is an important identity check. If the file is missing, the command reports that it cannot find the path. If the signature is invalid or absent, do not replace it with another downloaded copy. Continue with Windows repair and investigate the file’s origin.

You can also calculate a hash for comparison with a known-good file from the same Windows build:

Get-FileHash "$env:windirSystem32ntdsbsrv.dll" -Algorithm SHA256

There is no single universal hash, size, or current version that applies to every Windows release. Do not compare the result with an unrelated Windows installation.

Fix 1: Install pending Windows updates and restart

A failed or incomplete servicing operation is a realistic cause of a missing or damaged Windows component.

On Windows 11:

1. Open Start > Settings.
2. Select Windows Update.
3. Click Check for updates.
4. Install all applicable updates.
5. Restart when Windows requests it.
6. Check Windows Update again after the restart.
7. Reproduce the original error.

On Windows 10:

1. Open Start > Settings.
2. Select Update & Security.
3. Choose Windows Update.
4. Click Check for updates.
5. Install the available updates.
6. Restart the computer.
7. Test the application or service again.

If the error began after an update, open View update history and note the failed or incomplete installation. On a server, apply the current cumulative update intended for the exact Windows release rather than using an old hotfix intended for a different build.

A historical Microsoft case involved dsamain.exe crashing during an AD LDS topology check on Windows 8.1 and Windows Server 2012 R2. Microsoft listed ntdsbsrv.dll among the updated files. That case does not make the historical update a general solution for every missing-DLL message.

Fix 2: Repair Windows with DISM, then SFC

This is the safest general repair for a genuinely missing or corrupted Windows component. DISM repairs the Windows component store first. SFC then uses that repaired source to check protected system files.

Close running applications, save your work, and open an elevated Command Prompt:

1. Open Start.
2. Type cmd.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Run this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for it to reach completion. Do not close the window just because progress appears to pause.

When DISM finishes, run:

sfc /scannow

Let the scan reach 100 percent, then restart Windows.

Understand the result

SFC may report one of these outcomes:

• Did not find any integrity violations: Windows protected files appear intact. Investigate the named application, process, dependency, or AD role.
• Found corrupt files and successfully repaired them: Restart and test again.
• Found corrupt files but was unable to fix some of them: Run DISM again, review %windir%LogsCBSCBS.log, and use a matching repair source or in-place repair.
• Could not start the repair service: Restart, confirm that Windows servicing is working, and run the commands again from an elevated prompt.

Running sfc /scannow repeatedly without repairing the component store first is not a useful strategy when SFC cannot replace files.

If you prefer assistance identifying which Windows components need attention rather than repeatedly hunting through logs and rerunning commands, Outbyte PC Repair can scan for issues and show what it finds; repair actions are handled by the full version. It is optional, and DISM/SFC remain the supported Microsoft repair path.

Fix 3: Use a matching DISM repair source

DISM normally obtains repair files through Windows servicing. If Windows Update cannot provide them, specify a repair source from the same Windows version.

An administrator may use a source such as:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\serverc$windows /LimitAccess

The source must match the installed operating-system version and architecture. A source from another build can leave you with version mismatches or create new servicing problems.

Before using this method:

1. Confirm the Windows edition and build with Settings > System > About.
2. Confirm whether the installation is 64-bit or 32-bit.
3. Use a trusted Windows installation or repair source matching that build.
4. Open Command Prompt as administrator.
5. Run the DISM command.
6. After DISM completes, run:

sfc /scannow

1. Restart Windows and test again.

Do not copy only ntdsbsrv.dll from another computer. A Windows component includes servicing metadata, dependencies, permissions, and version relationships that a loose file copy does not repair.

Fix 4: Repair or reinstall AD DS or AD LDS on a server

This branch applies to a domain controller or a server deliberately running Active Directory Lightweight Directory Services. It is not a general fix for a consumer PC.

AD DS servers

If the server was intended to provide AD DS and the role installation is incomplete, open Server Manager:

1. Sign in with an account authorized to administer the server.
2. Open Server Manager.
3. Select Manage > Add Roles and Features.
4. Continue through the wizard.
5. Select Role-based or feature-based installation.
6. Choose the correct destination server.
7. Select Active Directory Domain Services.
8. Add the management tools when prompted.
9. Complete the installation.
10. Restart if requested.
11. Apply the current cumulative updates for the server’s Windows release.

The documented PowerShell installation command is:

Install-WindowsFeature -Name AD-Domain-Services -IncludeManagementTools

Installing AD DS merely to make a DLL appear is inappropriate. Use it only when the server is supposed to provide domain services.

AD LDS servers

If the error names dsamain.exe or an AD LDS instance:

1. Confirm that the AD LDS role is intentionally installed.
2. Review Event Viewer for the corresponding directory-services errors.
3. Check Windows Update history.
4. Apply updates for the exact Windows Server release.
5. Restart the affected AD LDS service or server only during an approved maintenance window.
6. Verify that the AD LDS instance starts and that the original topology or application operation completes.

Do not use the Windows 8.1 and Server 2012 R2 AD LDS hotfix scenario as a universal missing-file repair. The correct update depends on the installed operating system and build.

Domain-controller warning

Do not replace ntdsbsrv.dll manually on a domain controller. A file from another machine can be the wrong architecture or build and may not match lsass.exe, Active Directory, or the component store.

If the directory database itself is damaged, use an AD-aware system-state backup and Microsoft’s forest-recovery procedures. Do not restore an arbitrary DLL as a substitute for directory recovery.

Fix 5: Check antivirus quarantine and malware cleanup

Windows Security may quarantine a file after a detection, or a malware-cleanup tool may remove a suspicious replacement. Check the security history before restoring anything.

In Windows Security:

1. Open Start.
2. Type Windows Security and open it.
3. Select Virus & threat protection.
4. Click Protection history.
5. Expand the relevant detection.
6. Review the original path and detection details.

Restore a quarantined file only when all of these are true:

• The path is the expected Windows system directory.
• The file is genuinely signed by Microsoft.
• The detection is known to be a false positive.
• The system is not showing other signs of compromise.
• Your administrator or security process approves the restoration.

If the file was in an application folder or user-writable directory, leave it quarantined until it has been investigated. Run a full Microsoft Defender scan, then repair Windows with DISM and SFC. A malware cleanup followed by a damaged system file is possible, but restoring an unverified file can reintroduce the original threat.

Fix 6: Repair the program that reports the error

If the error appears only when launching one application, first determine whether that application is actually involved with AD DS, AD LDS, or a Windows service. Do not assume that a program-specific error means the program legitimately ships with this DLL.

Try the application’s supported repair path:

1. Open Settings > Apps > Installed apps.
2. Select the affected application.
3. Open its menu and choose Advanced options, if available.
4. Select Repair.
5. Restart and test the application.
6. If Repair is unavailable or ineffective, uninstall and reinstall the application from its official vendor source.

For classic desktop software, use its own installer’s Repair option if provided. If the application is genuinely the failing component, reinstalling that program is the definitive fix. Do not place ntdsbsrv.dll into the program folder just to satisfy a message.

“The specified module could not be found” can also mean that a dependency of the named DLL is missing. Record the process name and application version, then use the application vendor’s supported installer or repair procedure.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 7: Investigate drivers only when evidence points there

A driver is not a first-line explanation for ntdsbsrv.dll. Use Device Manager only when the failure began after a driver change, the event names a driver, or the application vendor identifies a hardware dependency.

To inspect drivers:

1. Press Win + X.
2. Select Device Manager.
3. Expand the relevant category, such as Display adapters, Network adapters, or Storage controllers.
4. Right-click the suspected device.
5. Select Properties.
6. Review the General and Driver tabs.
7. If Windows reports a problem, choose Update driver or uninstall the device and restart according to the vendor’s instructions.
8. Prefer the hardware manufacturer’s driver for the exact Windows version and architecture.

Do not use a driver reinstall merely because a generic DLL page suggests it. If the process, update history, or vendor diagnostics identifies a driver issue, Outbyte Driver Updater can scan for outdated drivers and identify what needs attention; driver installation through the full version is optional and does not replace Windows component repair.

Why regsvr32 is the wrong repair

Do not run:

regsvr32 ntdsbsrv.dll

regsvr32 is intended for self-registering DLLs that expose registration entry points such as DllRegisterServer. Microsoft documents that a DLL without that entry point produces an error instead of repairing the file.

ntdsbsrv.dll is a Windows directory-services component, not a typical ActiveX control or self-registering application library. Registration does not restore a missing component-store payload, repair SFC corruption, fix AD DS, or resolve a missing dependency.

32-bit and 64-bit considerations

Do not move a DLL between System32 and SysWOW64 based on the directory names alone. On 64-bit Windows, System32 contains the native 64-bit system components, while SysWOW64 is used for 32-bit compatibility components. The correct location depends on the Windows component and architecture.

Use Windows Update, DISM, SFC, and the appropriate role installer to place the correct file. Do not mix a 32-bit file with a 64-bit installation or copy a file from a different Windows build.

If repair still fails

Try System Restore if the problem began recently and restore points are available:

1. Press Win + R.
2. Type:

rstrui.exe

1. Press Enter.
2. Choose a restore point from before the error appeared.
3. Review the affected programs.
4. Confirm the restore and restart Windows.

System Restore does not replace a proper domain-controller recovery plan.

If the component store remains unrecoverable, perform an in-place Windows repair using matching installation media and select Keep personal files and apps. Back up important data first and verify the media matches the installed edition and architecture.

Prevention and safe-source rules

• Keep Windows Update enabled and allow updates to complete before shutting down.
• Maintain current backups, especially system-state backups for domain controllers.
• Leave Microsoft Defender protections enabled unless an administrator has a documented reason not to.
• Do not download individual Windows DLLs from random repositories.
• Do not copy DLLs from another PC, even if the filenames match.
• Do not use regsvr32 as a generic missing-DLL command.
• Keep AD DS and AD LDS servers on supported cumulative updates.
• Investigate the failing process before repairing an apparently unrelated application.
• Treat a Microsoft-named DLL outside the Windows directory as suspicious until its signature and provenance are verified.

FAQ

Is ntdsbsrv.dll safe?

It is a legitimate Microsoft Windows directory-services component when it is the expected Windows file and carries a valid Microsoft signature. A file with the same name in an application or user-writable folder is not automatically safe.

Does every Windows 10 or Windows 11 PC need it?

No universal inventory proves that the same filename ships on every modern Windows edition. A normal consumer PC may not use AD DS or AD LDS, so absence alone does not prove corruption.

Is ntdsbsrv.dll a game DLL?

No. It is associated with Windows directory services. If a game reports it, investigate the process, installation, and Windows integrity rather than assuming the game should contain the file.

Can I download ntdsbsrv.dll?

Do not use a generic DLL download. There is no identified official standalone redistributable. Restore the component through Windows Update, DISM, SFC, the appropriate Windows role, or matching repair media.

Should I copy it to System32?

No. Manual copying can create a version, architecture, signature, or component-store mismatch. Let supported Windows servicing tools restore it.

Will SFC always fix it?

No. SFC may repair the file, report that Windows is already intact, or fail because the component store or repair source is damaged. Run DISM first and use matching repair media when required.

What does “entry point not found” mean?

It can indicate a version mismatch or an incompatible replacement file. Remove unauthorized copies and repair Windows rather than downloading another version.

What if the error names lsass.exe?

Treat it as a high-priority Windows or directory-services issue. Avoid manual file replacement and involve an administrator before restarting or repairing a domain controller.

What if the error names dsamain.exe?

Check whether AD LDS is installed, review directory-services events, and apply updates for the exact Windows Server version. The historical Microsoft AD LDS case is not a general missing-DLL fix.

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.