Forum Widgets
Latest Discussions
MCC Install Failure - Code 13631746
WSL_Mcc_Install_FromRegisteredTask log doesn't contain any useful information as to the failure unfortunately. ======================= Starting aziot-tpmd.socket...Started! Starting aziot-edged.service...Started! Done. Successfully applied configurations Successfully completed MCC device registration Starting cron job to update host every 4 hours Successfully added cron job to update host every 4 hours You have successfully deployed your server and cache node installation process will begin. It could take up to 30 minutes for the cache node software to download and begin caching. [08/15/2025 12:11:15] MCC install has completed within WSL Ubuntu distro [08/15/2025 12:11:15] Validating MCC install to ensure it has completed successfully [08/15/2025 12:11:15] Retrieved MCC install log, and it is not null or empty [08/15/2025 12:11:15] Validating that there are no common errors being reported in the install logs [08/15/2025 12:11:15] Failure: MCC failed to install during deployment, please check install from registered task install logs to diagnose issue and retry, Return Code: 13631746 [08/15/2025 12:11:15] System.Management.Automation.RuntimeException: Failure: MCC failed to install during deployment, please check install from registered task install logs to diagnose issue and retry, Return Code: 13631746 [08/15/2025 12:11:15] [2025-08-15] [12:11:15 PM] [08/15/2025 12:11:15] WSL MCC install failed (ReturnCode: 13631746) [08/15/2025 12:11:15] [2025-08-15] [12:11:15 PM] [08/15/2025 12:11:15] Installer return code D00102
Air-Gap System Deployment
Everything I've read indicated that MCC must be deployed on an Internet connected system. However, Microsoft Copolite said it can be deployed on an air-gap (i.e. closed, non-Internet facing) system and to use the pre-seeding tool to download contents. My main interest is to use MCC to assist with future Windows OS upgrade and (secondary) patching on my closed network. I currently pull-down patches via a connected WSUS and then sneakernet them over to the WSUS servers on our closed networks. Has anyone successfully deployed MCC in an air-gap environment and operating as intended? Any lessons learned? Thanks in advance.
Waiting for MCC container to become available
Hi, Trying to setup Intune Connected Cache and getting stuck on MCC Install Waiting for MCC container to become available. running on Server 2022 VM with nested virtulization turned on and using a groupMSA account. I have set this up fine on one of our other domains\tenancy. Any ideas? Tried starting from scratch several times and not sure whats stopping it. Thanks ScottCache server hostname source & LocalPolicyMerge setting
hi In our organization we have the LocalPolicyMerge setting set to false thus blocking all standard or custom locally created inbound MDE firewall rule. Outbound does not have any such restriction. We do see that the clients does not receive OptionID235 value from DHCP server. We did see a note in the Microsoft documentation [Delivery Optimization reference] been called out for this, but with less information on what is the configuration or setting that gets blocked. If the LocalPolicyMerge setting is configured, such as part of security baselines, it can impact DHCP client and prevent it from retrieving this DHCP option, especially in Autopilot scenarios. Does anyone have the same issue and what are the rules that were created to have this working? Thank you.MCC Phantom Install
Installing on Windows 2022. WSL and WSL kernel are fully updated. MCC claims it installed successfully, but there is no distro installed. wsl --list says none exist. The wslip.txt file just shows: System.Object[] COMPLETED Starting MCC installation from scheduled task [07/30/2025 17:03:04] Verifying VHDX file exists and is accessible: c:\mccwsl02\Ubuntu-24.04-Mcc-Converted.vhdx [07/30/2025 17:03:04] VHDX file verified: Size 132074438656 bytes, accessible for import [07/30/2025 17:03:04] Importing MCC Ubuntu image from c:\mccwsl02\Ubuntu-24.04-Mcc-Converted.vhdx to WSL [07/30/2025 17:03:04] Completed imported MCC Ubuntu image from c:\mccwsl02\Ubuntu-24.04-Mcc-Converted.vhdx to WSL [07/30/2025 17:03:04] Validating that import was successful [07/30/2025 17:03:17] WSL Ubuntu Image detected running on IP : System.Object[], configuring port proxy [07/30/2025 17:03:18] Completed configuration of port forwarding [07/30/2025 17:03:18] Setting WslMccUbuntuEthZeroIp [07/30/2025 17:03:18] Successfully validated that WSL Imported MCC Ubuntu Image, WSLStatusText : Installed [07/30/2025 17:03:19] Creating cache folder locations within Ubuntu image [07/30/2025 17:03:19] Successfully completed creating cache folder locations within Ubuntu image [07/30/2025 17:03:19] Running MCC install command line within WSL Ubuntu distro... [07/30/2025 17:04:28] MCC install command line has completed within WSL Ubuntu distro [07/30/2025 17:04:28] Validating MCC install to ensure it has completed successfully [07/30/2025 17:04:28] Successfully verified that MCC has been installed on Ubuntu WSL instance [07/30/2025 17:04:30] Waiting for MCC container to become available... [07/30/2025 17:04:35] Waiting for MCC container to be downloaded (could take up to 30 minutes)... [07/30/2025 17:06:15] Jul 30 17:05:11 ***Removed for Privacy*** aziot-edged[4186]: 2025-07-30T21:05:11Z [INFO] - Pulling image via tag msconnectedcacheprod1.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:2.0.0.2112_e... [07/30/2025 17:06:15] Jul 30 17:06:14 ***Removed for Privacy*** aziot-edged[4186]: 2025-07-30T21:06:14Z [INFO] - Successfully pulled image msconnectedcacheprod1.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:2.0.0.2112_e [07/30/2025 17:06:20] MCC container detected as running, waiting for MCC to return ready status code [07/30/2025 17:06:34] Successfully validated MCC install, returned 200 for content request [07/30/2025 17:06:34] Setting LastCompletedInstallStepw2 [07/30/2025 17:06:34] MCC Install Task has returned success [07/30/2025 17:06:34] Final validation, ensuring that MCC is up and responding to requests [07/30/2025 17:06:34] Checking for netsh interface portproxy forwarding rules [07/30/2025 17:06:34] Successfully verified that MCC public port :80 has been forwarded to WSL [07/30/2025 17:06:34] Verifying symlink created: Ubuntu-24.04-Mcc [07/30/2025 17:06:34] Current execution context - User: ***Removed for Privacy***, Path: C:\Program Files\WindowsApps\Microsoft.DeliveryOptimization_1.0.24.0_neutral__8wekyb3d8bbwe\deliveryoptimization-cli [07/30/2025 17:06:34] MCC Runtime Account: ***Removed for Privacy*** [07/30/2025 17:06:34] Validating WSL distribution using gMSA account [07/30/2025 17:06:34] Current execution context - User: ***Removed for Privacy*** [07/30/2025 17:06:34] Checking for WSL distribution: Ubuntu-24.04-Mcc as runtime account: ***Removed for Privacy*** [07/30/2025 17:06:34] Created temporary task directory: c:\mccwsl02\TempWslCheck_a0d047e2-1dc9-45ce-be9b-a145ecbb5f3d [07/30/2025 17:06:34] Starting WSL distribution check task 'WSLDistroCheck_1654293464' [07/30/2025 17:06:35] Waiting for WSL distribution check task 'WSLDistroCheck_1654293464' to complete (max 30 seconds)... [07/30/2025 17:06:37] Task 'WSLDistroCheck_1654293464' finished. State: Ready, LastResult: [07/30/2025 17:06:37] Reading WSL distribution check result from file: c:\mccwsl02\TempWslCheck_a0d047e2-1dc9-45ce-be9b-a145ecbb5f3d\wsl_distro_check_result.txt [07/30/2025 17:06:37] Check result: U b u n t u - 2 4 . 0 4 - M c c - B a s e U b u n t u - 2 4 . 0 4 - M c c [07/30/2025 17:06:37] WSL distribution 'Ubuntu-24.04-Mcc' found for runtime account: ***Removed for Privacy*** [07/30/2025 17:06:37] Setting up certificate directories and WSL symlinks for gMSA account via scheduled task approach [07/30/2025 17:06:37] Creating Certificates directory: c:\mccwsl02\Certificates [07/30/2025 17:06:37] Certificates directory created successfully [07/30/2025 17:06:37] Creating certs subdirectory: c:\mccwsl02\Certificates\certs [07/30/2025 17:06:37] Certs subdirectory created successfully [07/30/2025 17:06:37] Creating logs subdirectory: c:\mccwsl02\Certificates\logs [07/30/2025 17:06:37] Logs subdirectory created successfully [07/30/2025 17:06:37] Creating WSL symlinks and config using scheduled task approach for gMSA account [07/30/2025 17:06:37] Registering WSL symlink setup task 'WSLSymlinkSetup_1872124169' using gMSA account for ***Removed for Privacy*** [07/30/2025 17:06:37] Starting WSL symlink setup task 'WSLSymlinkSetup_1872124169' [07/30/2025 17:06:37] Waiting for WSL symlink setup task 'WSLSymlinkSetup_1872124169' to complete (max 45 seconds)... [07/30/2025 17:06:43] Task 'WSLSymlinkSetup_1872124169' finished. State: Ready, LastResult: [07/30/2025 17:06:43] WSL Setup Results: Directory setup: Symlink creation: Subdirectories: Config file: Symlink verification: lrwxrwxrwx 1 root root 28 Jul 30 17:06 windowsCerts -> /mnt/c/mccwsl02/Certificates Config verification: Config file exists SUCCESS: WSL setup completed Directory setup: Symlink creation: Subdirectories: Config file: Symlink verification: lrwxrwxrwx 1 root root 28 Jul 30 17:06 windowsCerts -> /mnt/c/mccwsl02/Certificates Config verification: Config file exists SUCCESS: WSL setup completed [07/30/2025 17:06:43] WSL symlink and config creation completed successfully via scheduled task [07/30/2025 17:06:43] Successfully created WSL symlink for gMSA account using scheduled task approach [07/30/2025 17:06:43] Successfully created config file for gMSA account using scheduled task approach [07/30/2025 17:06:43] Cleaning up temporary task directory: c:\mccwsl02\TempWslCheck_a0d047e2-1dc9-45ce-be9b-a145ecbb5f3d [07/30/2025 17:06:43] ============================================================== [07/30/2025 17:06:43] TLS INFRASTRUCTURE SETUP RESULT DETAILS: [07/30/2025 17:06:43] ============================================================== [07/30/2025 17:06:43] WSLDistroFound: True [07/30/2025 17:06:43] CertificatesDirectoryCreated: True [07/30/2025 17:06:43] WSLSymlinkCreated: True [07/30/2025 17:06:43] ConfigFileCreated: True [07/30/2025 17:06:43] HasLocalAccountCredential: False [07/30/2025 17:06:43] ErrorMessage: [07/30/2025 17:06:43] ErrorDetails: None [07/30/2025 17:06:43] SUCCESS CALCULATION BREAKDOWN: [07/30/2025 17:06:44] [07/30/2025 17:06:44] Has Local Credentials = False [07/30/2025 17:06:44] WSLDistroFound = True [07/30/2025 17:06:44] CertificatesDirectoryCreated = True [07/30/2025 17:06:44] WSLSymlinkCreated = True [07/30/2025 17:06:44] ConfigFileCreated = True [07/30/2025 17:06:44] FINAL SUCCESS RESULT: True [07/30/2025 17:06:44] ============================================================== [07/30/2025 17:06:44] [07/30/2025 17:06:44] TLS infrastructure setup completed successfully [07/30/2025 17:06:44] [07/30/2025 17:06:44] Successfully received response from MCC content server, status description: OK, System.Net.HttpWebRequest.URL, System.Net.HttpWebRequest.StatusCode [07/30/2025 17:06:44] Successfully verified MCC is installed, running and responding to requests! [07/30/2025 17:06:44] Setting LastCompletedInstallStep [07/30/2025 17:06:44] Setting InvocationExitCode [07/30/2025 17:06:44] Unregistered base Ubuntu image version: Ubuntu-24.04-Mcc after successful install of MCC [07/30/2025 17:06:44] Setting InvocationEndTime [07/30/2025 17:06:44] Setting InvocationState [07/30/2025 17:06:44] Installer return code 0 ********************** Windows PowerShell transcript end End time: 20250730170644 **********************
Stuck on "MCC container detected as running, waiting for MCC to return ready status code"
Hi all, We’ve followed Microsoft’s guide to set up Microsoft Connected Cache, but we’re hitting a roadblock. When attempting to deploy the cache node, the process gets stuck at the following message: "MCC container detected as running, waiting for MCC to return ready status code" It doesn’t move past this point. We haven’t been able to find any clear documentation or community guidance on what this specific status means or how to troubleshoot it. Has anyone else run into this issue, and if so, how did you resolve it? Thanks in advance for any help,generateCsr.sh failing
Hi, I'm trying to run ./generateCsr.sh to generate a CSR, but it is failing with the following errors: [2025-08-18 09:27:23] [GENERATE-CSR-BASH-SCRIPT] - Executing docker command: docker exec MCC bash -lc "source /tls/call-csr-endpoint.sh 'RSA' '2048' 'srv1_csr_20250818_092719' '<SUBJECT>' '<SAN>'" [2025-08-18 09:27:23] [GENERATE-CSR-BASH-SCRIPT] - bash: /root/.bash_profile: Permission denied <snip> [2025-08-18 09:27:25] [GENERATE-CSR-BASH-SCRIPT] - mkdir: cannot create directory '/keys': Permission denied [2025-08-18 09:27:25] [GENERATE-CSR-BASH-SCRIPT] - chmod: cannot access '/keys': No such file or directory [2025-08-18 09:27:25] [GENERATE-CSR-BASH-SCRIPT] - /tls/call-csr-endpoint.sh: line 159: netstat: command not found [2025-08-18 09:27:25] [GENERATE-CSR-BASH-SCRIPT] - CSR script completed successfully [2025-08-18 09:27:25] [GENERATE-CSR-BASH-SCRIPT] - windowsCerts directory does not exist, CSR generated directly in certs directory [2025-08-18 09:27:25] [GENERATE-CSR-BASH-SCRIPT] - ERROR: CSR file not found at expected location: /var/mcc/certs/certs/srv1_csr_20250818_092719.csr MCC software version 2.0.0.2112_e I've tried both Ubuntu 24.04 and Alma Linux 8. No CSR is generated Any ideas?Win 2025 - MCC Install Failure
WSL_Mcc_Install_Transcript [08/11/2025 14:41:51] Completed configuration of port forwarding [08/11/2025 14:41:51] Setting WslMccUbuntuEthZeroIp [08/11/2025 14:41:51] Creating cache folder locations within Ubuntu image [08/11/2025 14:41:51] Successfully completed creating cache folder locations within Ubuntu image [08/11/2025 14:41:51] Running MCC install command line within WSL Ubuntu distro... [08/11/2025 14:45:27] MCC install command line has completed within WSL Ubuntu distro [08/11/2025 14:45:27] Validating MCC install to ensure it has completed successfully [08/11/2025 14:45:27] Failure: MCC failed to install during deployment, please check install from registered task install logs to diagnose issue and retry, Return Code: 13631746 [08/11/2025 14:45:27] System.Management.Automation.RuntimeException: ScriptHalted [08/11/2025 14:45:27] [2025-08-11] [02:45:27 PM] [08/11/2025 14:45:27] WSL MCC install failed (ReturnCode: 13633026) [08/11/2025 14:45:27] [2025-08-11] [02:45:27 PM] [08/11/2025 14:45:27] Setting InvocationExitCode [08/11/2025 14:45:27] Setting InvocationErrorMessage [08/11/2025 14:45:27] Setting LastCompletedInstallStep Unregistering. [08/11/2025 14:45:28] Unregistered base Ubuntu image version: Ubuntu-24.04-Mcc after successful install of MCC WSL_Mcc_Install_FromRegisteredTask_Transcript [✓] Certificate matches expected thumbprint! Geo certificate verification successful. Fetching Geo response... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 270 100 270 0 0 29 0 0:00:09 0:00:09 --:--:-- 62 Using default MCC KV host. [!] Only 1 cert(s) found. Server may not be sending full chain. MCCKV certificate verification failed. Exiting. [08/11/2025 14:45:26] MCC install has completed within WSL Ubuntu distroMinor Improvement for v2
You might receive the below error during installation System.Management.Automation.RuntimeException: WSL MCC setup requires Hyper-V to be installed on this machine, please install Hyper-V and re-run installation : Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All The suggested fix only applies to Windows 11 installations. Windows server installs require the below command. All of this info is listed in the prerequisites but it might catch some people out. Install-WindowsFeature -Name Hyper-V -IncludeManagementTools
