authz.dll Problems: Restore Windows Authorization Safely

“The program can’t start because authz.dll is missing from your computer.” You may also see “authz.dll was not found,” “authz.dll could not be loaded,” or a Bad Image message when Windows or an application tries to start.

The 60-second answer

authz.dll is a genuine Microsoft Windows system DLL. Its internal description is Authorization Framework, and it provides the Windows AuthZ API used by applications to evaluate permissions, access tokens, security descriptors, ACLs, and auditing contexts. It is part of Windows, not a Visual C++ Redistributable, DirectX package, or .NET runtime.

As an Amazon Associate I earn from qualifying purchases.

The safest repair is to restore Windows components rather than download a replacement file:

1. Restart the computer and install pending Windows updates.
2. Open Command Prompt as administrator.
3. Run DISM first:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Then run System File Checker:

sfc /scannow

1. Restart Windows and test the affected application again.

Microsoft documents DISM and System File Checker as the supported way to repair the Windows component store and protected system files.

Do not download authz.dll from a random DLL website, copy it from another computer, or try to register it with regsvr32. Those actions can introduce the wrong architecture, an incompatible Windows build, malware, or a new loading problem.

What is authz.dll

authz.dll is the Windows Authorization Framework DLL published by Microsoft Corporation. Applications use the AuthZ authorization API when they need to evaluate whether a user or security token can access a resource.

Microsoft identifies the file as Authz.dll, with the related header authz.h and import library Authz.lib. The AuthzInitializeResourceManager documentation describes the API and its Windows requirements. Microsoft also lists related authorization functions.

Because this is a Windows component, an error involving the file does not automatically mean that the application that displays the message supplied it. The application may simply be the first program to request the damaged or missing system component.

Where authz.dll should be located

The correct location depends on Windows architecture and on the architecture of the program loading the file.

• On 64-bit Windows, the native 64-bit system copy normally belongs in %SystemRoot%System32.
• On 64-bit Windows, 32-bit applications normally access the 32-bit system view through %SystemRoot%SysWOW64.
• On 32-bit Windows, the system copy is normally in System32.

System32 does not mean “32-bit.” On 64-bit Windows, it is normally the location used by native 64-bit system files. Windows uses WOW64 redirection so that 32-bit applications can access their compatible system files. Microsoft explains this behavior in its WOW64 compatibility documentation.

You can inspect the expected locations without changing anything:

dir "%SystemRoot%System32authz.dll"
dir "%SystemRoot%SysWOW64authz.dll"

A file being absent from one of these locations does not, by itself, prove that Windows is broken. The result depends on your Windows architecture, the program architecture, and the particular Windows release. Do not use an old version or file-size listing as a universal requirement for current Windows installations.

What the error messages mean

The wording can come from Windows Loader, an application, or both. Common variants include:

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

authz.dll was not found.

authz.dll could not be loaded.

authz.dll is either not designed to run on Windows or it contains an error.
Error status 0xc000012f.

These messages are related, but they do not always identify the underlying cause.

A “missing” message can mean the file was deleted, quarantined, damaged, or inaccessible. A “could not be loaded” message can also indicate that a dependency failed, the binary has the wrong architecture, or the file is invalid. The application may name authz.dll even when authz.dll is not the original source of the problem.

The fastest diagnostic question is whether one program fails or several.

If only one program fails

The application installation may be damaged, incomplete, incompatible, or using a private copy of a dependency. Repair or reinstall that program from its original vendor. If it is a game or launcher, use its built-in verify or repair function first.

If several programs fail

Treat the problem as a Windows component, update, security, storage, or malware issue. Start with DISM and SFC rather than reinstalling every affected application.

Fix 1: Restart and install Windows updates

A restart can complete a pending servicing operation or release a file that was locked during an earlier update. It is simple, but it is worth doing before deeper repair.

1. Save your work.
2. Select Start.
3. Select Power.
4. Choose Restart.
5. After signing in, open Settings.
6. On Windows 11, select Windows Update.
7. On Windows 10, select Update & Security, then Windows Update.
8. Select Check for updates.
9. Install all available updates.
10. Restart again if Windows requests it.

If the error began immediately after an update, Windows Update may have failed to finish servicing the component. Follow Microsoft’s Windows Update troubleshooting guidance if updates repeatedly fail.

Test the affected application after the restart. If the message returns, continue with the repair commands below.

Fix 2: Repair Windows with DISM and SFC

This is the primary repair for a missing or corrupted Windows copy of authz.dll.

DISM repairs the Windows component store, which supplies clean protected files. SFC then checks protected system files and replaces damaged copies using that repaired component store. Run them in this order.

Open an elevated Command Prompt

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt in the results.
4. Select Run as administrator.
5. Select Yes if User Account Control asks for permission.

The title bar should indicate that the window has administrator privileges. A normal Command Prompt may not be able to repair protected Windows files.

Run DISM

Enter this command exactly:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Press Enter and allow the operation to finish. It can appear to pause at a percentage for a while. Do not close the window simply because progress is slow.

When DISM completes, read the result. A successful repair normally reports that the restore operation completed successfully. If DISM reports that it could not find source files or could not repair the image, continue to the source-repair section below rather than copying authz.dll manually.

Run System File Checker

After DISM finishes, run:

sfc /scannow

Press Enter and wait until verification reaches 100 percent.

SFC may report that it found no integrity violations, repaired corrupted files, or found files it could not repair. Restart Windows after the scan, even if the result appears successful.

Test the result

After restarting:

1. Open the application that produced the error.
2. Repeat the action that previously failed.
3. Check whether the missing or load error returns.
4. If multiple programs were affected, test more than one.

If SFC repaired files and the application now starts, no manual DLL replacement is needed.

If SFC says it could not repair some files, run DISM again if necessary, review the result, and check the CBS log rather than downloading individual files. Repeated repair failures can point to update damage, disk errors, malware, or a Windows installation that needs recovery.

The manual process requires waiting through several scans and interpreting results that can be difficult to connect to one particular file. Outbyte PC Repair can scan for the underlying system problems and show what it found; its repair actions require the full version, and it is optional rather than required for repairing authz.dll.

Fix 3: Use a matching Windows repair source if DISM cannot repair

DISM normally obtains repair files through Windows servicing. If those files are unavailable or damaged, Microsoft supports using a matching Windows installation source with /Source and, when appropriate, /LimitAccess.

This is more advanced because the source must match the installed Windows edition, language, architecture, and build closely enough for servicing. An arbitrary ISO or another computer’s files can make the situation worse.

The general form is:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:<repair-source> /LimitAccess

The exact source path depends on the installation media and the image inside it. Do not guess the image or point DISM at a random folder. Use Microsoft’s SFC and DISM source repair guidance to identify the appropriate source for your installation.

After DISM completes successfully, run:

sfc /scannow

Restart and test again. If the source does not match, stop using it and move to Windows recovery or repair installation rather than forcing files into place.

Fix 4: Check Windows Security Protection History

Windows Security may quarantine a file after detecting a threat or a suspected false positive. This is a possible cause, but an authz.dll error is not proof of malware.

To inspect the history:

1. Open Start.
2. Type Windows Security.
3. Open the application.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent detections and actions.
7. Expand an item to see its path and status.

If Windows Security identifies a file from an unexpected application folder, do not restore it automatically. Leave it quarantined, update your security definitions, run a full scan, and repair the application or Windows component from an official source.

Only consider restoring a quarantined file when you can establish that it is a genuine Windows file and the detection is a false positive. In most cases, repairing Windows with DISM and SFC is safer than restoring a questionable copy.

Run a full scan:

1. Open Windows Security.
2. Select Virus & threat protection.
3. Select Scan options.
4. Choose Full scan.
5. Select Scan now.

If repairs repeatedly revert, or if other files disappear, back up important data and investigate malware and storage health before continuing.

Fix 5: Repair or reinstall the affected application

If only one application reports the error, Windows may be healthy and the application may be damaged.

Repair a Windows application

On Windows 11:

1. Open Start.
2. Select Settings.
3. Select Apps.
4. Select Installed apps.
5. Find the affected application.
6. Select the three-dot menu beside it.
7. Select Advanced options.
8. Select Repair.
9. Start the application again.

The Repair option attempts to correct the installation without removing its data. If it does not work, the same page may provide Reset, which can remove application data, or you can uninstall and reinstall the program.

For a traditional desktop program:

1. Open Control Panel.
2. Select Programs.
3. Select Programs and Features.
4. Select the affected program.
5. Look for Repair or Change.
6. Follow the installer instructions.
7. Restart if requested.

For games and launchers, use the launcher’s Verify, Verify integrity, Repair, or equivalent command before reinstalling. If the program has a vendor-provided repair utility, use that utility rather than replacing authz.dll in its folder.

If reinstalling the application fixes the problem, the original installation was likely damaged or incomplete. If the same error appears in several applications, return to Windows component repair instead of reinstalling programs individually.

Fix 6: Check architecture and loading problems

A 32-bit application and a 64-bit application do not always use the same system view. On 64-bit Windows, both 64-bit and 32-bit system components may be present, with WOW64 redirecting 32-bit applications appropriately.

Do not copy a 64-bit file into a 32-bit application directory or a 32-bit file into a 64-bit system directory. A file with the right name can still be the wrong architecture or Windows build.

A “Bad Image” or “not designed to run on Windows” message commonly points to corruption, an invalid binary, or an architecture mismatch. It does not prove that downloading another copy will help.

Windows also searches for DLL dependencies according to defined loading rules. A message saying that a module was not found can mean that a dependency could not be loaded, not necessarily that the named file is absent. Microsoft documents this behavior in its DLL search order guidance.

The safe response is to repair the originating Windows component or application. Avoid moving DLLs between folders to change which copy loads.

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

Fix 7: Update or reinstall a related driver only when symptoms support it

A driver is not the normal source of a missing Windows authz.dll, but a failed update, damaged system integration, or broader Windows instability can make driver-related troubleshooting relevant. Do not replace a driver merely because the error mentions a DLL.

Check Device Manager for visible hardware problems:

1. Right-click Start.
2. Select Device Manager.
3. Expand categories related to the application, such as Display adapters, Network adapters, or Sound, video and game controllers.
4. Look for a yellow warning icon.
5. Right-click the affected device.
6. Select Properties.
7. Review the General tab and Device status.
8. Select the Driver tab.
9. Use Update Driver only when an update is appropriate and comes from Windows or the hardware manufacturer.
10. Restart Windows after a driver change.

If the problem started immediately after a driver update, use Roll Back Driver when that button is available. If the driver installation is clearly damaged, uninstalling the device and restarting can allow Windows to reinstall it, but follow the hardware manufacturer’s instructions for specialized devices.

Manually checking hardware sites and comparing driver versions can take time, especially when several devices are involved. Outbyte Driver Updater can scan and identify outdated drivers; installation through its full version is optional, and a driver tool is not a substitute for DISM, SFC, or repairing the application that actually fails.

Fix 8: Do not use Windows Features or regsvr32 for this file

Windows Features can enable or disable optional Windows components, but enabling a random feature will not restore a damaged authz.dll. Do not use Turn Windows features on or off as a general DLL repair method.

Likewise, do not run:

regsvr32 authz.dll

regsvr32 is intended for DLLs that expose registration entry points such as DllRegisterServer. authz.dll is an authorization API and runtime system DLL, not a normal self-registering COM component. Microsoft describes the command’s registration behavior in its regsvr32 documentation, but it does not identify Authz.dll as a registration target.

Running the command may produce an error and does not repair the Windows component store.

Fix 9: Use System Restore or Windows recovery

If the issue began after installing software, a driver, or an update, System Restore may return system files and settings to an earlier restore point.

1. Open Start.
2. Type Create a restore point.
3. Open the matching result.
4. Select System Restore.
5. Select Next.
6. Choose a restore point from before the problem began.
7. Select Next, then Finish.
8. Allow Windows to restart.

System Restore does not normally remove personal files, but it can remove programs, drivers, and updates installed after the selected restore point. Microsoft explains the process in its System Restore guidance.

If DISM and SFC fail, Windows Update remains broken, or system files keep becoming damaged, use Microsoft’s Windows recovery options. Depending on the Windows version and available options, you may be able to reinstall Windows through Windows Update while preserving apps, files, and settings. Installation media is a more disruptive fallback and should be approached only after backing up important data.

Why downloading authz.dll is unsafe

Do not obtain authz.dll from an isolated DLL download site or copy it from another PC.

That approach can fail because:

• The file may belong to a different Windows build.
• The file may be the wrong 32-bit or 64-bit architecture.
• The file may not match your servicing level or language.
• The download may be modified or malicious.
• The real problem may be a missing dependency or damaged component store.
• Replacing one file can hide a broader Windows or storage problem.

Safe sources are Windows servicing, Windows Update, matching Microsoft installation media, System Restore, and the original application vendor when only that application is affected. A standalone current Microsoft download for replacing authz.dll is not the recommended repair path.

FAQ

Is authz.dll a legitimate Microsoft file?

Yes. authz.dll is the Microsoft Windows Authorization Framework DLL and supports the Windows AuthZ authorization API.

Is authz.dll part of Windows?

Yes. It ships as a Windows component. It is not supplied by Visual C++, DirectX, or .NET.

Where is authz.dll on Windows 11 and Windows 10?

The native system copy is normally in System32. On 64-bit Windows, 32-bit applications normally use the 32-bit system view through SysWOW64. The exact result depends on architecture and Windows servicing state.

Should I download a replacement copy?

No. Repair Windows with DISM and SFC, use Windows Update or matching installation media, or repair the affected application. Random replacement files can be unsafe or incompatible.

Should I reinstall Visual C++ or DirectX?

Not as a direct fix for a missing Windows authz.dll. Those packages contain different runtime files.

Does regsvr32 authz.dll fix the problem?

No. authz.dll is not a normal self-registering COM DLL, so registration is not the correct repair.

Why does only one game or program show the error?

That program may have a damaged installation, an incompatible update, or a failed dependency. Use its repair or file-verification function, then reinstall it from the original vendor if necessary.

What if DISM and SFC do not fix it?

Check Windows Update, Protection History, storage health, and recent restore points. If repairs continue to fail, use System Restore or supported Windows recovery options rather than copying the DLL manually.

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.