Poly Lens Control Service 5.1.2088 loads Terminal Services WMI provider every 60 seconds

[mickrussom]

Poly Lens Control Service 5.1.2088 loads Terminal Services WMI provider every 60 seconds

Product classification

• Product: HP Poly Studio Desktop App for Windows

• Application version: 5.1.0.1111

• Component: Poly Lens Control Service / LensService.exe

• Control-service version: 5.1.2088

• Device: Poly Savi W8220T / Savi 8200 Office Series

• USB hardware ID: VID_047F&PID_AC29

• Operating system: Windows 11 x64

• Reproducibility: 100 percent on the affected system

• Severity: Persistent event-log pollution and unnecessary WMI provider activation; device audio remains functional

Short form-ready description

On Windows 11, Poly Lens Control Service 5.1.2088, installed with Poly Studio Desktop 5.1.0.1111, triggers an approximately once-per-minute WMI provider-start cycle while the system and Poly Savi W8220T are idle. The principal provider is Win32_WIN32_TERMINALSERVICE_Prov from %SystemRoot%\system32\tscfgwmi.dll. A passive 600.4-second observation recorded 11 Event ID 5857 provider-start events, with a median interval of 60.2597 seconds and a projected rate of approximately 1,583 Event 5857 entries per day. Stopping Poly Lens Control Service stops the recurring pattern; starting it resumes the pattern. Removing the old Plantronics Hub, uninstalling/reinstalling Poly Studio and Lens Control Service, and resetting Poly application state did not correct it. The headset and Windows USB/audio/HID drivers operate normally. Please escalate this to the Poly Studio/Lens engineering team as a reproducible background-service polling defect.

Full defect description

Poly Lens Control Service appears to perform an unconditional periodic WMI query approximately every 60 seconds. This repeatedly activates the Windows Terminal Services WMI provider and writes Event ID 5857 entries to Microsoft-Windows-WMI-Activity/Operational, even when Poly Studio, the computer, and the connected headset are idle.

The repeating provider is:

Provider     : Win32_WIN32_TERMINALSERVICE_Prov
ProviderPath : %SystemRoot%\system32\tscfgwmi.dll
Event ID     : 5857
Result       : 0x0

This is not a headset audio-driver failure. Windows recognizes the Savi 8200 base as a normal USB composite, HID, and USB audio device. Audio works. The issue is background behavior in the Poly Lens Control Service.

Steps to reproduce

1. Install HP Poly Studio Desktop 5.1.0.1111 and Poly Lens Control Service 5.1.2088 on Windows 11.

2. Connect a Poly Savi W8220T / Savi 8200 Office Series base by USB (VID_047F&PID_AC29).

3. Confirm that Poly Lens Control Service is running and that the device is detected by Poly Studio.

4. Enable or inspect Microsoft-Windows-WMI-Activity/Operational in Event Viewer.

5. Leave Poly Studio and the headset idle for at least ten minutes.

6. Filter the channel for Event ID 5857.

7. Observe Win32_WIN32_TERMINALSERVICE_Prov loading at an approximately 60-second cadence.

8. Stop Poly Lens Control Service and repeat the observation. The recurring Terminal Services provider-start pattern stops.

9. Start Poly Lens Control Service and repeat. The recurring pattern resumes.

No reboot is required to reproduce the service-off/service-on change.

Passive post-reinstall measurement

Observation started: August 22, 2026 18:33:05 local time
Observation ended: August 22, 2026 18:43:05 local time
Observation duration: 600.4 seconds

Results:

Event ID 5857 count                 : 11
Event ID 5858 count                 : 1
All WMI-Activity events             : 12
5857 provider-start bursts          : 11
Median interval between bursts      : 60.2596876 seconds
Projected all WMI events per day    : 1,727
Projected Event 5857 entries per day: 1,583

Event 5857 provider counts:

Count  Provider                           Provider path
-----  --------                           -------------
9      Win32_WIN32_TERMINALSERVICE_Prov   %SystemRoot%\system32\tscfgwmi.dll
1      WMIProv                            %systemroot%\system32\wbem\wmiprov.dll
1      ScheduledTaskProv                  %SYSTEMROOT%\System32\wbem\schedprov.dll

The event count per minute during the observation was:

18:33  1
18:34  1
18:35  1
18:36  2
18:37  1
18:38  1
18:39  1
18:40  1
18:41  1
18:42  1

The extra event at 18:36 was associated with a secondary provider; the Terminal Services provider itself followed the approximately one-minute cadence.

Service and process state

During the entire passive observation:

Service      : Poly Lens Control Service
Executable   : C:\Program Files\Poly\Lens Control Service\LensService.exe
Status       : Running
Startup type : Automatic
Process ID   : 27084

The service consumed almost no CPU during the ten-minute observation, but it continued to trigger the WMI provider lifecycle and associated Operational log entries.

Troubleshooting already completed

• Confirmed that Windows detects all USB composite, HID, media, microphone, and headphone functions with status OK.

• Confirmed normal audio operation through the Savi 8200 Office Series device.

• No legacy Plantronics Hub 3.xx present 

• Closed all Poly Studio, LegacyHost, LensDisplayManager, and LensService processes.

• Removed Poly Studio Desktop and Poly Lens Control Service without deleting Windows USB/audio/HID driver packages or INF files.

• Preserved/renamed prior Poly application state directories so the reinstall would start with clean state.

• Installed a fresh copy of Poly Studio Desktop 5.1 and Lens Control Service.

• Confirmed that the Savi device is detected and functional after reinstall.

• Repeated the ten-minute passive WMI observation after the clean reinstall.

• Confirmed that the approximately 60-second pattern remains.

• Performed a service A/B test: the recurring pattern disappears when Poly Lens Control Service is stopped and returns when the service is started.

These results make stale Plantronics Hub components, corrupt application state, Windows audio drivers, and the physical headset unlikely causes.

Expected behavior

An idle device-management service should not repeatedly load the Terminal Services WMI provider every minute. Session-state changes should preferably be event-driven. If polling is unavoidable, the result should be cached and the interval should be substantially longer, without repeatedly creating WMI provider-start events.

Actual behavior

While Poly Lens Control Service is running, it causes a consistent approximately one-minute WMI provider-start pattern, dominated by Win32_WIN32_TERMINALSERVICE_Prov. This produces roughly 1,300 Terminal Services provider-start entries per day and approximately 1,583 total Event 5857 entries per day on this system.

User impact

• Pollutes the WMI Operational log with approximately 1,500 provider-start events per day.

• Reduces the signal-to-noise ratio for actual WMI troubleshooting and security review.

• Causes unnecessary WMI provider activation on an otherwise idle workstation.

• Forces the user to stop the Lens service or run Poly Studio only on demand to keep the event log clean.

• Makes long-uptime systems accumulate large volumes of non-actionable telemetry.

This is not being reported as a high-CPU or audio outage issue. It is a deterministic service-design or polling defect with operational and diagnostic consequences.

Requested engineering action

Please escalate this report to the HP Poly Studio Desktop / Lens Control Service engineering team and:

1. Identify the LensService operation that queries Terminal Services state every approximately 60 seconds.

2. Replace periodic WMI polling with an event-driven Windows session notification mechanism where possible.

3. Otherwise cache the session state and substantially increase or back off the polling interval.

4. Avoid repeatedly unloading/reloading the Terminal Services WMI provider.

5. Provide a supported option to disable continuous background monitoring while retaining on-demand device configuration.

6. Add the defect and tracking identifier to the Poly Studio Desktop known-issues or release-notes page.

Please provide the internal defect/tracking ID and identify the Poly Studio/Lens Control Service version targeted for correction.

Attachments

Primary attachment:

POLY_WMI_POST_REINSTALL_20260822-183305.txt

The transcript contains the complete ten-minute passive observation, service/process state, provider counts, periodicity calculation, and start/end timestamps.

Additional evidence is available

• Service stopped versus service running A/B observation

• Windows Plug and Play inventory for VID_047F&PID_AC29

• Signed-driver inventory

• Poly application and service installation inventory

• Poly Studio/LegacyHost logs

.

[SteffenBaierUK]

Hello @mickrussom ,

Welcome to the HP Poly community.

This is just a Peer-to-peer community forum and not HP Poly Support. We are all just Volunteers.

If no other volunteers reply, I suggest you contact the HP Support organization in your region. Details are in my Signature.

If this is not possible, please open a Lens Mopinion Bug via https://lens.poly.com/appfeedback

Best Regards

Steffen Baier