Unable to mount file/folder backups in Windows Explorer

I am unable to mount file/folder backups in Windows Explorer
I eventually get the error '[drive letter]:\ is not accessible. The parameter is incorrect'
The backup can be seen in Win Explorer and has been assigned a drive letter but if selected it returns the above error
I have the issue with two file backups on two different external drives
Both of the backups are of two different network locations
However, I can mount and browse the two file backups if I boot into Win PE
Broadly speaking I can mount disk images OK (albeit I seem to have to mount from a full image for one particular part which is on the same disk as another part that mounts from an incremental OK else I get the same above error!?)
Firstly, what is the issue here?
Secondly, should I be worried about restoring to a newtork location?
I'm on Win 10 19033.1 & Reflect 7.2.4557
I've reinstalled Reflect and uninstalled QTabBar so far to no avail

Thank you for your reply but it's not quite the same issue in that I van't even browse the directory structure instead getting the error
Consequently, using 'Open with' made no difference
Thing of note is that one file/folder backup is from a QNAP NAS and the other is from a Melco (music server)
The backups were completed over the network on my main PC

I have proved an issue to Everything whereby I am unable to mount file/folder backups in Windows Explorer
I have disabled Everything in startup and now mounting is now OK
It actually appears that the mount is successful but it cannot be seen in Win Explorer if the Everything process is running
If you kill the process then the mount is accessible
Not sure why but I will contact the dev for Voidtools

Maybe this can help: Macrium unable to browse backup

AndreTen said:

Thanks for posting back would be interesting to see Voidtools respond.

Heard back from David at Void Tools (Thanks to David for a quick response)
My guess is Everything is accessing the NTFS volume before it is truely available. This very early access might be causing Macrium to incorrectly mount the volume.
I've added a 3 second delay before accessing NTFS volume which should confirm my suspicion.
I can confirm that nightly build 961 fixes the issue