The process of installing, configuring, and customizing Visual Studio to support development workflows across languages, platforms, and workloads.
Hi @Dušan Štefanco ,
Thank you for the information you’ve shared. I really appreciate the detail you’ve provided.
First, I want to highlight that you’re approaching this in the right direction. It is true that even when performing an offline installation, Visual Studio still references a channel manifest, which may point to Microsoft’s online feed. The reason you’re seeing this specifically with Visual Studio 2026 is due to its stricter update enforcement logic compared to earlier versions.
To help prevent this behavior, I suggest trying the following steps:
- Go to your layout folder
- Open
response.json - Find
"channelUri": "<some Microsoft URL>" - Change it local channel file (or internal share) Example:
"channelUri": ".\\ChannelManifest.json"Please ensure that the ChannelManifest.json file is sourced from your layout (already generated) and corresponds to your intended frozen version (e.g., 18.6).
I understand that you’ve already tried using the --channeluri parameter. Even so, I’d still suggest verifying the configuration above to ensure it is being applied correctly. If the issue persists after this, the remaining option would be to recreate the layout using the latest available update for Visual Studio 2026.
Add on, trying to use another release version (18.1) of Visual Studio 2026 could be a possible work around as it works in your case. It's a smart move when you decided to think out of the box!
I hope this explanation helps clarify the situation and provides a path forward. If you have any questions or need further assistance, please don’t hesitate to reach out, I’m always happy to help.
Additionally, I would greatly appreciate it if you could take a moment to share your feedback on my support by following this instruction.
Thank you again for your time and collaboration!