#####In this scenario I ran "meteor create" and "meteor" as a regular user. I get silently dumped back to the command prompt. Switching to an admin user WITHOUT removing the lock file and trying to run "meteor" results in the mongo error regarding lock files. I cannot get meteor to run at all using just a regular user. As you can see removing the lock file as a regular user makes no difference.
C:\Users\ciwolsey\Desktop>meteor create test4 test4: created. To run your new app: cd test4 meteor C:\Users\ciwolsey\Desktop>cd test4 C:\Users\ciwolsey\Desktop\test4>meteor [[[[[ C:\Users\ciwolsey\Desktop\test4 ]]]]] => Started proxy. => Started MongoDB. Building the application - C:\Users\ciwolsey\Desktop\test4>del .meteor\local\db\mongod.lock C:\Users\ciwolsey\Desktop\test4>meteor [[[[[ C:\Users\ciwolsey\Desktop\test4 ]]]]] => Started proxy. => Started MongoDB. Building the application / C:\Users\ciwolsey\Desktop\test4>
C:\Users\ciwolsey\Desktop\test4>meteor [[[[[ C:\Users\ciwolsey\Desktop\test4 ]]]]] => Started proxy. Unexpected mongo exit code 100. Restarting. Unexpected mongo exit code 100. Restarting. Unexpected mongo exit code 100. Restarting. Can't start Mongo server. MongoDB had an unspecified uncaught exception. This can be caused by MongoDB being unable to write to a local database. Check that you have permissions to write to .meteor/local. MongoDB does not support filesystems like NFS that do not allow file locking. C:\Users\ciwolsey\Desktop\test4>del .meteor\local\db\mongod.lock C:\Users\ciwolsey\Desktop\test4>meteor [[[[[ C:\Users\ciwolsey\Desktop\test4 ]]]]] => Started proxy. => Started MongoDB. => Started your app. => App running at: http://localhost:3000