exit exit

Область применения: Windows Server (половина ежегодного канала), Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012 Applies to: Windows Server (Semi-Annual Channel), Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012

Выход из интерпретатора команд или текущего пакетного скрипта. Exits the command interpreter or the current batch script.

Синтаксис Syntax

Параметры Parameters

Параметр Parameter	Описание Description
/b /b	Выход из текущего пакетного скрипта вместо выхода из Cmd.exe. Exits the current batch script instead of exiting Cmd.exe. Если выполняется из-за пределов пакетного скрипта, выполняет выход из Cmd.exe. If executed from outside a batch script, exits Cmd.exe.
Указывает числовое число. Specifies a numeric number. Если указан параметр /b , переменной среды ERRORLEVEL присваивается это число. If /b is specified, the ERRORLEVEL environment variable is set to that number. Если интерпретатор команд закрывается, код завершения процесса устанавливается в это число. If you are quitting the command interpreter, the process exit code is set to that number.
/? /?	Отображение справки в командной строке. Displays help at the command prompt.

Примеры Examples

Чтобы закрыть интерпретатор команд, введите: To close the command interpreter, type:

Getting «exit status 1: ‘C:\Program’ is not recognized as an internal or external command» when switching versions #168

Comments

lnaie commented May 12, 2016 •

I have installed v1.1.0 in «C:\Program Files\nvm». All good but when I’m trying to switch to a version I have installed I get:

The text was updated successfully, but these errors were encountered:

andrehdias commented May 30, 2016

The problem is with the spaces in URL(C:\Program Files). Try to install the nvm directly in C:/ or in other folder without spaces in the PATH.

lnaie commented Jun 2, 2016

Yes, but that is :)).

coreybutler commented Jun 4, 2016

enaldick commented Mar 23, 2017

windows

move to path there without whitespace

running cmd as administrator
and then mklink it to the new path there without whitespace.

rwadkins commented Jul 14, 2017

One of my users is having the same problem. However, moving nvm to another folder doesn’t work for us, because our security policies don’t allow us to run applications outside of Program Files or Program Files (x86) folders. It would be helpful if the code allowed it to run in a directory with spaces.

AlexYalovoy commented May 16, 2018

Change root directory for version of nodes (without spaces)
Then You can install there node and use it
Example:
nvm root C:\nodejs\nvm
nvm install 10.0.0
nvm use 10.0.0

JoshRosenstein commented Oct 9, 2018

Issue is old but for anyone that lands here you can reinstall nvm as mentioned above,
Or use short path. Changing C:\Program Files\nvm with nvm root C:\PROGRA

1\nvm
Might also want to use shortPath for NVM_SYMLINK : C:\Program Files\nodejs to C:\PROGRA

havettaa commented Dec 12, 2018

You have changed the default path during installation.
I uninstalled nvm, and installed it with default paths, all works fine.

vaishnavravi33 commented Jun 10, 2020

The problem is with the spaces in URL(C:\Program Files). Try to install the nvm directly in C:/ or in other folder without spaces in the PATH.

Yes, That’s work thanks 🙂

ChrisTranzynergy commented Oct 22, 2020

So if I put a space in my name when I got the computer, I’m just screwed forever, huh?

bhupender005 commented Nov 7, 2020 •

a better solution is : #405

Open Cmd, go to the Users directory, type dir /x and you will see the shortened version of the name of the users. (ALEXKA

1 in my case)
Inside the nvm installation (AppData\Roaming\nmv in my case) there is a settings file, edit the first line and instead of having the space name put that shortened version and leave the rest the same like this :
root: C:\Users\ALEXKA

zohar1000 commented Feb 13, 2021

@bhupender005 that’s greate, better than all the other answers, thanks!

VishwasGajawada commented Feb 14, 2021

@bhupender005 Thanks for your neat risk-free solution

valdezm commented Feb 27, 2021 •

If you manually move the nvm folder to for instance to C:\nvm you will need to:

Update the environment variable( NVM_HOME , both user and system ENV variables) so that your terminal recognizes the new location:

Once the environment variables are updated and you restart your terminal/command prompt, nvm should work, but the settings are still attached to the previous location, which will cause an error if you attempt to nvm list or mostly any other command.

Running nvm root will show that old location, all you have to do is set it with nvm root C:\nvm
(given the location you updated it to was C:\nvm , which is the same location you set the environment variable to).

Otherwise you will get errors saying that nvm is referencing the old path.

once that is done your symlink is now corrupt C:\Program Files\nodejs variable NVM_SYMLINK .

You have to manually update the symlink by right-clicking the properties(of the symlink at: C:\Program Files\nodej ) and specifying the location of an executable node, which is where you moved it: C:\nvm\v6.11.3 and select the executable node file.

then restart the terminal/cmd and nvm off and nvm on and it will work, you will see if you issues the nvm list command:

• 6.11.3 (Currently using 64-bit executable)
  (given that 6.11.3 is the version you have)

Save command output on variable and check exit status

The following command will resolve google ip

Sometimes (especially when internet connection is lost) this command fail with this error

When the command fail and i use $# the output is 0 for the assigment

How could i save the output of command in variable, also check if the command succeeded

5 Answers 5

You should use $? instead of $# .

Do something like below :

Edit : In reply to this comment answering the question in title :

Save command output on variable and check exit status

As @chepner pointed out in this comment, an assignment doesn’t meddle with the exit status of command. So :

You can avoid accessing $? , and simply:

Example:

The following function will print «fail» and return 1.

Thus, if we do the following:

We’ll get no output, yet store print_and_fail output to $foo — in this case, «fail».

But, take a look at the following function, which will print «success» and return 0.

Let’s see what happens now:

You can check the return or use command-substitution and check the resulting variable. e.g.

(you can do the reverse check for failure with -z

I recommend against the use of $? as much as possible, as it is fragile and easy to overlook when refactoring. If someone adds a line in between the command and $? , the script will break in non-obvious ways.

If you want to both assign the output to a variable and check the exit code at the same time, you can just do both in your conditional block:

Since you are using Bash, you can use something like the following script which can capture stdout, stderr and the return code https://gist.github.com/jmmitchell/c4369acb8e9ea1f984541f8819c4c87b

For easy reference I have copied the script here:

RebeccaWhit3 / Complete List of Environment Variables in Windows 10.md

Full List of Environment Variables in Windows 10

Information

**Environment variables** are a set of dynamic named values that can affect the way running processes will behave on a computer. The variables can be used both in scripts and on the command line. Environment variables makes it easy when certain standard directories and parameters need to be referenced but where the actual locations or names can vary from computer to computer.

This tutorial will show you a complete list of environment variables that can be used to reference standard directories and parameters in Windows 10.

User environment variables are stored in the registry key below:

System environment variables are stored in the registry key below:

You can open a Command Prompt, type set , and press Enter to display all current environment variables on your PC.

You can open PowerShell, type Get-ChildItem Env: , and press Enter to display all current environment variables on your PC.

Table of Environmental Variables

Environment Variables	Values (may vary)
%ALLUSERSPROFILE%	C:ProgramData
%APPDATA%	C:Users(user-name)AppDataRoaming
%CD%	Current directory full path
%CMDCMDLINE%	Returns exact command line used to start current cmd.exe session.
%CMDEXTVERSION%	Number of current command processor extensions.
%CommonProgramFiles%	C:Program FilesCommon Files
%CommonProgramFiles(x86)%	C:Program Files (x86)Common Files
%CommonProgramW6432%	C:Program FilesCommon Files
%COMPUTERNAME%	BRINK-PC
%COMSPEC%	C:WindowsSystem32cmd.exe
%DATE%	Current date in format determined by Date command
%ERRORLEVEL%	Number defining exit status of previous command or program
%HOMEDRIVE%	C:
%HOMEPATH%	C:Users(user-name)
%LOCALAPPDATA%	C:Users(user-name)AppDataLocal
%LOGONSERVER%	\MicrosoftAccount
%NUMBER_OF_PROCESSORS%	8
%OS%	Windows_NT
%PATH%	C:\WINDOWS C:WINDOWS\system32 C:WINDOWS\System32\Wbem C:\Windows\system32\WindowsPowerShell\v1.0
%PATHEXT%	COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
%PROCESSOR_ARCHITECTURE%	AMD64
%PROCESSOR_IDENTIFIER%	Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
%PROCESSOR_LEVEL%	6
%PROCESSOR_REVISION%	3c03
%ProgramData%	C:ProgramData
%ProgramFiles%	C:Program Files
%ProgramFiles(x86)%	C:Program Files (x86)
%ProgramW6432%	C:Program Files
%PROMPT%	Code for current command prompt format. Code is usually $P$G
%PSModulePath%	C:Windowssystem32WindowsPowerShellv1.0Modules
%PUBLIC%	C:UsersPublic
%RANDOM%	To get random number between 0 and 32767
%SessionName%	When logging on directly to machine, returns «Console». When client connects via terminal server session, is combination of connection name, followed by pound symbol <#>and session number.
%SystemDrive%	C:
%SystemRoot%	C:Windows
%TEMP%	C:Users(user-name)AppDataLocalTemp
%TIME%	Current time in format determined by Time command
%TMP%	C:Users(user-name)AppDataLocalTemp
%USERDOMAIN%	BRINK-PC
%USERDOMAIN_ROAMINGPROFILE%	BRINK-PC
%USERNAME%	(user-name)
%USERPROFILE%	C:Users(user-name)
%WINDIR%	C:Windows

Credits:

Brink Administrator

Exit a for loop in batch

I wan’t to leave the for loop if the count j reaches 0 .

2 Answers 2

Here is your batch code rewritten and commented:

I hope you don’t really need to recursively process files in C:\dsd_imports\ad_and_deal as this would result in processing also the files already processed in subdirectory in_process .

For understanding the used commands and how they work, open a command prompt window, execute there the following commands, and read entirely all help pages displayed for each command very carefully.

Extra information about comparing values with IF

The IF equal operator == results always in a string comparison while operator EQU first always tries an integer comparison and performs also a string comparison if this is not possible as it can be proven with:

The output on execution is:

In the batch code above the double quotes around the arguments !FileCount! and 0 can be safely removed which is not always the case, but here it is.

I added the double quotes to make it clear for everybody that strings are compared because the double quotes of both arguments are compared as well.

The == operator of IF could be coded in C for example with this code:

So the difference on using «!FileCount!» == «0» versus !FileCount! == 0 is that strcmp has to compare 4 versus 2 bytes including the terminating null byte. This does not make a real difference as it could be proven by modifying the code above and run strcmp for example 100.000.000 times in a loop and measure the execution time for this again and again done compare in caches of the core/processor.

The usage of SETLOCAL and ENDLOCAL within the FOR loop and not outside makes a difference in time required for batch file execution completion because of all the operations done by those two commands as described in bottom half of this answer.

So faster would be definitely:

But this faster batch code does not work if any file found by FOR contains 1 or more exclamation marks. The reason is that first ! in a file name is interpreted as begin of a delayed environment variable reference which is removed from file name if there is no second ! which is interpreted as end of delayed environment variable reference and the string between those two ! in file name would be replaced by most likely nothing on expanding %%I before calling the other batch file.

This always unwanted behavior can be seen by running this batch file:

The output of this batch file executed on Windows XP and Windows 7 is:

For completeness the equivalent C code for operator EQU :

It can be already seen here on comparing this C code for demonstrating EQU behavior with the C code above for demonstrating == behavior that an integer comparison caused by using EQU results in more CPU instructions being executed than on doing a string compare with using == operator. On running the application in single step mode also into the standard library functions strcmp and strtol it is even clearer that the processor has to do many more instructions to run an integer comparison in batch file than a string comparison.

This second application written in C demonstrates perfect what happens often unexpected for batch file writers on using numbers with 1 or more leading zeros in batch file on comparing values with EQU or using them in an arithmetic expression, i.e. in string after set /A .

For example compile above code to equ.exe and run following:

The result I get with equ.exe compiled with gpp 4.7.3 (DJGPP package) is:

The first comparison «08» EQU «08» is executed as string comparison because of » in both arguments.

The second comparison 08 EQU 8 is finally also executed as string and not as integer comparison because first argument starts with a leading 0 and is therefore interpreted by function strtol with third parameter base being 0 as octal number which is invalid because of containing the digit 8. Valid octal numbers have only digits in range 0-7. So string to long integer conversion fails and for that reason a string comparison is executed for 08 compared with 8 .

The third comparison 14 EQU 14 is executed as integer comparison with both numbers being interpreted decimal.

The fourth comparison 014 EQU 014 is executed also as integer comparison, but with both numbers being interpreted octal.

The fifth comparison 0x14 EQU 0x14 is executed again as integer comparison, but with both numbers being interpreted hexadecimal explaining twice 20 as output number.

So it is advisable to run always a string comparison of two values in batch files wherever possible with using operator == and without or with using explicitly surrounding double quotes.

It is absolutely useless to measure time differences on == versus EQU using a batch file because the time needed by Windows command interpreter to parse the command lines in batch file before executing the IF condition is many times the amount of time required for the compares itself as demonstrated by the compiled C/C++ code used internally.

Of course this also means using == or EQU does not make a real difference for the user regarding total time needed to accomplish the task done with the batch file. But for other reasons than execution time using == or EQU makes often a difference.