Forum Discussion
Install failed at Attempting to get task info for MCC Install Scheduled Task
It seems the issue all along was that the account I was using as the MCC account didn't have the Log on as a batch job permission assigned.
Hi,
Thanks for sharing the log snippet — this finally clarifies the failure.
Your scheduled task is created successfully, but it never runs. The key indicators are:
- TaskState: Ready
- LastRunTime: 11/30/1999 (the task never executed)
- LastTaskResult: 267011
Exit code 267011 means the task could not start because the user account used for the task could not be logged on.
This usually happens on Server 2025 when:
✔️ 1. The system was not rebooted after enabling Hyper‑V or WSL
Task Scheduler is present but not fully initialized. A reboot is required before running the MCC installer.
✔️ 2. The scheduled task is created under a local account that cannot log on
Some Server 2025 builds block non‑interactive local accounts from starting scheduled tasks until after a reboot.
✔️ 3. The first run left partial state
Even if the task is deleted, the runtime account may still be in an inconsistent state.
✔️ Recommended steps
- Reboot the server
- Open an elevated PowerShell
- Remove any leftover MCC folders: Remove-Item -Recurse -Force "C:\ProgramData\Microsoft\ConnectedCache"
- Remove any MCC‑related scheduled tasks
- Run the installer again from an elevated session
If the task still doesn’t start, we can check the exact account used by the task and adjust its logon permissions.
Let me know what happens after a clean reboot + reinstall.
It seems the issue all along was that the account I was using as the MCC account didn't have the Log on as a batch job permission assigned.
Hi,
Great — thanks for confirming the root cause. Yes, the “Log on as a batch job” permission is required for the MCC service account, otherwise the scheduled task cannot start.
Glad it’s working now!