- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Installing OS, 10 years ago:
Windows: click a couple of buttons enter username and password
Linux: Terminal hacking, downloading shell scripts from github
Installing OS today:
Linux: click a couple of buttons, enter username and password
Windows: Terminal hacking, downloading shell scripts from github.
Link to video: https://m.youtube.com/watch?v=qKRmYW1D0S0
When the BSOD code has nothing to do with your actual problem
Well OBVIOUSLY you need to set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session\Windows\Microsoft\Win10\MSWindows\CockNBalls\BSODWord to 0 then restart your computer.
Sorry, that was before KB1103995. The new method requires you to check a box in your OneDrive account first before the entry is respected.
Except you already have that update installed, the box is not checked and the entry is still respected, nobody could possibly tell you why because that’s not how it’s supposed to work and everyone else works as stated! And now you have to live with the knowledge that your system is in some unobserved quantum superposition with a critical fix in place which may stop working at any moment for any reason and nobody can tell you how you even managed to get into this situation…
NOOOOOO please you’re reawakening 20+ years of accumulated Windows trauma 😭 😭 😭
That was so confusing and stressful I don’t know how I --or anyone-- survived the mental strain of regularly troubleshooting Windows
You forgot that you also need to create a new 32bit word entry with the value of the amount of system RAM in gigabytes times 2 divided by the square root of your age times 10.
Otherwise BSODWord won’t be picked up.
Edit: also you need to redo that every time your system updates because Windows update will reset all those values