After installing Win 7 update(2017-06 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4022719), maybe not limited to this), minimized window cannot pop up to the top layer RRS feed

  • Question

  • I am from National Insruments, we have a software product called Lookout, when we install the update 2017-06 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4022719), there is a problem for window to pop up.

    In our software, there is a control panel(panel 1), in panel 1,there is a button(button1) which is connected to another control panel(panel2).

    If we click button1, panel can pop up. Before we install the update, the normal action is panel can pop up on the top layer, which can been seen in the following picture.

    But after we install the ipdate, the phenomenon is strange, when clicking button2, panel 2 can pop up, but under panel1, we have to click on the button for another time, then panel 2 can show up in the front, this phenomenon is not expected.

    I wonder if there are some changes causing this reaction. For example, modifying register key of fixed value of windows parameters , anyone has any ideas or recommendations?

    • Edited by Everestbovey Wednesday, June 21, 2017 6:24 AM
    • Moved by Xavier Xie-MSFT Thursday, June 22, 2017 1:38 AM not uwp development issue
    Wednesday, June 21, 2017 6:16 AM

All replies

  • Hi Everestbovey,

    Thanks for your posting.

    Since your question was not related to UWP development, it’s out of the scope for this forum. You’d better post a new thread on MS answer site:

    You would get better support there. Thanks for your understanding. 

    Best Regards,

    Xavier Eoro

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Thursday, June 22, 2017 1:38 AM
  • Hi,

    we have found that the error may located to after sending the message "WM_MIDRESTORE", and this message is handled by the function "DefMDIChildProc function", which is defined in user32.dll, so we doubt the update changed something in the function "DefMDIChildProc function", I think this problem is related to development, can you help to look into this problem?

    Monday, June 26, 2017 2:45 AM
  • Also, we want to replace the user32.dll with the original one to validate our doubt, but it seems there is no way for us to do this, do you have any recommendations?
    Monday, June 26, 2017 2:51 AM