FAQ – Why does the c-entron.NET interface freeze?

(As of: May 2026)

Available as a subscription: Core · Pro · Ultimate

Re:

🖥️ IT / Technology
⚙️ Administration

Question

Why does the c-entron.NET interface freeze and stop responding to input?

Short answer

If the c-entron.NET user interface freezes, it means the code is stuck in an infinite loop—almost always caused by third-party code (Microsoft or DevExpress). Common causes include a corrupted layout profile or a display scaling setting other than 100%.

Solution / Overview

Please check the following points:

Is the user using a custom layout profile? If so: Delete the layout profile from the database.
Is the monitor's display scaling set to anything other than 100% (e.g., 125% or 150%)? If so, set the display scaling to 100%.
Does the screen still freeze after deleting the layout profile? If so, check the display scaling.
Are the symptoms (missing, wobbly, or flickering elements) still occurring? Contact Support.

Background

The freezing of the user interface is usually caused by an infinite loop in third-party code (Microsoft or DevExpress)—and only very rarely by the actual c-entron code. This manifests itself as UI elements such as text boxes and buttons that are invisible, wobbly, or flickering.

Common Mistakes

Common causes or misunderstandings include:

The layout profile is damaged (corrupt) – this can cause an infinite loop, even if it is not immediately apparent.
The display scaling is not set to 100%—values such as 125% or 150% may or may not cause problems.
Simply restarting the application is expected to resolve the issue—though the underlying cause (profile or scaling) will remain.

Tip

After deleting the layout profile, a default profile will be created automatically the next time you launch the application. Try using this default profile first before configuring a new custom layout—this will help you quickly determine whether the profile was the cause of the issue.

Re: