Build of ANYTHING fails early on with "vcvarsall.bat returned 255"

[j-xella]

Operating system

WIN 10 Enterprise 22H2

Compiler

VS 2022

Steps to reproduce the behavior

vcpkg install omniorb:x64-windows --debug

Failure logs

...
[DEBUG] Found path: C:\Program Files\PowerShell\7\pwsh.exe
[DEBUG] 1006: CreateProcessW("C:\Program Files\PowerShell\7\pwsh.exe" --version)
[DEBUG] 1006: cmd_execute_and_stream_data() returned 0 after  1105716 us
[DEBUG] command line: cmd /d /c "C:\Program Files (x86)\Microsoft Visual Studio\2022\Enterprise\VC\Auxiliary/Build\vcvarsall.bat" -vcvars_ver=14.36.32532 amd64   2>&1 <NUL  & echo cdARN4xjKueKScMy9C6H & set
[DEBUG] 1007: CreateProcessW(cmd /d /c "C:\Program Files (x86)\Microsoft Visual Studio\2022\Enterprise\VC\Auxiliary/Build\vcvarsall.bat" -vcvars_ver=14.36.32532 amd64   2>&1 <NUL  & echo cdARN4xjKueKScMy9C6H & set)
[DEBUG] 1007: cmd_execute_and_stream_data() returned 255 after  2802303 us
[DEBUG] **********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.6.13
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************

error: while trying to get a Visual Studio environment, vcvarsall.bat returned 255
[DEBUG] D:\a\_work\1\s\src\vcpkg\base\system.process.cpp(1284):
[DEBUG] Time in subprocesses: 4694304us
[DEBUG] Time in parsing JSON: 462us
[DEBUG] Time in JSON reader: 855us
[DEBUG] Time in filesystem: 129544us
[DEBUG] Time in loading ports: 119141us
[DEBUG] Exiting after 4.9 s (4856342us)

Additional context

There were similar issues reported earlier:

• vcpkg install (manifest mode) fails: "vcvarsall.bat failed with exit code 255" #17730
• error: while trying to get a Visual Studio environment, vcvarsall.bat returned 255 #33298

However, this time it is with newer version of compilers, so maybe the problem is somewhere else?

The --debug invocation gives a command line that failed. When I replay that command

cmd /d /c "C:\Program Files (x86)\Microsoft Visual Studio\2022\Enterprise\VC\Auxiliary/Build\vcvarsall.bat" -vcvars_ver=14.36.32532 amd64   2>&1 <NUL  & echo cdARN4xjKueKScMy9C6H & set

in a new command window, I don't see any errors, just a list of environment variables:

**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.6.13
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************
cdARN4xjKueKScMy9C6H
ALLUSERSPROFILE=C:\ProgramData
APClientType=FAT
APDesktop=C:\Users\XXX\Desktop
APPDATA=C:\Users\XXX\AppData\Roaming
...

Versions:

• vcpkg package management program version 2024-04-23-d6945642ee5c3076addd1a42c331bbf4cfc97457
• vcpkg repository on commit 7eb700c9688daed6d8bdcdc571ebe3eedea6a774

[StarGate-One]

cmd /d /c "C:\Program Files (x86)\Microsoft Visual Studio\2022\Enterprise\VC\Auxiliary/Build\vcvarsall.bat" -vcvars_ver=14.36.32532 amd64 2>&1 <NUL & echo cdARN4xjKueKScMy9C6H

One issue I see is the path - C:\Program Files (x86) is where Visual Studio 2019 and older reside as they were 32-bit (x86) programs. Visual Studio 2022 is 64-bit (x64) and should be found in C:\Program Files, that is unless the Visual Studio Installer was over-ridden to something other than the default when VS2022 was installed.

[j-xella]

One issue I see is the path - C:\Program Files (x86) is where Visual Studio 2019 and older reside as they were 32-bit (x86) programs. Visual Studio 2022 is 64-bit (x64) and should be found in C:\Program Files, that is unless the Visual Studio Installer was over-ridden to something other than the default when VS2022 was installed.

I have no control over the location of VS - I request it and it gets installed from a centralized package repository in our organisation. That being said, installation location should not be of importance, right? Otherwise, VS 2022 seems to work OK, even when being installed in a wrong folder.