0xC0000034ApplicationMedium
Error 0xC0000034 — STATUS_OBJECT_NAME_NOT_FOUND | Application Error Fix
Windows 10Windows 11Windows Server 2016Windows Server 2019Windows Server 2022
What Does 0xC0000034 Mean?
Object Name not found. The specified file, device, registry key, or other named object does not exist in the expected location.
Real-World Causes
- 1Required file was deleted, moved, or never installed
- 2Application references a registry key that was removed
- 3Installation was incomplete and missing files
- 4Corrupted Boot Configuration Data (BCD) during boot
Symptoms
- ⚠Application fails to start with missing file messages
- ⚠Windows fails to boot with error 0xC0000034
- ⚠Registry-dependent features stop working
- ⚠Installation or update processes fail
Ad Space – header
DIY Fix
Beginner-friendly steps you can try at home
- 1Reinstall the application that is reporting the error
- 2For boot failures, use Windows Recovery Environment to run 'bootrec /rebuildbcd'
- 3Run 'sfc /scannow' to restore missing system files
- 4Restore the file from a backup or the Recycle Bin
Advanced Fix
For experienced users and IT professionals
- 1For BCD errors: boot from installation media, open Command Prompt, run 'bootrec /fixmbr', 'bootrec /fixboot', 'bootrec /rebuildbcd'
- 2Use Process Monitor to identify exactly which object name is not found
- 3Repair Windows installation with an in-place upgrade using matching installation media
- 4Check disk integrity: chkdsk /f /r
Ad Space – after-fix
Frequently Asked Questions
What if I get this error during Windows boot?
Boot from Windows installation media, select Repair your computer > Troubleshoot > Command Prompt, then run 'bootrec /rebuildbcd'. This rebuilds the Boot Configuration Data that Windows needs to start.
Can System Restore fix this?
Yes, if the file or registry key existed at a previous restore point. Boot into Recovery Environment and use System Restore to revert to a point before the error started occurring.
Related Error Codes
About the Author
Windows Troubleshooting Team
Verified against official Microsoft documentation and real-world diagnostic data. Error behavior confirmed across Windows 10, Windows 11, and Windows Server.