starred/vscode-dark-islands
1
0
Fork 0
mirror of https://github.com/bwya77/vscode-dark-islands.git synced 2026-05-09 08:25:35 +02:00
Code Issues 62 Projects Packages Wiki Activity

[GH-ISSUE #121] [BUG/Windows] Islands Dark recommended setup can leave VS Code in a broken state on Windows #83

New issue
Open
opened 2026-05-06 13:13:10 +02:00 by BreizhHardware · 2 comments
BreizhHardware commented 2026-05-06 13:13:10 +02:00
Owner
Copy link

Originally created by @RE-TikaRa on GitHub (Mar 31, 2026).
Original GitHub issue: https://github.com/bwya77/vscode-dark-islands/issues/121

Summary

After following the recommended Windows setup for Islands Dark, VS Code eventually became unbootable on startup.

I now get this popup when launching VS Code:

There was an error while Opening file handle:
"C:\Users\Tika\AppData\Local\Programs\Microsoft VS Code\NUL"

Failed to create file handle: Access is denied
Please verify there are no Visual Studio Code processes still executing.

This looks like a Windows-reserved device name (NUL) ended up being treated as a real file path.

Environment

  • OS: Windows 11 24H2 (build 26100.7171)
  • VS Code: User Setup installed under %LOCALAPPDATA%\Programs\Microsoft VS Code
  • Theme/setup: Islands Dark from this repo
  • Related extension installed by the recommended setup: subframe7536.custom-ui-style (observed locally as 0.6.8)

What I found locally

After the failure, there is a literal zero-byte file named NUL inside the VS Code install root:

C:\Users\Tika\AppData\Local\Programs\Microsoft VS Code\NUL

I also found that the VS Code installation had already been patched by Custom UI Style:

  • .custom-ui-style backup files exist in the install tree
  • patched workbench files are present
  • my user settings contain a large custom-ui-style.stylesheet block from this setup

So this does not look like a normal color theme issue. It looks related to the recommended "theme + Custom UI Style" installation path.

Steps that led here

  1. Use the recommended Islands Dark installation flow on Windows.
  2. Let it install/configure Custom UI Style.
  3. Use VS Code normally.
  4. After a later restart and/or VS Code update, launch VS Code again.
  5. VS Code fails very early during startup with the ...\\NUL access denied popup.

Expected behavior

The recommended setup should not leave VS Code in a broken state, and should never create or reference a reserved Windows device name like NUL inside the install directory.

Actual behavior

VS Code fails to start until I disable/remove the injected UI customization and clean the installation.

Local evidence

  • A literal file exists here:
    C:\Users\Tika\AppData\Local\Programs\Microsoft VS Code\NUL
  • The file is zero bytes.
  • The VS Code install tree also contains Custom UI Style backup artifacts such as:
    C:\Users\Tika\AppData\Local\Programs\Microsoft VS Code\cfbea10c5f\resources\app\product.1.113.0.custom-ui-style.json
  • Patched workbench files exist, for example:
    C:\Users\Tika\AppData\Local\Programs\Microsoft VS Code\cfbea10c5f\resources\app\out\vs\workbench\workbench.desktop.main.custom-ui-style.css
  • My user settings contain a large custom-ui-style.stylesheet block.

Notes

I understand the README says a "corrupt installation" warning is expected because Custom UI Style modifies VS Code internals.

However, this issue is more severe than that warning:
it can block VS Code from starting at all on Windows.

Because this repo explicitly recommends and installs Custom UI Style, I am reporting it here first.
If this should be reported upstream instead, I can move it there.

I am not claiming this repo directly creates the NUL file by itself, but the failure happened in the exact installation path modified by the recommended Islands Dark + Custom UI Style setup.

Questions

  • Is this a known Windows issue with the recommended setup?
  • Is there a safe update path for VS Code when using Islands Dark + Custom UI Style?
  • Should the Windows install/uninstall flow explicitly run a rollback/cleanup step before or after VS Code updates?
  • Would you consider documenting a "theme-only" install path more prominently for users who want the color theme without patching the VS Code installation?

attachments-checklist.md
local-evidence.md

Originally created by @RE-TikaRa on GitHub (Mar 31, 2026). Original GitHub issue: https://github.com/bwya77/vscode-dark-islands/issues/121 ## Summary After following the recommended Windows setup for Islands Dark, VS Code eventually became unbootable on startup. I now get this popup when launching VS Code: There was an error while Opening file handle: "C:\Users\Tika\AppData\Local\Programs\Microsoft VS Code\NUL" Failed to create file handle: Access is denied Please verify there are no Visual Studio Code processes still executing. This looks like a Windows-reserved device name (`NUL`) ended up being treated as a real file path. ## Environment - OS: Windows 11 24H2 (build 26100.7171) - VS Code: User Setup installed under `%LOCALAPPDATA%\Programs\Microsoft VS Code` - Theme/setup: Islands Dark from this repo - Related extension installed by the recommended setup: `subframe7536.custom-ui-style` (observed locally as 0.6.8) ## What I found locally After the failure, there is a literal zero-byte file named `NUL` inside the VS Code install root: `C:\Users\Tika\AppData\Local\Programs\Microsoft VS Code\NUL` I also found that the VS Code installation had already been patched by `Custom UI Style`: - `.custom-ui-style` backup files exist in the install tree - patched workbench files are present - my user settings contain a large `custom-ui-style.stylesheet` block from this setup So this does not look like a normal color theme issue. It looks related to the recommended "theme + Custom UI Style" installation path. ## Steps that led here 1. Use the recommended Islands Dark installation flow on Windows. 2. Let it install/configure `Custom UI Style`. 3. Use VS Code normally. 4. After a later restart and/or VS Code update, launch VS Code again. 5. VS Code fails very early during startup with the `...\\NUL` access denied popup. ## Expected behavior The recommended setup should not leave VS Code in a broken state, and should never create or reference a reserved Windows device name like `NUL` inside the install directory. ## Actual behavior VS Code fails to start until I disable/remove the injected UI customization and clean the installation. ## Local evidence - A literal file exists here: `C:\Users\Tika\AppData\Local\Programs\Microsoft VS Code\NUL` - The file is zero bytes. - The VS Code install tree also contains Custom UI Style backup artifacts such as: `C:\Users\Tika\AppData\Local\Programs\Microsoft VS Code\cfbea10c5f\resources\app\product.1.113.0.custom-ui-style.json` - Patched workbench files exist, for example: `C:\Users\Tika\AppData\Local\Programs\Microsoft VS Code\cfbea10c5f\resources\app\out\vs\workbench\workbench.desktop.main.custom-ui-style.css` - My user settings contain a large `custom-ui-style.stylesheet` block. ## Notes I understand the README says a "corrupt installation" warning is expected because `Custom UI Style` modifies VS Code internals. However, this issue is more severe than that warning: it can block VS Code from starting at all on Windows. Because this repo explicitly recommends and installs `Custom UI Style`, I am reporting it here first. If this should be reported upstream instead, I can move it there. I am not claiming this repo directly creates the `NUL` file by itself, but the failure happened in the exact installation path modified by the recommended Islands Dark + Custom UI Style setup. ## Questions - Is this a known Windows issue with the recommended setup? - Is there a safe update path for VS Code when using Islands Dark + Custom UI Style? - Should the Windows install/uninstall flow explicitly run a rollback/cleanup step before or after VS Code updates? - Would you consider documenting a "theme-only" install path more prominently for users who want the color theme without patching the VS Code installation? [attachments-checklist.md](https://github.com/user-attachments/files/26379118/attachments-checklist.md) [local-evidence.md](https://github.com/user-attachments/files/26379117/local-evidence.md)
BreizhHardware commented 2026-05-06 13:13:10 +02:00
Author
Owner
Copy link

@simohauml commented on GitHub (Apr 9, 2026):

Similar here. My VSCode can start up but the theme not working with error in Custom UI, can not load json files.

<!-- gh-comment-id:4218346273 --> @simohauml commented on GitHub (Apr 9, 2026): Similar here. My VSCode can start up but the theme not working with error in Custom UI, can not load json files.
BreizhHardware commented 2026-05-06 13:13:11 +02:00
Author
Owner
Copy link

@raaid3 commented on GitHub (Apr 16, 2026):

Similar here. My VSCode can start up but the theme not working with error in Custom UI, can not load json files.

Try it with this fork, I use a lighter weight extension and give you instructions on what to add to your settings.json: https://github.com/raaid3/vscode-dark-islands

<!-- gh-comment-id:4256691308 --> @raaid3 commented on GitHub (Apr 16, 2026): > Similar here. My VSCode can start up but the theme not working with error in Custom UI, can not load json files. Try it with this fork, I use a lighter weight extension and give you instructions on what to add to your settings.json: https://github.com/raaid3/vscode-dark-islands
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
0.0.3
bwyatt-custom
0.0.2
Labels
Clear labels   
bug

   
bug

   
duplicate

   
enhancement

   
enhancement

   
Missing Info

   
pull-request
Mirrored from GitHub Pull Request

  
wontfix
No labels
bug
bug
duplicate
enhancement
enhancement
Missing Info
pull-request
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vscode-dark-islands#83
No description provided.