Potential Bitlocker Issue: Aurora mounts external folder, when mount doesn't exist for that path

[AlphaKnightRadiant]

Issue where Aurora Agent Is mounting certain folders that Exist in C:/ for basic windows paths (program files, system32etc) and mounts them as F:/4/Windows

The F drive exists, but no F:/4/ path exists.

This leads to sigma rulesets firing for "unusual folder" when the folder path has been mistakenly set by aurora agent.

Screenshot for context.

Proof path doesn't exist:

[nasbench]

cc @secDre4mer