MongoDB lock file

Hi all,

Not sure if others have come across the issue with the LOCK file in MongoDB, but I have noticed for corrupted cubes with this file that is nested, it won't let me delete the folder even as an Admin.

I found out that I need to manually drill into the file (C:\ProgramData\Sisense\PrismServer\ElastiCubeData\xxxxxxxxx_2017-3-21_6-37-23\dbfarm\xxxxxx), delete the LOCK file, and then I can move or delete the whole folder without having to turn off the Sisense.Repository services. 

Googling around I guess this is what is created when abruptly turning off the MongoDB? Just wondering if other folks have any info. on this.