When you have a scheduled task configured with the option "Do not store password. The task will only have access to local resources", each time the task runs, it may leak 4 KB memory (and internally it's 64 KB) in the svchost.exe instance which hosts the Task Scheduler service.
This normally won't be an issue, but if the machine keeps running for long time and the task runs frequently, the leaked memory would become considerable eventually, which may cause the svchost.exe process to be instable.
As that instance of the svchost.exe process also hosts other services like User Profile Service, you may encounter symptoms like logon failure (get the error message "The User Profile Service service failed the logon. No more threads can be created in the system.")
This normally won't be an issue, but if the machine keeps running for long time and the task runs frequently, the leaked memory would become considerable eventually, which may cause the svchost.exe process to be instable.
As that instance of the svchost.exe process also hosts other services like User Profile Service, you may encounter symptoms like logon failure (get the error message "The User Profile Service service failed the logon. No more threads can be created in the system.")