Windows 10: we can't connect to Microsoft family at the moment

is anyone seeing this message in red text about not being able to connect to family at the moment in settings. For past few days I am seeing this come up on occasion, it often goes away after a short while and is pretty infrequent but I reckon I have seen it about 5 or 6 times in the last few days. It makes me think its a server side issue and whilst it doesn't seem to be having an adverse effect it's slightly annoying. This is an anniversary updated pc, not yet offered creators update but it never used to do this until recently and there have been no updates of late

:)

 

We can't connect to Microsoft Family at the moment

Sending screenshots would be a useful feature for the forum.

Update diagnostics errors

PacjageID: WindowsUpdateDiagnostic

Error Code: 0x803C0103

Source Engine

Context: Elevated

Family Error

We cant connect to Microsoft Family at the moment so your family on this device might not be up to date

No Code

 

We can't connect to Microsoft Family at the moment

I spent last two days searching for a solution and I actually have a workaround:

At home I have 2 networks: 1 for family and 1 for visitors

Family network uses its own SSID and ethernet cable, visitors has its own SSID.

Family net have this configuration (this is the type of configuration everybody has in their houses):

Gateway: 10.0.0.1

DNS: 10.0.0.13 (it is a raspberry pi)

Netmask: 255.255.255.0

Visitors net have this one (this is a bridged network isolated from the 1st one):

Gateway: 10.0.2.1 (this os the same device as the previous one, but with VLAN)

DNS: 8.8.8.8

Netmask: 255.255.255.0

That said, connecting to the family network (WiFi or cable) always I have "can't connect to ms family network", but like magic if I use the visitors network, everything works perfectly. Oh, don't think it is related to DNS server because it is not, I tested
hundred times with the same google DNS server (8.8.8.8) and with others like Microsoft and so...

So I would suggest try to connect to another network or try to change IP range of your local network.

cheers,

Adriano Krauthein