Well, now you know why it is a terrible idea to store critically important startup-time configuration files (for any app) on a network drive that may or may not exist.
If you want to continue down this path despite the lessons you've learned, then your simplest option is to just not run Rainmeter at startup. Instead, run it when the network drive becomes available.
For example, create a scheduled task that runs a PS or CMD script on startup that tests for the path being available, and when it is, it runs the app. There is a simple PowerShell command-let named Test-Path you could use. You could also use task scheduler to test for the event of the drive getting mapped and fire it then.
Statistics: Posted by SilverAzide — Yesterday, 3:57 pm