You’d be surprised how caked a charge port can be, you know you’ve cleaned it correctly when the plug goes in all the way and doesn’t stick out a bit.

When it still doesn’t connect correctly and/or you feel play in de cable/chargeport, it might just need replacing.

I agree, the encryption should be deliberate choice. And we’ve said nothing yet about the impact on performance.

You used to almost be forced to make a recovery CD or USB when encrypting a drive, now people don’t even know how ‘important’ the MS account actually is.

Bypassnro is the old method, no longer working since 24H2. I’ve tested this method on GitHub and it works for normal AND S-mode devices.

• Ctrl + Shift + J before selecting secondary keyboard layout (sometimes you need to click on the outside borders of the form so the dev console pops up)
• Type this (can use autocomplete): WinJS.Application.restart(“ms-cxh://LOCALONLY”)
• Setup with local account

All the time, then people get ran around in circles, are given a too technical explanation and give up more often than not.

The encryption is not inherently a bad thing, but forcing people into account creation is where the trouble starts. With piss-poor customer support as the cherry on top, this should never be allowed.

You are wrong for now, it is still possible.

• Ctrl + Shift + F3 during setup gives you access to sysprep
• In an admin CMD you can excecute the BypassNRO.cmd script. In C:\Windows\System32\oobe\
• I have encountered one 24H2 installation where the oobe folder was empty, but if you copy the file from another device it works just the same
• Reboot from sysprep and you can now select “Install without internet” when selecting a WIFI

This will not work if you’re already connected to a wifi. BypassNRO sets a registry flag, so it’s only a matter of time till they patch it out, but it works for now.

Edit: Rufus also allows the creation of a local user when making the installation USB, skipping the entire setup process.