Last active
March 10, 2022 04:35
-
-
Save deadlydog/5e80fb5ebfc1d26720274beb0ba3792b to your computer and use it in GitHub Desktop.
Paste this into the PowerShell command line and you'll get an odd `An error occurred while creating the pipeline` error. Remove one "d" from the end and you'll get the expected `Get-Something is not recognized as a name of a cmdlet` error. This info is related to this tweet: https://twitter.com/deadlydog/status/1500295904615702531?s=20&t=7XvHRhT…
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Get-Something dslkfjds lkjfdsl jflkdsfljdsalkf dslkf jlkdsjf lkdsj fljds lkf jdsalkf dslkfj dslfj lkdsjf ldskj flkds jflkjds lkf jdslfk jdsalkf jds jflkds jflkdsjflkds flkjdsflk jdslkf lkdsjflkdsj fljds lkf jdslfj sldjf kds flk jdsfl dsf dsljf ds jfhds lf jdsjf dsljflkds jfsjldsj fl jdsflkjdsflkjds dsfadsf dd |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just to close the loop on this, it looks like the problem is being caused by the antimalware software on my machine (distributed by our organization) thinking the long command may be a malicious attack. This explains why my coworkers could reproduce the issue, but not other people.