isatq.dll is a Microsoft Internet Information Services (IIS) file, so a missing-file error usually points to an incomplete IIS installation, Windows component corruption, or an old IIS-dependent utility. Do not download a random copy of isatq.dll; first identify the program requesting it and repair the Windows component that owns it.
What this file actually does
isatq.dll has the internal description Asynchronous Thread Queue. It is associated with Microsoft Internet Information Services and belongs to IIS server infrastructure, including the historical IIS metabase component.
As an Amazon Associate I earn from qualifying purchases.
On systems using the relevant IIS components, the expected location is:
%SystemRoot%System32inetsrvisatq.dll
On a typical Windows installation, that expands to:
#1 Best Overall
C:WindowsSystem32inetsrvisatq.dll
The file is not a Visual C++ runtime, DirectX component, ordinary game dependency, or general-purpose DLL that should be copied into an application’s folder.
IIS has separate 32-bit and 64-bit components. A 32-bit program can require the x86 IIS component even when Windows itself is 64-bit. Do not replace one architecture with a file taken from another Windows installation.
Microsoft’s historical IIS file manifests document x86 and x64 builds of isatq.dll, but they do not represent a complete version list for every current Windows release. The correct file is the one restored by the matching Windows or IIS installation source.
Match the symptom to the likely cause
| Symptom or situation | Most likely cause | Best first action |
|---|---|---|
| Error appears when launching an IIS administration tool | IIS is incomplete or damaged | Repair the IIS role or Windows features |
| Error began after removing IIS | An old utility still expects IIS files | Reinstall the required IIS component or remove the obsolete utility |
| Error began after an update, cleanup, or disk problem | Windows component corruption | Run DISM, then SFC |
| Windows Security shows a quarantine event | The file was removed by antivirus | Verify the file and detection before restoring anything |
dnsdiag.exe reports ISATQ.dll was not found |
A legacy Windows Server utility expects IIS-related files | Confirm whether the utility is still needed |
| The file exists but cannot be loaded | A dependency, architecture, or component mismatch | Check the path, signature, and calling program |
| The message appears in a game or unrelated application | The program may be obsolete or incorrectly packaged | Reinstall or replace that program rather than downloading the DLL |
The wording may vary:
This application failed to start because isatq.dll was not found.
isatq.dll is missing or corrupted.
isatq.dll could not be loaded.
Cannot find isatq.dll.
The procedure entry point could not be located in isatq.dll.
The important detail is the executable that produced the message. A missing DLL name alone does not prove that every Windows installation should contain the file.
1. Identify the program requesting isatq.dll
Before changing Windows, find the exact caller.
Check the title bar and full error dialog. If the message appears only after launching a shortcut, right-click that shortcut, select Properties, and inspect the Target field.
Also check:
- Press Windows key, type Event Viewer, and open it.
- Expand Windows Logs.
- Select Application.
- Look for an error at the time the message appeared.
- Open the event and note the Faulting application name or related executable.
You can also use Reliability Monitor:
- Press Windows key.
- Search for View reliability history.
- Open the result.
- Select the red error on the date of the failure.
- Expand Technical details and identify the affected application.
If the caller is an IIS management tool, server utility, SMTP-related component, Exchange-era program, or old Windows Server tool, repairing IIS is more appropriate than installing a runtime package.
If the caller is an old application that should not use IIS, reinstall that application from its original, trusted installer. If IIS is not installed and no required program needs it, adding random IIS files is not a proper fix.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →2. Check the expected IIS location
Use File Explorer to inspect the expected directory:
- Press Windows key + E.
- Click the address bar.
- Enter:
C:WindowsSystem32inetsrv
- Press Enter.
- Look for
isatq.dll.
You can also check from an elevated Command Prompt:
- Open Start.
- Type Command Prompt.
- Right-click Command Prompt.
- Select Run as administrator.
- Run:
dir "%SystemRoot%System32inetsrvisatq.dll"
If Windows reports that the file cannot be found, the IIS component may not be installed or may be damaged.
If the file exists somewhere else, do not immediately trust it. A filename does not establish authenticity. Right-click the file, select Properties, and inspect the Digital Signatures tab. The publisher should be Microsoft Corporation for a genuine Microsoft system component.
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 →Also check the path. A copy in a download folder, temporary directory, game directory, or unrelated application folder needs additional verification. Do not move it into System32, SysWOW64, or the application directory merely because the filename matches.
3. Repair IIS through Windows Features
Use this method when the failing program genuinely requires IIS and you are using Windows 10 or Windows 11 client editions.
- Press Windows key + R.
- Type:
optionalfeatures
- Press Enter.
- Find Internet Information Services.
- Expand it and review the selected components.
- If IIS is not selected, select the components required by the application.
- If IIS is already selected, clear the selection, click OK, restart when prompted, then return to the same dialog and enable IIS again.
- Allow Windows to complete the installation.
- Restart the computer if Windows requests it.
- Launch the original program again.
Do not enable every IIS subcomponent without a reason. The required features depend on the program, Windows edition, and whether it needs web server, management, metabase, compatibility, or other IIS functionality.
Microsoft’s IIS installation guidance covers enabling IIS through Control Panel → Programs and Features → Turn Windows features on or off.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC 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 & 11After installation, you can test whether the web server responds:
- Open a browser.
- Go to:
http://localhost
A response from the local IIS installation confirms that the web server is active, although it does not by itself prove that every required legacy component is installed.
Repair IIS on Windows Server
On Windows Server, use Server Manager:
- Open Server Manager.
- Select Manage.
- Choose Add Roles and Features.
- Continue through the wizard until Server Roles.
- Select Web Server (IIS).
- Review the required role services.
- Continue through the wizard.
- Select Install.
- Restart if requested.
- Retest the application or server utility.
If the application is an old Exchange, SMTP, or Windows Server utility, confirm its documented prerequisites before changing roles. Installing the modern IIS role may not recreate every dependency expected by an obsolete utility.
4. Repair Windows component corruption with DISM and SFC
Use this path when the error began after an interrupted update, disk problem, system cleanup, failed servicing operation, or unexplained file disappearance.
Free tools Windows power users keep installed
One-click scans. No signup required.
Open Command Prompt as administrator and run these commands in order:
DISM.exe /Online /Cleanup-Image /RestoreHealth
Wait for DISM to finish. Then run:
sfc /scannow
DISM repairs the Windows component store. SFC checks protected system files and replaces damaged copies when a suitable component source is available.
Possible SFC results include:
- Windows Resource Protection did not find any integrity violations: Windows protected files passed the check.
- Windows Resource Protection found corrupt files and successfully repaired them: restart and test the original program.
- Windows Resource Protection found corrupt files but was unable to fix some of them: investigate the CBS log and repair the Windows image or installation source.
- Windows Resource Protection could not perform the requested operation: restart and run the scan again, or use Safe Mode if the problem continues.
Restart after both commands, then run Windows Update and test the original caller.
Repeating SFC without knowing what changed rarely helps. Outbyte PC Repair can provide a scan that shows related system problems, while repairs are performed by the full version; it is optional, and Microsoft’s DISM and SFC commands remain the direct repair path.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
When DISM cannot find repair files
If DISM reports that source files cannot be found, use a matching Windows installation source. Microsoft documents the following pattern:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\serverc$windows /LimitAccess
The source must match the installed Windows version and architecture. Do not point DISM at an arbitrary computer or copy a DLL from another machine. A mismatched source can leave the component store inconsistent.
If you do not have a matching source, repair Windows Update or use official installation media that corresponds to the installed release. After DISM completes, run:
sfc /scannow
again.
5. Check Windows Security quarantine
If isatq.dll disappeared suddenly, antivirus quarantine is a possible cause.
Recommended Free Tools
For Microsoft Defender:
- Open Windows Security.
- Select Virus & threat protection.
- Select Protection history.
- Open detections recorded around the time the file disappeared.
- Inspect the detected path and threat details.
Do not restore the file solely because an application says it is missing. First confirm that:
- The file was located under the expected IIS directory.
- Its publisher and digital signature identify Microsoft Corporation.
- The detection is consistent with a false positive.
- A current security scan does not identify an active threat.
If the file was a genuine Microsoft-signed IIS component and the detection is confirmed as a false positive, use the restoration controls documented by Microsoft Defender. If the detection is credible, do not restore it. Remove the threat and reinstall IIS through Windows Features or Server Manager instead.
A malware verdict cannot be established from the filename alone, and a missing file does not prove that antivirus caused the problem.
6. Check whether IIS is actually required
Not every computer needs IIS.
You probably need IIS if you run:
- A local website or web application.
- An IIS administration tool.
- A server application whose requirements explicitly name IIS.
- A legacy Windows Server utility that depends on IIS infrastructure.
You may not need IIS if:
- The error comes from an obsolete utility installed accidentally.
- The program was removed but left behind a shortcut or service.
- The failing application has no legitimate web-server function.
- The error appears after launching software that should have bundled its own dependencies.
IIS Express is not automatically equivalent to the Windows IIS role. Installing IIS Express may not provide the same server infrastructure or file layout expected by an older tool.
If the program is no longer needed, uninstall it through Settings → Apps → Installed apps or Control Panel → Programs and Features. Remove its leftover shortcut or scheduled task only after confirming that it is not part of a required service.
7. Understand the legacy dnsdiag.exe case
A documented Windows Server 2003 scenario involves dnsdiag.exe, a utility from the Windows Server 2003 Resource Kit. When neither Exchange nor the SMTP service is installed, the utility can report that ISATQ.dll was not found.
That does not mean the DLL should be downloaded separately. It means the old utility expects an IIS-related dependency that may not exist in the current installation.
If this is your situation:
- Confirm that the executable is actually
dnsdiag.exe. - Check its file location and installation source.
- Determine whether the utility is still required.
- If it is required, follow the utility’s original prerequisites and install the matching Windows/IIS components.
- If it is not required, uninstall or replace the obsolete utility.
Do not assume that installing a current IIS package will make every Windows Server 2003-era tool compatible with Windows 10 or Windows 11.
8. Do not use regsvr32 as a first-line repair
regsvr32 is used for DLLs that expose registration entry points such as DllRegisterServer. It is commonly associated with COM and ActiveX registration.
Running this command is not a general missing-DLL repair:
regsvr32 isatq.dll
There is no established basis for treating isatq.dll as a self-registering COM or ActiveX DLL. The command may return an error stating that the required entry point was not found.
Use regsvr32 only when the software vendor or Microsoft documentation specifically says that the exact DLL must be registered. For isatq.dll, restore the IIS or Windows component instead.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute9. Avoid manual DLL downloads and copying
Random DLL download sites create several problems:
- The file may contain malware.
- It may be from the wrong Windows release.
- It may be the wrong x86 or x64 architecture.
- It may require dependencies that are also missing.
- It may not match Windows servicing metadata.
- It may hide the reason IIS or Windows lost the component.
Do not copy a downloaded file into:
C:WindowsSystem32
C:WindowsSysWOW64
Do not place it beside a game or application just to suppress the error. The correct sources are Windows Features, Server Manager, Windows Update, official Windows installation media, and the original trusted installer for the program that needs the file.
10. Consider System Restore after a recent system change
If the error began immediately after removing software, installing an update, running cleanup, or changing system components, System Restore may help.
- Press Windows key + R.
- Enter:
rstrui.exe
- Press Enter.
- Select a restore point created before the problem began.
- Review the affected programs.
- Start the restore.
System Restore normally reverts system files, registry settings, and installed programs without removing personal documents. It does not replace a proper IIS repair when IIS is missing, and it may not be available on every system.
After restoration, check Windows Update and confirm that the original program still has its required IIS features.
Free tools Windows power users keep installed
One-click scans. No signup required.
11. Driver updates are usually unrelated
isatq.dll is an IIS component, not a hardware driver. Updating a graphics, chipset, network, or storage driver will not normally restore it.
Only investigate drivers if the DLL error appeared alongside broader system instability, disk errors, or device failures. Open Device Manager by right-clicking Start and selecting Device Manager, then look for warning icons and check the affected device’s status.
Best Value
If several devices need attention, Outbyte Driver Updater can scan for outdated drivers, while the full version handles installation; it is optional and does not replace repairing IIS or Windows.
FAQ
Is isatq.dll safe?
A genuine copy in the expected IIS directory, signed by Microsoft Corporation, is consistent with the documented Windows component. A filename alone does not prove safety. Verify the path, digital signature, and antivirus status.
Is isatq.dll part of Windows?
It is associated with Microsoft IIS, which is a Windows component or server role. It is not guaranteed to be present on every Windows installation because IIS is optional and the file is strongly associated with older IIS generations.
Do I need IIS on Windows 10 or Windows 11?
Only if a required application, local website, administration tool, or legacy utility depends on it. If no legitimate program needs IIS, identify and repair or remove the obsolete caller instead of enabling unnecessary server features.
Should I install Visual C++ Redistributable, DirectX, or .NET?
Usually not. Those packages are not the normal repair for an IIS-owned isatq.dll error. Repair IIS or Windows components first.
Is IIS Express enough?
Not necessarily. IIS Express and the Windows IIS role are different products and may not provide the same files or compatibility components expected by an older utility.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsWhy does a 32-bit program fail on 64-bit Windows?
The program may require the x86 IIS component. Windows architecture alone does not tell you which component the application needs. Restore the matching IIS feature rather than copying an x86 or x64 DLL manually.
What if the file exists but the error says it cannot be loaded?
The message may indicate a missing dependency, incorrect architecture, damaged file, or incompatible legacy program. Confirm the caller, verify the signature and path, repair IIS, and run DISM followed by SFC.
What if DISM and SFC do not fix the problem?
Check antivirus quarantine, confirm that IIS is installed, and verify that the application is compatible with the current Windows version. If DISM needs a source, use matching official installation media. If the caller is obsolete, reinstall or replace that utility rather than adding an isolated DLL.
Can I register isatq.dll with regsvr32?
Not as a standard repair. regsvr32 applies to DLLs that provide registration entry points, and there is no verified reason to assume that isatq.dll does. Restore the owning IIS component instead.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →What is the safest fix?
Identify the executable first. Then repair IIS if that program needs IIS, run DISM and SFC if Windows is damaged, investigate quarantine if the file vanished suddenly, and reinstall or remove an obsolete utility if IIS is not actually required.
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.
