Hi Xie Steven,
I understand that you are specifically trying to identify the Windows version or build in which this behavior first changed, rather than when WM_SETTINGCHANGE itself was introduced.
As mentioned in the existing answer, there does not appear to be publicly available documentation that identifies the exact Windows build that first started sending this notification in the undocking scenario you described. Since determining whether this is a Windows behavior change or regression would require deeper investigation beyond what can be verified through the community forum, I recommend contacting Windows Developer Support.
Microsoft provides technical support options there for Windows SDK and application development issues. When submitting your request, it would be helpful to include the affected Fujitsu models and Windows builds you listed here, as well as the last known Windows build where the behavior did not occur, if you have that information. This should give the support team a clearer regression boundary to investigate.
I hope this helps point you to the appropriate team for a more definitive investigation. Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. My role is limited to providing technical guidance on reported issues, requests, or ideas.
I know this isn't the news you were hoping for, but I wanted to make sure you got the most accurate information about your situation. Thank you so much for your understanding.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.