-
Notifications
You must be signed in to change notification settings - Fork 17
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
Resource do not work on Windows 10 #47
Labels
Comments
mhendric
added
bug
The issue is a bug.
help wanted
The issue is up for grabs for anyone in the community.
labels
Feb 14, 2019
Looks like a bug to me. Thanks for the report! |
FrelVick
added a commit
to FrelVick/xBitlocker
that referenced
this issue
Feb 15, 2019
Can someone add the missing if statement and updated code as from FrelVick proposed. `
` |
This was referenced Jun 24, 2019
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Due to this function Assert-HasPrereqsForBitlocker the resource doesn't start on the Windows 10. If you perform all the steps manually it works perfectly.
Since Get-WindowsFeature doesn't exists on client OS the function throw
which is not true for Pro, Enterprise, and Education editions of Windows 10.
if( ((Get-CimInstance -ClassName Win32_OperatingSystem).ProductType -eq 1) -and (get-command enable-bitlocker -ErrorAction SilentlyContinue)) then {It is a workstation with BitLocker available, don't throw}
Little check like that one could help you to avoid false negative assert.
Regards,
Viktor Frelikh
The text was updated successfully, but these errors were encountered: