in it was measured, not inferred; the method section is included because a reproducible report gets
triaged and a vague one does not.
—
**Title:** `HideMeetingInfoOnMeetingUI(true)` does not hide the meeting information panel — meeting ID
and passcode remain reachable from the top-bar chip
**SDK:** Meeting SDK for Windows 7.1.5.43953 (C# wrapper), .NET 10, Windows 11 26200
**Summary**
`IMeetingUIElemConfiguration::HideMeetingInfoOnMeetingUI(true)` hides only the encryption /
meeting-info shield indicator in the top right. The chip in the **top left** — the meeting name on a
licensed plan, “Meeting NN-Minutes” on a basic plan — is unaffected, and clicking it opens a panel
showing:
- invite link
- meeting ID
- passcode
- host
- participant ID
- numeric (telephone) passcode
For an application that must not display meeting credentials, this makes the setting ineffective:
the credentials are two clicks away with the setting enabled.
**Expected**
`HideMeetingInfoOnMeetingUI(true)` prevents the meeting information from being displayed, or an API
exists to suppress that panel.
**Actual**
Only the shield indicator is hidden. The panel remains reachable.
**Reproduction**
1. `Initialize` + `SDKAuth`.
2. Before joining, on the meeting configuration:
`HideMeetingInfoOnMeetingUI(true)`, `DisableFreeMeetingRemainTimeNotify(true)`,
`HideUpgradeFreeMeetingButton(true)`.
3. Join a meeting.
4. Click the chip at the top left of the meeting window.
The panel appears with the fields listed above.
**How this was measured** (so the finding is not a matter of interpretation)
Two runs differing in exactly one flag, each captured with `PrintWindow(hwnd, hdc, 2)` against the
SDK’s meeting window (`ConfMultiTabContentWndClass`), then compared pixel by pixel:
| Region | `HideMeetingInfo` on vs off | `DisableFreeMeetingRemainTimeNotify` true vs false |
|—|—|—|
| top-left chip | identical | identical |
| encryption/meeting-info shield | **differs** | identical |
So the setting demonstrably works — on the shield — and nothing reaches the chip. Both polarities of
`DisableFreeMeetingRemainTimeNotify` were tried, since the parameter is named `bDisable` while the
documented default is FALSE, and because `EnableInviteButtonOnMeetingUI` is inverted in the same
interface. It is not a polarity issue.
**Confirmed on both plan types.** Initially this looked like a basic-plan artefact, because the chip
shows the 40-minute countdown there. On a **licensed** account the chip shows the meeting name and
opens the same panel, so it is not plan-specific.
**Other APIs tried, none of which help**
- `SetMeetingTopic` — accepted (`SDKERR_SUCCESS`) but did not change the chip’s label on a
40-minute-limited meeting; the countdown appears to take precedence. It is also documented as
affecting “the meeting information page” rather than hiding it.
- `HideUpgradeFreeMeetingButton`, `DisableFreeMeetingRemainTimeNotify` — no observable effect on the
chip.
- Every header was searched for `info`, `topic` and `title`: `HideMeetingInfoOnMeetingUI` and
`SetMeetingTopic` are the only relevant methods in the SDK. `IMeetingUIController` can hide chat,
toolbars, the participants list and the join-audio dialog, but not this panel.
**Questions**
1. Is there a supported way to hide the meeting information panel in the default UI? If not, can one
be added — for example extending `HideMeetingInfoOnMeetingUI` to cover the panel, or a
`HideMeetingInfoPanelOnMeetingUI`?
2. Is the top-left chip’s behaviour with `HideMeetingInfoOnMeetingUI(true)` intended? The method name
and the documented description (“visibility of meeting info button”) suggest it should cover it.
3. Is custom UI mode (`ENABLE_CUSTOMIZED_UI_FLAG`) the only supported route today?
**Secondary issue, same SDK version** (worth reporting separately if preferred)
`sdkExt.dll` faults with `0xC0000005` on application shutdown, reproducibly — 13 occurrences in one
afternoon of testing, every time the app was closed while or after being in a meeting. The process
crashes rather than exiting cleanly. Faulting module `sdkExt.dll 7.1.5.43953`, fault offset
`0x1afcb0`.
**Two wrapper omissions, unrelated to the above but worth fixing**
The C# wrapper does not project methods that exist natively and are already generated by the SDK’s own
intermediate C++ wrap layer, so they are unreachable from C#:
- `IMeetingUIElemConfiguration::HideShareButtonOnMeetingUI` — declared six lines below
`HideMeetingInfoOnMeetingUI` in the same interface, and generated in
`meeting_configuration_wrap.{h,cpp}`, but absent from `meeting_configuration_dotnet_wrap.{h,cpp}`.
- `IMeetingUIController::SetMeetingTopic` — generated in `meeting_ui_ctrl_wrap.{h,cpp}`, absent from
`meeting_ui_ctrl_dotnet_wrap.{h,cpp}`. Likewise `IMeetingService::CanSetMeetingTopic` /
`SetMeetingTopic`.
Both were added locally in three lines each, following the file’s existing pattern, and work as
documented. It would be preferable not to maintain a patched vendor wrapper.