Which OS version the system started pushing this WM_SETTINGCHANGE window message

Xie Steven 831 Reputation points
2026-11-17T09:09:16.9733333+00:00

When our app runs on a tablet, it is displayed in full-screen mode. The tablet comes with a docking station, and users can detach the tablet from the dock during use. Recently, due to changes in a specific OS version, the system pushes a WM_SETTINGCHANGE window message when the tablet is detached from the dock, causing our full-screen app to exit full-screen mode.

The known devices and OS versions affected by this issue are as follows:

  • Fujitsu FMVQ01011 STYLISTIC Q7312/NB Windows 11 Pro 25H2 (Build 26200.7171)
  • Fujitsu FARQ23001 ARROWS Tab Q739/AB Windows 11 Pro 26H2 (Build 26300.9457)

I would like to know from which OS version the system started pushing this WM_SETTINGCHANGE window message.

Windows development | Windows API - Win32

1 answer

Sort by: Most helpful
  1. Gatlin Le (WICLOUD CORPORATION) 1,475 Reputation points Microsoft External Staff Moderator
    2026-11-17T10:54:18.09+00:00

    Hi @Xie Steven ,

    Microsoft documentation doesn't specify which Windows version or build first sent this notification when a device is undocked, and I haven't found a public Microsoft source that identifies one. The GetSystemMetrics function reference describes the behavior without a version: when SM_SYSTEMDOCKED changes, the system broadcasts WM_SETTINGCHANGE with "SystemDockMode" in lParam, and when SM_CONVERTIBLESLATEMODE changes, it uses "ConvertibleSlateMode".

    I also ran a test on Windows 11 Pro 26H2, build 26300.9457. The environment was a virtual machine with one 1920x1080 display at 96 DPI. I used two minimal borderless full-screen test windows: a Win32 window that passes every message to DefWindowProcW, and a .NET Framework 4.8 WinForms window that uses its default WndProc handling. To avoid affecting other applications, I didn't broadcast the message. Instead, I sent WM_SETTINGCHANGE with SendMessageW only to each test window. I used these payloads: lParam set to NULL, "SystemDockMode", "ConvertibleSlateMode", wParam set to SPI_SETWORKAREA with a NULL lParam, and a burst of 20 alternating "SystemDockMode" and "ConvertibleSlateMode" messages. I ran each case three times on each window.

    Across the 30 runs where I sent messages, I didn't observe either window leaving full screen during the roughly 1.5 seconds I monitored each run, and the windows received all 264 messages I sent. I also resized the windows on purpose as a control, and my check flagged each of those as no longer full screen. Please note that this was a simulated message test on a VM. It wasn't a physical undock on a Fujitsu tablet and didn't use your application, so it doesn't confirm or rule out the behavior you're seeing, and it doesn't identify the first Windows version involved.

    I realize that results from both of the builds you listed would give you a much clearer comparison. I ran this test on build 26300.9457, the 26H2 build from your list, but I wasn't able to cover 26200.7171 in my environment as well, so the results above describe only what I observed on build 26300.9457.

    I understand that a clear version boundary matters when you're supporting users on these devices. What I can share in this thread is limited to public documentation and what I observed in my own testing, and I don't have access to Windows build history or internal change records. For a definitive answer on whether a specific Windows build changed this behavior, Windows Developer Support is the right channel, because they can investigate it at the product level.

    I hope the documentation and test results above help narrow things down on your side. If this helps clarify what is and isn't documented for this undock scenario, I'd appreciate it if you could take a moment to follow the steps in this guidance, so others with a similar scenario can find this information more easily.

    Thank you.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.