vEthernet (WSL) is not created after the on-logon job execution

[wikiped]

vEthernet (WSL) is not created after the on-logon job execution

[wikiped]

Thanks for reporting this observation.

It is difficult to guess what might be the exact reason for this behavior, but the thing is that if the module reports success - this means the adapter has been set up - because it's presence and actual parameters are validated after the the module tries to set it up.

The only thing I can think of is that adapter is being setup by mangling with Windows internals and I noticed that high level commands like ipconfig do NOT reflect the changes straight away and this delay depends on how busy the system is doing whatever it is doing or whatever the user has tasked it to do at the moment when the adapter was setup. I.e. the system needs some time to sync the changes in virtual devices state with it's internal representation of that state.

The delay you had set might be letting the module to run when the system is less busy and therefore the changes are reflected quicker (which might feel like immediately).

To validate this hypotheses you might try (without setting the delay manually) let the script do its job, and run ipconfig after some time (whatever time you found suitable for the delay).

If the hypotheses holds true I might add an option to have the delay for the scheduled task script (i.e. with -RunOnlyIfIdle and -IdleWaitTimeout parameters).