MongoDB Community Service Not Starting – Error 1067 After Windows Update

Hello Team,

I’m facing an issue with MongoDB Community Edition on Windows. Below are the details:

  • MongoDB Version: Community Edition 8.0 (installed via .msi)
  • Initial Install Date: 10th May 2025
  • Issue Started: After Windows Update on 16th May 2025
  • Error Message:
    When starting the MongoDB service via services.msc, I receive the following error:
    Error 1067: The process terminated unexpectedly.

:hammer_and_wrench: Troubleshooting Steps Taken:

  • Initially, MongoDB was working fine after installation.

  • After a Windows update on 16th May, MongoDB service stopped working.

  • Tried restarting the service manually → still fails with error 1067.

  • Reinstalled MongoDB → it works temporarily, but eventually stops again.

  • Checked mongod.log, which showed:

{"t":{"$date":"2025-05-19T16:00:54.670+05:30"},"s":"I",  "c":"CONTROL",  "id":31445,   "ctx":"conn147","msg":"Frame","attr":{"frame":{"a":"7FF61BA5244A","module":"mongod.exe","file":".../src/mongo/transport/service_executor_synchronous.cpp","line":154,"s":"`mongo::transport::service_executor_synchronous_detail::ServiceExecutorSyncImpl::SharedState::schedule'::`2'::<lambda_1>::operator()","s+":"CA"}}}
{"t":{"$date":"2025-05-19T16:00:54.670+05:30"},"s":"I",  "c":"CONTROL",  "id":31445,   "ctx":"conn147","msg":"Frame","attr":{"frame":{"a":"7FF61BA511A2","module":"mongod.exe","file":"C:/Program Files/Microsoft Visual Studio/2022.1/VC/Tools/MSVC/14.31.31103/include/thread","line":55,"s":"std::thread::_Invoke<std::tuple<`mongo::stdx::thread::thread<`mongo::transport::launchServiceWorkerThread'::`3'::<lambda_1>,0>'::`1'::<lambda_7_> >,0>","s+":"32"}}}
{"t":{"$date":"2025-05-19T16:00:54.670+05:30"},"s":"I",  "c":"CONTROL",  "id":31445,   "ctx":"conn147","msg":"Frame","attr":{"frame":{"a":"7FF92E7F1BB2","module":"ucrtbase.dll","s":"configthreadlocale","s+":"92"}}}
{"t":{"$date":"2025-05-19T16:00:54.670+05:30"},"s":"I",  "c":"CONTROL",  "id":31445,   "ctx":"conn147","msg":"Frame","attr":{"frame":{"a":"7FF930937374","module":"KERNEL32.DLL","s":"BaseThreadInitThunk","s+":"14"}}}
{"t":{"$date":"2025-05-19T16:00:54.672+05:30"},"s":"I",  "c":"CONTROL",  "id":23131,   "ctx":"conn147","msg":"Failed to open minidump file","attr":{"dumpName":"C:\\Program Files\\MongoDB\\Server\\8.0\\bin\\mongod.2025-05-19T10-30-54.mdmp","error":"Access is denied."}}
{"t":{"$date":"2025-05-19T16:00:54.673+05:30"},"s":"F",  "c":"CONTROL",  "id":23137,   "ctx":"conn147","msg":"*** immediate exit due to unhandled exception"}
  • Yesterday, I resolved the “Access is denied” issue with the minidump path, and MongoDB successfully generated a dump file.
  • On inspecting the dump, I found the exception code: 0xc000001d, which indicates an illegal instruction exception.

Please advise on:

  • How to properly interpret or resolve this exception code
  • If a specific MongoDB build is recommended for my setup

Try installing the mongoDB community server out side the Program Files.
It will work because the Program Files won’t allow to write the log file and data file.

C:\Program Files\... is a bad place for storing application data or log files. In C:\Program Files\... you should store only the Mongo binaries. For all others better create dedicated folders or use folder like c:\ProgramData
Did you use a configuration file for proper setup? The default config which comes with the installation is rather pointless. Personally I don’t see any reason to install MongoDB with .msi setup. You are much more flexible when you unzip the .zip download.

See my repository mongoDB-oneClick to get an idea how it can be done.