![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 78%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
Microsoft Configuration Manager
An integrated solution for for managing large groups of personal computers and servers.
4,540 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 0%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
Brother there could be multiple reasons from which you're facing this error, I have listed some of the common methods that can be used to fix this.
- Increase the Timeout Value
The default timeout is 120 minutes, but if the installation takes longer, you might want to increase this. You can modify the timeout settings in SCCM by doing the following:
- Go to Administration > Client Settings in the SCCM console.
- Right-click your client settings and select Properties.
- Under the Deployment tab, you can increase the "Maximum wait time for deployment" to a higher value (e.g., 240 minutes).
This will allow more time for the process to complete before SCCM gives up.
- Check the Installation Command
Review the command line you're using to deploy VSCode. If it's a custom installation, ensure there are no issues like missing parameters or conflicting flags that might cause it to hang. Typically, the VSCode installer has options for silent installation (/silent or /verysilent), so make sure you are using the correct silent install flags.
Example:
bash
Copy code
VSCodeSetup-x64-<version>.exe /verysilent /norestart
- Check Client Device Logs
Review the client-side log files, specifically:
- AppEnforce.log (Located in
C:\Windows\CCM\Logs\) – It will give you more details about why the installation is failing or taking too long. - execmgr.log – This will tell you about the execution status of the deployment.
Look for any errors or warnings that might indicate what's causing the hang-up.
- Check for System Resource Constraints
If the client device is under heavy load or has limited resources (e.g., CPU, RAM), it might delay the installation process. Check if the device is busy with other processes or if there's not enough available disk space. You can also try deploying to a different client to see if the issue is device-specific.
- Test the Deployment Manually
To verify the issue isn't with the SCCM deployment itself, try manually installing VSCode on a client machine using the same command line you're using in SCCM. This will help you determine whether the issue is specific to the SCCM deployment or with the VSCode installer itself.
- Check Network and Connectivity
Ensure that the client has good network connectivity to the SCCM distribution point, and that there are no network issues that could cause delays or timeout issues during the installation.
- Review the SCCM Package Source
Make sure the VSCode installation files on the SCCM distribution point are not corrupt. If in doubt, re-upload the VSCode setup package to SCCM and re-distribute it to the clients.
- Check for Conflicting Applications or Policies
If there are any other applications, antivirus programs, or GPOs that might interfere with the VSCode installation, they could be causing the installer to hang. Try temporarily disabling antivirus or checking for conflicting software during the installation.
- Recheck the Client Installation Status
Sometimes, SCCM clients might have issues with their own configurations or the installation status can become out of sync. Try restarting the SCCM client service on the affected machine or even reinstalling the SCCM client to ensure everything is working correctly.
