Upon examination, turns out my test was run across a MicroSloth update process (it can't get anymore confusing than that 
![[Image: clear.png]](https://www.wilderssecurity.com/styles/default/xenforo/clear.png)
). Anyway, I went back to prior update time (via my primary imaging software), allowed my System to receive and install the current MS update cycle, reBOOTed to allow it to settle, then took my pre and post Hasleo OS partition images to reexamine the results. This time, no errors whatsoever. Repeated the process, all seems well... and a very quick restore to my NvME-based OS partition.
MicroSloth update quirk...???
). Anyway, I went back to prior update time (via my primary imaging software), allowed my System to receive and install the current MS update cycle, reBOOTed to allow it to settle, then took my pre and post Hasleo OS partition images to reexamine the results. This time, no errors whatsoever. Repeated the process, all seems well... and a very quick restore to my NvME-based OS partition.MicroSloth update quirk...???