Is there any chance this is related to the SBAT update from Windows? Since the upgrade was from 16 to 17, which needs to do some work on the bootloader, maybe it's related? Just a guess...
If you are willing to do a fresh install, it would certainly help. Fresh install is like the good old "turn it off and back on", it works wonders on odd issues like this.