@zwass Using sysinternal psexec I could start the Osqueryd under system account. Now "Could not initialize Databse" error is no more there. Following is the cmd output..c:\ProgramData\osquery\osqueryd>osqueryd.exe --verbose I0914 164538.033174 11392 init.cpp:402] osquery initialized [version=3.3.0] I0914 164538.135848 11392 system.cpp:366] Found stale process for osqueryd (12 316) I0914 164538.136852 11392 system.cpp:398] Writing osqueryd pid (13816) to \Pro gramData\osquery\osqueryd.pidfile I0914 164538.139935 11392 extensions.cpp:343] Could not autoload extensions: F ailed reading: \ProgramData\osquery\extensions.load I0914 164538.228579 5296 watcher.cpp:583] osqueryd watcher (13816) executing worker (12040) I0914 164538.252595 12660 init.cpp:399] osquery worker initialized [watcher=13 816] I0914 164538.255599 12660 rocksdb.cpp:134] Opening RocksDB handle: \ProgramDat a\osquery\osquery.db I0914 164539.477429 12660 database.cpp:564] Checking database version for migr ation I0914 164539.480234 9584 interface.cpp:265] Extension manager service startin g: \\.\pipe\osquery.em I0914 164539.480234 12660 auto_constructed_tables.cpp:86] Removing stale ATC e ntries I0914 164540.620872 12088 events.cpp:783] Starting event publisher run loop: w indows_events I0914 164540.620872 12660 main.cpp:109] Not starting the distributed query ser vice: Distributed query service not enabled.