New
#21
Thanks for the responses, and I'll reply to some of the specific points:
They're on different physical drives. I'll post a Disk Mgmt pic if it helps things along after I post this cluster of replies.
I don't like to have all my eggs in one OS basket. And anyway, my dual boot enables access to a dependable frozen-in-time 2013 install of Win7 that can run things that are broken in Win10. Of course, that Win7 OS is blocked from the Internet, to prevent any updates throwing a spanner in the works. Could I trust a virtual one to act the same way? I think not!
I'm not overclocking. And since W10 was "working on updates" and telling me it'll take a while, we can't call it an RSOD. Is there such a thing as a Red Screen of Life?
Having searched for (and found) accent color, I see that red was indeed selected, for some reason. So, thanks for that!
By using the "install updates and shut down" option, rather than the "install updates and restart" option, I'd hoped to be able to defer further use of Win10 until the next morning. With previous Windows, the install package would be downloaded, and when one next fired up that particular OS, the package would then get unpacked and integrated with the OS. But I always had a choice of whether or not to fire up that particular OS.