Windows 10: System.Diagnostics.Process launches the app in background

Hi,I'm using System.Diagnostics.Process to launch an exe app from within another desktop app. This seems to work fine when running the command from a normal desktop application. However, when I try to run the command from a JavaScript based desktop, it launches the app in the background. I checked that "WindowStyle" is "normal" and that "CreateNoWindow" is "false".Please advise why it launches the app in the background and how to force launching it in the foreground.Thanks,Suhair

:)

 

Windows Mail app background bug

Sorry, not sure what you mean. I was talking about choosing a background through the "Browse" button and then repeating that step again with another background. In that case the Mail app won't apply that 2nd background.

 

Why do Windows 10 foreground apps mysteriously launch as background processes?

Occasionally Task Manager shows that "Store", "Settings", and/or "Calculator" are mysteriously running as background processes.

• There's no corresponding foreground application, just the background processes.
  
• I haven't interactively run either during the current session.
  
• Neither is listed in the "Everything" tab of AutoRuns.
  

As discussed in my answer to this SuperUser question, these two background processes cause a delay in executing Windows shortcut keys. But besides that, it's just plain weird.

Does anyone know why these foreground apps are mysteriously launching themselves as background processes?

And, ideally, how I can prevent it from happening? As discussed elsewhere (SuperUser and Thomas Vanhoutte), I could uninstall the Calculator and Store apps. But it seems like overkill to uninstall them just to defeat a shortcut key delay.

 

Desktop app runs as background process?

Thank you for your reply, Joy.

I tried what you suggested and unfortunately my application isn't listed there. It's not a Windows 10 app, but an older 32-bit application that should run in windowed mode, but for some reason when I double click its icon it starts as a background process
instead of a windowed app. That happens in most of the cases, fortunately, at the end it somehow starts as a desktop app. But I cannot reproduce this behavior.

As a temporary solution, to keep it in windowed mode I never shut the computer down, but instead I leave the application running and put the computer to sleep.

Is there a setting to instruct Windows to run my application as a desktop application and not as a background process? Thank you.

Regards,

A