Windows 10: Sharing via Workgroup suddenly stopped working; semaphore timeout

echo "Hello World!";

Got a new PC last month; all was fine for the first few weeks until yesterday when Win 10 (Enterprise) decided it couldn't access any shared workgroup folders - and that my other PCs couldn't access its own shared folders either. Now when I try to click a link to a shared folder on another PC, Directory Opus (eventually) gives me a semaphore timeout error. Windows Explorer does nothing. Network folder shows only my router. & When I'm trying to get in here via other PCs I just get the standard "not available" error I get as if it's switched off.

It is the "main" PC of the group, i.e. the one wired into the router. Other PCs (and my Android devices) can access other PCs shared folders.

I have already updated my Realtek drivers. Settings in Network and Sharing centre all OK. I have changed no other settings that should affect this. Internet access all OK.

Edit: have tried System Restore, to two different points. Still no way in or out on the workgroup folders. Homegroup is not an option for me BTW.

Still, Windows 10 is given away for nothing, isn't it.

:)

 

Error 0x80070079

Error 0x80070079: The semaphore timeout period has expired when access network share

 

My HP Spectre model: 13t-v000, Windows 10, 64-bit, v1709 with Intel Core i7-6500U Laptop gives error when doing System Image Backup.

My back up location is a partition drice at an external WD drive.

I don't have third party virus software.

I backup System Restore to this location before.

I tried System Image Backup as it told on this web site after a clean boot.

They didn't work.

Error says:

"The Backup Failed.

Windows backup encountered an error when accessing the remote shared folder.

Please retry the operation after making sure that the remote shared folder is available and accessible

(0x8078015B)

Additional Information:

The semaphore timeout period has expired. (0x80070079)"

I googled error numbers on internet end up with some information that doesn't work for me.

Is there any solution for this problem?

Thanks for any help...

 

Late Edit: I am using 1703, OS Build 15063.608

 

Solved: it was just that SMB1 was disabled. I know the risks of enabling SMB1, but it's a small home network and well-protected.

MS shouldn't have disabled it; I own my devices.