ntdll.dll Errors: Fix Missing Files and App Crashes on Windows

If ntdll.dll is missing, not found, or named in a crash report, the correct fix depends on the exact error. ntdll.dll is a genuine Microsoft Windows system component, so downloading a replacement DLL or registering it with regsvr32 is usually unsafe and will not address the underlying problem.

For a genuinely missing or corrupted system file, install Windows updates, run DISM, then run System File Checker. If only one game or application crashes while Windows itself works normally, repair that application and investigate its files, plug-ins, overlays, drivers, or memory instead.

As an Amazon Associate I earn from qualifying purchases.

What ntdll.dll is

ntdll.dll is Windows’ NT Layer DLL. It provides much of the Windows Native API and low-level user-mode operating-system support used by core Windows components and ordinary applications. Microsoft documents native applications and the role of the Native API in its Sysinternals technical material. Microsoft’s explanation of native applications

It is part of Windows, not a separate Visual C++ runtime, DirectX package, .NET installation, game component, or device driver. Many unrelated applications use Windows functions that ultimately pass through ntdll.dll, which is why the file can appear in an error involving a browser, game, printer utility, video editor, installer, or business application.

Standard Windows metadata identifies the file as:

• File description: NT Layer DLL
• Product: Microsoft Windows Operating System
• Original filename: ntdll.dll
• Publisher: Microsoft Corporation

A Microsoft Q&A crash report shows the same type of file metadata. Microsoft Q&A example showing ntdll.dll metadata

There is no single correct universal version number or file size. Microsoft services ntdll.dll with Windows, so its version and size vary according to the Windows release, build, architecture, and cumulative updates installed on the PC. A version number copied from another computer is not a safe replacement.

Where ntdll.dll should be located

On 32-bit Windows, the normal location is:

%windir%\System32\ntdll.dll

On 64-bit Windows, there are normally two architecture-specific copies:

%windir%\System32\ntdll.dll
%windir%\SysWOW64\ntdll.dll

The names are misleading:

• System32 contains the native 64-bit system files on 64-bit Windows.
• SysWOW64 contains the 32-bit system files used by 32-bit applications.

WOW64 redirects 32-bit applications to the appropriate system locations. Do not copy the file from System32 to SysWOW64, or the other way around. The files are intended for different architectures. Microsoft’s File System Redirector documentation

A 32-bit program may also require 32-bit application runtimes even when it is running on 64-bit Windows. A 32-bit process cannot execute a 64-bit DLL as though it were a 32-bit library, and the reverse is also true. Microsoft’s 32-bit application guidance

Identify which ntdll.dll error you have

The filename appears in several different classes of problems. They do not all call for the same repair.

Missing or not found

Typical messages include:

The program can't start because ntdll.dll is missing from your computer. Try reinstalling the program to fix this problem.

This application has failed to start because ntdll.dll was not found. Re-installing the application may fix this problem.

These messages can mean that Windows cannot find the system file, but they can also be caused by another missing dependency in the application’s loading chain. Check the complete dialog, the application path, and whether the problem affects more than one program.

Windows loader status 0xC0000135 corresponds to a missing required DLL. The filename shown in the message may be the first file Windows reports rather than the only missing component. Microsoft Q&A example involving status 0xC0000135

Bad image or damaged file

You may see wording such as:

C:\Windows\System32\ntdll.dll is either not designed to run on Windows or it contains an error.

This points more strongly toward corruption, an architecture mismatch, a damaged application-local DLL, or an incompatible application. It does not mean that manually downloading another copy is safe.

Missing procedure entry point

A program may report:

The procedure entry point [function name] could not be located in the dynamic link library ntdll.dll.

This commonly indicates that an application or one of its DLLs expects an API that is not available in the installed Windows environment, or that the wrong DLL has been placed in the application folder. Reinstall or update the application and remove manually copied DLLs before considering deeper Windows repair. Microsoft Q&A example involving a missing entry point

regsvr32 reports that DllRegisterServer is missing

If you ran:

regsvr32 ntdll.dll

you may have received:

The module "ntdll.dll" was loaded but the entry-point DllRegisterServer was not found.

That result is expected. regsvr32 is for DLLs that expose registration functions such as DllRegisterServer. ntdll.dll is a Windows system library, not a COM or ActiveX registration DLL. Running the command again, adding /u, or trying Safe Mode will not repair it. Microsoft’s regsvr32 documentation and DllRegisterServer documentation

Event Viewer names ntdll.dll as the faulting module

Event Viewer may show entries such as:

Faulting module name: ntdll.dll
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Exception code: 0xc0000005

or:

Exception code: 0xc0000374

This does not prove that ntdll.dll caused the crash. Windows may detect an application’s invalid memory operation, buffer problem, or heap corruption inside a system library.

0xc0000005 is an access violation. 0xc0000374 indicates heap corruption. Both can result from an application defect, plug-in, overlay, injected security software, invalid memory use, or unstable hardware. Microsoft’s access violation explanation and Microsoft’s NTSTATUS documentation

Before repairing Windows, ask:

• Did Windows install an update immediately before the problem?
• Did the application or game update?
• Did antivirus software quarantine anything?
• Was the program moved, modified, cracked, modded, or manually patched?
• Does one application fail, or do several unrelated programs fail?
• Does the problem affect one Windows user profile?
• Does it happen during gaming, printing, video playback, startup, or installation?
• Is the application 32-bit or 64-bit?
• Does Event Viewer identify another DLL earlier in the crash chain?

Fix ntdll.dll problems in order

Start with the repair that matches the symptom. Do not perform every step blindly if only one application is affected.

1. Install pending Windows updates

Time needed: Usually 10 to 30 minutes, depending on the update and restart time.

Windows updates can replace damaged system components and resolve compatibility problems between an older application and the installed Windows build.

On Windows 11:

1. Open Start.
2. Select Settings.
3. Select Windows Update.
4. Select Check for updates.
5. Install every available update.
6. Restart Windows, even if the update screen does not immediately require it.
7. Test the affected program again.

On Windows 10:

1. Open Start.
2. Select Settings.
3. Select Update & Security.
4. Select Windows Update.
5. Select Check for updates.
6. Install available updates.
7. Restart Windows and retest the program.

Microsoft’s current update instructions are available here: Install Windows updates

If Windows Update fails, note the exact error code rather than repeatedly restarting. Continue with DISM and SFC below. If the error started immediately after a Windows update and affects only an old application, the problem may be compatibility-related rather than a missing system file.

2. Repair Windows components with DISM and SFC

Time needed: Around 15 to 45 minutes, sometimes longer on a damaged installation.

This is the correct first repair for a missing, corrupted, or bad-image ntdll.dll error affecting Windows itself. DISM repairs the Windows component store, which provides the source that SFC uses to restore protected system files.

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Select Yes if User Account Control asks for permission.
6. Run this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for DISM to finish. Do not close the window if the progress appears to pause.
2. After DISM completes successfully, run:

sfc /scannow

1. Wait until the verification reaches 100 percent.
2. Restart Windows.
3. Test the affected program.

Microsoft specifically recommends running DISM before SFC. Microsoft’s DISM and SFC repair guidance

The SFC result tells you what happened:

• Windows Resource Protection did not find any integrity violations: Windows protected files appear intact. Focus on the application, drivers, overlays, security software, or hardware.
• Windows Resource Protection found corrupt files and successfully repaired them: Restart and retest. This is the result most likely to resolve a genuinely damaged system DLL.
• Windows Resource Protection found corrupt files but was unable to fix some of them: Run DISM again, restart, and run SFC again. If the result persists, use a repair reinstall or matching Windows installation media.
• DISM cannot find the source files: Windows may need a matching repair source or installation media.

If Windows Update cannot provide the repair source, Microsoft documents this form:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

Replace C:\RepairSource\Windows with a trusted, matching Windows installation or component source. Do not use a random folder or an unrelated Windows build. Microsoft’s repair-source instructions

If manually checking the same commands repeatedly is becoming guesswork, Outbyte PC Repair can scan for issues and show what it finds; the free scan identifies problems, while repair is performed by the full version, and it is not required for DISM or SFC.

3. Repair or reinstall the affected application

Time needed: Around 10 to 30 minutes, plus download time.

If only one program fails and DISM and SFC report no corruption, treat the application as the primary suspect.

First check whether the application has a built-in repair option:

1. Open Settings.
2. Select Apps.
3. Select Installed apps on Windows 11, or Apps & features on Windows 10.
4. Select the affected program.
5. Choose Advanced options if available.
6. Select Repair.
7. Launch the program again.
8. If it still fails, return to the same screen and select Reset only if you understand that the application’s local settings or cached data may be removed.

For a traditional desktop program:

1. Open Control Panel.
2. Select Programs.
3. Select Programs and Features.
4. Select the application.
5. Look for Repair or Change.
6. Follow the application’s installer prompts.

If no repair option exists, uninstall the program, restart Windows, and reinstall it from the developer’s official distribution channel. Do not copy a replacement ntdll.dll into the application folder.

If the issue began after a patch, update the application first. If the program was modified, cracked, manually patched, or installed from an untrusted source, replace it with a clean official installation.

4. Verify game files through the launcher

Time needed: Around 5 to 60 minutes, depending on the game and the number of files that must be replaced.

A game update, failed download, disk error, or antivirus quarantine can damage files that later crash inside ntdll.dll.

For Steam:

1. Open Steam.
2. Select Library.
3. Right-click the game.
4. Select Properties.
5. Select Installed Files.
6. Select Verify integrity of game files.
7. Wait for the process to finish.
8. Restart Steam and launch the game.

Steam provides its own instructions for verifying the integrity of game files.

For Epic Games Launcher:

1. Open Epic Games Launcher.
2. Select Library.
3. Select the three dots beside the game.
4. Select Manage.
5. Select Verify.
6. Wait for the verification to complete.
7. Launch the game again.

Epic documents this process in its game file verification instructions.

Before retesting, temporarily remove mods, injectors, reshade files, unofficial patches, and overlays. A clean game installation can still crash if an incompatible plug-in is loaded into it.

5. Remove overlays, plug-ins, and injected utilities

Time needed: 10 to 30 minutes.

An application that crashes in ntdll.dll may be receiving code from an overlay or utility that hooks into its process. Common examples include game overlays, recording tools, RGB utilities, hardware monitors, accessibility software, compatibility shims, and third-party security modules.

Temporarily disable or remove:

• Game overlays
• Mods and plug-ins
• Screen recording or performance overlays
• DLL injectors
• Compatibility layers
• Unofficial launchers
• Recently installed security software
• Hardware monitoring utilities

Test the application after each category is disabled. If the crash stops, re-enable items one at a time until the conflicting component is identified.

If the problem occurs only under one Windows user profile, create a temporary local profile and test the application there. A successful test suggests a profile-specific setting or extension, but it does not prove the Windows installation is damaged.

6. Check antivirus quarantine and run a malware scan

Time needed: 10 minutes for history checks; longer for a full or offline scan.

A security product may quarantine an application file or, in rare cases, flag a system file. Do not restore a file merely because its name is ntdll.dll. Malware can use the same filename, and a legitimate system file must be checked by its path, Microsoft signature, and detection details.

In Windows Security:

1. Open Start.
2. Type Windows Security.
3. Open the app.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent detections.
7. Check the file path and detection name.
8. Restore a quarantined file only after confirming that the detection is a false positive and the file is a genuine Microsoft system file.

Microsoft warns that restoring a real threat can expose the computer. Microsoft’s Protection History guidance

If infection is plausible:

1. Open Windows Security.
2. Select Virus & threat protection.
3. Select Scan options.
4. Select Microsoft Defender Offline scan.
5. Select Scan now.
6. Save open work before Windows restarts.

Defender Offline scans before the normal Windows environment loads. Microsoft Defender Offline guidance

After dealing with a confirmed false positive or malware incident, run DISM and SFC again.

7. Update, reinstall, or roll back the relevant driver

Time needed: 15 to 45 minutes.

Driver conflicts are more likely when games, browsers, video editors, printing software, or hardware-accelerated applications crash while Windows system checks are clean.

Pay particular attention to drivers updated immediately before the problem:

• Graphics
• Audio
• Printer
• Storage
• Chipset
• Network
• Security or virtualization software

Start with Windows’ supported Device Manager process:

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant device category.
4. Right-click the device.
5. Select Update driver.
6. Select Search automatically for drivers.
7. Restart Windows if prompted.

If the issue began after a driver update:

1. Right-click Start.
2. Select Device Manager.
3. Expand the device category.
4. Right-click the device.
5. Select Properties.
6. Open the Driver tab.
7. Select Roll Back Driver if available.
8. Restart Windows.

To reinstall a driver:

1. Open Device Manager.
2. Right-click the affected device.
3. Select Uninstall device.
4. Confirm the removal.
5. Restart Windows.
6. Allow Windows to reinstall the driver, or install the correct driver from the device manufacturer.

Microsoft documents this process in its driver update and reinstallation guidance.

When several driver versions are involved, Outbyte Driver Updater can scan and identify stale drivers instead of making you hunt through manufacturer pages; the free scan shows what it finds, while installation is handled by the full version, and it is not required if you prefer manual updates.

After changing a graphics, audio, or storage driver, retest the original workload rather than relying only on a desktop launch.

8. Use a clean boot to isolate third-party services

Time needed: 20 to 40 minutes.

A clean boot starts Windows with Microsoft services and essential startup components while temporarily excluding many third-party services. It can show whether an overlay, security program, updater, or background utility is involved.

1. Press Windows key + R.
2. Type msconfig.
3. Press Enter.
4. Open the Services tab.
5. Select Hide all Microsoft services.
6. Select Disable all.
7. Open the Startup tab.
8. Select Open Task Manager.
9. Disable enabled nonessential startup items.
10. Close Task Manager.
11. Select OK in System Configuration.
12. Restart Windows.
13. Test the application.

If the error disappears, re-enable services and startup items in groups until the conflicting program is identified.

After testing, restore normal startup:

1. Press Windows key + R.
2. Type msconfig.
3. Press Enter.
4. On the General tab, select Normal startup.
5. Select OK.
6. Restart Windows.

Microsoft’s clean-boot instructions are available here: How to perform a clean boot in Windows

9. Install the runtime that the application actually requires

Time needed: 10 to 30 minutes.

Visual C++, DirectX, and .NET can cause application launch errors, but they do not normally repair ntdll.dll. Install them only when the application or its installer identifies that runtime as missing or damaged.

Visual C++ Redistributable

Use Microsoft’s official Visual C++ Redistributable packages:

• vc_redist.x86.exe for 32-bit applications
• vc_redist.x64.exe for 64-bit applications
• vc_redist.arm64.exe for ARM64 applications

A 32-bit game may need the x86 package even on 64-bit Windows. Older applications may also require separate older Visual C++ generations, including 2013 or earlier. These packages remain side by side when applications need them. Do not uninstall older runtimes simply because the newest package is installed.

Use Microsoft’s latest supported Visual C++ Redistributable downloads.

DirectX legacy components

Some older games require legacy side-by-side components that are not supplied by the main DirectX version built into Windows. Microsoft’s DirectX End-User Runtimes package is named:

directx_Jun2010_redist.exe

The package supplies legacy components such as D3DX, XInput 1.3, XAudio 2.7, XACT, and Managed DirectX 1.1. It does not replace the DirectX version built into Windows. Microsoft’s DirectX End-User Runtimes June 2010 download

.NET Framework

Use the official .NET Framework Repair Tool only when the application or installer identifies .NET Framework as the failing component.

Installing one of these runtimes merely because Event Viewer mentions ntdll.dll is not a definitive fix.

10. Test memory, storage, firmware, and hardware stability

Time needed: 30 minutes to several hours, depending on the tests.

If different applications crash with different faulting modules, or if crashes are random and load-dependent, investigate the hardware rather than replacing ntdll.dll.

Look for:

• Overclocking
• XMP or EXPO memory profiles
• CPU or GPU undervolting
• Unstable BIOS settings
• Failing RAM
• Storage errors
• Outdated firmware
• Overheating

Start by returning BIOS performance settings to their defaults. Then run Windows Memory Diagnostic:

1. Open Start.
2. Type Windows Memory Diagnostic.
3. Open the tool.
4. Select Restart now and check for problems.
5. Allow the test to complete.
6. After Windows starts, open Event Viewer.
7. Select Windows Logs.
8. Select System.
9. Find the MemoryDiagnostics-Results event.

Microsoft recommends Windows Memory Diagnostic when recurring system crashes may involve memory. Microsoft’s troubleshooting guidance for recurring crashes

Also check storage health with the computer or drive manufacturer’s official diagnostics. Update BIOS or firmware only through the system or component manufacturer’s supported instructions.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Why ntdll.dll errors happen

The most useful distinction is whether Windows itself is damaged or whether another program caused the failure.

Clue	More likely cause	Appropriate response
Several unrelated applications fail	Windows component corruption, malware, hardware, or a driver conflict	Windows Update, DISM, SFC, security checks, and hardware diagnostics
One application fails	Application bug, damaged files, plug-in, overlay, or compatibility issue	Update, repair, verify, remove modifications, or reinstall the application
Error names System32 or SysWOW64 and says missing or bad image	Missing or corrupted Windows component	DISM, SFC, updates, then repair reinstall if necessary
Event Viewer names ntdll.dll with 0xc0000005	Access violation caused by application code, injected software, or memory	Repair the application, remove injectors, test drivers and memory
Event Viewer names ntdll.dll with 0xc0000374	Heap corruption or invalid memory use	Investigate application files, plug-ins, overlays, and hardware
Problem began after antivirus detection	Quarantine, false positive, or malware	Check Protection History, verify the file, and run Defender Offline if needed
Entry point or bad-image error follows manual DLL copying	Architecture or version mismatch	Remove the copied DLL and reinstall the application
Only an older application fails after Windows changes	Compatibility problem or missing application update	Update the application, use System Restore if appropriate, and contact its vendor

Corrupted or missing Windows files

This is the most likely category when multiple unrelated programs fail, the error points to a Windows directory, or SFC reports corruption. An interrupted update, disk problem, malware incident, or failed servicing operation can damage protected system files.

Use Windows Update, DISM, and SFC first. If the issue remains, use a Windows repair reinstall rather than manually replacing ntdll.dll.

The application crashed inside Windows code

A faulting module is not necessarily the root cause. An application can corrupt memory and continue running until Windows detects the problem in a system routine. This is especially important for access violations and heap corruption.

If DISM and SFC are clean and only one program fails, repairing Windows repeatedly is unlikely to solve the application defect. Update the application, remove plug-ins and overlays, verify its files, and contact the application vendor if the crash continues.

Driver, overlay, or security conflict

Hardware-accelerated applications often load graphics, audio, capture, security, or monitoring components into the same process. A conflict can surface as an ntdll.dll crash even though the system DLL is healthy.

A clean boot and careful driver rollback can isolate this category.

Architecture or version mismatch

A 32-bit program uses the 32-bit Windows environment, while a 64-bit program uses the 64-bit environment. A manually copied library, an outdated application, or a mismatched application-local DLL can cause bad-image and entry-point errors.

Remove manually copied DLLs from the application directory and reinstall the program from its official source. Do not substitute a different Windows build’s ntdll.dll.

Windows update regression or old software

If a program worked until a feature or cumulative update, install the latest available Windows update and check for an application update. If only an old program is affected, the developer may need to update it for the current Windows environment.

System Restore can return system files, registry settings, drivers, and installed programs to an earlier restore point without removing personal files. Microsoft’s System Restore guidance

Do not download or copy ntdll.dll

Do not download ntdll.dll from a random DLL website. A downloaded copy may contain malware, belong to another Windows build, use the wrong architecture, or simply fail to fix the actual missing dependency.

Also avoid copying the file from:

• Another computer
• An older Windows installation
• A different Windows build
• System32 into SysWOW64
• SysWOW64 into System32

Windows system DLLs are version- and architecture-specific. Manual replacement can interfere with Windows servicing and create an architecture mismatch. An application-local DLL can also be loaded before the system directory in some situations, so copying a file into the application folder may introduce a new conflict rather than solve the original one. Microsoft’s DLL search-order documentation and DLL security guidance

Microsoft documents manual SFC replacement only as an advanced recovery technique when the CBS log identifies a damaged file and a trusted, matching source is available. That is not the same as downloading an arbitrary DLL. DISM, SFC, Windows Update, and a repair installation are safer approaches.

Repair Windows without deleting personal files

Windows 11 repair reinstall

Time needed: 30 minutes to several hours.

Windows 11 may offer a repair reinstall through Windows Update:

1. Open Start.
2. Select Settings.
3. Select System.
4. Select Recovery.
5. Find Fix problems using Windows Update.
6. Select Reinstall now.
7. Follow the prompts.
8. Keep the computer connected to power while Windows reinstalls the current version.

This process repairs Windows system files and components while preserving apps, files, and settings. Microsoft’s repair-reinstall instructions

In-place repair with installation media

If the Windows 11 option is unavailable, or if you are repairing Windows 10, use matching Windows installation media:

1. Obtain official installation media for the installed Windows edition and architecture.
2. Start Windows normally.
3. Open the installation media from within Windows.
4. Run setup.exe.
5. Choose Change what to keep when prompted.
6. Select Keep personal files and apps.
7. Continue the installation.

Do not boot from the media and choose a clean installation unless you have backed up your files and deliberately intend to erase the existing installation. Microsoft documents the in-place process in Reinstall Windows with installation media

If Windows will not boot

When Windows cannot start normally, use Windows Recovery Environment rather than copying ntdll.dll from another computer.

Depending on what is available, use:

• Startup Repair
• Offline DISM and SFC
• System Restore
• Safe Mode for diagnosis
• Matching Windows installation media

If you use offline repair commands, confirm the Windows drive letter shown in Recovery Environment before running commands. It may not be C: while Windows is offline.

If the system recently changed and a suitable restore point exists, System Restore can be preferable to a destructive reset. Back up important files before advanced recovery.

Frequently asked questions

Is ntdll.dll a virus?

The genuine Windows copy is a Microsoft system file. A file with that name in an unexpected location, without a valid Microsoft signature, or flagged by security software may be malicious or tampered with. Check the path, signature, and Protection History rather than trusting the filename alone.

Should I register ntdll.dll with regsvr32?

No. ntdll.dll is not a COM or ActiveX registration DLL and normally does not export DllRegisterServer. The resulting error is not evidence that the file needs registration.

Should I download a new copy of ntdll.dll?

No. Use Windows Update, DISM, SFC, or a repair reinstall. A random replacement can have the wrong version or architecture and may introduce malware.

Why does Event Viewer blame ntdll.dll when only my game crashes?

Windows may detect the game’s invalid memory operation inside ntdll.dll. Verify the game files, remove mods and overlays, update the game and drivers, and investigate memory if multiple programs crash.

Does installing Visual C++ fix ntdll.dll?

Not normally. Visual C++ Redistributables fix missing Visual C++ runtime dependencies when an application actually requires them. They do not replace the Windows copy of ntdll.dll.

Do I need both x86 and x64 Visual C++ packages?

Install the architecture required by the application. A 32-bit application can require x86 Visual C++ even on 64-bit Windows. Older Visual C++ generations may also be needed side by side.

Does DirectX 12 include every DirectX component?

No. Older games may require legacy side-by-side components supplied by Microsoft’s DirectX End-User Runtimes June 2010 package. Installing that package does not replace the main DirectX version built into Windows.

SFC repaired files, but the error returned. What now?

Investigate disk health, malware, failed servicing, unstable memory, and third-party software. Repeated corruption can indicate a problem beyond the individual DLL.

SFC and DISM are clean. Should I reinstall Windows?

Not immediately. If only one application fails, repair or reinstall that application first, remove overlays and plug-ins, and update its drivers. Consider a repair reinstall when Windows has broader symptoms or the application-specific investigation is exhausted.

What information should I provide to the application vendor?

Record the exact error text, application name and version, Windows edition and build, whether the program is 32-bit or 64-bit, the Event Viewer exception code, recent updates, installed mods or overlays, and whether other applications fail. Include crash dumps if the vendor requests them, but do not upload personal files or security logs without reviewing them.

The practical rule is simple: repair Windows when Windows files are actually damaged, and repair the application when one application merely reports ntdll.dll as its crash location.

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.