-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GNS3 client also is open a permanent cmd prompt with shortcut gns3.lnk #3290
Comments
This should have been fixed in v2.2.31 Please comment back if you still have the problem. Thanks 👍 |
Hi @grossmj I've upgraded to 2.2.31 but it has the same behavior remains. Thanks, |
Have you uninstalled GNS3 first before re-installing? |
Hola @mortiz-code Encontraste alguna solución, en mi caso actualicé a Windows 11 22H2 y me salió este "problema". Quedo atento a tus comentarios. Saludos. |
Hola. No, el problema sigue ahi. Nunca se soluciono. |
Having the same issue on windows 11 with v2.2.36 |
Still happening on 2.2.37 on windows 11 |
Hey, I have the same bug on GNS3 v2.2.38 and my OS is also Windows 11 Edit: Running GNS3 as an Administrator makes the cmd go away as soon as it apears. Some of my classmates who also have windows 11 where having the same problem and they also "fixed" it running GNS3 as an Administrator |
Interesting, I'll try it tomorrow and let you know if it works. |
I have looked more into it and this may be because of this issue: microsoft/terminal#12464 |
My last attempt to fix that issue seems to work: 3c8cff2 Please report back if you still get the problem. Thanks. |
You can edit the shortcut to use the legacy Console, on the options tab enable "Use legacy console". |
Hi folks,
Describe the bug
After upgrading to 2.2.29 when I open the GNS3 client also is open a permanent cmd prompt with shortcut gns3.lnk that only goes away with I close GNS3 Client. If I close the cmd the GNS3 client also is closed.
GNS3 version and operating system (please complete the following information):
Screenshots or videos
Version:
CMD:
Additional context
It's a cosmetic problem, GNS3 works well but I don't understand why it started behaving like this.
Thanks!
The text was updated successfully, but these errors were encountered: