Everything incorrectly treating "fake" drive letter mapped to subdirectory

[kauffy]

I recently consolidated what was my `D:` drive onto a huge drive I have called `A:`.
`A:` contains a subdirectory called `\D\`, which is where `D:`'s contents now live.

To keep things from breaking, I mapped `D:\` to that directory. To do the mapping, I added a registry entry mapping the DOS object `D:` to the path `A:\D\`. This works perfectly for nearly all purposes (some operations will still see `\D\` under `A:`, but for everything else, `A:\` contains no `\D\` and `D:\` appears to be its own drive. Perfect.

The problem is that Everything is indexing the content on `A:\` ITSELF as though it were on `D:\` directly.

For example:
`A:\LP-vlt\Glasses.mp4` (a real file at the proper location)
also shows in Everything as
`D:\LP-vlt\Glasses.mp4` (even though LP-vlt is *not* in A:\D\)

I tried using the exclusions for Folders to prevent `A:\D\` from being indexed, but it doesn't look like I can stop it from indexing the volume `D:`

In any case, I would think this is unexpected behavior. Is there a workaround, or potentially a fix on the horizon?

Thanks!

[kauffy]

To add, in case this helps:
If I search for `A:\.*` using regex, it will not return `A:\D\` which is expected/desired.

If I search for something that is only in `A:\`, it returns both the `A:\file.ext` and `D:\file.ext` (and there is no actual `D:\file.ext`).

[void]

Please send your Help -> Troubleshooting information

What is shown under Tools -> Options -> NTFS?