Cannot install VS Enterprise from offline package - Error 5003

Question

Cannot install VS Enterprise from offline package - Error 5003

Patrik Perkovic 0

I'm trying to wrap VS2022 Enterprise for the purpose of deployment via Intune as a Win32 app. In my testing, the installer is failing to run offline, with error code 5003.
Layouts have been re-downloaded just in case of corruption etc.

Looking for a workaround or solution!

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

1 answer

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 1

Varsha Dundigalla(INFOSYS LIMITED) 2,700 Microsoft External Staff

Thank you for reaching out.

Error 5003 typically occurs because the Visual Studio offline installer is not fully self-contained. Even when using a layout, the bootstrapper may:

Attempt to connect to the internet to download missing components or updates.
Try to update itself to a newer version that doesn’t match your packaged layout.
Fail if the layout is incomplete (missing workloads, languages, or certificate requirements).

When deploying via Intune as a Win32 app, these attempts fail because the installer cannot access the internet and expects a truly offline setup.

Workaround Suggestions

Run the Installer in True Offline Mode

Use the following switches to prevent the installer from accessing the internet:

--noWeb: Blocks all online access.
--noUpdateInstaller: Prevents the installer from trying to update itself.

These flags ensure the installer relies only on your offline layout.

Verify the Integrity of Your Layout

Before deployment, verify and fix the layout to ensure all packages are present and uncorrupted:

Use --verify to check for missing packages.
Use --fix to repair the layout if needed.

This step reduces the chance of encountering error 5003 due to incomplete downloads.

Include All Required Workloads and Languages

By default, the layout may only contain the core installer. If you don’t explicitly add workloads (e.g., .NET desktop, ASP.NET web development), the installer might attempt to fetch them online later.

Use the --add switch for each workload and language pack you need. You can also use a .vsconfig file to standardize workload selection across environments.

Make the Layout Accessible to Client Machines

Ensure the layout is properly packaged and accessible during deployment. This could mean:

Hosting it on a shared network location.
Including it in the Win32 app package.
Using relative paths or launching the installer from within the layout directory.

This avoids failures due to missing files or incorrect paths.

Test Locally Before Intune Deployment

Simulate the offline install on a test machine without internet access. If it succeeds, you can be confident it will work when deployed via Intune.

Also, check logs (dd_bootstrapper*.log) for detailed error traces if issues persist.

Summary

Error 5003 stems from the installer trying to connect online or encountering missing layout components.
The fix is to force offline mode and ensure your layout is complete and verified.
Always test locally before wrapping into Intune for deployment.

References

Let me know if you need any further help with this. We'll be happy to assist.

If you find this helpful, please mark this as answered.

Patrik Perkovic 0 Reputation points

2025-09-12T03:43:48.87+00:00
Hello,

Please see my findings below:

When running the installer with --noWeb and --noUpdateInstaller, it launches briefly (about one second) and then closes without any error or warning message.

Running --verify followed by --fix does not change the outcome, regardless of whether the endpoint has internet access. Should I expect to see any confirmation that verification or fixing was successful?

I initially created the layout using: --add Microsoft.VisualStudio.Workload.Data --add Microsoft.VisualStudio.Workload.DataScience --includeRecommended

Are these parameters sufficient for the workloads, or is there anything else required that may be missing?

The layout is stored on C:\Temp for testing. Permissions are confirmed as correct, and I have successfully deployed other applications (e.g., Office 365) from this location without issue.

Testing has been performed both in a virtual machine without internet access and on a physical machine with internet access. The result is the same in both environments.

No installation log is being generated in the root install folder that I can see.
Varsha Dundigalla(INFOSYS LIMITED) 2,700 Reputation points Microsoft External Staff

2025-09-12T08:42:21.53+00:00
Thank you for reaching

Could you please review the installation steps again with a few key adjustments? Based on your findings, it seems the layout might be missing some critical components, or the installer is exiting silently due to validation or path issues. Below are refined suggestions that can help resolve Error 5003 and ensure a successful offline deployment of Visual Studio 2022 Enterprise via Intune:

Workaround Suggestions to Resolve Error 5003

Recreate the Layout with Complete Workloads

Your current layout includes Data and DataScience workloads, but Visual Studio also depends on core workloads and shared components.

Why this helps: Adding workloads like Managed Desktop, .NET Core Tools, and CoreEditor, along with --includeRecommended and --includeOptional, ensures all required base components are present. This eliminates silent exits due to missing dependencies.

Verify and Fix the Layout

Even if no confirmation appears, running --verify and --fix silently checks and repairs missing or corrupted files.

Why this helps: A clean, validated layout guarantees that all files are intact before deployment. Without this step, installation can fail early without clear errors.

Use True Offline Parameters

Always run the installer with --noWeb and --noUpdateInstaller.

Why this helps: These flags force the installer to rely solely on the layout files, avoiding failed online checks or bootstrapper mismatches — especially important in Intune deployments.

Check Layout Path and Permissions

Even though permissions are confirmed, consider moving the layout to a simpler path like C:\VSLayout.

Why this helps: This avoids path-length or environment issues that can cause the installer to fail silently.

Enable Logging for Diagnosis

Explicitly enable logging using the --log parameter and check %TEMP% for dd_* log files.

Why this helps: Logs provide visibility into why the installer exits. If issues persist, they’ll help pinpoint whether it’s due to missing components, certificates, or something else.

Install Certificates

Visual Studio layouts include a \Certificates folder. These must be installed on the target machine.

Why this helps: Without these certificates, the installer may silently fail during package validation. Installing them ensures all components are trusted.

Test with a Minimal Workload

Try installing a smaller workload like Managed Desktop first.

Why this helps: If the minimal test succeeds, the issue lies in specific workloads. If it fails the same way, the root cause is likely with the layout or bootstrapper.

Update the Installer When Online

On a machine with internet access, run the installer with --update before retrying offline.

Why this helps: Ensures the bootstrapper matches the layout channel, removing version mismatch as a cause for silent exits.

Helpful References

Here are official Microsoft resources that provide more detail on each step:

Create an Offline Installation of Visual Studio https://free.blessedness.top/en-us/visualstudio/install/create-an-offline-installation-of-visual-studio

Command-Line Parameters for Visual Studio Installer https://free.blessedness.top/en-us/visualstudio/install/use-command-line-parameters-to-install-visual-studio

Export and Use a .vsconfig File https://free.blessedness.top/en-us/visualstudio/install/import-export-installation-configurations

Visual Studio Certificates for Offline Install https://free.blessedness.top/en-us/visualstudio/install/troubleshooting-installation-issues#certificate-issues

Intune Win32 App Deployment Guide https://free.blessedness.top/en-us/mem/intune/apps/apps-win32-app-management

Let me know if you need any further help with this. We'll be happy to assist.

If you find this helpful, please mark this as answered.
Varsha Dundigalla(INFOSYS LIMITED) 2,700 Reputation points Microsoft External Staff

2025-09-17T09:40:43.37+00:00

Hope you're doing well. I wanted to follow up to see if the issue has been resolved or if it’s still ongoing. If my previous response was helpful, you can mark it as answered, as this may assist others as well. We plan to close this thread on 27 September, so please let me know if you have any updates before then.
Varsha Dundigalla(INFOSYS LIMITED) 2,700 Reputation points Microsoft External Staff

2025-09-23T11:33:24.28+00:00

Hope you're doing well. I wanted to follow up to see if the issue has been resolved or if it’s still ongoing. If my previous response was helpful, you can mark it as answered, as this may assist others as well. We plan to close this thread on 27 September, so please let me know if you have any updates before then.
Varsha Dundigalla(INFOSYS LIMITED) 2,700 Reputation points Microsoft External Staff

2025-09-26T11:09:34.3633333+00:00

As we haven’t received any further updates or follow-up on this thread, it has now been closed. If you need additional assistance or have new information to share, please feel free to post a new thread. We’ll be happy to support you further as needed.

Share via

Cannot install VS Enterprise from offline package - Error 5003

1 answer

Your answer