Windows File and Folder Sharing fails with Multiplicity running

Windows Sharing stops with Multiplicity

Hi

Having issues with Windows File Sharing. I have called Microsoft Support to help and we have found that if you load Multiplicity the File and Folder sharing fails to work i.e. the shared folders do not appear in Explorer. Removing Multiplicity allows Sharing to work.

I'd welcome ways to overcome this snag, please.

Thanks

Nik

2,933 views 4 replies
Reply #1 Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

Reply #2 Top


if you load Multiplicity the File and Folder sharing fails to work i.e. the shared folders do not appear in Explorer.
End of quote

Fails to show on the local PC or a remote viewer?  Also, fails to show them at all or that they are shared?

I see no issue locally:

I also tested that another PC \ person I shared it with could see and access it (they, the remote did not have MP installed, however).

Sean Drohan
Stardock Support Manager

Reply #3 Top

Hi

Sorry to say that testing this again today  the Windows File and Folder Sharing was working without KVM3  - then loaded Multiplicity KVM3 -  rebooted and subsequently lost the shared folders ICONs on both PCs in Explorer. Deleted Multiplicity and they appear again!

I have checked Norton and Multiplicity is "allowed"  on both PCs = I cannot see why this is happening as the programme has been running OK for a long time. But I now have a need to file share between the two PCs as a priority which currently means that I cannot use Multiplicity which is a great shame.

Maybe it works on your PCs but not on mine. Yesterday, the Microsoft Tech support reckoned that Norton was to blame but we re checked this, and Multiplicity as well,  Norton was found to be OK but not Multiplicity... :( Checked again this morning still the same...

My spec - Windows 10 Home 21H2 (19044,1566)  used for  Gaming

As a suspicion - I checked the Services and found that Function Discovery Provider Host was not running ....(although this is set to Automatic) still checking this out as I write...

Any assistant would be gratefully received.

Nik

 

Reply #4 Top

The closest we could likely come to finding the culprit is a 'scotched earth' attempt - a clean boot under a brand new Win admin account on each PC - meaning, it would reduce the 3rd party influences (settings, accounts, and apps) to a minimum in an effort to see if the issue still exists...

https://forums.stardock.com/486104/multiplicity-support-faq#cleanboot

Sean Drohan
Stardock Support Manager