Skip to main content
This page lists known errors and issues that users may encounter when installing or using Vibrancy Continued, along with their solutions.
If you’re experiencing issues, check this page first before opening a new issue on GitHub.

​
Permission Errors

​
EACCES: permission denied on macOS

This error occurs when your VSCode installation is owned by another user. Solution: Run the following commands exactly as-is in the Terminal app to take ownership of the files, and enter your password when prompted: 
sudo chown -R $(whoami):staff "/Applications/Visual Studio Code.app/"
sudo chmod -R 755 "/Applications/Visual Studio Code.app/"
A reinstallation will also fix this issue without any loss of settings.

​
EROFS: read-only file system on macOS

Your installation of VSCode is affected by App Translocation, a macOS security feature. Solution: You have two options to fix this:
Run the following terminal command:
sudo xattr -dr com.apple.quarantine "/Applications/Visual Studio Code.app"

​
Administrator Privileges Required on Windows

You see a prompt: “Run Visual Studio Code with administrator privileges” When this occurs: This usually appears on Windows when you are using the VSCode System Installer. Solution:
  1. Close VSCode completely
  2. Run VSCode as administrator (right-click the VSCode icon and select “Run as administrator”)
  3. Retry the action you were performing (Enable/Reload/Disable Vibrancy)

​
Windows-Specific Issues

​
Window Cannot Be Resized/Moved/Maximized

This is a known issue with VSCode 1.86+ on Windows related to Electron 27 and hardware acceleration.
By default, when Vibrancy is installed on VSCode 1.86 and newer on Windows, your VSCode windows may stop being resizable, snappable or maximizable. Solution: Follow these steps to properly configure Vibrancy on Windows:
  1. Update your VSCode shortcut to include --disable-gpu-compositing at the end of the “Target” field:
"C:\Users\User\AppData\Local\Programs\Microsoft VS Code\Code.exe" --disable-gpu-compositing
  1. (Optional) Update your shell configuration to add the same argument to code, needed if VSCode isn’t running when you use the code command
  2. Install Vibrancy Continued
  3. Go to settings and check Disable frameless window (vscode_vibrancy.disableFramelessWindow)
  4. Press F1 and select Reload Vibrancy
For more information, see GitHub issues #140 and #122.

​
Window Lag When Dragging (Windows 10)

If you’re experiencing lag when dragging the VSCode window on Windows 10, this is a known issue related to the Acrylic blur effect. Solution: Please read the detailed discussion here for workarounds and solutions.

​
Editor Support Issues

​
”Your code editor is not supported”

This error appears when trying to use Vibrancy Continued with an unsupported code editor. Supported editors: For Windows users with unsupported editors: If you’re using an unsupported code editor on Windows, you must perform the Windows installation steps prior to activating Vibrancy Continued.

​
Visual Effect Issues

​
Effect Doesn’t Work Correctly in VSCode Terminal

The terminal may not render the transparency effect correctly with certain renderer settings. Solution: Change the renderer type of the terminal to dom by adding this to your settings: 
"terminal.integrated.gpuAcceleration": "off"

​
Effect Doesn’t Work, But There Are No Errors

The extension is installed but you don’t see any transparency effects. Possible causes and solutions:
Ensure that you don’t have transparency effects disabled globally through your OS settings.
  • Windows: Look under Settings > Personalization > Colors > Transparency effects
  • macOS: Look under System Preferences > Accessibility > Display > Reduce transparency
This setting may be called “Transparency effects” or “Reduce transparency.”
Check the Console section in VSCode’s Developer Tools for any error messages:
  1. Open the command palette (F1 or Cmd/Ctrl+Shift+P)
  2. Search for “Developer: Toggle Developer Tools”
  3. Check the Console tab for errors
If nothing else worked, try reinstalling VSCode. You won’t lose any settings and this will ensure that your VSCode installation is consistent.

​
Nothing Happens First Time Reload/Enable Vibrancy is Used

Vibrancy doesn’t activate the first time you try to enable it. Solution: This is a known issue with Vibrancy sometimes not working on the first try after VSCode updates. Simply perform the same action again to resolve.
If the extension still doesn’t work after the second attempt, check the other solutions on this page.

Build docs developers (and LLMs) love

Get started for freeTalk to us