script.dll errors usually mean Windows cannot find or load a DLL required by a particular program. The filename belongs to more than one product, so the correct fix depends on whether the caller is Microsoft USMT, an ordinary application, or an unrelated private installation file.
The 60-second answer
Do not download a replacement script.dll from a random DLL website.
First identify the program that displays the error:
- If it appears while running a migration, imaging, ScanState, LoadState, or deployment task, repair the matching Windows Assessment and Deployment Kit (ADK) installation and select User State Migration Tool (USMT).
- If it appears when launching one ordinary application, repair or reinstall that application using its original vendor installer.
- If several Windows components are failing, repair Windows with DISM and SFC.
- If the file was quarantined, verify its original path and signer before restoring it.
- If the file is present but still fails, investigate dependencies, architecture, and DLL search order.
Historical Windows inventories associate a Microsoft copy with:
Recommended Free Tools
#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)
%WINDIR%System32USMTscript.dll
That is not proof that every modern Windows 10 or Windows 11 installation contains this exact file. Microsoft distributes USMT through the Windows ADK rather than as a standalone script.dll download. Microsoft’s USMT overview explains its migration and deployment role.
What exactly is script.dll
script.dll has been indexed with descriptions including “v1 Script Module” and “INF Script Module.” The description difference is a reminder that file metadata alone does not identify the owner conclusively.
Historical Windows file inventories place a Microsoft-associated copy in the USMT directory alongside script_a.dll. The indexed Microsoft copy is a 32-bit Windows XP-era file identified as version 5.1.2600.5512, approximately 0.21 MB in size. Treat those details as identification clues, not as instructions to copy an old DLL into a current Windows installation.
The name is not exclusive to Microsoft. A separately indexed 64-bit script.dll is attributed to Corel’s installation program. It should not be treated as a Microsoft Windows variant unless its original installer and digital signature establish that ownership.
PC 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 & 11Outdated 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 matchThat distinction matters because two files can have the same filename while having different:
- Exported functions
- Dependencies
- Internal versions
- Digital signatures
- CPU architectures
- Expected installation directories
- Owning applications
A 32-bit program may need a 32-bit private DLL even when it runs on 64-bit Windows. Conversely, placing a 64-bit file beside a 32-bit executable will not solve the problem.
Find which program requested the DLL
Before repairing anything, establish the caller. The error dialog is often more useful than the filename.
Check the dialog and shortcut
Note:
- The title of the error window
- The program name mentioned in the message
- Whether the error appears during startup or only after opening a specific application
- The shortcut being used
- The program’s installation folder
Right-click the shortcut, select Properties, and inspect Target on the Shortcut tab. The executable named there is the likely caller.
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 problemsIf the error occurs during migration or deployment, record the command or tool being run. ScanState.exe, LoadState.exe, imaging scripts, and deployment environments point toward USMT or the ADK.
Check Task Manager
If the program remains open:
- Press Ctrl+Shift+Esc.
- Select Details.
- Look for the suspected executable.
- Right-click it and choose Open file location.
The folder containing the executable helps distinguish an application-private DLL from a Windows component. A script.dll beside an application executable belongs to that application unless its installer proves otherwise. A file under System32USMT points toward the historical Microsoft/USMT identity.
Check Event Viewer
For an application that closes immediately:
- Press Win+R.
- Type
eventvwr.msc. - Press Enter.
- Open Windows Logs → Application.
- Look for an error at the time of the failure.
- Read the Faulting application name, Faulting module name, and any referenced path.
Event Viewer may identify the executable but does not always identify every missing dependency. “The specified module could not be found” can mean that a dependency of script.dll is missing, not necessarily that script.dll itself is absent.
Check the file’s path, architecture, and signature
Use File Explorer to search only in relevant locations first:
- The failing application’s installation folder
%WINDIR%System32USMT- Any folder used by the migration or deployment tool
Do not assume that a file in the Windows directory is genuine. Right-click the file, select Properties, and review:
- Digital Signatures
- Details
- General
- File location
- File size and version information
A Microsoft-owned file should have metadata and a signer consistent with Microsoft and its owning Windows component. An application-private file should match the vendor and product that installed it. An unsigned file in a writable application or temporary directory deserves additional scrutiny.
On 64-bit Windows, System32 normally contains 64-bit system binaries, while SysWOW64 contains many 32-bit Windows binaries. However, the historical Microsoft path for this file is specifically System32USMT, and the right location still depends on the package that owns it. Do not move the file between these directories to experiment.
Fix 1: Repair or reinstall the application that reports the error
This is the safest first fix when the error appears while launching one ordinary program.
Use Windows app repair
For a modern packaged application:
- Open Settings.
- Select Apps → Installed apps.
- Find the affected application.
- Select the three-dot menu.
- Choose Advanced options.
- Select Repair.
- Launch the application again.
If Repair does not work, return to the same page and choose Reset only if you understand that it may remove application data and settings.
For a traditional desktop program:
- Open Settings → Apps → Installed apps.
- Select the application.
- Choose Modify, Change, or Repair, if available.
- Follow the installer prompts.
- Restart Windows and test the program.
The wording varies by installer. If no repair option exists, uninstall the application, restart Windows, and reinstall it from the original vendor installer or trusted installation media.
Why reinstalling is better than copying
The application installer may also supply:
- Supporting DLLs
- Configuration files
- Registry entries
- Runtime dependencies
- Correct 32-bit or 64-bit binaries
- Required permissions
Copying only script.dll can leave the dependency chain broken. It can also place a same-named DLL where another program loads it accidentally.
Rank #2
- MICROSOFT WINDOWS 11 PRO (INGLES) FPP 64-BIT ENG INTL USB FLASH DRIVE
If the problem began after an application update, reinstall the current version first. If the application is legacy software, use the installer intended for that application’s architecture and Windows compatibility mode only when the vendor’s documentation calls for it.
Free tools Windows power users keep installed
One-click scans. No signup required.
Fix 2: Reinstall USMT through the Windows ADK
Use this path when the error occurs during Windows migration, deployment, imaging, or a task involving ScanState or LoadState.
USMT is distributed as part of the Windows ADK. It is not normally repaired by downloading an isolated DLL.
Install the matching ADK component
- Open Microsoft’s Windows ADK download and installation page.
- Download the ADK version appropriate for the deployment environment.
- Run the installer as an administrator.
- Choose the option to install on this computer.
- In the feature selection screen, select User State Migration Tool (USMT).
- Complete the installation.
- Use the USMT architecture matching the migration target.
- Retry the migration or deployment operation.
Do not mix files from an older Windows installation with a newer ADK. If a deployment server, technician computer, and target image use different ADK generations, align the components according to Microsoft’s USMT guidance.
If USMT was already installed, run the ADK installer again and choose its repair or modification option when offered. Confirm that User State Migration Tool (USMT) remains selected.
Confirm whether this fixed the problem
The repair is successful when:
- The migration tool starts without the
script.dllmessage ScanStateorLoadStateprogresses past the previous failure- The installed USMT directory contains the files supplied by the ADK installer
- No unrelated application begins loading the USMT DLL
If the error remains, check the exact executable path in the migration command. A third-party migration utility may have its own private script.dll and may require its own installer instead.
Fix 3: Repair Windows with DISM and SFC
Use Windows repair when multiple system components are failing, the issue followed a Windows update, or the file is expected to be protected by the Windows component store. This is not the most useful first step for a single application-private DLL.
Run DISM first
- Open Start.
- Type
Command Prompt. - Right-click Command Prompt.
- Select Run as administrator.
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for the command to finish.
- Restart Windows.
DISM repairs the Windows component store, which SFC may need as a source for replacement files.
Run SFC second
Open an elevated Command Prompt again and run:
sfc /scannow
Wait until verification reaches 100 percent, then restart Windows and retry the failing operation.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Success means SFC reports that it found and repaired integrity violations, or that it found no integrity violations and the Windows system files are intact. If it reports that some files could not be repaired, repeat the repair process only after checking the command output and available disk space. For an offline Windows installation, use Microsoft’s documented /Source, /OffBootDir, and /OffWinDir options with a matching repair source.
Outbyte PC Repair can reduce the manual work of repeatedly hunting through repair results and guessing what changed; its free scan shows what it identifies, while repair is performed by the full version. It is optional, and it does not replace reinstalling the owning application or ADK component when that is the actual cause.
If DISM and SFC report no corruption
Do not keep copying DLLs or repeatedly running the same commands. If Windows repair succeeds but one program still reports script.dll, the remaining cause is probably:
- The application’s private copy
- A missing dependency
- A 32-bit/64-bit mismatch
- A damaged application configuration
- A broken application update
- A DLL loaded from the wrong search-path directory
Return to the caller-identification step and repair that product.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix 4: Check antivirus quarantine
A security product may remove a legitimate file, but do not assume that a quarantine event is a false positive.
- Open Windows Security.
- Select Virus & threat protection.
- Choose Protection history.
- Find the detection matching the time of the error.
- Record the detection name and original file path.
- Compare that path with the expected application or USMT location.
- Verify the file’s digital signature and owning product.
- Restore or allow it only when the file is confirmed genuine.
- If it is not verified, leave it quarantined and reinstall the owning software.
If the file was in a temporary, download, or unexpected writable directory, treat the event as potentially malicious rather than restoring it.
Fix 5: Investigate dependencies and DLL search order
A missing-module message does not always mean the named DLL is absent. Windows searches several locations, including the application directory and system directories, according to its DLL search rules.
Possible situations include:
script.dllexists, but one of its dependencies is missing- The application loads a same-named DLL from the wrong directory
- A private DLL has the wrong architecture
- A required runtime or component was removed by an incomplete uninstall
- A malicious DLL is being loaded from an earlier search location
Use the application’s original installer to restore its complete dependency set. Avoid placing replacement DLLs in the application directory unless the vendor’s installation instructions explicitly require it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
An unexpected unsigned script.dll, especially one recently created in a writable folder, should be treated as suspicious. Quarantine it through Windows Security, run a full Microsoft Defender scan, and reinstall the affected application from trusted media.
Should you reinstall Visual C++, DirectX, .NET, or a driver
There is no reliable evidence tying the Microsoft-named script.dll to Visual C++ Redistributable, DirectX, .NET, a GPU driver, Photoshop, or Skype. Do not install these packages solely because a generic article lists them.
Install or repair a runtime only when the failing application’s own documentation or installer identifies it as a requirement. A missing dependency may be reported through script.dll, but the correct dependency must be identified from the owning product rather than guessed.
Rank #3
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
Likewise, update a driver only when the failing program is a hardware or driver utility, the event log identifies a driver component, or the hardware vendor directs you to do so.
Check Device Manager when hardware software is involved
- Right-click Start.
- Select Device Manager.
- Expand the relevant category.
- Right-click the device.
- Select Properties.
- Review the General tab for an error code.
- Open the Driver tab to see the provider and installed driver details.
- Use Update Driver only with a driver supplied through Windows Update or the hardware manufacturer.
- Restart Windows and retest the affected utility.
Outbyte Driver Updater can spare you from manually checking which of many device drivers is stale; its free scan identifies what it finds, while driver installation is handled by the full version. It is optional, and it cannot replace reinstalling an application that privately owns script.dll.
Why regsvr32 usually does not apply
regsvr32 is not a general DLL repair command. It calls the DLL’s DllRegisterServer entry point, and only self-registering DLLs that export that function should be registered.
A missing or damaged USMT helper file is not repaired by registering it. Reinstall USMT through the ADK. For an application-private DLL, use the application’s repair or reinstall process.
If the vendor explicitly tells you to register its DLL, use the command and architecture they provide. For example, a 32-bit application may require the 32-bit regsvr32 located under SysWOW64 on 64-bit Windows, while a 64-bit application uses the copy under System32. Do not substitute paths or register script.dll speculatively.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why manually copying script.dll is unsafe
Manual copying is risky because:
- The filename is shared by unrelated products
- The replacement may have the wrong architecture
- Its dependencies may still be absent
- The file may be modified or malicious
- Windows may load it from an unintended search location
- It can conceal a damaged installer or compromised application
The safe sources are the original application installer, the matching Windows ADK from Microsoft, Windows repair sources, and Windows Update. Microsoft does not distribute this file as a standalone download.
When to use System Restore or Windows repair
Use System Restore when:
- The failure began after a known software or system change
- A suitable restore point exists
- Repairing or reinstalling the owning product did not help
To check:
- Open Start.
- Type
Create a restore point. - Open the result.
- Select System Restore.
- Choose a restore point from before the problem began.
- Review affected programs.
- Start the restore only after saving current work.
If Windows has broader corruption and DISM/SFC cannot repair it, consider an in-place Windows repair using official installation media that matches the installed edition and language. Back up important files first. A clean installation should be a last resort, not the first response to one ambiguous DLL error.
Common error messages explained
“The program can’t start because script.dll is missing from your computer”
The file may genuinely be absent, or the application may be looking in the wrong location. Identify the application and reinstall its owning package.
“The specified module could not be found”
The named file may be missing, but a dependency may also be the real problem. Check the application installation and architecture before replacing anything.
“script.dll is either not designed to run on Windows or it contains an error”
This commonly indicates a corrupted file, wrong architecture, incompatible version, or invalid binary. Reinstall the owning application or ADK component.
“Entry point not found in script.dll”
The program found a DLL but loaded an incompatible version. This is strong evidence of a same-name collision or version mismatch. Remove the incorrect private copy through the owning installer rather than registering another DLL.
FAQ
Is script.dll a Windows system file
A Microsoft-associated, historical copy is documented under %WINDIR%System32USMT. That does not establish that every current Windows 10 or Windows 11 installation contains it, or that every script.dll belongs to Windows.
Is script.dll part of USMT
The strongest historical evidence places the Microsoft file in the USMT directory. Modern USMT is installed through the Windows ADK, so migration-related errors should be fixed by repairing or reinstalling the matching ADK component.
Is the 64-bit version interchangeable with the Microsoft file
No. The indexed 64-bit entry is attributed to Corel’s installation program and should be treated as a separate same-name collision unless its original installer proves otherwise.
Should I download script.dll
No. A random download may contain the wrong product, version, architecture, or malicious code, and it may not include the missing dependencies. Reinstall the owning application, ADK component, or Windows component instead.
Will SFC restore script.dll
Only if Windows recognizes the relevant copy as a protected system file and has a valid repair source. If SFC reports no corruption, repair the application or ADK package that requested the file.
Does regsvr32 fix script.dll
Usually not. It applies only to DLLs that support DllRegisterServer, and it does not restore missing files or dependencies.
What if the file is nowhere on the computer
Identify the caller, then reinstall that product. If the caller is a migration or deployment tool, install USMT through the matching Windows ADK.
What if the error appears at startup
Use Task Manager’s Startup apps, the shortcut’s target, and Event Viewer’s Application log to identify the program launching it. Disable or uninstall the responsible obsolete application only after confirming what it is.
What if Windows repair succeeds but the program still fails
That points away from Windows corruption and toward the application’s private DLL, dependencies, configuration, or architecture. Repair or reinstall the application from its original source.
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.
