Electron Process Execution Failure with FSLogix

 

Technical Note: Electron Process Execution Failure with FSLogix

1. Overview

When running Electron-based applications in environments using FSLogix Profile or Office Containers, users may encounter issues where the Electron process fails to launch or execute properly. This behavior has been observed in Azure Virtual Desktop (AVD), Windows Virtual Desktop (WVD), and other environments where FSLogix filter drivers are active.

2. Symptoms

  • Electron-based applications (e.g., desktop apps built on Electron, CLI wrappers) do not start, remain unresponsive, or terminate silently.

  • No visible logs or error messages are generated by the application.

  • Standard executables run correctly when placed outside of the FSLogix-controlled profile path (e.g., copying to C:\Temp allows execution).

  • The issue is reproducible across all Electron apps in the FSLogix-managed profile.

3. Root Cause

The issue is linked to FSLogix filter drivers (frxdrv, frxdrvvt, frxccd) interfering with how Electron performs:

  • File I/O redirection

  • Process spawning

  • Temp/cache file usage

Electron apps rely heavily on filesystem operations and IPC channels. Certain FSLogix driver feature flags appear to block or alter these operations, preventing the Electron runtime from initializing correctly.

4. Resolution

The workaround is to adjust the SupportedFeatures registry value for all three FSLogix drivers:

Registry Keys

HKLM\SYSTEM\CurrentControlSet\Services\frxdrvvt\SupportedFeatures
HKLM\SYSTEM\CurrentControlSet\Services\frxdrv\SupportedFeatures
HKLM\SYSTEM\CurrentControlSet\Services\frxccd\SupportedFeatures

Value to Set

  • Hexadecimal: b or Decimal: 11

Steps

  1. Open Registry Editor (regedit.exe) with administrative privileges.

  2. Navigate to each of the keys listed above.

  3. Modify the SupportedFeatures value:

    • Change from existing value to 11 (decimal) or b (hex).

  4. Close the Registry Editor.

  5. Reboot the system to apply changes.

5. Verification

  • Launch the affected Electron-based application.

  • Confirm that the process executes normally under FSLogix-managed profiles.

  • Validate logs (if available) to ensure no startup errors persist.

6. Considerations

  • This change alters how FSLogix drivers handle certain feature flags. Microsoft has not fully documented the meaning of value 0x11.

  • The fix is widely reported to resolve Electron startup issues and other CLI/runtime failures (e.g., Azure CLI, AWS CLI).

  • Apply in test environments first before deploying broadly.

  • Track FSLogix release notes for a permanent fix (future builds may eliminate the need for this workaround).

7. References

Comments

Post a Comment

Popular posts from this blog

KB: Azure ACA Container fails to start (no User Assigned or Delegated Managed Identity found for specified ClientId)

Image
When deploying secure workloads using Azure Container Apps (ACA) , teams often face confusion between User Assigned Managed Identities (UAMI) and App Registrations . While both entities are visible in Azure Active Directory and have similar identifiers (Application ID, Object ID), they serve very different purposes . This confusion can lead to authentication failures when accessing services like Azure App Configuration or Key Vault . A common issue occurs when a container app is configured with a managed identity, but the environment variables or role assignments mistakenly reference an App Registration instead, causing errors like: "No User Assigned or Delegated Managed Identity found for specified ClientId" This article breaks down the difference between UAMI and App Registrations, explains why this issue happens, and outlines the correct approach to resolve it. Symptoms Azure Container App fails to authenticate to Azure App Configuration or other services. Logs...
Read more

KB:RMM VS DEX (Remote Monitoring Management vs Digital Employee Experience)

Digital Employee Experience (DEX) and Remote Monitoring and Management (RMM) tools serve different purposes and cater to distinct aspects of IT and employee management. Digital Employee Experience (DEX) Focus: Enhancing the overall experience of employees with their digital workplace tools and environment. Key Features: User Experience Monitoring: Tracks how employees interact with software and hardware, identifying issues impacting productivity. Performance Analytics: Provides insights into the performance of applications from the end-user's perspective. Feedback Mechanisms: Allows employees to report issues and give feedback on their digital tools and environment. Employee Well-being: Monitors factors that affect employee satisfaction and well-being, such as system performance and usability. Proactive Support: Identifies potential issues before they become significant problems, enabling proactive IT support. Goals: Improve employee satisfaction and productivity. Ensure a sm...
Read more