edit: for anyone curious, the problem was Xorg wasnt loading or something (stuck on systemd 'graphical interface target reached' with no graphical interface). because of a typo in a config file.
You need to rethink your reinstall process. My root is on a separate drive from my home directory. My home directory has a script that installs all of my basic software, along with any specific config files that don't reside in my home directory naturally. I can reinstall the system in about an hour.
I have only really done this while i used windows, on linux i have always been able to find a solution that didn't require reinstalling; on windows on the other hand i had a time where it just started to bluescreen at every boot out of nowhere...
backup on another physical disk of important data (usually a subset of /home )
other partition for OS testing
other working device for instructions and search online (mobile phone is usually enough)
documented setup for complex tools, e.g /home/Prototypes where you might have container setups, e.g docker-compose.yml
Usually if you have this in place its a matter of hour, at most. Sure in 1h you will not have ALL the apps you need perfectly configured but, for me at least, enough to feel at "home" again. It's usually about having ~/.bashrc or ~/.tridactilrc in place but if you do have /home on another partition, it's basically "free".
Goddammit I'm literally right now trying to decide if I want to spend an entire day wiping and reinstalling the OS in my main PC or if I can live with the current glitches for now. Full disclosure, in my case the glitchy behaviour is entirely on me trying to tinker with the OS and accidentally breaking stuff, not an issue with Linux or the distro.
When you install, partition your drive. /home goes on its own partition and will probably be the largest one. Then you can wipe the / partition and reinstall all you want, takes 15 minutes
I guess the "small bug" is that you have microsoft windows on the drive for dual booting. Otherwise I wouldn't know what sort of bug you'd get rid of like this.
I recently fucked a system because I wanted to resize the swap partition. Started throwing time after trying to recover. Realized that even if I succeeded, I'd have spent more time recovering than it would take to reestablish a new system, and no important data was on the system.
nixOS. But seriously. You can change something in the config file, and if it doesn't work, you can roll back to a previous file. It can also control for things like custom kernels.
I have some Linux servers in hyper v virtual machines and i just revert then to a previous snapshot if I mess anything up instead of bothering with diagnosing what I did 🙃
Haven't needed to do either yet since I started using #EndeavourOS. I'm a bit surprised, given how many posts I've seen about people bricking their Arch installs.