Ironically I've been able to get non-headless (headful?) working, but headless would be better for testing :/ Goodbye.įailed to generate minidump.Illegal instruction (core dumped) The display compositor is frequently crashing. If people start using WSL elevated just so they can run their webpage test scripts, that gets more ugly. This wasn't as much of a problem back in 2016 when the only thing people reasonably expected to work was ping. But the more surface you guys cover, the higher the risk that 'You need to run WSL as Administrator or it doesn't work right' becomes idiomatic. I've just about got WSL nmap running and understand the dilemma. I empathise entirely that the problem worms real fast. Mapping WSL UID 0 to Windows Administrator privileges is another matter. That UserVoice you mention is more about people annoyed by the popup notification.

The message doesn't mean much though, since by that point Chrome has skidded off the track and probably doesn't know up from down.īut yep, recent Chrome (headless and otherwise) works fine if you start WSL escalated. That run above wasn't elevated of course, but Chrome is under the impression network namespace available anyway. I had wondered but didn't have my container thing handy to try (hence the hedge).

Google chrome administrator privileges