Did :/

It won't show the firewall status if it's unable to connect or contact another host.
hmm, that sounds like it's a rule set up for limewire. Do you think that's what the LimeXXXD represents?
If it were a port forward rule then a new one would need to set for WireShare.
Router rules set up for specific ports or applications can only be used for a specific computer on the network and only one specific program (a different port for each program.) A new rule needs to set for each program. Not too different to the Windows Firewall approach.

LimeXXXD - I replaced TCP and UDP with XXX. Here's how it shows up.
Note: it's not there by default - it only shows up when WireShare is running. I can do a test and set it manually for WireShare if you think it will make any difference but previously it was running on UPnP, I didn't touch the router's settings.

Yes it might simply be the name of the rule rather than the application.

Have you checked your internal ip address to be sure you are actually running on the one listed? However as you said, if it only shows if WireShare is running then sounds like that part is fine.
A quick google: (1) Click the Start icon and select Settings. (2) Click the Network & Internet icon. (3) To view the IP address of a wired connection, select Ethernet on the left menu pane and select your network connection, your IP address will appear next to "IPv4 Address".

Perhaps try changing the port number you have listed in those rules. Also change it to the same port in WireShare's settings. Perhaps change to a port number in the 30000 or 40000 or 50000 range.

I can tell you from experience if any other program has run using the same port forwarded port earlier in the same computer session, then the router will make that port unavailable for any other program. (My suspicions you might have run LimeWire, etc. using same port prior to running WireShare.)

Note: I'm no doubt in a different timezone and might need to continue discussing this later if the problem is not solved. Super late here now.

Checked the IP Address, it's the same. Checked port in WireShare, same. I noticed the port changes every time you install/reinstall WireShare so I'm pretty sure that's not the culprit, I can do a test and change it and also make the manual forwarding rule.

Tested the manual port forwarding - no difference, and it doesn't link to a specific application, just IP address. The UPnP tab just shows which app is using that port so probably the name is hardcoded into WireShare (they didn't bother to change it or something)
Still no go...I can't for the life of me figure out what might have happened. The only thing that changed, basically, is Windows, so I'm pretty sure this is OS related.

Your experience has taught me a little (re: UPnP.) Windows is not my primary OS and only use it for testing.

Sometimes a reboot can help. That's as long as it does not affect anything else you are doing on the computer.

Is port forwarding out of the question? Just a suggestion. I always port forward my p2p apps because it's far more reliable for long sessions.

As far as I know, Windows does have a habit of resetting some security settings to default during updates (including some firewall settings.) Have you checked Windows Defender or that another security app is not blocking WireShare to the outside world? Re-check any system setting that might possibly affect WSHR.

Talk later, I'm off to bed for now.

Thanks for your help.
Port forwarding is not out of the question but I did test it (manually set up port forwarding) and there is no change.
I checked the firewall settings again and again, everything is at it should be :/

Did you have any luck?

I did some kind of update for Win 10 and then installed WireShare. I had the identical problem with no hosts showing in advanced window. I set up port forwarding, added WSHR to the Windows firewall exceptions. I don't know why but the only thing that appeared to fix it was to go to the WireShare program folder & set the properties of WSHR to open as Admin. This then set the program to connect and non-firewalled. However you said you installed WSHR with admin permissions which should be the same thing. Perhaps you can re-check this.

Will give it a try and post update.
EDIT: Okay, here's an interesting take - I tried a previous version of WireShare (5.6.4.2) and it worked straight out of the box, no firewall exception needed, no run as administrator, nothing, just install and run - worked. I thought about trying this earlier but I couldn't find previous versions for some reason, but now when I checked the Google Drive link, I noticed there were 2 previous versions available so I gave it a try.
Any idea why this one works out of the box and 5.6.6 doesn't?
I tried what you suggested with the version and setup I had from yesterday but it didn't work. Firewall exceptions were added (both outgoing and incoming), I changed the default listening port and made sure it was being forwarded from the router, I ran the program as an administrator after which I set its properties to always open as administrator...still nothing. I thought that maybe something was off with the installation so I thought I should redownload the installer from a different source and start clean - that's when I came about the older versions.
Below you have the advanced tools coonections that are showing up right now, does everything look good to you?