Error 1067: The Process terminated unexpectedly

elsie de vos 0 Reputation points
2026-03-02T08:53:19.2966667+00:00

i try to install Autodesk Dektop Connector on a Mac with a virtual machine Windows 11.

When i want to start the Service Autodesk File System Monitor Service, i aways get Error 1067: The Process terminated unexpectedly

Windows for business | Windows Server | Devices and deployment | System management components
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. VPHAN 42,480 Reputation points Independent Advisor
    2026-03-04T10:20:06.92+00:00

    Hi elsie de vos,

    How is your issue going? Has it been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)

    VP

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. VPHAN 42,480 Reputation points Independent Advisor
    2026-03-02T09:34:03.3433333+00:00

    Hi elsie de vos,

    The Error 1067 you are experiencing is directly tied to the hardware architecture and environment of your Mac rather than a simple configuration issue. Most modern Mac computers utilize Apple Silicon, which is an ARM-based processor. Consequently, your virtual machine is running the ARM-specific version of Windows 11. While Windows 11 on ARM is excellent at translating standard applications, it cannot reliably translate software that installs deep, low-level system components. The Autodesk File System Monitor Service relies heavily on complex file system filter drivers to synchronize your cloud data. Because the Windows emulation layer cannot process these deep architectural drivers, the service instantly crashes upon startup and generates this specific termination error.

    Furthermore, official Autodesk documentation explicitly states that the Desktop Connector is not designed to function within any virtual machine environment, regardless of whether it is an Intel or ARM-based Mac. If you were running an older Intel Mac, you could potentially attempt to clear out leftover installation data by deleting the Desktop Connector folders located in the hidden directory at C:\Users\YourUsername\AppData\Local\Autodesk\Desktop Connector. You would also need to remove the configuration files found in the Windows Registry, which is a database of system settings, under the path HKEY_CURRENT_USER\Software\Autodesk\Autodesk Desktop Connector. However, since you are dealing with a fundamental virtualization limitation, these standard troubleshooting steps will not resolve the underlying incompatibility.

    Until Autodesk releases an official ARM-compatible update or provides dedicated virtual machine support, this background service will not function on your current setup. You will need to bypass the Desktop Connector entirely and manage your files directly through the Autodesk Docs or BIM 360 web interfaces. Alternatively, you can use a standard Intel or AMD-based Windows computer running natively for your synchronization tasks.

    Hope this answer brought you some useful information. If it did, please hit "accept answer". Should you have any questions, feel free to leave a comment.

    VP

    Was this answer helpful?

    0 comments

  3. AI answer

    2026-03-02T08:53:31.61+00:00

    Error 1067 indicates that a Windows service process aborted during startup. In the provided context, this error is documented for services that fail to start because of configuration or permission issues, particularly around service-related folders and files.

    For Windows services such as OpenSSH or Remote Desktop Services, error 1067 commonly occurs when:

    • Required folders or files have incorrect NTFS permissions (too restrictive or too permissive), preventing the service account from writing logs or configuration.
    • The service crashes or hangs during initialization.

    For example, OpenSSH 9.5 Server can fail with error 1067 if C:\ProgramData\ssh or C:\ProgramData\ssh\logs have incorrect permissions. The documented fix is to correct the folder ACLs so that:

    • SYSTEM and Administrators have Full control (including Modify, Read & execute, List folder contents, Read, Write).
    • Non‑administrative users (for example, Authenticated Users) have only Read & execute, List folder contents, and Read.

    This is done through the folder Properties → Security tab in File Explorer.

    The same principle applies to other services that fail with 1067: verify that the service’s program data, configuration, and log directories allow write access for the service account (typically LocalSystem or a specific service user) and that non‑admin users do not have inappropriate write access that might cause the service to refuse to start.

    If a service continues to fail with 1067 after permissions are corrected, the next step is to review the Windows Event Log (System and Application logs) for service‑specific errors or crashes and address those according to the vendor’s guidance.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.