thanks for taking the time to create a howto.
but please consider that:
--allow-non-empty does nothing on windows.
as per the documentation --allow-non-empty Allow mounting over a non-empty directory (not Windows).
--allow-other does nothing on windows. i know this from testing myself.
--cache-db-purge is for a cache backend, not for a mount, and which really should not be used unless there is a specific reason to do so
shell:startup have you tested this?
as i understand it, that will run a batch file, if and only if a user has logged on, not at system startup.
so what about command line only versions of windows servers, which often a user does not login at system startup such as windows server nano and the windows server hyper-v edition, which has no shells, no gui, no system tray to run RBTray, no desktop, no icons, no windows explorer, no control panel and so on.
that is why, on micro$oft windows, the best way to run a process as system startup is task scheduler or perhaps nssm.
as per task scheduler, there is a difference between run a batch file as
after a user log in manually
perhaps you can tweak your settings and turn it into a wiki,
i have created several wikis such as
The shell:startup command works, the only reason for it is because I couldn't even get to install nssm. And couldn't get Task Scheduler to open cmd and also enter a command.
I posted what worked for me but it looks like it a very cheap no-no way to do it. I basically copy pasted from anywhere until it worked for me with no knowledge.