Add -noprofile flag for windows powershell to avoid permission issues #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We recently had an issue with this hard drive encryption check on a developers windows machine that was using powershell profiles.
In the
main.log
we found the following error on this command:As this command is just running a simple query the powershell scripts don't appear necessary so to avoid this issue for others in future this change just adds the no profile flag to stop powershell attempting to load profiles on launch.