Closed tzilber-sq-zz closed 4 years ago
Same issue here. No workaround? Was this introduced in Vagrant 2.2.6, and if so, is it worth trying to downgrade?
Downgrading to 2.2.5 does not fix it, nor does downgrading Windows 10 from 1909 to 1903 (since I thought that may be a factor), but simply removing the body of the function in question and inserting return $true
in its place allows Vagrant to proceed past this check.
Hardly a solution, but if, like most of us, your entire professional life requires Vagrant in some form or another, you can move on with life. :)
I'll add whatever I can to help identify the root-cause here as time permits. From what little debugging I've been able to do, it seems like a SID cannot be translated to an account or similar.
I'm getting the same issue. :(
@nwent I observed this same issue when I ran vagrant from inside C:\Windows\System32
(since that's where launching an administrative powershell console defaults to).
@tzilber
It's likely you have the same issue as your log indicates you're running from C:\Windows\System32
INFO environment: - cwd: C:/WINDOWS/system32/Skadi/Vagrant/skadi_server/virtualbox
Navigate to a temporary folder and try again - it should resolve the issue. The fix (#11271) is only going to stop it from failing with an error - in which case it'll just report failed access if you're running from system32
You can validate by running the failing powershell manually
#----------------------------------
# Successfully Running in C:\Temp
#----------------------------------
PS C:\temp> $(Get-ACL -Path .).Access | where {
>> $_.IdentityReference.Translate([System.Security.Principal.SecurityIdentifier]).Value -eq "S-1-5-18" -and
>> $_.FileSystemRights -eq "FullControl" -and
>> $_.AccessControlType -eq "Allow" -and
>> $_.IsInherited -eq $true}
FileSystemRights : FullControl
AccessControlType : Allow
IdentityReference : NT AUTHORITY\SYSTEM
IsInherited : True
InheritanceFlags : ContainerInherit, ObjectInherit
PropagationFlags : None
#----------------------------------
# Failure in system32
#----------------------------------
# Navigate there
PS C:\temp> cd C:\Windows\System32\
# Verify access
PS C:\Windows\System32> $(Get-ACL -Path .).Access | where {
>> $_.IdentityReference.Translate([System.Security.Principal.SecurityIdentifier]).Value -eq "S-1-5-18" -and
>> $_.FileSystemRights -eq "FullControl" -and
>> $_.AccessControlType -eq "Allow" -and
>> $_.IsInherited -eq $true}
Exception calling "Translate" with "1" argument(s): "Some or all identity references could not be translated."
At line:2 char:9
+ $_.IdentityReference.Translate([System.Security.Principal.Sec ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : IdentityNotMappedException
Exception calling "Translate" with "1" argument(s): "Some or all identity references could not be translated."
At line:2 char:9
+ $_.IdentityReference.Translate([System.Security.Principal.Sec ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : IdentityNotMappedException
Exception calling "Translate" with "1" argument(s): "Some or all identity references could not be translated."
At line:2 char:9
+ $_.IdentityReference.Translate([System.Security.Principal.Sec ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : IdentityNotMappedException
Exception calling "Translate" with "1" argument(s): "Some or all identity references could not be translated."
At line:2 char:9
+ $_.IdentityReference.Translate([System.Security.Principal.Sec ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : IdentityNotMappedException
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Vagrant version
Vagrant 2.2.6
Host operating system
Windows 10
Debug output
Expected behavior
Vagrant opens
Actual behavior
Steps to reproduce