The short version
- 01Confirm the error occurs while starting an Office application on Windows.
- 02Ask the administrator to update Office when the organization manages updates.
- 03For an unmanaged installation, run the documented Office Automatic Updates task.
- 04Use Office's Modify > Online Repair procedure, allowing for repair of the whole suite.
- 05Check Office Software Protection Platform only if the installed Office version provides that service.
- 06Use Microsoft's version-specific reinstall route if the earlier Office remedies fail.
Raw message
0xc0000142 — STATUS_DLL_INIT_FAILED
Likely causes
- DLL initialization fails during application startup.
- Microsoft's Office-specific update, installation or applicable protection-service checks may resolve the startup failure.
Confirm the application before using Office's procedure
Microsoft's NTSTATUS table calls 0xc0000142 STATUS_DLL_INIT_FAILED. The repair route here is its dedicated Office startup article; it is not a universal fix for every app showing the same code. That article names a fix in Office Version 2102 or later. Use current Office updates, or ask the administrator when updates are managed.
Update Office, then use the suite repair
The manual update route opens Task Scheduler > Task Scheduler Library > Microsoft > Office and runs Office Automatic Updates 2.0. If updating fails, choose the Office product in Windows' installed apps and select Modify > Online Repair. Microsoft notes that this repairs the whole suite, even if only Word or Excel failed.
Keep the service check specific to older versions
If Office Software Protection Platform is listed in Services, Microsoft's procedure checks Automatic startup and Running status. Newer Office versions may not have that service; skip that step when absent. Its final route uninstalls and reinstalls the applicable Office version, preserving documents. The linked article states the current uninstall-tool limitations.
Sources and review notes
Checked on . The status meaning is from Microsoft; all repair steps here are scoped to the Office article. Checking the application and distinguishing a historical minimum version from current updates are editorial guidance. Other applications need their publisher's initialization investigation. Glitchary is independent of Microsoft.