Oh, so essentially the same bug that existed since windows 98? Where you could, on the login screen, click the little question mark, which would open windows help, then you could click on "open file", navigate to C:\windows and just double click on explorer.exe, which would log you in without a password?
Windows 98 was not intended to offer meaningful local security. The password prompt was used to collect the username/password to use to connect to network resources. (And also, perhaps confusingly, the password prompt was overloaded to select the local user profile, if such feature was enabled - but entering a new username would create a new account, so being a barrier to using the computer was never the point.)
Windows 98 wasn't a true multi-user operating system anyway, security was a simulation. Only the NT line was multiuser at the time (and later XP through 10).
The Windows 98 issue was a bug. The example given involving Windows 7 and renaming executables is NOT a bug. If you give someone unrestricted access to the hardware, they have unrestricted access to the hardware. Working as intended.
You want someone not to be able to mess with a Windows installation? Activate Bitlocker.
That's why this Windows 10 issue IS a bug. Because it bypasses Bitlocker and allows a normal user to escalate to local admin. The Windows 7 issue is NOT a bug because it allows no such escalation (since no security was ever stopping local HDD access anyway).
