Uploaded image for project: 'Communication Studio'
  1. Communication Studio
  2. COMSTUDIO-492

ComStudio Error When Saving Projects with Microsoft Defender Controlled Folder Access Enabled

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: V2.0.109
    • Fix Version/s: V2.0.202, V2.1
    • Component/s: None
    • Labels:
      None
    • Account:
      SUI Communication Studio 1 (operative) (SUICOMMUNI)

      Description

      When Microsoft Defender's Controlled Folder Access (CFA) is enabled on Windows 11, the Documents folder is protected by default. ComStudio uses the Documents folder as the default location for saving project files  (e.g. C:\Users\<user>\Documents\CommunicationStudio).

      Because of this, Microsoft Defender blocks ComStudio from creating or writing project files in the protected Documents folder. The user sees a warning popup and ComStudio closes unexpectedly — which appears to be an application error from the user's perspective.

      Reproduction Steps

      1. Ensure Microsoft Defender Controlled Folder Access is enabled on Windows 11.
      2. Launch Communication Studio.
      3. Create a new project — the default save path points to the Documents folder.
      4. Attempt to save the project.
      5. A error  depending on Microsoft Defender behavior appears, and ComStudio closes.

      Verified Workarounds

      Two workarounds have been confirmed:

      1. Choose a different project folder during project creation — ComStudio works properly when saving to a location outside the protected Documents folder.
      2. Add ComStudio as an allowed app in Windows Security:
        • Open Windows Security → Virus & threat protection → Manage ransomware protection → Controlled folder access.
        • Under Allowed apps, add CommunicationStudio.exe.

      Affected Functionality

      • Project creation and saving — all new projects that use the default Documents path.

      Proposed Improvements

      The following improvements were suggested for consideration:

      1. Improve the error message — provide a clearer, user-friendly warning that explains the cause (antivirus/tagged file) and suggests the workaround(s) at the point where the failure occurs, rather than letting the application close silently.

      References

       

        Attachments

          Expenses

            Activity

              Status Description

                People

                • Reporter:
                  DBock Daniel Bock
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: