Api-ms-win-core-version-l1-1-1.dll 64 Bit -

Informative Paper: Understanding and Fixing Api-ms-win-core-version-l1-1-1.dll (64-Bit) api-ms-win-core-version-l1-1-1.dll is a specialized system component known as an ApiSet Stub DLL

. It acts as a bridge between applications and core Windows functions, specifically those related to file versioning and system information. Stack Overflow 1. Technical Purpose and Origin

This DLL is part of the "API Set" architecture introduced by Microsoft to provide a stable interface for developers across different versions of Windows. Stack Overflow

: It redirects application calls for version-related data (like checking a program's build number) to the actual implementation in larger system files like kernelbase.dll Version History api-ms-win-core-version-l1-1-0.dll : Introduced in Windows 10 (Build 10240). api-ms-win-core-version-l1-1-1.dll : Specifically introduced in Windows 10 (Build 10586) Subsequent Changes

: In later Windows 10 builds (14393+), these functions were often consolidated back into the Stack Overflow 2. Why "Missing" Errors Occur

The most common cause for a "Missing api-ms-win-core-version-l1-1-1.dll" error is operating system incompatibility , particularly when running modern software on Windows 8 or 8.1 Legacy OS Issues

: Because this specific DLL was introduced in Windows 10, software updated to require it (such as Microsoft 365/Office version 2006) will fail to launch on older systems like Windows 8. Bit Architecture (64-Bit vs. 32-Bit)

: On a 64-bit system, the file must be present in two locations to support both 64-bit and 32-bit applications: 64-bit location C:\Windows\System32 32-bit (compatibility) location C:\Windows\SysWOW64 Microsoft Learn 3. Resolution Strategies

If you encounter this error, several official and community-tested methods can resolve it:

1. Install the Latest Visual C++ Redistributable (Most Common Fix)

Since this DLL is part of the Universal C Runtime, the easiest fix is to install the latest Visual C++ Redistributable packages.

Steps:

Go to Microsoft’s official download page for Visual C++ Redistributable.
Download the x64 (64-bit) version.
Run the installer as Administrator.
Restart your PC.

Pro tip: Also install the x86 version if you run older 32-bit apps. Both can live side-by-side safely.

Why You Should Never Download the DLL from “DLL Websites”

A quick Google search will reveal dozens of websites offering a free download of api-ms-win-core-version-l1-1-1.dll. Do not use them. Here’s why:

File Mismatch: Since this is an API Set forwarder, a standalone DLL file of this name is not meant to exist in System32 or SysWOW64. Adding it manually can break Windows file protection.
Malware Risks: Cybercriminals frequently package malware inside popular DLL names. Downloading from unknown sources is a leading cause of ransomware and trojan infections.
Version Conflicts: Even if you find a "64 bit" version, it may be compiled for a different Windows build or architecture, leading to the infamous 0xc000007b error (invalid Win32 application).

The correct solution involves updating your operating system or installing the proper runtime components from Microsoft.

Top 5 Ways to Fix the Error (64-bit Systems)

Why you might see an error

Common error messages:

"The program can't start because api-ms-win-core-version-l1-1-1.dll is missing from your computer."
"api-ms-win-core-version-l1-1-1.dll was not found."
Crash or failure to launch after a Windows update or when running software compiled for a different Windows version.

Typical causes:

Running software that requires a newer Windows Universal C runtime or Visual C++ runtime than installed.
Corrupted or missing system components after an interrupted update.
Using a 32-bit/64-bit mismatch (trying to run a 64-bit app with only 32-bit runtime present).
Malware or user-installed replacement DLLs (rare but possible).
Manually copying DLLs from untrusted sites (unsafe and can break system integrity).

Conclusion

The api-ms-win-core-version-l1-1-1.dll 64 bit error is not a sign of a broken computer—it is a sign of an outdated one. As software continues to evolve, older Windows versions lose support for modern runtime components. By installing the Universal C Runtime update, updating your Visual C++ Redistributables, or upgrading to a newer Windows version, you will resolve the issue safely and permanently.

Avoid the temptation to download standalone DLL files. Trust Microsoft’s official update channels and official runtime installers. Your system’s stability and security depend on it.

Have you resolved your error? If you continue to face issues, check your application’s official support forums or contact the developer. In most cases, the solutions above will have your 64-bit applications running smoothly again within minutes.

api-ms-win-core-version-l1-1-1.dll (64-bit) is a system component that belongs to the Windows API-set—a collection of libraries used by the operating system to manage versioning information for software and hardware. When this "piece" of code is missing, applications (especially games or newer software running on older versions of Windows) may fail to start. Why the error happens This specific DLL is often part of the Universal C Runtime (CRT) or related Windows updates. Errors usually occur if: Operating System mismatch

: You are trying to run a modern program on an older OS (like Windows 7 or 8) that doesn't have these specific API sets by default. Missing Runtime Visual C++ Redistributable

packages, which contain these files, are not installed or are corrupted. How to fix it Install Windows Updates

: Ensure your OS is fully up to date. Many API-set DLLs are delivered through Windows Update Visual C++ Redistributable : Download and install the latest Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022 . You should install both the (64-bit) and (32-bit) versions for maximum compatibility. KB2999226 Update

: If you are on Windows 7 or 8.1, this specific update for the Universal C Runtime often resolves missing api-ms-win-core Avoid Manual Downloads

: Be cautious of "DLL download" websites. Downloading individual DLLs from third-party sites can lead to malware or further system instability. It is safer to install the official Microsoft packages. www.threesl.com Warning for Windows 7 users

: Some modern software (like newer versions of Adobe apps or certain Steam games) now requires "Version L1-1-1" or higher, which may not be natively supported on legacy systems without specific patches or "wrapper" files created by the modding community. Are you seeing this error while trying to launch a specific game or piece of software?

I have problem with dll files Need this api-ms-win-core-memory-l1-1-6.dll

api-ms-win-core-version-l1-1-1.dll file is a 64-bit Windows API set library component essential for the operating system, often required for running modern applications, particularly those utilizing the Universal C Runtime (UCRT).

Errors related to this file typically indicate that it is missing, corrupted, or that the application requiring it cannot find the correct version. Recommended Fixes: Install Windows Updates:

Running Windows Update is the most reliable way to restore missing system files like this one. Go to Settings > Update & Security and install all pending updates. Install/Repair Visual C++ Redistributable: The file is often included with the Microsoft Visual C++ Redistributable for Visual Studio . Downloading and running the vcredist_x64.exe (64-bit) installer can fix the issue. Run System File Checker (SFC): Open Command Prompt as Administrator and run sfc /scannow to scan for and repair corrupted system files. Avoid DLL Download Sites: It is highly recommended not to download individual

files from third-party sites, as these can be outdated, incorrect, or malicious. Use official Microsoft updates or reinstallation methods instead.

If a specific application is triggering this error, reinstalling that program may also resolve the problem.

How to Fix Api-ms-win-core-version-l1-1-1.dll Missing Errors (64-Bit)

If you’ve tried to launch a modern game or a high-end software suite only to be met with the error "The program can't start because api-ms-win-core-version-l1-1-1.dll is missing from your computer," you aren’t alone.

This specific DLL (Dynamic Link Library) file is part of the Windows API Sets. While the error looks intimidating, it usually boils down to a communication gap between your software and your operating system. Here is everything you need to know to get back up and running. What is Api-ms-win-core-version-l1-1-1.dll?

This file is a "stub" DLL. In newer versions of Windows, Microsoft reorganized how system functions are stored. Instead of one massive file, they use API Sets to redirect software requests to the correct system library.

The version-l1-1-1 file specifically handles version checking—allowing a program to ask Windows, "What version are you running?" If this file is missing or corrupted, the program crashes because it can't verify if your system meets its requirements. Why is it Missing? Api-ms-win-core-version-l1-1-1.dll 64 Bit

Outdated OS: This file is native to Windows 10 and 11. If you are running Windows 7 or 8.1, many modern apps expect this file to be there, but it doesn't exist in the older architecture.

Missing Visual C++ Redistributables: Many apps rely on the Microsoft Visual C++ packages to bridge the gap between the app code and the Windows API.

Corrupt System Files: A sudden power loss or failed update can corrupt the system's library folder. How to Fix the Error (Step-by-Step) 1. Install the Microsoft Visual C++ Redistributable

This is the most common fix. These packages contain the "Universal C Runtime" (UCRT), which includes the API set libraries. Go to the official Microsoft download page.

Download the architecture-specific installer. For a 64-bit system, you need vc_redist.x64.exe.

Pro Tip: Even on 64-bit systems, many apps are 32-bit. It is often safest to install both the x86 and x64 versions. 2. Run the System File Checker (SFC)

If the file is missing due to corruption, Windows can often repair itself. Type cmd in your Windows search bar.

Right-click "Command Prompt" and select Run as Administrator. Type sfc /scannow and hit Enter. Restart your computer once the process reaches 100%. 3. Update Windows

Since this DLL is a core part of the Windows API Set, Microsoft frequently pushes fixes for it via Windows Update. Go to Settings > Update & Security > Windows Update. Click Check for updates.

If you are on Windows 7, ensure you have the KB2999226 update installed, which brings the Universal C Runtime to older systems. 4. Reinstall the Application

Sometimes the error isn't with Windows, but with how the application was installed. If a specific game (like Elden Ring or Horizon Zero Dawn) is throwing this error, the installation might have skipped registering the necessary dependencies. Uninstalling and doing a fresh "clean" install can resolve the link. A Warning on "DLL Download" Sites

When searching for "Api-ms-win-core-version-l1-1-1.dll 64 Bit," you will find many websites offering a direct download of the single .dll file. Avoid these.

Downloading individual DLLs from third-party sites is risky for two reasons: Security: These files can contain bundled malware.

Compatibility: A DLL is rarely a "standalone" fix. If you drop a random 64-bit DLL into your system folder, it may still fail because it lacks the registry keys and dependency files that come with an official Microsoft installer.

The Api-ms-win-core-version-l1-1-1.dll error is almost always a sign that your system needs the latest Visual C++ Redistributable or a Windows Update. Fix the foundation of your OS, and the error will usually vanish on its own.

Which operating system (Windows 7, 10, or 11) are you currently running so I can provide the specific update link?

The Mysterious Case of Api-ms-win-core-version-l1-1-1.dll 64 Bit

It was a typical Monday morning for John, a software engineer at a reputable tech firm. He arrived at the office, sipped his coffee, and booted up his computer. As he logged in, he noticed something strange. His computer was taking an unusually long time to start up. He brushed it off as a minor glitch, thinking it would resolve itself.

However, as he began to work on his project, he encountered a frustrating error message: "The file api-ms-win-core-version-l1-1-1.dll is missing." He tried to launch his application, but it refused to open. The error message seemed to suggest that a crucial DLL (Dynamic Link Library) file was nowhere to be found.

John was perplexed. He had no recollection of deleting or modifying any system files, and his computer had been functioning smoothly until this morning. He decided to investigate further.

The Search Begins

John dove into the world of DLL files and Windows core libraries. He discovered that api-ms-win-core-version-l1-1-1.dll was a legitimate Microsoft DLL file, responsible for handling version-related functions in Windows. It was a 64-bit file, which meant it was designed for 64-bit versions of Windows.

As he dug deeper, John found that the file was part of the Windows API (Application Programming Interface), which allowed developers to interact with the operating system. He realized that the file was not just any ordinary DLL, but a critical component of the Windows core.

The Conspiracy Unfolds

John's investigation led him to suspect that the issue might not be with the file itself, but with the way it was being referenced by the system. He hypothesized that some software or update might have altered the file's registration or dependencies.

He checked the Event Viewer logs and found a suspicious entry: "The DLL file api-ms-win-core-version-l1-1-1.dll was not found due to an incorrect configuration in the registry." The log hinted at a registry error.

The Resolution

John decided to try a few troubleshooting steps:

System File Checker (SFC) scan: He ran an SFC scan, which verified the integrity of system files, including DLLs. The scan detected a corrupted registry entry and fixed it.
Registry repair: He manually cleaned up the registry, removing any erroneous entries related to the DLL file.
System Update: He ensured that his Windows installation was up-to-date, as newer updates might have addressed the issue.

After completing these steps, John rebooted his computer. To his relief, the error message disappeared, and his application launched successfully.

The Takeaway

The mysterious case of api-ms-win-core-version-l1-1-1.dll 64 Bit had been solved. John learned that even the most seemingly obscure errors can have logical explanations. He realized the importance of:

Regular system maintenance
Verifying system file integrity
Keeping the registry clean and organized

From that day on, John made sure to stay vigilant, knowing that a single misstep in the complex world of system files and registry entries could lead to frustrating errors. The experience had taught him the value of patience, persistence, and thorough investigation in resolving even the most enigmatic technical issues.

Epilogue

As John returned to his project, he couldn't help but wonder about the countless other DLL files and system components working behind the scenes to keep his computer running smoothly. He appreciated the intricate dance of code and libraries that enabled his applications to function. The experience had given him a newfound respect for the inner workings of his computer and the importance of maintaining a healthy, stable system.

Api-ms-win-core-version-l1-1-1.dll is a system-level component of the Windows Operating System, specifically part of the ApiSet Stub library. It is not a software product you "review" in the traditional sense, but rather a dependency required for programs to interact with Windows versioning APIs. Key Technical Insights

Purpose: It acts as a "cog" in the Windows machinery, providing instructions for software to check the OS version or compatibility. Go to Microsoft’s official download page for Visual

64-Bit Architecture: The 64-bit version is specifically designed for x64 applications running on 64-bit versions of Windows.

Distribution: This file is typically distributed through the Microsoft Visual C++ Redistributable packages or standard Windows Updates. Common Issues and Solutions

If you are searching for a "review" because you encountered an error stating this file is missing, it usually indicates a corrupted installation or an outdated OS.

Update Windows: The most reliable "fix" is to run Windows Update to ensure your system files are current.

Visual C++ Redistributable: Many users find success by reinstalling the Visual C++ Redistributable for Visual Studio, which often contains these API sets.

Avoid DLL Download Sites: Experts strongly advise against downloading individual .dll files from third-party websites, as they can contain malware or be incompatible with your specific system version.

Are you currently seeing a "Missing DLL" error message when trying to launch a specific program? AI responses may include mistakes. Learn more

I have problem with dll files Need this api-ms-win-core-memory-l1-1-6.dll

Fixing the "Api-ms-win-core-version-l1-1-1.dll" Missing Error on 64-Bit Windows

If you’ve tried to launch a modern game or a high-end creative suite and were met with a popup stating that api-ms-win-core-version-l1-1-1.dll is missing from your computer, you aren't alone. This specific error is common on Windows 7, 8, and sometimes even early versions of Windows 10.

Here is a straightforward guide to understanding why this happens and how to fix it without downloading sketchy files from the internet. What is this DLL file?

The api-ms-win-core-version-l1-1-1.dll is part of the Windows API Set. These files act as a bridge, allowing software developers to communicate with the Windows operating system. The "l1-1-1" version specifically handles version-checking functions.

When you see this error, it usually means the software you are trying to run is looking for a library that doesn’t exist in your current version of Windows, or your system files have become corrupted. Method 1: Install the Windows Update (KB2999226)

Most of the time, this DLL is missing because the Universal C Runtime (CRT) isn't installed or updated. This is a common requirement for apps built with Visual Studio. Go to the official Microsoft Download Center. Look for the update KB2999226.

Download the version specifically for Windows x64-based systems. Restart your computer after installation. Method 2: Update Visual C++ Redistributable Packages

Since this file is a component of the Visual C++ library, installing the latest redistributable often registers the missing DLL. Navigate to the Microsoft Visual C++ downloads page. Download the VC_redist.x64.exe file.

Run the installer and select "Repair" if it’s already installed, or "Install" if it’s new. Reboot your system. Method 3: Run the System File Checker (SFC)

If the file should be there but is corrupted, Windows has a built-in tool to fix itself. Type cmd in your Windows search bar. Right-click Command Prompt and select Run as Administrator. Type the following command and hit Enter:sfc /scannow

Wait for the process to finish (it may take 10–15 minutes). If Windows finds a discrepancy, it will automatically replace the missing DLL. Method 4: Update Windows

If you are on Windows 7 or 8, Microsoft released various "Rollup" updates that include these API sets. Go to Settings > Update & Security > Windows Update. Click Check for updates.

Ensure all "Optional" updates related to the .NET Framework or C++ are installed. Important: Avoid "DLL Download" Sites

A common instinct is to search for the specific DLL name and download it from a third-party site. Do not do this.

These files are often outdated or incompatible with 64-bit systems.

They are a common delivery method for malware and keyloggers.

Manually dropping a DLL into System32 without properly registering it rarely fixes the underlying issue.

The api-ms-win-core-version-l1-1-1.dll error is almost always solved by updating the Universal C Runtime or the Visual C++ Redistributables. By using official Microsoft installers, you ensure your 64-bit system remains secure and stable.

The silence in the server room was broken only by the rhythmic pulse of blue LEDs and the low hum of cooling fans. Inside the architecture of System32, life was usually a series of predictable handshakes and hand-offs. But tonight, there was a hole in the world.

"Entry point not found," the Kernel whispered, its voice echoing through the registry hives.

The Application, a massive, multi-threaded beast designed for high-end rendering, was shivering. It had just tried to cross the bridge into the OS layer, but the bridge was gone. It was looking for Api-ms-win-core-version-l1-1-1.dll 64 Bit , a tiny but vital piece of the Universal C Runtime.

Deep in the directory shadows, a fragmented Shortcut watched the chaos. "He isn't coming," the Shortcut muttered. "He belongs to the newer builds. We’re running on an older heart—Windows 7. This app thinks it’s in the future."

The DLL in question was a phantom—a "Set" library that acted as a translator between the software and the Windows Versioning API. Without it, the Application couldn't even tell what year it was, let alone how to run.

"I can't initialize," the Application groaned, its memory addresses beginning to leak. "I need that 64-bit link. My instructions are written in a language the Kernel doesn't speak yet." A frantic Search protocol scurried through the C:\Windows\System32

folders, sweeping aside old log files and dusty drivers. It found other versions—the

—but they were like keys that almost fit the lock, yet remained stubbornly stuck.

Suddenly, a prompt appeared in the physical world above. A user, frustrated and tired, had finally typed the command: Update for Universal C Runtime in Windows.

The system shivered. New data packets began to rain down like starlight. Among them, glowing with 64-bit precision, was the missing file. It slid into its slot in the System32 directory with a satisfying digital click. In simpler terms

The Application stopped shivering. The "Entry point not found" error vanished into the recycle bin. With the Api-ms-win-core-version-l1-1-1.dll

finally acting as the bridge, the rendering engine roared to life, and the screen above finally turned from a cold, error-gray to a vibrant, functional glow. The ghost had been found. technical steps to fix this specific DLL error on an older system?

The api-ms-win-core-version-l1-1-1.dll file is a critical component of the Windows API Set, used by software to access specific operating system features. If you are seeing a "missing" or "not found" error, it typically means a program—frequently Microsoft Office 365 or Word—cannot find the libraries it needs to run on older operating systems like Windows 8 or Windows 7. Understanding the 64-Bit File Structure

On a 64-bit Windows system, DLL files are organized in a way that often confuses users: 64-bit DLLs are actually stored in C:\Windows\System32. 32-bit DLLs are stored in C:\Windows\SysWOW64.

You may also find this specific DLL in the downlevel subfolders of these directories. Common Fixes for "Missing" Errors

Do not download individual DLL files from unofficial third-party websites, as they may contain malware. Instead, use these verified methods:

api-ms-win-core-version-l1-1-1.dll (64-bit) is a critical component of the Windows API Set architecture, functioning as a "virtual DLL" or stub. It does not contain actual code but instead serves as an indirection layer that redirects application calls to the correct underlying system libraries, such as kernel32.dll kernelbase.dll ofekshilon.com The Architecture of Redirection

Introduced during the "MinWin" refactoring effort (starting with Windows 7/8), API Sets like api-ms-win-core-version-l1-1-1.dll

were designed to decouple applications from the physical location of system functions. This allows Microsoft to move functions between different internal DLLs without breaking software that relies on them. ofekshilon.com Virtual Identity

: The library is not a physical file in the traditional sense; it is a contract name recognized by the Windows library loader. The "Version" Contract

: This specific set handles versioning-related functions (e.g., GetFileVersionInfo VerQueryValue 64-Bit Context

: On 64-bit systems, the 64-bit version of this stub resides in C:\Windows\System32

, while the 32-bit version for compatibility (WoW64) is found in C:\Windows\SysWOW64 Common Issues and Disruption

Errors involving this file typically manifest as "api-ms-win-core-version-l1-1-1.dll is missing". These errors often arise from two distinct scenarios: Microsoft Learn

api-ms-win-core-debug-l1-1-1.dll Error Windows 11 | 2 Ways To FIX

The Mysterious Case of the Missing DLL

It was a typical Monday morning at TechCorp, a leading software development company. Emma, a skilled software engineer, was working on a critical project, a 64-bit Windows application that required precise calculations and robust performance. As she booted up her computer and logged in, she noticed something was off. Her usually reliable Windows 10 system was displaying an error message that made her heart sink:

"Api-ms-win-core-version-l1-1-1.dll is missing. Please reinstall the program."

Emma tried to brush it off, thinking it was just a minor glitch. But as she began to work on her project, she realized that the error was not just a one-time thing. Every time she tried to run her application, the same error popped up. The Api-ms-win-core-version-l1-1-1.dll file seemed to have vanished into thin air.

Panicked, Emma searched online for solutions, but the usual fixes – reinstalling the program, running System File Checker (SFC), and updating Windows – didn't work. She tried to manually download the missing DLL from various websites, but they were either fake or incompatible with her 64-bit system.

As the day wore on, Emma's colleagues began to experience similar issues. Their 64-bit Windows systems were all displaying the same error message. The company's IT department was stumped, and the development team was on the verge of a meltdown.

That's when Jack, a grizzled veteran of the IT department, stepped in. He had seen this type of error before, back in the Windows XP days. He explained to Emma and the team that the Api-ms-win-core-version-l1-1-1.dll file was a critical component of the Windows API, responsible for handling version information.

Jack suspected that the problem lay with a recent Windows update that had caused a mismatch between the 64-bit and 32-bit versions of the DLL. He proposed a solution: to manually replace the missing DLL with a compatible version from a trusted source.

Emma and the team were skeptical, but they had no other leads. Jack carefully guided them through the process, and to their surprise, it worked. The Api-ms-win-core-version-l1-1-1.dll file was replaced, and the error disappeared.

The team breathed a collective sigh of relief as their application began to run smoothly once more. Emma turned to Jack and asked, "How did you know about this?" Jack smiled and replied, "Well, I've been around the block a few times. I've seen my fair share of DLL hell."

The team laughed, and Emma realized that sometimes, the most seemingly insurmountable problems require old-school expertise and a deep understanding of the Windows ecosystem.

From that day on, Emma made sure to keep her system up to date and to appreciate the importance of a reliable IT department. And Jack? He was hailed as a hero, his knowledge and experience invaluable to the team.

The End

I hope you enjoyed this story! The "Api-ms-win-core-version-l1-1-1.dll 64 Bit" error may seem like a minor issue, but it can be a frustrating and challenging problem to resolve. This story highlights the importance of having experienced IT professionals and a solid understanding of Windows system internals.

If you’re seeing the error "api-ms-win-core-version-l1-1-1.dll is missing," you aren't alone. This specific error often pops up for users on Windows 7, 8, or 8.1 when trying to run modern applications like Microsoft Office 365, Sea of Thieves, or newer games. Why is this happening?

This DLL is part of an "API Set"—a library that modern Windows versions (Windows 10 and 11) use to manage versioning. When an app built for a newer OS tries to run on an older one, it looks for this file and fails because the older system doesn't natively include it. How to Fix It (The Safe Way)

Avoid downloading individual DLL files from "DLL fixer" websites, as they often contain malware or cause system instability. Instead, try these verified methods: why prompt api-ms-win-core-errorhandling-l1-1-1 this errror

This is a great question, because that filename often triggers confusion and worry. Let me tell you the story of api-ms-win-core-version-l1-1-1.dll—what it is, why you’re seeing it, and what you should (and shouldn’t) do.

What is this DLL file?

Technically, this file is part of the Windows API Sets. The naming convention provides clues about its function:

Api: It is an Application Programming Interface.
Ms-Win-Core: It belongs to the core Windows functionality.
Version: It deals with version checking and operating system versioning.
L1-1-1: This is a specific versioning code used by Microsoft to manage dependencies.

In simpler terms, this Dynamic Link Library (DLL) allows programs to query the version of the Windows operating system. Applications use it to check if they are running on a compatible version of Windows (e.g., Windows 10 vs. Windows 11) or to access version-specific features. It acts as a "minifile" that redirects requests to the main system files (like kernel32.dll or kernelbase.dll) that actually perform the work.