If you come across the “the ordinal 1 could not be located in the dynamic link library” error, SQL Server Service Manager is usually the cause and you should disable it. Other solutions include rolling back drivers, uninstalling and reinstalling drivers, performing SFC and DISM scans, running Windows Store Apps troubleshooter, etc.
A List Of Possibilities
All in all, in the course of operation, Windows computers could run into a lot of errors. Still, once it comes to “the ordinal 1 could not be located in the dynamic link library”, you should keep in mind these suspects:
- SQL Server Service Manager
- Drivers
- Corruption
- Bugs
What You Could Do
Disable SQL Manager
- Step 1: Right-click an empty space on the taskbar, pick Task Manager and go to the Startup tab.
- Step 3: Locate SQL Server Service Manager, right-click it and pick Disable.
- Step 3: After you finish, restart your computer and see how things turn out
Roll Back Drivers
You recently updated one of your drivers? Then it’s highly likely that the driver update is responsible for “the ordinal 1 could not be located in the dynamic link library” error. To dismiss the error, you have no choice but to roll back the driver to a previous version.
- Step 1: Go to Search bar, type devmgmt.msc then press Enter to open Device Manager.
- Step 2: Locate the updated driver, right-click it and pick Properties.
- Step 3: Go to the Driver tab, hit Roll Back Driver and restart your computer once the process completes.
Uninstall And Reinstall Drivers
You still see the error even though you have rolled back the driver? In that case, you should uninstall and reinstall the driver.
- Step 1: Go to Search bar, type devmgmt.msc then press Enter to open Device Manager.
- Step 2: Locate the updated driver, right-click it and pick Uninstall device.
- Step 3: Check the checkbox next to Delete the driver software for this device before hitting OK.
- Step 4: Restart your computer.
- Step 5: When the screen comes back on, launch your web browser and download the latest version of the driver you previously updated.
- Step 6: Right-click the downloaded driver then pick Properties.
- Step 7: Navigate to the Compatibility tab and check the check box next to Run this program as an administrator.
- Step 8: Select Apply and choose OK
- Step 9: Close everything, double-click the downloaded driver and follow onscreen instructions to initiate the update.
- Step 10: The moment the process wraps up, restart your computer.
Perform SFC And DISM Scans
- Step 1: Go to Search bar, type cmd and hit Run as administrator.
- Step 2: In Command Prompt (Admin), type the command sfc /scannow and press enter to perform the SFC scan.
- Step 3: When the SFC scan completes, type each of the following commands and press Enter every time you complete one to perform the DISM scan:
- DISM /Online /Cleanup-Image /ScanHealth
- DISM /Online /Cleanup-Image /CheckHealth
- DISM /Online /Cleanup-Image /RestoreHealth
- Step 4: As soon as the DISM scan completes, restart your computer.
Run Windows Store Apps Troubleshooter
- Step 1: Press Windows + I to open Settings.
- Step 2: Choose Update & Security then select Troubleshoot.
- Step 3: Pick Additional troubleshooters and click Windows Store Apps.
- Step 4: Hit Run the troubleshooter then wait until the troubleshooting completes.
- Step 5: Assuming that the troubleshooter manages to identify the cause, click Apply this fix.
Other Common Questions
What is the purpose of troubleshooters on Windows?
In layman’s terms, Windows troubleshooters allow people to tackle quite a few issues that complicate the performance of computers. Common troubleshooters include Windows Update, Internet Connection, Power, Windows Store Apps and so on. Each of the troubleshooters is designed to analyze and fix specific troubles.
Can I perform the SFC scan after the DISM scan?
Generally speaking, SFC and DISM scans excel at taking care of the corruption that plagues system files of Windows PC. Still, to get the desired result, it’s strongly recommended that you perform the SFC scan before the DISM scan.
As PCWorld’s senior editor, Mark focuses on Microsoft news and chip technology, among other beats. He has formerly written for PCMag, BYTE, Slashdot, eWEEK, and ReadWrite.