-
-
Notifications
You must be signed in to change notification settings - Fork 157
Description
TL;DR
Allow users to set a configurable delay (in ms) before selected mods load at boot or login, to avoid issues where mods fail to initialize properly if started too early.
Hi!
First of all, love Windhawk so much with how much it has helped me make my Windows installs feel like my own.
Now here is the:
Feature request
Add the ability for users to configure a delay (in milliseconds) before a selected mod starts after boot or login.
Examples:
- Start Mod1 5000ms after login
- Start Mod7 10000ms after boot
(It might make sense to include this setting in each mod’s “Advanced” tab, so users can configure different delays per mod — just an idea for where it could fit.)
Why this is needed
Some mods fail to load correctly when Windows starts, especially on slower PCs or when many programs run at startup. This can cause mods to be loaded in the background but not visible or usable by the user until they are manually reloaded.
Example: Internet Status Indicator often fails to appear in the tray if loaded too early, but works fine after reloading.
(!!! There is nothing wrong with the mod itself !!!)
A configurable startup delay could solve this issue for current and future mods.
Current workarounds
The only working fixes I've found for these issues is either:
- Manually disable and re-enable the mod after each reboot. (possibly even user log outs, unsure however)
- The user reduces their amount of startup programs
- The user gets a faster computer that can handle it
- Delay when it starts [Which is also what this issue is requesting as a fix] (tested this with other programs that have the same issue (that aren't Windhawk mods) thru task scheduler with success)
If there is any more info that is needed (or if I posted this in a wrong way/place) then please notify me. I am although slow to respond, so please be patient if I am!