Nothing more to explain... this is what it looks like:

Dev tools (ctrl+shift+I) shows like this:

Tried running as administrator, running from different units... always the same result.
Any clue?
I wonder if this is related to #1866 ?
SOLVED! Same problem as in here . My laptop was set to force NVIDIA graphics instead of integrated ones. Switch this to force integrated graphics and Etcher starts without problems.
Thanks!
@jhermsmeier Maybe something to add to the docs?
I have an AMD graphic card, so the solution up there didn't work for me. I was facing the same problem until I did change the compatibility mode to Windows Vista, in the Compatibility tab on the executable' Properties menu.
I hope it helps.
I have an AMD graphic card, so the solution up there didn't work for me. I was facing the same problem until I did change the compatibility mode to Windows Vista, in the Compatibility tab on the executable' Properties menu.
I hope it helps.
well it works
Look like Etcher use component of base browser (maybe Internet Explorer), but you all not use/update IT. I use other OS and it work.
Having same problem Windows, hp laptop. Intel HD graphics 620. Blank grey screen on running npm start.
worked when using internet explorer, failed with chrome
[saintaardvark] This issue has attached support thread https://jel.ly.fish/#/5fb31974-788e-459e-aad5-51895f4fddaa
Same problem, Windows 7, Intel HD Graphics 3000. v1.5.86 seems to work in Vista compatibility mode (although etching fails), but I can't get v1.5.95 working at all.
Same problem with Windows 10, AMD CPU and GPU.
@imarindam can you try updating the .NET framework? if that doesn't work, another thing to try is running from C: in case you're using the portable version.
You might also try downgrading and running with compatibility mode as previously mentioned by @poshest.
This is probably not related to Etcher itself so I wouldn't know how to proceed if none of these options work
Most helpful comment
I have an AMD graphic card, so the solution up there didn't work for me. I was facing the same problem until I did change the compatibility mode to Windows Vista, in the Compatibility tab on the executable' Properties menu.
I hope it helps.