My app calls DeviceInformation.CreateWatcher() with DeviceInformationKind.AssociationEndpoint. After the watcher is started it returns endpoints with System.Devices.Aep.ProtocolId set to known protocols such as UPnP {0e261de4-12f0-46e6-91ba-428607ccef64} WSD {782232aa-a2f9-4993-971b-aedc551346b0} DNS-SD {4526e8c1-8aac-4153-9b16-55e86ada0e54} And this, which isn't documented anywhere - {9f73fafd-2343-4bf9-a532-ad20e2674bea} What protocol is that?

I think I found it. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Device Association Framework\InboxProviders\ contains all the protocols listed here: https://github.com/MicrosoftDocs/windows-uwp/blob/docs/windows-apps-src/devices-sensors/enumerate-devices-over-a-network.md#enumerating-devices-over-networked-or-wireless-protocols Plus several more, including IPP, that contains a protocol ID=9f73fafd-2343-4bf9-a532-ad20e2674bea. So it must mean the endpoint is an IPP printer.

Unknown protocol ID returned from DeviceInformation.CreateWatcher

Anonymous

My app calls DeviceInformation.CreateWatcher() with DeviceInformationKind.AssociationEndpoint. After the watcher is started it returns endpoints with System.Devices.Aep.ProtocolId
set to known protocols such as

UPnP {0e261de4-12f0-46e6-91ba-428607ccef64}
WSD {782232aa-a2f9-4993-971b-aedc551346b0}
DNS-SD {4526e8c1-8aac-4153-9b16-55e86ada0e54}

And this, which isn't documented anywhere -

{9f73fafd-2343-4bf9-a532-ad20e2674bea}

What protocol is that?

Roy Li - MSFT 32,051 Reputation points Microsoft Vendor

2022-06-08T03:08:32.977+00:00

Could you please share more detailed information about this? It will be better if you could share the code that you are using. Also, could you please tell me what device you are using for testing protocol ID?
Anonymous

2022-06-08T19:12:35.407+00:00
string[] properties = new[] { _deviceAddress, _category, _manufacturuer, _nameDisplay, _protocolId, _aepContainerId, _aepId, }; _deviceWatcher = DeviceInformation.CreateWatcher("", properties, DeviceInformationKind.AssociationEndpoint); _deviceWatcherHelper.StartWatcher(_deviceWatcher);

Where _protocolId is "System.Devices.Aep.ProtocolId". The device of interest is a printer for which I get:

0e261de4-12f0-46e6-91ba-428607ccef64 - Yes, the printer supports UPnP protocol

782232aa-a2f9-4993-971b-aedc551346b0 - Yes, the printer also supports WSD protocol

9f73fafd-2343-4bf9-a532-ad20e2674bea - ?? - undefined

System.Devices.Aep.DeviceAddress for (3) is http://192.168.x.x:631/ipp/print, which corresponds to what we would expect from DNS-SD, but in that case the protocol id should be 4526e8c1-8aac-4153-9b16-55e86ada0e54
Roy Li - MSFT 32,051 Reputation points Microsoft Vendor

2022-06-09T08:15:05.473+00:00

Could you please tell me what printer you are using? Also, do you have other printers to test?
Anonymous

2022-06-09T16:30:55.983+00:00

Using:
Canon G5000 Series
Canon G6000 Series
Canon TS9000 Series
Canon MF240 Series
All of these support both WSD and IPP printing.

1 answer

Anonymous

2022-06-11T00:58:07.337+00:00

I think I found it. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Device Association Framework\InboxProviders\ contains all the protocols listed here:

https://github.com/MicrosoftDocs/windows-uwp/blob/docs/windows-apps-src/devices-sensors/enumerate-devices-over-a-network.md#enumerating-devices-over-networked-or-wireless-protocols

Plus several more, including IPP, that contains a protocol ID=9f73fafd-2343-4bf9-a532-ad20e2674bea. So it must mean the endpoint is an IPP printer.
Please sign in to rate this answer.
Roy Li - MSFT 32,051 Reputation points Microsoft Vendor

2022-06-13T01:54:35.507+00:00

Glad to hear that. It's really appreciated to share the information here. Having a good day.
Sign in to comment