So with the move to Windows 11 22H2 and the change to Terminal as the default, there has been some additional changes to CMD. I would like to know what has changed to cause the different behavior in CMD. I have tried to run in Terminal using CMD, I have also started CMD on it own and tried the Legacy mode, all of which has the new behavior in Windows 11.
Below are two examples of the same command being run and the different outcomes.
Old Version: Windows 11 21H2
C:Windowssystem32>SC CONFIG ThisProgram binPath= """"C:Program Files (x86)ThisProgramThisProgram.exe""""
[SC] OpenService FAILED 1060:
The specified service does not exist as an installed service.
New Version: Windows 11 23H2
C:Usersjameson.turner>SC CONFIG ThisProgram binPath= """"C:Program Files (x86)ThisProgramThisProgram.exe""""
DESCRIPTION:
Modifies a service entry in the registry and Service Database.
USAGE:
sc <server> config [service name] <option1> <option2>...
OPTIONS:
NOTE: The option name includes the equal sign.
A space is required between the equal sign and the value.
To remove the dependency, use a single / as dependency value.
type= <own|share|interact|kernel|filesys|rec|adapt|userown|usershare>
start= <boot|system|auto|demand|disabled|delayed-auto>
error= <normal|severe|critical|ignore>
binPath= <BinaryPathName to the .exe file>
group= <LoadOrderGroup>
tag= <yes|no>
depend= <Dependencies(separated by / (forward slash))>
obj= <AccountName|ObjectName>
DisplayName= <display name>
password= <password>
Based on the two examples above I would not expect different outcomes in the same program.
Let me know if any additional details would help. Thanks!
Jameson Turner is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.