Dynamics AX 2012: Forms on opening hide behind in the back


In Dynamics AX 2012, when you open the forms,  you might see some of them open behind the other forms. User may get the impression that the form was never opened.  This happens if the form opened slowly;  a cold start, uniqueness of the data including large number of records or complexity of the form may cause the form to load up slowly.  The form hide behind the other form because of Windows’s ‘ForegroundLockTimeout’.

Doing the following changes to your system could fix this issue.  Since it involves changing a registry key in your system, take necessary precautions.

Create a Restore point before performing the steps below as a precaution.



1. Open registry>> Start>>Type regedit>>press enter.

2. Locate the key:

HKEY_CURRENT_USER\Control Panel\Desktop

3. On the right pane right click on the following key and select modify:

4. ForegroundLockTimeout

5. Select Base as decimal and then type 0 (zero) in the value data box and click on Ok.

6. Exit from registry and restart the computer.


Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows

Comments (10)

  1. Yogesh Kasat says:

    Thanks for info. Do we need to change it for all the user machines?

  2. Ray Bennett says:

    @Yogesh Kasat: Yes, this will need to be done on each machine which is running the AX client.

  3. Yogesh Kasat says:

    thanks Ray.. We tried these steps. but did not work, not sure what we could be missing.

  4. Rif says:

    Not working all the time for us also

  5. Not working for me either 🙁

  6. Andy Barnett-Picking says:

    We have also tried this and it didn't resolve it for our customer.

    However we have a working theory that that the problem manifests itself on clients running windows 7/Win2k3 Terminal server or earlier, since we are unable to reproduce our customer's problem on the MS Contoso system running win2k8. Perhaps the performance team can investigate this angle ?

  7. Andreas Synning says:

    We have the same problem. We are running AX-client as remote app on Windows 2012 terminal servers.

    Changing the register key didn’t fix it for us.

    Only Windows 7 users have this problem, Windows 8 user’s seems to be fine.

    But we found a workaround.

    Make sure that language bar is open and visible on the taskbar when the remote session is running.

    To do that:

    1. Let the user login with Remote Desktop to the terminal server

    2. Go into Control panels and Language

    3. Add at least one extra language.

    4. Go into Advanced settings

    5. Make sure that “Use the desktop language bar when it’s available” is checked

    6. Click on Options to the right

    7. In the options for the language bar make sure that ”Docked in the taskbar” is selected.

    8. Apply all settings and log out of the Remote Desktop

    9. Start the remote app again and the windows will behave normal again

  8. Luca says:

    Hi Andreas Synning,

    it is possible to suggest that the setting via GPO?

  9. Kevin DeVoe says:

    We are facing this same problem and the registry key change did not work.

  10. mac says:

    Registry changing did not resolve problem in my company. Adding extra language also not working (windows 2012 RDP, remote app on windows 10/8/7).

    Has anybody solved the problem?

Skip to main content