(1) "IMO, this is a problem if you want to get really competent in using W10 By the time you have something under your control, they change it, and force it you. This can lower your efficiency in an office/business environment."
That's right. I like things to remain as they are, but they've moved certain settings to different screens. Control Panel stuff is getting put into the "START, Settings" screens. OTOH, they did make things easier by putting most settings into the Search bar & into Cortana for the asking. That was good. Also, it seems most/all the old apps are still here too, such as Backup & Restore.
But I think it was the removal of Homegroups that possibly accidentally resulted in the network sharing problem you face. I never used Homegroups that I'm aware of. I can't find it anywhere now, but I do believe I'd seen it in earlier versions of Windows. Looks like I'm in a Workgroup now & that I cannot join a Domain because mine is Home Edition (I guess)...
(a) Type "Workgroup" into Search, & select "Change Workgroup name".
A System Properties requestor opens at the Computer Name tab.
(b) Click the "Change" button in the System Properties requestor.
The "Computer Name/Domain Changes" requestor opens...
I don't actually care much about any of that. I've only got this one computer, & I'd move files from one to the other using a USB drive, anyhow. But I do appreciate the capability (provided I wouldn't also suffer your problem).
(2)
(a) "Did you check the Power Options in the Control Panel? I also turn on the Hibernate power option there."
I did indeed look there. Hibernate was fine, but the word "Sleep" no longer appeared. It wasn't just shaded -- it was gone! It appears Sleep mode is provided by my Intel(R) HD Graphics Family driver, & that Windows will only put it into menus & settings screens when it exists. That driver was installed & fully up-to-date, but there was a message in Device Manager (and occasionally at boot) that stated Windows would not start it due to compatibility problems. It didn't say so, but the incompatibility was with Windows Defender's Core Protection/Memory Integrity feature. Once I turned that off, a reboot was all that was necessary for the driver to "start". And all is back to normal.
(b) "Out of curiosity, have you tried turning it back on to see if there is/was a driver update that solved the problem?"
Yep, this is thrown into Action Center, at "Defender, Device Security, Core Isolation details" when I try to switch on Memory Integrity...
Then the Defender settings screen shows...
It's showing the same driver twice I guess because I tried to turn it on twice. I'm resigned to doing without it. Windows Defender still provides plenty of other protections.