title: Mongo Memory Server is not starting at all
body: <p>EDIT (its been a entire day since I asked the question and still no luck on finding an answer on my end)</p>
  <p>EDIT (this mongodb memory server works fine on my ubuntu laptop)</p>
  <p>I am trying to run mongo memory server and am getting a error here is the code</p>
  <pre class="lang-js prettyprint-override"><code>const { MongoMemoryServer } = require(&quot;mongodb-memory-server&quot;);
  const mongoose = require(&quot;mongoose&quot;);
  
  (async () =&gt; {
    const mongod = new MongoMemoryServer();
    const mongoUri = await mongod.getUri();
  
    await mongoose.connect(mongoUri, {
      useNewUrlParser: true,
      useUnifiedTopology: true,
    });
  })();
  </code></pre>
  <p>here is the error from running <code>node --trace-warnings</code> on my file (I also turned debig on for mongo memory server)</p>
  <pre><code>  MongoMS:MongoMemoryServer Called MongoMemoryServer.ensureInstance() method +0ms
    MongoMS:MongoMemoryServer  - no running instance, call `start()` command +1ms
    MongoMS:MongoMemoryServer Called MongoMemoryServer.start() method +0ms
    MongoMS:MongoMemoryServer starting with port 57263, since undefined was locked: 57263 +6ms
    MongoMS:MongoMemoryServer Starting MongoDB instance with following options: {&quot;port&quot;:57263,&quot;dbName&quot;:&quot;cf1c3af6-a5d2-4336-b79b-a96fda68286d&quot;,&quot;ip&quot;:&quot;127.0.0.1&quot;,&quot;storageEngine&quot;:&quot;ephemeralForTest&quot;,&quot;dbPath&quot;:&quot;C:\\Users\\skyle\\AppData\\Local\\Temp\\mongo-mem--10532-zQjLbcla6wmr&quot;,&quot;tmpDir&quot;:{&quot;n,&quot;storageEngine&quot;:&quot;ephemeralForTest&quot;,&quot;dbPath&quot;:&quot;C:\\Users\\skyle\\AppData\\Local\\Temp\\mongo-mem--10532-zQjLbcla6wmr&quot;,&quot;tmpDir&quot;:{&quot;name&quot;:&quot;C:\\Users\\skyle\\Appl\\Temp\\m},&quot;uri&quot;:&quot;mongodb://127.0.0.1:Data\\Local\\Temp\\mongo-mem--10532-zQjLbcla6wmr&quot;},&quot;uri&quot;:&quot;mongodb://127.0.0.1:57263/cf1c3af6-a5d2-4336-b79b-a96fda68286d?&quot;} +2ms
    MongoMS:MongoBinary MongoBinary options: {
    &quot;downloadDir&quot;: &quot;D:\\code\\thing\\node_modules\\.cache\\mongodb-memory-server\\mongodb-binaries&quot;,
    &quot;platform&quot;: &quot;win32&quot;,
    &quot;arch&quot;: &quot;x64&quot;,
    &quot;version&quot;: &quot;4.0.14&quot;,
    &quot;checkMD5&quot;: false
  } +0ms
    MongoMS:MongoBinary MongoBinary: Download lock removed +6ms
    MongoMS:MongoInstance Mongo[57263]: Called MongoInstance._launchKiller(parent: 10532, child: 5804): +0ms
    MongoMS:MongoInstance Mongo[57263]: Mongod instance closed with an non-0 code! +7ms
    MongoMS:MongoInstance Mongo[57263]: CLOSE: 3221225781 +0ms
    MongoMS:MongoInstance Mongo[57263]: MongodbInstance: Instance has failed: Mongod instance closed with code &quot;3221225781&quot; +1ms
  (node:10532) UnhandledPromiseRejectionWarning: Mongod instance closed with code &quot;3221225781&quot;
      at emitUnhandledRejectionWarning (internal/process/promises.js:170:15)
      at processPromiseRejections (internal/process/promises.js:247:11)
      at processTicksAndRejections (internal/process/task_queues.js:96:32)
  (node:10532) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a c                                       hich was not handled with .catch(). To terminate the node process on unhandled promise rejatch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `-atch block, or by rejecting a promise w-unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)                                        -rejection.org/api/cli.html#cli_unhandlxit code.
  (node:10532) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.                                                                                                            e the Node.js process with a non-zero e
      at emitDeprecationWarning (internal/process/promises.js:180:11)
      at processPromiseRejections (internal/process/promises.js:249:13)
      at processTicksAndRejections (internal/process/task_queues.js:96:32)
    MongoMS:MongoInstance Mongo[57263]: [MongoKiller]: exit - [null,&quot;SIGTERM&quot;] +2ms
  </code></pre>
  <p>I have absolutely 0 idea whats going on and have been stuck for quite some time any help would be appreciated,</p>
  <p>OS: Windows 10,
  node version: 14.17.0,
  mongodb-memory-server version: 6.9.6,
  mongoose version: 5.12.11,</p>