To workaround this issue you should dispose the Instance property of RadMessageBox after each show of message box. For example:

WORKAROUND: 
RadMessageBox.Show("Text");
RadMessageBox.Instance.Dispose();

If you are using themes, consider the following approach:
            RadMessageBox.SetThemeName("Windows7");
            RadMessageBox.Show("This is some long text that sometimes does not wrap as it should.");
            var field = typeof(RadMessageBox).GetField("radMessageBoxForm", BindingFlags.NonPublic | BindingFlags.Static);
            field.SetValue(null, null);

To reproduce:
Add a RadForm and set its icon property. You will notice that the Form's icon is changed but it is not in the taskbar.

On Windwos XP , Windows Vista, Windows 7 the RadForm/ShapedForm hides the taskbar when it is set to Auto-Hide. When you try to show the taskbar it appears behind (under) the RadForm instead of infront (over) it.

1. Create a new Form that inherits from RadForm and add some rad controls.
2. Checkin the file in your source control system
3. Open the form in design time will cause checkout

When you set the FormBorderStyle property to FormBorderStyle.None, the form size defined initially is changed.

Setting the RightToLeftLayout to true together with RightToLeft = Yes, cuts off the form

it seems to be when I'm deriving from RadForm the NotifyPropertyChanged Doesn't seem to work

It is binding to the Text Propery of the dockwindow. what i am trying to do is bind to a propery of my class called FormText (This is not the Frm.Text but Frm.FormText) a completly diffrent property. This is not possible to do with the below code.

What I am ultimelty trying to do is have a class that is derived from RadForm so i can add a BindingSource to the form and load it with data.
I'm then trying to bind to the Possition and Item Count fo the BindingSource to show the user what record/how many records there are.

I need to re-bind this each time the tab is changed so the user is always seeing the records for the Selected form

Resolution: 
Scenario is not common and the issue is not related directly to our form. Since our RadForm is ISupportInitialize and in the case that the developer does not call Form EndInitialize method the Microsoft binding will reject the binding because Form IsInitialized property is false. So these methods must be called:
((System.ComponentModel.ISupportInitialize)(radForm1)).BeginInit();
((System.ComponentModel.ISupportInitialize)(radForm1)).EndInit();

To reproduce:
- Set the StartPosition to CenterScreen
- Show the form on a HDPI monitor

Workaround:
var form = new RadForm();

float dpiX, dpiY;
Graphics graphics = this.CreateGraphics();
dpiX = graphics.DpiX /100;
dpiY = graphics.DpiY /100;

form.StartPosition = FormStartPosition.Manual;
var monSize = Screen.FromControl(this).Bounds;
var centerX = (monSize.Width / 2) - (form.DesktopBounds.Width * dpiX / 2);
var centerY = (monSize.Height / 2) - (form.DesktopBounds.Height * dpiY/ 2);
form.Location = new Point((int)centerX,(int) centerY);
form.Show();

To reproduce:

1. Create a new .NET 7 project and add a RadForm to it with a single control (e.g. RadButton).

2. Open the designer and have a look at the form's Size.

3. Move the button and save the changes

4. Close the designer and open it again.

Expected result: the RadForm's Size is unchanged

Actual result: the RadForm gets smaller, its height is reduced.

To reproduce:
- Create a new form.
- Change the Localizable property to true.
- Add a RadLabel to the form.
- Select the label and change its name to "name with space" and press Enter.
- VS editor will say that it is an invalid name and return the name to previous value.
- Now look at designer.cs file of the form and you will see a lot of RootElement properties getting values form resource!

Same issue can be reproduced by localizing a custom control:
- Open UserControl.cs in Design mode.
- On property editor, change property Language from "(Default)" to "Portuguese (Brazil)".
- Now change a label text  to "Nome".
- See file EditUserControl.Designer.cs. It has many RootElement lines!

Workaround:
Delete the generated code and rebuild.

FIX. RadForm text flickers on change

To reproduce:
- Create a RadForm with a public label in it. 
- Inherit the new form and change the label text.
- Open the second form at design time - the file status is changed to modified.

FIX. RadRibbonForm - setting the FormBorderStyle property does not take effect

1. Create RadRibbonForm and add code to start maximized 
2. Add status strip with some items on the ribbon form 
3. in the form constructor create a MDI child form, set it to start maximized and show it 
4. The result is that there is gap between the child form and the status strip

Workaround:
protected override void OnShown(EventArgs e)
{
    base.OnShown(e);
 
    this.WindowState = FormWindowState.Minimized;
    this.WindowState = FormWindowState.Maximized;
}

When RadMessageBox has not owner and it is using in form that has TopMost = true throws exception after first call of RadMessageBox.Show()

Steps to reproduce:

1.Create From with TopMost  = true

2. Add button and insert the following code in press event:
RadMessageBox.Show("Text");
3.Run application and press the button two times.

Workaround after each show of RadMessageBox add this code snippet:
RadMessageBox.Instance.Dispose();

A possible workaround is to set the RadControl.EnableDpiScaling property to false.
static class Program
{
    /// <summary>
    /// The main entry point for the application.
    /// </summary>
    [STAThread]
    static void Main()
    {
        RadControl.EnableDpiScaling = false;

        Application.EnableVisualStyles();
        Application.SetCompatibleTextRenderingDefault(false);
        Application.Run(new RadForm1());
    }
}

Another workaround is to mark the application as DPI-aware: https://docs.telerik.com/devtools/winforms/telerik-presentation-framework/dpi-support

Workaround: set the RadRibbonFormBehavior1.AllowTheming property of the form to false

public class RadForm1
{
	public RadForm1()
	{
		InitializeComponent();

		this.RadRibbonFormBehavior1.AllowTheming = false;

	}
}

The controls inside the form are not scaled correctly when the Form is shown on a monitor with DPI higher than 150%. An important step here is that the main monitor where the form is shown has a higher DPI. Moving the form from a monitor with 100% to a monitor with a higher DPI will not reproduce this behavior.

How to reproduce: set the Size property of the form in the designer of Visual Studio, pay attention to the serialized ClientSize value. Run the form and check the ClientSize, it has increased

Workaround: 
public partial class Form2 : RadForm
{
    public Form2()
    {
        InitializeComponent();
        Padding p = TelerikDpiHelper.ScalePadding(this.FormBehavior.ClientMargin, new SizeF(1f / this.RootElement.DpiScaleFactor.Width, 1f / this.RootElement.DpiScaleFactor.Height));
        this.MaximumSize = new Size(this.Size.Width - p.Horizontal, this.Size.Height - p.Vertical- this.FormBehavior.ClientMargin.Bottom + this.FormElement.TitleBar.Size.Height);
    }

    protected override void OnShown(EventArgs e)
    {
        base.OnShown(e);

        this.MaximumSize = new Size(0, 0);
    }
}

When the RadForm is used as MDI Child hosted by RadDock, the rendering of the form is not appropriate.