# Obtaining a log file

**URL:** <https://community.factoryio.com/t/obtaining-a-log-file/46>\
**Category:** Support\
**Created:** [February 20, 2020, 11:58am UTC](https://community.factoryio.com/t/obtaining-a-log-file/46 "2020-02-20T11:58:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![brunovgr](https://dub1.discourse-cdn.com/flex017/user_avatar/community.factoryio.com/brunovgr/32/12_2.png) [@brunovgr](https://community.factoryio.com/u/brunovgr)\
**Post date:** [February 20, 2020, 11:58am UTC](https://community.factoryio.com/t/obtaining-a-log-file/46/1 "2020-02-20T11:58:20Z")

</div>

Sometimes, we might ask you to send us a file that logs the behavior of Factory I/O so we can find out what’s causing the problem you are reporting.

In order to obtain this file start by launching Factory I/O with administrator privileges: right-click on the Factory I/O icon and select ’ **Run as administrator** ’ from the context menu.

![](https://europe1.discourse-cdn.com/flex017/uploads/factoryio/original/1X/4d2f034e1338fcddc358c1d3b9d239404b36e6b4.png)

Then, use Factory I/O until you trigger the problem. When that happens, you can close the application. The resulting log will be saved to Player.log file located in 'C:\Users\username\AppData\LocalLow\Real Games\Factory IO _’_ .

In order to easily access this file, run the console command **app.copy\_log()**. This command copies the Player.log file to …\Documents\Factory IO and renames it ‘log YYYY-MM-DD HH-mm-ss.txt’