1

I have Windows 10 pro insider preview build 11099.

The problem is that cmd.exe doesn't open a window when I start it from the run... It starts a process as I can see in the task manager but I cant see it.

Even when I go to C:\Windows\System32 and click on cmd.exe it is the same.

BUT when I search for cmd in the Windows menu it is working!

A closer look on the Task Manager shows that when I start cmd from the Windows menu it starts a proccess under the Apps section, and from the run it starts a process under the Background processes / Windows processes

How can I fix this?

Oz Bar-Shalom
  • 186
  • Are you sure the cmd window isn't appearing off-screen? See http://superuser.com/questions/53585/how-to-move-windows-that-open-up-offscreen – Ƭᴇcʜιᴇ007 Jan 18 '16 at 19:02
  • Yes I'm sure. This is not what's going on. – Oz Bar-Shalom Jan 18 '16 at 19:05
  • If you roll back to the previous build, does CMD work as expected? That's can be a problem with fast-ring, you're using a beta software package, so you may be hitting bugs that can't be fixed until the next version comes along. Test the previous (or a stable) version, and if it works, then it's a bug in the new version. – Ƭᴇcʜιᴇ007 Jan 18 '16 at 19:27
  • Unfortunately the even happened in the last build before I installed the update – Oz Bar-Shalom Jan 18 '16 at 19:31
  • Check the properties of the CMD link shown in the search window, and try entering that in Run. – DrMoishe Pippik Jan 18 '16 at 20:24
  • The target of the CMD link is %windir%\system32\cmd.exe. even when I put that on the run it does not working... (When I click the link from the menu it works well) – Oz Bar-Shalom Jan 18 '16 at 20:28
  • I'd add /D switch (disable execution of AutoRun commands from registry) and some innocuous command, e.g. %windir%\system32\cmd.exe /D /K ver. – JosefZ Jan 18 '16 at 23:58
  • What happens if you open a cmd prompt (from the menu), then enter start cmd.exe at the prompt? This is essentially (supposed to be) the same as launching cmd.exe from run, and normally it should open a second cmd prompt. – dxiv Jan 19 '16 at 03:55
  • Not it is not the same. As in the question in bold one process is opened under the Apps sections (the cmd that I can see) and from the run it opens a process under the background processes. And starting cmd.exe with the /D /K flags didn't help. – Oz Bar-Shalom Jan 19 '16 at 04:40
  • Entering start cmd.exe from the command prompt didn't work. – Oz Bar-Shalom Jan 19 '16 at 04:49
  • Entering start cmd.exe from the command prompt didn't work. In what way did it not work - was there an error, did a second cmd process get started at all, did it (not) have its own console window, or ...? – dxiv Jan 19 '16 at 05:11
  • It starts a new process under background processes which I can't see its window. No any errors. – Oz Bar-Shalom Jan 19 '16 at 05:17
  • If you ALT-TAB after start cmd.exe, how many cmd consoles do you get in the list - one or two? – dxiv Jan 19 '16 at 05:22
  • Just one console – Oz Bar-Shalom Jan 19 '16 at 05:23
  • One last question... If you enter start notepad.exe at the same cmd prompt where you tried start cmd.exe, does Notepad open normally? – dxiv Jan 19 '16 at 05:26
  • Yes, start nodepad.exe from the command prompt works well and open a notepad window. Not like when I type start cmd.exe – Oz Bar-Shalom Jan 19 '16 at 05:29
  • That's quite odd. I don't have any good guess at this point, but the previous q&a narrowed it down a bit and might help someone with a better crystal ball. – dxiv Jan 19 '16 at 05:34
  • Try downloading Process Explorer. Find cmd.exe in the list, then right click -> Properties -> Bring to Front. Does the window appear? – spherical_dog Jan 19 '16 at 22:49
  • Preview versions are sure to contain bugs. – Moab Jan 19 '16 at 23:14
  • I'm running into the same issue with Windows 10 Build 11099. Process Explorer shows that is a child conhost.exe (a child of CMD.exe) is sitting around using about 20%. What is sad is that DropBox also fires of cmd.exe behind the scenes and it too is getting the same hanging behavior adding another 20% CPU usage. – Ants Jan 22 '16 at 13:56
  • Additional info: conhost.exe that runs behind Powershell.exe does NOT seem to exhibit the hanging behavior. – Ants Jan 22 '16 at 20:08

1 Answers1

0

After many troubleshooting I tried to login with a diffrent user profile, and suddenly the cmd.exe worked from the run.

So I realized there is a problem (a bug maybe) with my currect user profile. I deleted my profile and the problem solved !

Realy hope this will help someone with the same issue.

How to delete user profile on Windows 10:

To remove profile type sysdm.cpl in run and press enter to open System Properties.

When the System Properties opened go to Advanced tab and click Setting in User Profiles section to open it. Next select Account Unknown and hit delete button then hit Yes.

Oz Bar-Shalom
  • 186