nowadays, many PCs do start from a NVME drive which is lightning fast. Windows 10 tends to start quickly for this reason but most of the network adapters or better their drivers, can't initialize that quickly as it should be. Windows build 1809 did come with a bug, too, that does reinforce this issue further.
As a result, most of my mapped network shares do not work after logon and their icons show a red cross.
Usually a click on those icons/drives will solve this issue, even within Directory Opus. Unfortunately Win10 does report in its notification area about network drives that are unavailable right after logon, but that's a different story.
Why posting this here? I wonder if DO could do this job of "clicking" on those network icons (that I've added to the toolbar)?
I could image that an autorun script, if such function is available at all, would run after starting DO. This script should iterate through all mapped network drives and perform a certain action that forces the OS to access those drives, similar to my manual click.
Don't know which action this should be at them moment, perhaps count all root folder or similar.
Maybe this would solve the issue with red crosses or inaccessible drives.