Black screen when launching local

Support
1

Hello,

I just got local 2.2.4 on Windows 10, installation went smoothly, however I can’t start it. It’s stuck on a black screen. Buttons are still there (little hand when I move over them).

Here is a screenshot:

image
image1920×1080 184 KB

And here is the log file (I copy-past the last lines, it’s the same over and over every 4 lines) :

Jun 1, 2018, 5:44 PM GMT+2 - error: [main/index] Error: spawn wscript.exe ENOENT
at exports._errnoException (util.js:1050:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:367:16)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)

Jun 1, 2018, 5:45 PM GMT+2 - info: [main/index] Existing Pressmatic data does not exist.

Jun 1, 2018, 5:45 PM GMT+2 - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘’,
stderr: ‘Host does not exist: “local-by-flywheel”\n’ }

Jun 1, 2018, 5:45 PM GMT+2 - info: [renderer/CheckEnvPage] Check system promise response:
[ ‘virtualbox-not-ready’, ‘machine-does-not-exist’ ]

Jun 1, 2018, 5:45 PM GMT+2 - error: [main/index] Error: spawn wscript.exe ENOENT
at exports._errnoException (util.js:1050:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:367:16)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)

Jun 8, 2018, 9:29 AM GMT+2 - info: [main/index] Existing Pressmatic data does not exist.

Jun 8, 2018, 9:29 AM GMT+2 - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘’,
stderr: ‘Host does not exist: “local-by-flywheel”\n’ }

Jun 8, 2018, 9:29 AM GMT+2 - info: [renderer/CheckEnvPage] Check system promise response:
[ ‘virtualbox-not-ready’, ‘machine-does-not-exist’ ]

Thanks in advance!
David

2

By the way I never installed virtualbox, is it a prerequisite?
I’m quite sure it has nothing to do with it but just in case, I installed Ubuntu on VMware.

3

Hi David,

Local will automatically install VirtualBox. Local won’t connect with VMWare Fusion/Workstation at this time.

As far as the blank screen goes, that might be caused by a driver issue.

Please make sure your graphics card driver is up-to-date. If you’re using an Nvidia GPU, GeForce Experience makes it easy to update the drivers for your GPU. Otherwise, if you have an AMD GPU, you can update by going here: https://support.amd.com/en-us/download

4

OMG I’m not sure I’m feeling more stupid or thankful!
In doubt, I’ll just thank you, that works perfectly…

1 Like