msdt70.dll Errors: Repair the Legacy Designer on Windows

msdt70.dll is a real Microsoft Visual Database Tools component, not a general Windows system file. When Windows reports that msdt70.dll is missing, was not found, or could not be loaded, the affected program is usually an old SQL Server, Visual Studio, Access, or database-design tool that expects the legacy Microsoft shared designer files.

The safest solution is to identify the program showing the error and repair or reinstall its original database-tools component. Do not begin by downloading msdt70.dll from a random DLL archive or copying it into System32.

#	Preview	Product	Price
1		Microsoft Windows 11 (USB)	$124.97	Buy on Amazon
2		64GB Bootable USB Installer for Windows 11, 10 & 7 Home/Pro with WinPE Repair Tools	$19.71	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

What msdt70.dll is

This DLL belongs to the old MSDesigners98 shared component family. SQL Server 2000 client tools installed files used by database designers, and those tools had to be installed on each development workstation rather than only on the database server.

It is not the same file as msdt.dll, the Microsoft Support Diagnostic Tool. Modern Visual Studio, current SQL Server Management Studio, and current database tooling do not normally install msdt70.dll.

#1 Best Overall

Sale

Microsoft Windows 11 (USB)

• 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)

$124.97

Buy on Amazon

A commonly listed historical file record identifies an x86 build as 7.0.8948.0, approximately 3.06 MB. That is not a universal replacement. Another historical SQL Server report identifies a separate build, so the correct version depends on the original application and installation media.

Which error are you seeing

The exact wording helps identify the failed part:

• “The program can’t start because msdt70.dll is missing from your computer.”
  The file is absent from the location expected by the old program, or the parent component was never installed.

• “This application failed to start because msdt70.dll was not found.”
  The application cannot resolve the legacy designer DLL.

  ×Performance · Free Tool

  Windows Errors? Fix Them Before They Spread

  Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.

  Fix My PC Now →Free scan · no reinstall

  Stop driver crashes →Fix Windows issues →
  Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

• “Error loading msdt70.dll. The specified module could not be found.”
  msdt70.dll may be missing, or one of its dependencies may be missing even though the named DLL exists.

• “[MS Design Tools] Class not registered.”
  The DLL may be present but its COM registration is damaged or registered in the wrong architecture.

• “[MS Design Tools] Invalid Class String.”
  The related designer registration is incomplete or points to an incompatible installation.

• SQL Server Management Studio or SqlWb.exe closes unexpectedly with an AccessViolationException when opening DTS Query Designer.
  This can indicate an incompatible or mixed set of legacy designer files rather than one missing DLL.

  ×Worth Installing

  Windows Errors? Fix Them Before They Spread

  Outbyte PC Repair · freeRepair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallFix My PC Now →
  Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The best first step is to note which application produced the message. If the error appears while opening Enterprise Manager, a DTS package, an Access database project, or an old Visual Studio database designer, repair that application’s client tools instead of treating the DLL as an independent download.

Fix 1: Repair or reinstall the original database tools

This is the most likely fix when msdt70.dll is genuinely missing.

The file historically came with SQL Server 2000 client tools and related Visual Database Tools components. Installing SQL Server or a database engine on another computer does not automatically install these design tools on the workstation where the error appears.

If you still have the original installation media

1. Close Enterprise Manager, SQL Server tools, Visual Studio, Access, and any program showing the error.
2. Open Settings.
3. Select Apps, then Installed apps.
4. Search for the related SQL Server, Visual Studio, Office, or database-tools installation.
5. If Windows provides Modify, Change, or Repair, select it.
6. Choose the option that installs or repairs Client Tools, Development Tools, Visual Database Tools, or the database-design components.
7. If the installer offers a feature tree, do not install only the database engine. Select the complete client/design component set required by the old project.
8. Finish the installer and restart Windows.
9. Open the original program and repeat the action that produced the error.

For older installers that do not appear in modern Settings:

1. Press Win + R.
2. Type appwiz.cpl and press Enter.
3. Select the related Microsoft product.
4. Choose Change or Repair.
5. Follow the feature-selection steps above.

If the repair option is unavailable, uninstalling and reinstalling the original client tools may be necessary. Use the same product family and service-pack level where possible. Do not combine an arbitrary copy of msdt70.dll with unrelated versions of the other MSDesigners98 files.

How to tell whether this worked

The repair succeeded if:

• the original application starts without the missing-file message
• the database project or designer opens
• DTS Query Designer loads without a registration error
• the expected MSDesigners98 folder contains the restored designer files

If the error returns immediately after reinstalling, check whether the installer actually included client or design tools. A server-only installation will not necessarily provide the workstation components.

There is no current supported Microsoft redistributable download page for msdt70.dll itself. For this obsolete component, legitimate installation media or the original product installer is safer than an isolated file download.

Fix 2: Locate the file before changing anything

A missing-file message can be misleading. The DLL may exist in the correct directory but fail because of registration or a missing dependency.

Open Command Prompt:

1. Press the Start button.
2. Type cmd.
3. Select Run as administrator.
4. Run these commands separately:

where /r "%ProgramFiles%" msdt70.dll
where /r "%ProgramFiles(x86)%" msdt70.dll

If Windows finds the file, record its complete path. The expected historical directory is similar to:

C:Program FilesCommon FilesMicrosoft SharedMSDesigners98

Do not copy the result into C:WindowsSystem32 or C:WindowsSysWOW64. The application may be designed to load the DLL from the shared Microsoft directory, and copying it elsewhere can create a second, conflicting installation.

If both commands return nothing, return to Fix 1. The correct response to a missing legacy application component is to repair its parent installer.

If the file exists but the program says it is missing, continue with the architecture and registration checks below.

Fix 3: Check the 32-bit registration path

Legacy SQL Server 2000 and Visual Studio 6-era database designers were 32-bit. A 64-bit Windows installation does not supply a 64-bit replacement for this component.

On 64-bit Windows:

• System32 contains native 64-bit system tools.
• SysWOW64 contains the 32-bit Windows tools.
• A 32-bit COM DLL should generally be registered with the 32-bit regsvr32.exe in SysWOW64.

This naming is confusing, but using the wrong registration tool can leave the 32-bit application unable to see the registration.

Before registering anything:

1. Confirm that the DLL came from the original Microsoft application installation.
2. Confirm that the path is the expected MSDesigners98 directory.
3. Close every program that uses the database designer.
4. Open Command Prompt as administrator.
5. Use the full path to the DLL.

For a 64-bit version of Windows, use:

"%SystemRoot%SysWOW64regsvr32.exe" /u "C:Program FilesCommon FilesMicrosoft SharedMSDesigners98msdt70.dll"
"%SystemRoot%SysWOW64regsvr32.exe" "C:Program FilesCommon FilesMicrosoft SharedMSDesigners98msdt70.dll"

The first command removes an existing registration, and the second creates it again. If your actual file is in a different legitimate installation directory, replace the quoted path with that path.

For 32-bit Windows, use:

"%SystemRoot%System32regsvr32.exe" "C:Program FilesCommon FilesMicrosoft SharedMSDesigners98msdt70.dll"

Restart the affected application and test the designer.

When registration is appropriate

Use regsvr32 only when the message specifically indicates a COM registration problem, such as:

• Class not registered
• Invalid Class String
• a designer that opens only after registration-related errors

A successful registration message does not prove that the application is fully repaired. Other shared designer DLLs, registry entries, or version-matched dependencies may still be missing.

Do not register every DLL in the folder. Register related files only when the original installer or a specific application error identifies them.

Microsoft’s documentation explains when DLL and OCX files can be registered with regsvr32: registering DLL and OCX files.

Rank #2

64GB Bootable USB Installer for Windows 11, 10 & 7 Home/Pro with WinPE Repair Tools

• [Win OS Install or reinstall] — Boot from the USB to install or reinstall Win 11, 10, or 7 Home & Pro editions. Includes OS installations and reinstallations media plus WinPE Utility Suite.
• [WinPE Repair & Recovery Tools] — Boot into the included WinPE utility suite to backup system and important files, troubleshoot startup problems, repair boot issues, recover data, recover Win User accounts password, and diagnose common PC problems.
• [All-in-One PC Rescue USB] — Combines Win 11, 10, and 7 installation media with PC repair, recovery, and diagnostic tools on one bootable 64GB USB drive, helping you troubleshoot and restore a computer without needing multiple discs or downloads.
• [Support] — Full instructions are included in packaging plus a printable copy of the instructions with troubleshooting information on the device. Also, a video “How to boot from a bootable USB drive.mp4” to help guide you through starting a PC from a USB drive. If you need help using the USB please contact us for assistance, we are here to help.
• [Video] - If you are new to booting from a USB drive or need a refresher see our video "How to boot from USB drive" both in description and on USB device.

$19.71

Buy on Amazon

Fix 4: Repair missing dependencies

The message “The specified module could not be found” does not always mean that msdt70.dll itself is absent. Windows can display the same message when a dependency required by the DLL cannot be loaded.

Use this sequence:

1. Run the where commands from Fix 2.
2. If msdt70.dll exists, do not download a replacement immediately.
3. Open Settings > Apps > Installed apps.
4. Select the parent SQL Server, Visual Studio, Office, or database-tools installation.
5. Choose Modify or Repair.
6. Reinstall the complete database-design feature set.
7. Restart Windows.
8. Test the original operation again.

If the installer has a log or component-selection screen, look for failed shared designer components rather than repairing only the named DLL.

A dependency failure is another reason copying one file rarely works. The legacy designer may require a matching group of files, registry entries, and supporting runtime components.

Fix 5: Check antivirus quarantine and recent cleanup

Security software, storage cleanup, or manual maintenance may have removed a shared legacy file.

Check quarantine

1. Open Windows Security from the Start menu.
2. Select Virus & threat protection.
3. Select Protection history.
4. Review entries around the time the application stopped working.
5. If msdt70.dll appears, verify that it belongs to the installed Microsoft product and that the original application is still installed.
6. Restore it only when the file is clearly associated with that trusted installation.
7. Repair the parent installation afterward.

Do not disable security software merely to install an anonymous DLL archive copy. If the file was quarantined because the installation itself is damaged or untrusted, reinstall the application from legitimate media instead.

Check whether cleanup removed shared files

If the error began after uninstalling SQL Server, Office, or an older Visual Studio installation, a shared MSDesigners98 component may have been removed. Reinstall or repair the application that still needs the designer. Do not restore the file by copying it from another computer unless the entire product installation and build are known to match.

Fix 6: Repair Windows components with DISM and SFC

msdt70.dll is not normally a Windows-protected system file, so DISM and SFC are secondary checks. They will not usually recreate a missing file owned by an old SQL Server or Visual Studio installer.

Run them in Microsoft’s documented order:

1. Open Start.
2. Type cmd.
3. Select Run as administrator.
4. Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for the command to finish. It may take time and can appear to pause.
2. Then run:

sfc /scannow

1. Wait until verification reaches 100 percent.
2. Restart Windows.
3. Test the original application.

If DISM reports that the repair completed and SFC reports no integrity violations, the Windows component store is not the likely source of this particular problem. Return to repairing the legacy application.

The Microsoft procedure is documented in Using System File Checker in Windows.

Repeatedly running SFC without checking the parent application will not restore an MSDesigners98 file that was never installed.

If manually hunting through Windows components and interpreting repeated DISM and SFC results is becoming the slow part, Outbyte PC Repair can scan for reported system problems and show what needs attention; repairs are performed by the full version. It is optional, and reinstalling the legacy database-tools product remains the definitive fix when that product owns the missing file.

Fix 7: Review Windows Features, updates, and compatibility

Windows Features will not normally provide msdt70.dll, but checking them can rule out a missing compatibility component.

1. Press Win + R.
2. Type:

optionalfeatures

1. Press Enter.
2. Review the available Windows features.
3. Do not enable unrelated legacy features simply because a DLL error appeared.
4. If the affected application’s own documentation requires a particular Windows compatibility feature, enable only that feature.
5. Select OK and restart if Windows requests it.

Also install pending Windows updates:

1. Open Settings.
2. Select Windows Update.
3. Select Check for updates.
4. Install available updates.
5. Restart Windows.
6. Test the application again.

Updates may improve compatibility, but they do not turn SQL Server 2000 Enterprise Manager or a Visual Studio 6-era designer into a supported modern application.

If the old program is still unstable after its files and registration are repaired, check the application crash details:

1. Right-click Start.
2. Select Event Viewer.
3. Open Windows Logs > Application.
4. Find the error recorded at the time of the crash.
5. Note the faulting application and faulting module.
6. Use that information to decide whether another shared designer DLL or the legacy program itself is failing.

Fix 8: Update drivers only when the evidence points there

A graphics or chipset driver is not the normal cause of a missing msdt70.dll message. Consider a driver check only if Event Viewer shows a driver-related fault, the application crashes rather than reports a missing file, or the problem began after a hardware or display-driver change.

To check drivers manually:

1. Right-click Start.
2. Select Device Manager.
3. Expand the device category related to the Event Viewer error.
4. Right-click the device.
5. Select Update driver.
6. Choose Search automatically for drivers.
7. Restart Windows if a driver is installed.
8. Test the original application.

Do not remove working drivers merely because this DLL error exists. For an old database designer, repairing the application remains more relevant than replacing unrelated hardware drivers.

If comparing device entries and hunting manufacturer packages is the difficult part, Outbyte Driver Updater can scan and identify reported driver updates; the full version performs the driver installation. It is optional and does not replace repairing the SQL Server or Visual Database Tools installation.

What not to do

Do not download an isolated DLL from a random website

Untrusted DLL download sites can provide:

• malware or tampered files
• the wrong build
• the wrong architecture
• a file with missing dependencies
• a file that does not match the installed service-pack level
• a DLL that still lacks the required COM registration

Even a clean-looking copy may not repair the actual cause.

Do not copy the file into System32 and SysWOW64

msdt70.dll is a legacy application component, not a normal Windows system DLL. Copying it into both directories can create conflicting copies and incorrect registry paths. Keep it with the original application’s shared designer installation.

Do not run regsvr32 as a generic repair command

Registration does not replace a missing file, repair dependencies, or restore every designer registry entry. Use it only for a verified COM-registration error and use the architecture that matches the failing application.

Do not assume Windows 11 or Windows 10 compatibility

An intact DLL does not guarantee that SQL Server 2000 Enterprise Manager, Access 2000 database projects, or Visual Studio 6-era designers will work correctly on a current Windows release. If the application still crashes after repair, use a supported replacement where possible or isolate the legacy software in an appropriately backed-up older environment.

Frequently asked questions

Is msdt70.dll part of Windows?

No. It is an application and shared-designer DLL associated with Microsoft Visual Database Tools and legacy Microsoft database products.

Is it part of modern Visual Studio?

The file has a Microsoft Visual Studio product association, but that does not mean current Visual Studio versions install it. It belongs to an obsolete generation of database-design components.

Is msdt70.dll 32-bit or 64-bit?

Historical copies are generally 32-bit/x86. A 32-bit legacy application on 64-bit Windows may need the 32-bit COM registration view and the SysWOW64regsvr32.exe tool.

Can Windows Update restore it?

Usually not. Windows Update can repair or update Windows components, but msdt70.dll normally comes from the original SQL Server, Visual Database Tools, Office, Access, or Visual Studio-era installation.

Should I use SFC for this error?

You can use DISM followed by SFC to rule out Windows corruption, but those tools will not normally recreate a missing legacy MSDesigners98 file. Repair the owning application first.

Why does the file exist but the program still fail?

The file may be registered incorrectly, registered with the wrong architecture, dependent on another missing DLL, or incompatible with the application’s other shared designer files. Re-register it only for a clear COM-registration error, then repair the complete component set if the problem continues.

What is the safest permanent fix?

Identify the failing legacy program and repair or reinstall its complete client or database-design tools from legitimate Microsoft installation media. If the program itself is no longer supported, replacing or isolating it may be safer than maintaining a single restored DLL.

Quick Recap

SaleBestseller No. 1

Microsoft Windows 11 (USB)

Make the most of your screen space with snap layouts, desktops, and seamless redocking.; FPP is boxed product that ships with USB for installation

$124.97

Bestseller No. 2

64GB Bootable USB Installer for Windows 11, 10 & 7 Home/Pro with WinPE Repair Tools

$19.71

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.