# Workspace Questions
### What happens if I add/remove/disable a Workspace while Media Composer is open?
Media Composer cannot cope with volumes mounting/ejecting (or connecting/disconnecting) while it’s open. If you need to add/remove/disable a Workspace, quit/exit Media Composer first.
### Why does Mimiq say my Workspace is `Unreachable`?
Either your shared storage is unavailable (e.g. disconnected from the network, powered off), or someone renamed the source folder you selected.
Take the appropriate action to make that source folder available again, then quit-then-relaunch Mimiq.
If Mimiq still says the Workspace is `Unreachable`, you may have to remove the Workspace and then re-add it.
### My SAN is mounted, so why does Mimiq say `No lockable volumes found`?
A SAN volume as is, is not compatible with Avid. You must add a folder on the SAN as a Workspace instead. As long as you have `read` and `write` permissions to that share, once you [add a folder from your SAN as a Workspace](#add-a-workspace), Mimiq will enable Bin Locking for that folder.
### Why is the option to Share a Workspace disabled?
Your Workspace is likely created on a volume where you do not have write permissions for the root. That makes it impossible for Mimiq to create a `Mimiq Settings` folder to store the Workspaces JSON files in. Either create the `Mimiq Settings` folder manually (easiest) or ensure you gain write permissions for the root folder of your storage (preferred).
### Why can't a Workspace be created using the root of a drive?
Because Avid volumes require write permissions, and the root of shared storage very often doesn't allow for that. Therefore, each Workspace should be staged from a subfolder—not from the parent volume (or "root") itself.
### Why is some of my media appearing in the wrong folder?
Is your media intermittently appearing in a `1` folder, instead of a `hostname.1` folder?
It is likely that you created a Workspace from the root of an external drive, which is a no-go, especially if it's already home to an Avid MediaFiles directory. Although Media Composer should always honour your Media Creation preferences, in this specific case that won't always happen.
Some background: Avid media can be stored on many types of drive, including direct-attached storage formatted with HFS+, APFS, or NTFS. In some workflows, we've seen users create a Workspace of the root of the drive, then layer a sync service on top, syncing the whole drive to their co-editors. This will trip up Media Composer into seeing an Avid-compatible volume (the Workspace) and the same volume as local storage. You want to avoid that by all means, as now all media exists twice.
If you need to sync two drives, sync the Workspace folders, and [don't create Workspaces using the root of the drive](#why-cant-a-workspace-be-created-using-the-root-of-a-drive).
### Why do Workspaces need to be staged from a subfolder on the parent volume?
Avid media can be stored on many types of storage, including direct-attached devices formatted with HFS+, APFS, or NTFS. In some workflows, users choose to stage their Mimiq Workspace on this kind of storage, with a sync service layered on top. This works well, but there’s a caveat.
Each Mimiq Workspace must be staged from a subfolder on the parent volume. If not, Media Composer (especially on macOS) will detect two volumes with the same name and Avid MediaFiles directory. This can cause unexpected behavior when importing, consolidating, or transcoding clips.
### Why am I asked to extend Mimiq when using LucidLink or Suite Studios?
You have a too-new LucidLink client installed, one that's not compatible with your installed version of Mimiq. First, check if you are eligible for updates. If not, you'll have to either extend your Mimiq license, or downgrade your LucidLink client.
Before updating your LucidLink client, always check the [Releases](https://docs.hedge.video/mimiq/releases) page to check which version of Mimiq is required.
### macOS keeps telling me `System Extension Blocked` after installing macFUSE. What can I do?
{% hint style="danger" %}
If your Mac is managed through MDM, stop now and contact your System Administrator.
{% endhint %}
Starting with macOS Big Sur, the local kernel extension (i.e. kext) database in macOS may not retain your decisions on approving third-party system or kernel extensions to load in macOS. If macOS doesn't load macFUSE despite multiple approvals from you, you can safely reset macOS' kext database, which revokes approval for all third-party kexts installed on your system volume.
Once you reset the local kext database, you can log back into macOS and approve any/all system or kernel extensions installed on your Mac.
1. Save any open work, then power down your Mac.
2. Once your Mac is fully powered down, [power up your Mac again in Recovery mode](https://support.apple.com/guide/mac-help/intro-to-macos-recovery-mchl46d531d6/mac).
3. Choose your system volume, log in with a macOS Administrator account, then launch Terminal.
4. Use this command to reset your Mac's Kernel Extension database:
1. `kmutil trigger-panic-medic --volume-root /Volumes/(SYSTEM VOLUME)`
* If your system volume has a space in its name (e.g. `Macintosh HD`), enclose the volume name in quotation marks (e.g. `"/Volumes/Macintosh HD"`).
2. Press the `(Return)` key.
* If you entered this command correctly, you'll see this response, `All third party kexts have been unapproved and uninstalled from /Volumes/(SYSTEM VOLUME).`
5. Restart your Mac.
Once you log into macOS, you'll likely be greeted with multiple dialog boxes saying...
* `System Extension Updated`
* `System Extension Blocked`
...along with confirmation that you triggered the `Panic Medic Boot`.
You've successfully reset your local kext database in macOS.
[Now you can approve macFUSE](#approving-macfuse-in-macos), and any other existing system or kernel extensions, to load in macOS.
### Why are drive labels not displayed in File Explorer for some Workspaces?
{% hint style="info" %}
This only concerns Windows users.
{% endhint %}
When you create a Workspace from a local drive, and that drive already has a label in File Explorer, the label of the parent drive takes precedence over the Workspace label assigned by Mimiq. In other words, File Explorer will display the existing label of the parent local drive instead of the Workspace label.
To make the Workspace's label visible in File Explorer, you can remove the label for the parent drive.
#### Local Drives
To display the Workspace label assigned through Mimiq, follow these steps to remove the label from the parent drive:
1. In File Explorer, create a new window, then locate the parent drive.
2. Right-click on the parent drive and select `Properties`.
3. In the `Properties` window, locate the `General` tab.
4. In the `Label` field, delete the existing label text.
5. Click `Apply` and then `OK` to save the changes.
#### LucidLink Filespaces
For a LucidLink Filespace, use PowerShell to remove the drive label:
1. Open PowerShell.
2. Run the following command:
`lucid config --set --local --FileSystem.MountPointWindowsLabel ""`
3. Remount the Filespace.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.hedge.video/mimiq/workspaces/workspace-questions.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.