

You had not explained how precisely you had interrupted the ongoing Windows 10 update. I suspect that maybe deleting $WINDOWS.~BT is going to cause major trouble on Windows 10. I wonder a bit whether permitting Windows 10 to restart and finish the interrupted update operation would not be the right approach. I do not know, because there is no Windows 10 on any of my machines.

May be none, maybe something which can be repaired, maybe something which cannot be repaired easily or not at all. I have got no clue which damage may have been caused to your Windows 10 installation. This in itself may not have been the wisest thing to do. You interrupted an ongoing Windows 10 update operation. Yet, I wonder a bit whether it may not be good luck that so far you have not succeeded in deleting the directory sub-tree $WINDOWS.~BT. Having only the end of a very long screen output is not particularly helpful. For such cases, where the screen output is so long that it exceeds the default terminal screen buffer, you can temporarily resize this terminal buffer from the default value (1000 lines or maybe 2000 lines) to 10,000 lines e.g.
