diff --git a/WindowsForms/Radial-Menu/Getting-Started.md b/WindowsForms/Radial-Menu/Getting-Started.md
index 4dc04f508..f1b7e520d 100644
--- a/WindowsForms/Radial-Menu/Getting-Started.md
+++ b/WindowsForms/Radial-Menu/Getting-Started.md
@@ -53,6 +53,9 @@ Menu items can be added into RadialMenu using `Items` collection in Smart Tags o
 
 ![Adding Menu Items in windows forms radial menu](Getting-Started_images/RadialMenu-img3.png) 
 
+N> In .NET Core, when adding child items to a RadialMenuItem directly from the Visual Studio Properties window, the default Collection Editor opens instead of the expected editor.
+Workaround: Use the main RadialMenu Collection Editor to add items, then configure the child items as needed. A permanent fix is in progress.
+
 ## Adding control manually using code
 
 To add control manually in C#, follow the given steps:
diff --git a/WindowsForms/Status-Bar/Getting-Started.md b/WindowsForms/Status-Bar/Getting-Started.md
index 90dc87461..5de9b23c9 100644
--- a/WindowsForms/Status-Bar/Getting-Started.md
+++ b/WindowsForms/Status-Bar/Getting-Started.md
@@ -25,6 +25,9 @@ To create a StatusBarAdv control through designer,
 
    ![Run the application in WindowsForms-Status Bar](overview_images/windowsforms-status-bar-run-application.jpeg) 
    
+N> In .NET Core, the StatusBarAdv control’s Collection Editor displays the title “ControlProxy`1 CollectionEditor” instead of “StatusBarAdvPanel CollectionEditor.”
+This is a known issue and does not affect functionality.
+For more details, see GitHub Issue [#14049](https://github.com/dotnet/winforms/issues/14049)
    
 ## Through code
 
diff --git a/WindowsForms/Tree-Navigator/Getting-Started.md b/WindowsForms/Tree-Navigator/Getting-Started.md
index 3ef2fa243..e1dea38f7 100644
--- a/WindowsForms/Tree-Navigator/Getting-Started.md
+++ b/WindowsForms/Tree-Navigator/Getting-Started.md
@@ -165,4 +165,7 @@ The following steps allows you to add TreeMenuItem to the TreeNavigator through
    
 ![Adding the Items](Getting-Started_images/ThroughDesigner2.png)
 
-![TreeNavigator Output](Getting-Started_images/Adding_TreeMenuitems.png)
\ No newline at end of file
+![TreeNavigator Output](Getting-Started_images/Adding_TreeMenuitems.png)
+
+N> In .NET Core, when adding child items to a TreeMenuItem directly from the Visual Studio Properties window, the default Collection Editor opens instead of the expected editor.
+Workaround: Use the main TreeNavigator Collection Editor to add items, then configure the child items as needed. A permanent fix is in progress.
\ No newline at end of file
diff --git a/WindowsForms/Wizard-Control/Getting-Started.md b/WindowsForms/Wizard-Control/Getting-Started.md
index 7b8bb113b..f3f245d02 100644
--- a/WindowsForms/Wizard-Control/Getting-Started.md
+++ b/WindowsForms/Wizard-Control/Getting-Started.md
@@ -48,6 +48,10 @@ The [WizardControl](https://help.syncfusion.com/cr/windowsforms/Syncfusion.Windo
 
 ![Drag and drop the wizard control to form](Getting-Started_images/GettingStarted-img2.png)
 
+N> In .NET Core, the Wizard control’s Collection Editor displays the title “ControlProxy`1 CollectionEditor” instead of “WizardControlPage CollectionEditor.”
+This is a known issue and does not affect functionality.
+For more details, see GitHub Issue [#14049](https://github.com/dotnet/winforms/issues/14049)
+
 ## Adding control manually in code
 
 To add control manually in C#, follow the given steps: