Windows 10 (v.1709) Networking Issue

2 Windows 10 computers on a home network (LAN) connected by a router;
they're both 64-bit; one is Home the other is Professional

Both are set to update automatically; are up to date; no special
configurations originating on this user's end

Previously no problems with Network[ing] on either station; each one could
see the other; could transfer files from one to the other

Now, apparently after the Windows Update to v.1709, the Network on both
computers recognizes each station as a 'Media Device' in the 'Media
Devices' category and does not recognize the stations as a computer in the
'Computers' category

The exception is that when only one of the stations is on and the other is
off, they will recognize themselves as a computer, NOT as a media device,
until the other is booted up, then it's back to the media device behavior

When I click the icon, it launches Windows Media Player, and then goes even
more wonkey until I exit

All other operations are normal and stable

*NOTE: I have searched. None of the web responses seem to apply, but then
again, these articles all seem to be responding to situations before v1709;
or combinations with different Windows releases (like XP, 7, 8.1, etc.)

It appears the problem may be widespread.

Any leads on a simple cohesive procedure to remedy this?

Thank you in advance.

Alexander Shofner-Geidt wrote:
2 Windows 10 computers on a home network (LAN) connected by a router;
they're both 64-bit; one is Home the other is Professional

Both are set to update automatically; are up to date; no special
configurations originating on this user's end

Previously no problems with Network[ing] on either station; each one could
see the other; could transfer files from one to the other

Now, apparently after the Windows Update to v.1709, the Network on both
computers recognizes each station as a 'Media Device' in the 'Media
Devices' category and does not recognize the stations as a computer in the
'Computers' category

The exception is that when only one of the stations is on and the other is
off, they will recognize themselves as a computer, NOT as a media device,
until the other is booted up, then it's back to the media device behavior

When I click the icon, it launches Windows Media Player, and then goes even
more wonkey until I exit

All other operations are normal and stable

*NOTE: I have searched. None of the web responses seem to apply, but then
again, these articles all seem to be responding to situations before v1709;
or combinations with different Windows releases (like XP, 7, 8.1, etc.)

It appears the problem may be widespread.

Any leads on a simple cohesive procedure to remedy this?

Thank you in advance.

https://answers.microsoft.com/en-us/...6ee6bcb?auth=1

"Then I read the answer of Ratandeep and compared the setting of

Windows Media Player Network Sharing Service

with another PC, I found that on normal PC, start type is set
to Manual, when PC in question is set to Automatic(Delay Start).

I stopped the service and set to Manual, problem solved.

I wondered why it's set to Automatic(Delay Start), though,
because I didn't use WMP on this PC at all.
"

It's possible that service has something to do with it.

One other user in the thread suggested there are some
GUIDs in the Registry associated with the issue as well.

Paul

"Paul" wrote in message news
Alexander Shofner-Geidt wrote:
2 Windows 10 computers on a home network (LAN) connected by a router;
they're both 64-bit; one is Home the other is Professional

Both are set to update automatically; are up to date; no special
configurations originating on this user's end

Previously no problems with Network[ing] on either station; each one could
see the other; could transfer files from one to the other

Now, apparently after the Windows Update to v.1709, the Network on both
computers recognizes each station as a 'Media Device' in the 'Media
Devices' category and does not recognize the stations as a computer in the
'Computers' category

The exception is that when only one of the stations is on and the other is
off, they will recognize themselves as a computer, NOT as a media device,
until the other is booted up, then it's back to the media device behavior

When I click the icon, it launches Windows Media Player, and then goes
even more wonkey until I exit

All other operations are normal and stable

*NOTE: I have searched. None of the web responses seem to apply, but then
again, these articles all seem to be responding to situations before
v1709; or combinations with different Windows releases (like XP, 7, 8.1,
etc.)

It appears the problem may be widespread.

Any leads on a simple cohesive procedure to remedy this?

Thank you in advance.

https://answers.microsoft.com/en-us/...6ee6bcb?auth=1

"Then I read the answer of Ratandeep and compared the setting of

Windows Media Player Network Sharing Service

with another PC, I found that on normal PC, start type is set
to Manual, when PC in question is set to Automatic(Delay Start).

I stopped the service and set to Manual, problem solved.

I wondered why it's set to Automatic(Delay Start), though,
because I didn't use WMP on this PC at all.
"

It's possible that service has something to do with it.

One other user in the thread suggested there are some
GUIDs in the Registry associated with the issue as well.

Paul

It's tied to "AutoPlay". For Win7 Control Panel Hardware and Sound
AutoPlay to see that WMP is joined at the hip with AutoPlay for all media
and devices.

Bob S.