# PowerShell logging artifacts with Sisulizer

**URL:** https://www.finalbuilder.com/forums/t/powershell-logging-artifacts-with-sisulizer/6812
**Category:** Bugs
**Created:** [July 20, 2020, 6:34am UTC](https://www.finalbuilder.com/forums/t/powershell-logging-artifacts-with-sisulizer/6812 "2020-07-20T06:34:17Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [July 20, 2020, 6:49am UTC](https://www.finalbuilder.com/forums/t/powershell-logging-artifacts-with-sisulizer/6812/3 "2020-07-20T06:49:35Z")

</div>

> [@larsfosdal](#):
>
> Some of its output is prefixed with what shows up like  
> 

That looks like a Byte Order Mark… I don’t know much about sisulizer but this looks to me like the tool is outputting the BOM when it’s stdout is redirected?

---

_[View the full topic](https://www.finalbuilder.com/forums/t/powershell-logging-artifacts-with-sisulizer/6812)._