Thank you for the replies.
Anything under a work is always a good news.
Removal about everything? Well, probably Fireshock. Since right click and uninstall and delete driver on bluetooth dongle will resulting on factory default after a reboot. And Shibari service removal, probably I could search google how to remove a service but it's nice to have.
@daltz333 OMG thank you!! It finally works again. I tried installing this one before but got an error as well, no idea if I did something wrong or something in my pc changed but now it worked. My antivirus seemed to put the 'Shibari.Dom.Server' in quarantine when I fired it up again to enable automatic startup but it seems fine now, and I can easily restore it if needed
Without HidGuardian and with a clean set of drivers I'd mentioned earlier, I've continued to fiddle with other things that required many reboots today. So far, I'm relatively happy to report that Exclusive Mode is achieved about 80% of the time. Heck, maybe it's fixed for the most part since the last update to DS4Windows. Maybe I'll never know if it's just my machine, or what causes the intermittent problems. : p
You're welcome to try out x360ce alpha (hence the word "try"). You can map your controllers from your DS4 and it'll create a system-wide XBox360 controller. Parsec can then grab this XBox360 and create an XBox360 on the host system.
Download the latest x360ce alpha at: https://github.com/x360ce/x360ce/releases
Map your controllers in the x360ce alpha application.
Press the "enabled mapped device" button after configuring your mappings
Restart Parsec and attempt to connect the host machine
If you don't mind, please report back whether or not this is working for you. That way we can help out other users with the same problems.
This is third-party software and in alpha condition, it may or may not work. So goodluck!