Hi, so I bought and upgraded to windows 10 today. All day long, at random intervals, I have a CMD window opening up and closing itself almost instantly with about 6 lines of text.
Unfortunately it happens so fast that I can't catch a glimpse of what it's really doing.
Are there any methods of disabling CMD from being launched(i doubt it but hey) or is there any way to figure out which process is causing this? any log file I can check?
It's incredibly frustrating because it minimizes whatever I'm doing.
SPECS: http://puu.sh/mx5EH/b4349f56f7.png
There was a case of this happening in old insider builds I remember.
I see from your specs you are on build 10240 - perhaps you should go to windows update and upgrade to the latest November build 10586 -perhaps it will go away..
As for checking it you could go to Task Scheduler > Actionand turn on All task history and then have a look in Event viewernext time it happens...
In addition, you can also download: Process Lasso Portable Edition (No installation needed)
Run to monitor all running processes and look in the Actions Log to determine what process invoked the command prompt.
In addition, you can also download: Process Lasso Portable Edition (No installation needed)
Run to monitor all running processes and look in the Actions Log to determine what process invoked the command prompt.
Log Name: Application
Microsoft-Windows-Immersive-Shell
Date: 15/01/2016 23:32:20
Event ID: 5973
Task Category: (5973)
Level: Error
Keywords:
User: DESKTOP-9L7AQU5 hyll
Computer: DESKTOP-9L7AQU5
Description:
Activation of application Microsoft.WindowsPhone_8wekyb3d8bbwe!CompanionApp.App failed with error: The specified module could not be found. See the Microsoft-Windows-TWinUI/Operational log for additional information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Immersive-Shell" Guid="{315A8872-923E-4EA2-9889-33CD4754BF64}" />
<EventID>5973</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>5973</Task>
<Opcode>0</Opcode>
<Keywords>0x2000000000000000</Keywords>
<TimeCreated SystemTime="2016-01-15T23:32:20.586705000Z" />
<EventRecordID>180</EventRecordID>
<Correlation />
<Execution ProcessID="4944" ThreadID="296" />
<Channel>Application</Channel>
<Computer>DESKTOP-9L7AQU5</Computer>
<Security UserID="S-1-5-21-1336496864-2095568290-40566579-1001" />
</System>
<EventData>
<Data Name="AppId">Microsoft.WindowsPhone_8wekyb3d8bbwe!CompanionApp.App</Data>
<Data Name="ErrorCode">-2147024770</Data>
</EventData>
</Event>
This is the event that caused the CMD pop-up I think. Can't be sure but it's the first thing I noticed.
Screenshot:
Edit: I also updated to the latest build
Another follow up
It happened again at 00:30
that is what Process Lasso showed for that time frame.
