Fix wevtapi.dll Errors That Prevent Microsoft Office from Opening
Question details
The user needs to resolve a wevtapi.dll error that prevents Microsoft Office applications from launching, including cases where Office repair fails and System File Checker stops at 77%.

- Product
- Microsoft Office and Windows Event Log components
- Device & OS
- Windows; version not provided
- Scenario
- Opening Microsoft Office applications when a Windows system DLL is damaged, inaccessible, or incompatible.
- Observed behavior
- Office applications fail to launch. The reported troubleshooting attempts include unsuccessful Office repairs and System File Checker failing at 77%, even in Safe Mode.
Record the complete error message and any file path it names, and confirm that you can run Command Prompt as an administrator. Close Office applications and connect to the internet before running DISM or installing Windows updates.
Repair Windows components with DISM and System File Checker
Start here because wevtapi.dll belongs to Windows, and repairing Office alone may not resolve damage to this system component.
wevtapi.dll supports Windows Event Log functions. DISM repairs the Windows component store that System File Checker uses to restore protected system files.
Open Start, type Command Prompt, right-click the result, and select Run as administrator. Approve the User Account Control prompt.
Enter DISM /Online /Cleanup-Image /RestoreHealth and press Enter. Wait for the command to finish; progress can pause for some time. If it fails, record the error code rather than assuming the repair succeeded.
After DISM completes successfully, enter sfc /scannow and press Enter. Allow the scan to finish. If SFC previously failed at 77%, check whether repairing the component store allows it to complete.
Restart the computer. Open Settings > Windows Update on Windows 11, or Settings > Update & Security > Windows Update on Windows 10, and select Check for updates. Install available updates, restart when requested, and try opening Office again.
Repair Microsoft Office after checking Windows
Use this if Windows repairs complete but Office applications still fail to open.
Investigate persistent SFC failures and DLL access errors
Use this when SFC repeatedly stops at 77%, DISM fails, or the error indicates that wevtapi.dll cannot be accessed.
Work with Office Documents in WPS Office
WPS Office is a free, lightweight, easy-to-use alternative for working with documents, spreadsheets, and presentations. Its familiar interface and Microsoft Office format compatibility make migration straightforward. It does not repair wevtapi.dll or Windows components, and an unresolved Windows fault may also affect other applications.

Frequently Asked Questions
What is wevtapi.dll, and why can it affect Office?
wevtapi.dll is a Windows system library used for Windows Event Log functions. If Windows cannot load it because it is damaged, inaccessible, or incompatible, applications that depend on those functions may fail. An Office startup error naming this file can therefore indicate a Windows issue rather than an Office installation issue.
What should I do if SFC always fails at 77%?
Open Command Prompt as administrator, run DISM /Online /Cleanup-Image /RestoreHealth, and then retry sfc /scannow after DISM succeeds. If SFC still fails, review %windir%\Logs\CBS\CBS.log and check the system drive. Repeatedly failing at the same percentage is not enough to identify the cause.
Why did Quick Repair and Online Repair not fix the error?
Office repair targets the Office installation; it does not replace every damaged Windows component. If wevtapi.dll or the Windows component store is affected, use DISM, SFC, and Windows Update before trying another Office repair.
Should I download a replacement wevtapi.dll?
No. Avoid third-party DLL download sites and manual replacement of Windows system files. Use an administrator Command Prompt to run DISM and SFC so Windows can restore components through its supported repair mechanisms.
Can WPS Office fix the wevtapi.dll error?
No. WPS Office can serve as an alternative for opening compatible Office files, but it cannot repair a Windows DLL. Resolve the Windows component or access problem first if it also prevents WPS or other applications from running.




