“The program can’t start because api-ms-win-core-job-l1-1-0.dll is missing”
Recommended Free Tools
The api-ms-win-core-job-l1-1-0.dll error usually means Windows could not resolve an API contract required by the application. api-ms-win-core-job-l1-1-0.dll is not a normal Visual C++ runtime file that you should download, copy, or register manually.
Use this order to find the correct fix.
Which fix applies to you
- Only one program fails: Repair or reinstall that application from its official installer. This is the most likely cause.
- Several unrelated programs fail: Update Windows, then run DISM and System File Checker.
- The error began after an application update or deployment to another PC: Check the application’s Windows version, CPU architecture, drivers, and bundled dependencies.
- The error began after an antivirus alert: Check Windows Security protection history before restoring or reinstalling anything.
- The application is old: It may require a Windows build that is no longer installed or supported.
- The message lists many
api-ms-win-core-*files: Treat this as an incompatible or incomplete application dependency chain, not as dozens of separate missing DLLs.
Do not download this filename from a random DLL website. A copied file can contain malware, target the wrong Windows build or architecture, and still leave the real dependency problem untouched.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
CORRSQ 30-in-1 Bootable USB Drive | $20.99 | Buy on Amazon |
| 2 |
|
5-in-1 Win Repair & Reinstall Bootable USB Flash Drive – Fix, Recover, or Reinstall Windows 11... | $24.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
What api-ms-win-core-job-l1-1-0.dll actually is
Microsoft describes API sets as contracts between Windows applications and the system components that implement Windows APIs. An API-set name can end in .dll, but that does not guarantee that a standalone file with that exact name exists on disk. See Microsoft’s Windows API sets documentation.
Free tools Windows power users keep installed
One-click scans. No signup required.
This API-set contract is associated with Windows job-object functionality. Microsoft lists it as an API location for IsProcessInJob. The implementation is normally provided through Windows system components such as KernelBase.dll, rather than through a separately downloaded copy of the API-set name.
#1 Best Overall
- 1. COMPATIBLE WITH WINDOWS 11, 10, 8.1 & 7 Designed for compatible 64-bit PCs and laptops that support USB booting. Works with Windows 11, Windows 10, Windows 8.1 and Windows 7 installation and recovery options.
- 2. INSTALL, REINSTALL & REPAIR Provides access to installation and recovery options for startup failures, boot errors, system crashes, failed updates, system repair and reinstallation. Results depend on the condition of the computer and the cause of the problem.
- 3. READY-TO-USE BOOTABLE USB Reusable installation and recovery media that helps eliminate the need to download large system files or create bootable media yourself. Insert the USB drive, open the computer’s boot menu and select the appropriate installation or recovery option.
- 4. HELP KEEP OLDER PCS USEFUL Refresh, reinstall or maintain a compatible older computer before deciding whether replacement is necessary. Suitable for home computers, office workstations, PC enthusiasts and technicians who regularly work with supported systems.
- 5. IMPORTANT COMPATIBILITY & LICENSE INFORMATION Supports compatible 64-bit computers with UEFI or Legacy BIOS USB booting. No Windows license, activation key or product key is included. Activation may require an existing digital license or a separately purchased valid product key. Back up important files before installation or repair.
That explains why searching C:WindowsSystem32 may not show a file named api-ms-win-core-job-l1-1-0.dll. Its absence alone does not prove that Windows is damaged.
The error is commonly raised while loading another DLL belonging to the program you launched. Native applications, older C or C++ software, LabWindows/CVI deployments, TestStand, LabVIEW components, proprietary drivers, and game middleware can all expose this type of dependency problem.
Fix 1: Repair or reinstall the affected application
When only one program reports the error, repair that program first. The application may have been built for another Windows release, deployed without all of its dependencies, or damaged during an update.
Try the application’s built-in repair option
- Close the affected program.
- Open Start > Settings > Apps > Installed apps.
- Find the program in the list.
- Select the three-dot menu beside it.
- Choose Advanced options, if available.
- Select Repair.
- Start the program again.
If there is no Repair button, open the program’s official installer and look for Repair, Modify, or Reinstall.
Reinstall from the official source
- Save your work and close the program.
- Open Start > Settings > Apps > Installed apps.
- Select the program and choose Uninstall.
- Restart Windows.
- Download the current installer from the program’s developer or organization.
- Install it using an administrator account.
- Restart Windows if the installer requests it.
- Test the program before copying back custom plugins or third-party add-ons.
If the program is part of a development or test environment, reinstall its official deployment package, drivers, and runtime components together. A parent application may start correctly while one deployed DLL still depends on files that were never copied to the target computer.
Check compatibility
If reinstalling does not help:
- Right-click the program’s shortcut.
- Select Properties.
- Open the Compatibility tab.
- Select Run this program as an administrator only as a diagnostic test.
- Do not enable an older compatibility mode permanently unless the vendor recommends it.
- Check the vendor’s requirements for your Windows version and processor architecture.
A 32-bit program can run on 64-bit Windows through WOW64, but its dependencies must still be compatible with the 32-bit process. A 64-bit DLL cannot be loaded by a 32-bit host, and the reverse is also true. On 64-bit Windows, System32 contains 64-bit system components while SysWOW64 contains 32-bit counterparts. Windows redirects 32-bit processes appropriately through its loader.
Do not choose a “32-bit” or “64-bit” download from a DLL catalog. The correct API-set environment is selected by Windows for the process that is running.
Fix 2: Install Windows updates
A system-wide Windows servicing problem can prevent API contracts from resolving correctly. Install pending updates before running repair commands.
- Open Start > Settings.
- Select Windows Update.
- Choose Check for updates.
- Select Download & install for available updates.
- Restart when prompted.
- Open Windows Update again and repeat the check until no further updates are offered.
- Launch the affected application.
This is especially important if the error began after a failed update, rollback, disk cleanup, or operating system migration.
Fix 3: Repair Windows with DISM and SFC
Use these commands when multiple unrelated programs fail, Windows components may be damaged, or updating did not resolve the problem. Microsoft recommends running DISM before System File Checker.
- Open Start.
- Type
Terminal. - Right-click Windows Terminal and select Run as administrator.
- Select Yes at the User Account Control prompt.
- Run this command:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for DISM to finish. Do not close the window if progress appears paused.
- Then run:
sfc /scannow
- Wait until the verification reaches 100 percent.
- Restart Windows.
- Test the affected program again.
Microsoft provides these steps in its System File Checker repair instructions.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If DISM cannot obtain repair files through Windows Update, Microsoft documents using a matching Windows repair source:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess
Replace the example path with a genuine source matching the installed Windows edition and build. Do not use an arbitrary folder downloaded from the internet.
Repeating SFC without identifying what changed can make troubleshooting slow and uncertain. Outbyte PC Repair provides a free scan that shows what it finds; repair is performed by the full version, so it remains optional and is not required for the Microsoft commands above.
How to interpret the result
- “Windows Resource Protection did not find any integrity violations”: Windows protected files were not detected as damaged. Focus on the application and its dependencies.
- “Windows Resource Protection found corrupt files and successfully repaired them”: Restart and test the application.
- SFC found corrupt files but could not repair some of them: Run DISM again, restart, and run SFC again. If the issue remains, use Windows recovery or application-side repair.
- DISM or SFC completes successfully but the program still fails: The missing dependency may belong to the application DLL rather than Windows.
SFC cannot rebuild an application’s incompatible dependency chain.
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 →Fix 4: Check antivirus quarantine
Security software may quarantine the application’s own DLL, a driver, or an installer component. The alert may mention the program’s file rather than a real Windows API-set file.
- Open Start.
- Search for Windows Security and open it.
- Select Virus & threat protection.
- Choose Protection history.
- Review entries created when the error began.
- Check the detected file path and publisher.
- If the file belongs to a trusted installation, confirm its provenance with the application vendor before restoring it.
- If it is not clearly legitimate, do not restore it. Remove the application and reinstall it from the official source.
- Run a security scan before launching the program again.
Microsoft explains Protection History and the risks of restoring quarantined files in its Defender quarantine guidance.
Fix 5: Install a separately required runtime only when identified
This filename does not, by itself, indicate that Visual C++, DirectX, or .NET is missing. Install an official runtime only when the application documentation requires it or the error also names runtime files such as vcruntime140.dll or msvcp140.dll.
For Visual C++, use Microsoft’s latest supported Visual C++ Redistributable downloads. Install the architecture required by the application, which may be 32-bit even when Windows itself is 64-bit.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Rank #2
- Dual USB-A & USB-C Bootable Drive – compatible with nearly all Windows PCs, laptops, and tablets (UEFI & Legacy BIOS). Works with Surface devices and all major brands.
- Fully Customizable USB – easily Add, Replace, or Upgrade any compatible bootable ISO app, installer, or utility (clear step-by-step instructions included).
- Complete Windows Repair Toolkit – includes tools to remove viruses, reset passwords, recover lost files, and fix boot errors like BOOTMGR or NTLDR missing.
- Reinstall or Upgrade Windows – perform a clean reinstall of Windows 7 (32bit and 64bit), 10, or 11 (amd64 + arm64) to restore performance and stability. (Windows license not included.). Includes Full Driver Pack – ensures hardware compatibility after installation. Automatically detects and installs drivers for most PCs.
- Premium Hardware & Reliable Support – built with high-quality flash chips for speed and longevity. TECH STORE ON provides responsive customer support within 24 hours.
Do not install multiple unrelated runtime packages just because the filename contains api-ms-win.
Fix 6: Update drivers and vendor dependencies
Some applications load drivers or native libraries supplied by hardware vendors. This is common with test equipment, industrial software, audio hardware, graphics components, and proprietary devices.
- Disconnect the affected device if the vendor instructs you to do so.
- Open Start, search for Device Manager, and open it.
- Expand the relevant category, such as Display adapters, Sound, video and game controllers, Universal Serial Bus controllers, or Ports.
- Right-click the device and select Properties.
- Open the Driver tab and note the provider and date.
- Select Update Driver and then Search automatically for drivers.
- If no suitable driver is found, obtain the current driver from the hardware vendor’s official support channel.
- Restart Windows and test the application.
Windows Update may not provide every vendor-specific runtime or driver. Reinstall the complete application package when its installer includes device support.
Outbyte Driver Updater provides a free scan that identifies driver versions; installation is performed by the full version, so it is optional. For this error, the application vendor’s driver package remains the definitive source when specialized hardware is involved.
Why regsvr32 is not the fix
Do not run:
regsvr32 api-ms-win-core-job-l1-1-0.dll
regsvr32 is intended for DLLs that expose a registration entry point such as DllRegisterServer, usually COM or ActiveX components. Microsoft documents the command’s scope in its regsvr32 documentation.
An API-set contract is not a COM component. Registration will not repair Windows and may produce an entry-point error.
Manual copying is also unsafe. An API-set name may be a virtual contract rather than a physical file, and a file from another Windows build may be incompatible or malicious.
Advanced diagnosis when the fixes fail
Collect these details before contacting the application vendor:
- The complete error text
- The affected program and the DLL it was loading
- Windows edition and build
- Whether Windows is 32-bit or 64-bit
- Whether the application is 32-bit or 64-bit
- Recent updates, rollbacks, antivirus alerts, or deployments
- The complete list of missing dependencies
- Whether other programs fail
A long list of api-ms-win-core-* names usually points to an application built for a different Windows environment or an incomplete deployment. Rebuild the application for the target operating system, install the vendor’s supported runtime package, or obtain a compatible version.
If DISM and SFC succeed but only one application still fails, use the vendor’s deployment diagnostics or a trusted dependency inspection tool. The reported API-set may be a dependency of the application DLL, not the first file that actually became unavailable.
If the issue began immediately after a known driver, update, or configuration change, use Start > Settings > System > Recovery and review the available recovery options. System Restore is a fallback, not a replacement for correcting an incompatible application.
FAQ
Is api-ms-win-core-job-l1-1-0.dll a genuine Windows file?
It is a genuine Microsoft API-set identifier. Microsoft states that API-set names may not correspond to standalone files on disk.
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 matchShould I download it?
No. Use Windows Update and Windows repair tools for system problems, or reinstall the affected application from its official source.
Is it part of Visual C++?
No evidence in this filename identifies it as a Visual C++ Redistributable component. Install Visual C++ only when the application requires it or separately reports Visual C++ runtime files.
Why does Windows say the DLL is missing if it is an API-set contract?
The loader reports the contract name it could not resolve. That name can look like a normal DLL even when Windows routes it internally to another host component.
Does finding the file in System32 prove the program will work?
No. Architecture, Windows build, loader search paths, application dependencies, and vendor drivers all affect whether a program can load.
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 problemsWhat if only one user account has the problem?
Test the program in a new Windows profile and check permissions and security software. Treat this as a diagnostic step, not proof that the API-set itself is missing.
Will DISM and SFC always fix the error?
No. They repair Windows components. They cannot make an old application compatible with a newer or older Windows release, replace a missing vendor driver, or correct an incomplete deployment.
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.
