[DOCS] add note about unicode BOM in password files (ethereum#20598)

wbt · fjl · web-flow · commit a1ea472395f5 · 2020-02-09T21:54:22.000+01:00
Co-authored-by: Felix Lange &lt;fjl@twurst.com&gt;
diff --git a/docs/_interface/FAQ.md b/docs/_interface/FAQ.md
@@ -59,3 +59,10 @@ Not only is storing the data very suboptimal, but due to the 200 modification /
 **A:** Unfortunately not. Doing a fast sync on an HDD will take more time than you're willing to wait with the current data schema. Even if you do wait it out, an HDD will not be able to keep up with the read/write requirements of transaction processing on mainnet.
 
 You however should be able to run a light client on an HDD with minimal impact on system resources. If you wish to run a full node however, an SSD is your only option.
+
+
+---
+
+**Q: When I try to use the --password command line flag, I get the error "Could not decrypt key with given passphrase" but the password is correct. Why does this error appear?**
+
+**A:** Especially if the password file was created on Windows, it may have a Byte Order Mark or other special encoding that the go-ethereum client doesn't currently recognize.  You can change this behavior with a PowerShell command like `echo "mypasswordhere" | out-file test.txt -encoding ASCII`.  Additional details and/or any updates on more robust handling are at <https://github.com/ethereum/go-ethereum/issues/19905>.
