-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problem bootstrapping vcpkg as 'system' user (SysWOW64 issue) #5248
Comments
Thanks for posting this issue! Looking at your comments in the other thread, it seems like the right answer is for us to detect if we are running as the system user and perhaps change the temp environment variable accordingly. I'd be happy to review a PR for such a feature! |
Git hash: c7d4696 Here is a build log that might explain why it does not work, and possibly juggle the brains on someone so this issue can get fixed. Thanks in advance!! To get this log file I had to do the following:
|
If we keep TMP, when run as 'system' user it is using Windows\Temp folder.
Looks like keep |
If we keep TMP, when run as 'system' user it is using Windows\Temp folder.
If we keep TMP, when run as 'system' user it is using Windows\Temp folder.
Thanks for posting this issue. This issue has been fixed. So I am closing this issue for now. |
I'm trying to bootstrap vcpkg as 'Local System' (from a service) - which fails.
It looks like SysWOW64 redirection is messing things up: dotnet/msbuild#185
Is there any way to use msbuild64 or override env:TMP for the bootstrap process?
(cleanEnvironmentHelper.ps1 seems to undo any environmental changes I try)
edit: removed troubleshooting comments, crossposted issue to dotnet/msbuild#4107
The text was updated successfully, but these errors were encountered: