# Stuck on "Checking System..."

**URL:** <https://community.localwp.com/t/stuck-on-checking-system/8068>\
**Category:** Support\
**Created:** [September 5, 2018, 10:47pm UTC](https://community.localwp.com/t/stuck-on-checking-system/8068 "2018-09-05T22:47:02Z")\
**Posts on this page:** 1\
**Showing post:** 45

<div class="post-metadata">

**Author:** ![ben.turner](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/ben.turner/32/5366_2.png) [@ben.turner](https://community.localwp.com/u/ben.turner)\
**Post date:** [July 2, 2019, 5:23pm UTC](https://community.localwp.com/t/stuck-on-checking-system/8068/45 "2019-07-02T17:23:32Z")

</div>

@nemateur -

I’m seeing this within the Local log:

```auto
May 30, 2019, 1:23 PM GMT+2 - warn: [main/set-docker-env] Unable to get Docker Machine env. This usually happens when there is a kernel panic inside the VM. Attempting to power cycle VM now. 
{ error:
   { killed: true,
     code: null,
     signal: 'SIGTERM',
     cmd:
      'C:\\Users\\lamim\\AppData\\Local\\Programs\\local-by-flywheel\\resources\\extraResources\\virtual-machine\\vendor\\docker\\windows\\docker-machine.exe env --shell bash local-by-flywheel' } }

```

That makes me think there is some sort of issue with the Docker daemon inside the Virtual Machine. Can you try restarting the VM by going to “Help \> Restart Local Machine”.

If that doesn’t work, then follow the steps outlined in this topic to forcefully shut down and restart the VM:

- [How can I forcefully restart the Local by Flywheel VM?](https://localbyflywheel.com/community/t/how-can-i-forcefully-restart-the-local-by-flywheel-vm/6388)

---

_[View the full topic](https://community.localwp.com/t/stuck-on-checking-system/8068)._