Installing 3.0.0-rc.6 causes BSOD on WSL
See original GitHub issueDo you want to request a feature or report a bug? bug
What is the current behaviour? BSOD on Windows 10
If the current behaviour is a bug, please provide the steps to reproduce.
- Used VS Code to start a remote session with my Ubuntu WSL installation
- Open integrated terminal
- Run `npm i -g preact-cli@3.0.0-rc.6
What is the expected behaviour? preact-cli installs successfully
If this is a feature request, what is motivation or use case for changing the behaviour?
Please mention other relevant information.
Please paste the results of preact info
here.
n/a
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Windows BSOD / hangs on boot when using WSL2 #5783
I did a fresh re-install as well. Can't get the Virtual Machine Platform working. It's causing the BSOD. Only working off WSL too....
Read more >Installing wsl and rebooting makes my laptop go into a bsod ...
Open Windows File Explorer. Copy any minidump files onto your Desktop, then zip those up.
Read more >Scoop buckets by number of stars - GitHub Pages
A searchable directory of buckets for the scoop package manager for Windows.
Read more >Hunting for Blues - the WSL Plan 9 Protocol BSOD - McAfee
In this research we explore the P9 protocol implementation within the Windows kernel and whether we could execute code in it from a...
Read more >BSOD when enabling Virtual Machine Platform in combination ...
I did a new install of windows 11 on my laptop. Everything was fine until I ran "wsl --install" Got the BSOD with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Quite happy to help with debugging this issue if it is recurring for you, but until I can reproduce locally it seems tricky. The symptoms of full kernel panic probably imply an issue upstream in node/npm or windows/wsl itself, since preact-cli is quite certainly within userspace.
I’ll close this for now
If you can somehow figure out which dependency causes it we can maybe try to fix it, but with the information we have right now I don’t think there’s much we can do