If you don't need network access, you don't actually need to store the Windows password in the Task (I believe Windows assumes that if you have the privileges to create a Task in the first place, you are OK to access local/internal resources). This has the added benefit in corporate environments (etc) - that have password-change policies that force 'new password every X days' - that you don't then have to go and change password in your Scheduled Tasks (because Windows doesn't do that for you...oh, no...)
But if you need network access, you do need to store the password (and update it if you change it - otherwise any such Tasks with embedded passwords would all suddenly start failing to log on if you didn't)
The decision what to use as the default is Microsoft's, and we don't change that default. We'd be damned by some if we did and damned by some if we didn't, and at least this way we can blame MS...
But if you need network access, you do need to store the password (and update it if you change it - otherwise any such Tasks with embedded passwords would all suddenly start failing to log on if you didn't)
The decision what to use as the default is Microsoft's, and we don't change that default. We'd be damned by some if we did and damned by some if we didn't, and at least this way we can blame MS...