Skip to content
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

Cmd.exe broken after switching to Legacy Mode (after having installed solarized using Update-Link) #46

Open
timblaktu opened this issue Mar 31, 2020 · 1 comment

Comments

@timblaktu
Copy link

Title says it all. Now I'm having this issue:

https://superuser.com/questions/1444057/cmd-not-working-outside-legacy-mode#

@rbeesley
Copy link
Collaborator

rbeesley commented May 1, 2020

@timblaktu, still this way? Can you provide more details like what version of Windows you're running and the steps you took to get into this state? I'd also be curious if you use ProcExp (SysInternals' Process Explorer) to watch what happens when you launch cmd. Do you see it opening a cmd.exe process? What happens if you use Win+R and run cmd.exe from there? I'm inclined to think this might be external, but I'd need to know more about this state before that is more clear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants