Windows 10: Windows CMD opened application using START - application closes when CMD window closes.

In my environment I cannot do anything until I'm connected to my company's VPN. So, there are several apps that I don't want to start until I'm connected: Outlook, OneDrive and Teams. I created a simple BAT file that I execute after I am connected. I've been using this for years. After some update, Outlook and OneDrive start as usual, but Teams opens and then close.I did some testing and it appears that Teams is staying connected to the CMD window and when it closes, Teams closes. Here's the code: echo Launching Outlook start "" "C:\Program Files x86\Microsoft Office\root\Office16

:)

 

Windows fails to open applications

Hi,

Once I have several applications open Windows XP Professional Service Pack 2 refuses to open further application. I have heavy-weight applications like Delphi and Eclipse open, but the OS has coped with this in the past.

No error messages are reported by the application I am attempting to open, and there are no messages in the event viewer. What is really strange is that once the OS gets itself into this state, it appears that the OS can't allocate enough memory to perform simple API calls. If I go into an application that is already open and try to open the file menu, or right click on the taskbar to open the context menu, nothing happens.

If I close a few applications, then the problem goes away. The Task Manager performance tab indicates that I still have ~1Gb of physical memory available.

I think this could be caused by:

- A memory module is damaged. My memory is comprised of 1x1Gb modules. When the system attempts to allocate memory in the second module, it is unable to. I think this is a bit of a long-shot because I wouldn't expect my PC to boot if a memory module was playing-up

- I've installed something that has put something malicious on my PC. The only things I've installed recently are PRGrep and WinGrep, but unfortunately I didn't make a system restore point, and windows hasn't retained those old restore points. However a full Sophos scan doesn't show-up anything.

Any suggestions on how to diagnose/fix this welcome because I'm baffled as to what is going on.

Thanks,

Frank.

 

2 CMD Screen Open and close after Windows 10 Clean Install

Hello,

Sorry for my english. After clean install windows 10 on my USB and after few PC open(still clean I can't install anything.), just for 1 time I see 2 CMD black and empty screen at startup. It close very fast and I can't see anything. If I create new user,
I see that screens when open new user too. Virus check and nothing. Please help me.

Step by step:

Clear HDD with format c: /fs:NTFS /p:2

Install Windows 10 Home

Installation Complated

Connect WİFİ

Windows 10 Install Automatically Nvidia Driver

Restart PC

Nothing everything normal

Close PC and Open again

Nothing everything normal (sometimes)

Again Close PC and Open again

2 CMD open and close very fast

sometimes this happen after few PC open and close. But I just see this only 1 time. Not every start.

 

[SOLVED] CMD becomes smaller and instantly closes: Can't use CMD

Hello. I've been having trouble using the command prompt recently. Whenever I open it, by any means, it quickly shrinks and closes, without me being able to use it.

I've already tried opening it as administrator, and executing it with the "/k" suffix.

Extra info 1: When I run the Power Shell (admin), and type in "cmd", the Power Shell version of the CMD is shrunk to the same smaller size. However, it doesn't close. So this means, yes, I can run the cmd indirectly through the Power Shell, but that is not
my intention. My intention is to fix the cmd.

Extra info 2: When I change the console dimensions, it only affects the "pre-shrink" dimensions. The shrunk dimensions remain the same, always.

Extra info 3: When I run a c++ console application, it works all right. However, if I use any "system" functions (cls, pause, title, etc...), the console shrinks at the moment of it's execution and the program terminates. This makes me believe the problem is
not with the console, but somewhere both cmd and system functions access... By the way, I noticed the problem for the first time while working with cpp applications, and this is the issue that annoys me the most.

These screenshots illustrate what happens when I try oppening the cmd via normal means, for example:

2: It imediately shrinks to this tiny window. This one lasts for a split second.

3: It quickly closes.

Please, help me fix my cmd. This issue is annoying me a lot and has been rendering useless many of my applications wich rely on the "system".