It's Windows 10, what you describe is what everyone else calls "Tuesday".
You don't need to employ my methodology to achieve something that Micro$haft can do all by itself without the aid of Ryzen Master.
The
ONLY time (and I am pretty sure I discussed this in one of my posts in this thread) I had serious problems was when I tried configuring the system in the BIOS with regard to the parameters
THAT WORK FLAWLESSLY when applied via Ryzen Master.
The result was garbage being displayed on a screen with the same background colour as a BSOD and a reboot (after reverting the settings) ending up in Windows going into repair mode (which restored the functionality). For good measure I decided to repeat that experiment, with the same result. So I gave that up as a bad idea, stupidity of course being, "Doing the same thing over and over and expecting a different result".
That having been said one of my prior corporate positions was Senior German Engineer for Enterprise Disaster-Recovery Tech-Support and my direct supervisor was the Vice-President for Tech-Support at a corporation that was, at that time, in the Top Ten of software companies worldwide.
So backups are a thing. You might want to try it sometime, it's amazing what kind of peace of mind that brings.
That being said, in the entire time I have been applying and refining my methodology over the past six months or so (I have been experimenting in total for about eight months), I have suffered no corruption of the OS.
I regularly check the health of the OS and I also know how to configure it so that it is a lot more robust than just leaving it the way M$ thinks it should be.
I have also deployed Windows 10 Enterprise, which prevents many of the shenanigans that the "Raptors from Redmond" are free to inflict on those who use other versions of the Win10.
In other words, I know what the fuck I am doing.