Now run any command, the Command Prompt window will stay open as long as you will keep it open. This registry will save to your Registry Editor of Windows. Windows Registry Editor Version ”C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe\” –noExit \ “& \\\ “%1\\\ “C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe\ “ –NoExit \ “-Command\” \”if ( ( Get-ExecutionPolicy ) –ne ‘AllSigned’) & \\\ ”%1” \\\ “\””Īfter saving the file, double click on it. For this, type the following code in your Notepad and save the file with the. You can prevent Command Prompt window from closing after running commands through adding a Registry Key in the Windows Registry. You can easily see each command which had run on the result of bat file in CMD as long as you do not press any key. This will keep the Command Prompt window open until you do not press any key.
Now add “PAUSE” word at the end of your bat file. The second way I am going to show you is also a simple method.Įdit your bat file by right clicking on it and select “Edit” from the list. My last resort would have been to try a system restore using a restore point, but I no longer have a restore point before Friday.This is the very easy and handy way to prevent the Command Prompt window from closing after running commands. The only change I can think of is I installed an update for Acronis TrueImage that same day. A reboot after that made Powershell stop working again. Also there was one time during one of the reboots where Powershell started working, but CMD was still broken. I've noticed that Powershell ISE works though. I'm kinda thinking it's a virus, even though Trend Micro doesn't find anything and neither does the Microsoft Safety Scanner. I've tried an in place upgrade using Media Creation Tool for 20H2, but it didn't help. DISM /online /scanhealth didn't find any issues.
A second scan didn't find anymore issues. SFC /scannow found issues and repaired them, but didn't resolve the issue. I've seen the %comspec% entry as well as a solution, but that wasn't the case for me either. I've checked every registry that was posted, but this isn't the case for me. I've done a lot of research and for most people, it seems their cause was a registry issue with the AutoRun key.
It happens regardless if it's elevated or not. It appears there's no text in the window before it closes. Whenever I try to open one, it closes instantly. It was working just fine earlier that morning though. Randomly last Friday afternoon, I noticed my command prompt and powershell stopped working.
0 kommentar(er)
