You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As reported by a user (Harry), there is an issue causing the below warning when using the Network Share Reconnecter script:
However I'm pretty sure this is not exclusively related to the script and also for me and on my machines it is definitively not occurring after every reboot. It happens just sporadically. Nonetheless, there is a solution for fixing this issue if you get annoyed by this tray warning. Hence, I created two registry scripts which will hopefully fix the issue. There are two scripts in the below archive. One for fixing the issue and one for restoring back to the original state.
To get this issue closed, there are even more approaches to fix this problem. One way you might prevent this notification message is by increasing the <delay> within the scheduler task file or in the corresponding scheduler task. You need to increase the delay for one or both of the triggers defined for the scheduler task. By default they are set to 15S and 10S. A value of 20S or 30S might give better results.
Finally I want to point on this StackOverflow Thread which contains more infos. That's all I can provide on this issue at the moment. It's at least not fixable within the script.
The text was updated successfully, but these errors were encountered:
As reported by a user (Harry), there is an issue causing the below warning when using the Network Share Reconnecter script:
However I'm pretty sure this is not exclusively related to the script and also for me and on my machines it is definitively not occurring after every reboot. It happens just sporadically. Nonetheless, there is a solution for fixing this issue if you get annoyed by this tray warning. Hence, I created two registry scripts which will hopefully fix the issue. There are two scripts in the below archive. One for fixing the issue and one for restoring back to the original state.
Registry_fix.zip
Explanation Readme
To get this issue closed, there are even more approaches to fix this problem. One way you might prevent this notification message is by increasing the
<delay>
within the scheduler task file or in the corresponding scheduler task. You need to increase the delay for one or both of the triggers defined for the scheduler task. By default they are set to15S
and10S
. A value of20S
or30S
might give better results.Finally I want to point on this StackOverflow Thread which contains more infos. That's all I can provide on this issue at the moment. It's at least not fixable within the script.
The text was updated successfully, but these errors were encountered: