Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, February 3, 2019 9:49 PM
This prompt looking for Script "vsdevcmd\ext\Active" which could not be found.
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.9.6
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
[ERROR:VsDevCmd.bat]Script "vsdevcmd\ext\Active" could not be found.
[ERROR:VsDevCmd.bat] *** VsDevCmd.bat encountered errors. Environment may be incomplete and/or incorrect. ***
[ERROR:VsDevCmd.bat] In an uninitialized command prompt, please 'set VSCMD_DEBUG=[value]' and then re-run
[ERROR:VsDevCmd.bat] vsdevcmd.bat [args] for additional details.
[ERROR:VsDevCmd.bat] Where [value] is:
[ERROR:VsDevCmd.bat] 1 : basic debug logging
[ERROR:VsDevCmd.bat] 2 : detailed debug logging
[ERROR:VsDevCmd.bat] 3 : trace level logging. Redirection of output to a file when using this level is recommended.
[ERROR:VsDevCmd.bat] Example: set VSCMD_DEBUG=3
[ERROR:VsDevCmd.bat] vsdevcmd.bat > vsdevcmd.trace.txt 2>&1
All replies (10)
Sunday, February 3, 2019 6:39 AM
when I open vc2017 command promt or run vcvarsx86_amd64.bat I got an error
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.9.6
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
[ERROR:VsDevCmd.bat] Script "vsdevcmd\ext\Active" could not be found.
[ERROR:VsDevCmd.bat] *** VsDevCmd.bat encountered errors. Environment may be incomplete and/or incorrect. ***
[ERROR:VsDevCmd.bat] In an uninitialized command prompt, please 'set VSCMD_DEBUG=[value]' and then re-run
[ERROR:VsDevCmd.bat] vsdevcmd.bat [args] for additional details.
[ERROR:VsDevCmd.bat] Where [value] is:
[ERROR:VsDevCmd.bat] 1 : basic debug logging
[ERROR:VsDevCmd.bat] 2 : detailed debug logging
[ERROR:VsDevCmd.bat] 3 : trace level logging. Redirection of output to a file when using this level is recommended.
[ERROR:VsDevCmd.bat] Example: set VSCMD_DEBUG=3
[ERROR:VsDevCmd.bat] vsdevcmd.bat > vsdevcmd.trace.txt 2>&1
VS configuration
{
"version": "1.0",
"components": [
"Microsoft.VisualStudio.Workload.NativeDesktop",
"microsoft.visualstudio.component.debugger.justintime",
"microsoft.visualstudio.component.graphics.win81",
"microsoft.visualstudio.component.vc.cmake.project",
"microsoft.visualstudio.component.vc.atl",
"microsoft.visualstudio.component.vc.testadapterforboosttest",
"microsoft.visualstudio.component.vc.testadapterforgoogletest",
"microsoft.component.vc.runtime.ucrtsdk",
"microsoft.visualstudio.component.windows81sdk",
"microsoft.visualstudio.component.vc.140"
]
}
Sunday, February 3, 2019 2:15 PM | 1 vote
Hi Rostyslav Nikitin,
Welcome to the MSDN forum.
Could you tell me the reason of running vcvarsx86_amd64.bat? Did you want to change the environment variables?
Based on your error message, it is caused in not set a value of VSCMD_DEBUG. You could refer to this Docs to Set Environment Variables for the Visual Studio Command Line.
Then try to repair your VS in control panel and reboot to test if error exists or not.
BTW, could you please share more requirement about what you want to do:)?
I looking forwards your reply.
Best Regards
May
MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]
Sunday, February 3, 2019 2:31 PM
Hi friend,
Welcome to the MSDN forum.
Refer to the description, it may be the following possible reasons:
1. VS didn't install well, the VsDevCmd can't run properly.
2. Your computer environment variable setting is incorrect.
To troubleshoot this issue, please try steps below:
1. Navigate to path:
C:\Program Files (x86)\Microsoft Visual Studio\2017\**\Common7\Tools
(*** is your VS edition: Enterprise, professional or community).
2. Find VsDevCmd file and execute to see if it shows detailed error. if there is, please tell us the error info.
3. Click Start and Edit the system environment variables, view and check those existing environment variables are correct.
4. Run the VS installer to repair and update, reboot your machine.
5. Check windows update and install the newest patches.
6. Launch Developer Command Prompt to see if it works fine.
Best regards,
Sara
MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]
Sunday, February 3, 2019 8:07 PM
VS does not have repair function. this output is maximum detailed output of this error. I get error when run "Developer command prompt VC 2017" (VsDevCmd)
I did reboot and update my PC
Sunday, February 3, 2019 11:32 PM
Hi,
Please read this article.
[note] this is written in Japanese. Please use machine-translation for your language.
/ja-jp/dotnet/framework/tools/developer-command-prompt-for-vs
Regards,
Ashidacchi -- https://ssl01.rocketnet.jp/hokusosha.com/default.html
Monday, February 4, 2019 12:04 AM
it's working, I don't know how but worked. Unfortunately I still got cl.exe not found error when try to compile python module
Monday, February 4, 2019 1:03 AM | 1 vote
Do you actually have the Visual C++ desktop workload in? Do you actually have the V141 tools installed?
If you have these, are you trying to build a module for the 64 bit perl interpreter? The developer command prompt defaults to 32 bit. If you want to get the 64 bit version then you need to go through the command prompt and run the developer command batch file manually:
or you can copy the shortcut in start and change it to add these arguments to the shortcut. Either way you need the C++ tools installed.
This is a signature. Any samples given are not meant to have error checking or show best practices. They are meant to just illustrate a point. I may also give inefficient code or introduce some problems to discourage copy/paste coding. This is because the major point of my posts is to aid in the learning process.
Monday, February 4, 2019 1:18 AM
Thanks, this command run prompt correctly, but it's means I must open it every time when I need compile python module?
I can add something to path and get automatic enabling needed VC vars ?
Monday, February 4, 2019 2:26 AM
Hi Rostyslav Nikitin,
How to repair VS, please see: /en-us/visualstudio/install/repair-visual-studio?view=vs-2017 then reboot and re-run Developer command prompt for VS 2017 to test.
Could you modify vsdevcmd.bat script? So far, this error indicates some change in script and the path not be found, which causing the environment to fail to initialize. If so, please restore it.
if it persists, please uninstall VS then re-install it:
How to completly uninstall VS: navigate to the file:** C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\layout** on your machine, find** InstallCleanup.exe** and launch it from an admin command prompt with a -full param: InstallCleanup.exe –full. If not, please manually delete the "%programfiles(x86)%\Microsoft Visual Studio\Installer” folder. Then run VS exe again.
please make sure you already followed the VS installation notes as below:
1.Disable antivirus(AVG) and anti-malware.
2.Visit Microsoft Update, scan your computer for available updates, and install any high-priority updates that are offered to you.
3.Clean up the %temp% folder
4.Run the VS installer as administrator
May
MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]
Monday, February 4, 2019 1:43 PM
> I can add something to path and get automatic enabling needed VC vars ?
You (or anyone else) can make a small batch file that calls vcdevcmd.bat with needed parameters. Put it in some place on your PATH.
-- pa