Resolving connection issues with Kosmos VM
Written by
Updated at December 17, 2025
Issue description
You cannot connect to a VM created based on a Kosmos VM image.
Solution
Check if the Kosmos VM is pingable from other VM instances within the same cloud network, then try to connect to the SAC console and check the statuses of services.
If the SAC console on the affected VM is unavailable (when trying to connect to it, you see this message: Unable to launch a Command Prompt. The service responsible for launching is not available), follow these steps:
- Create an image of the disk of the problematic VM.
- Attach this image as a secondary disk to another VM based on the Kosmos image.
- Run these commands in your command prompt:
bcdedit /store <mountedvolume>\boot\bcd /ems {default} on
bcdedit /store <mountedvolume>\boot\bcd /emssettings EMSPORT:1 EMSBAUDRATE:115200
Where `<mountedvolume>` is the letter of the secondary disk mounted to another VM booted from the Kosmos image.
- Detach the secondary disk from the VM.
- Create a VM using the modified image as a boot disk.
- Connect to the newly created VM.
If the issue persists
If the above actions did not help, create a support ticket
- ID of the VM.
- The time range during which you tried to connect to the VM.