Everything Dark Theme Not Working: How to Fix It

When the dark theme in voidtools Everything is not working, the problem is usually limited to one of four areas: Everything is using its own custom colors, Windows theme detection has not refreshed, a portable configuration is overriding the installed configuration, or result highlighting is creating poor contrast even though the main window is dark. The fastest solution is to test default colors first, restart the application correctly, and then change one visual setting at a time.

This guide focuses specifically on theme, color, and contrast problems in Everything on Windows. It also explains how to recognize a separate search or indexing problem, so you do not rebuild the database, change services, or alter network settings unnecessarily. Everything is a filename search application from voidtools. It is not the same component as Windows Search, and changing Windows indexing options usually does not repair Everything's interface colors.

1. Confirm the Symptom With a Small Safe Test

Before changing settings, identify exactly which part of the interface is wrong. A theme problem can affect the window background, search box, result list, menus, status bar, selected rows, matching-text highlights, or only one of these areas. That distinction determines which setting to inspect.

1.1 Test the main window and result list separately

Open Everything normally and search for the name of a file you know exists. Use a simple filename term without filters, regular expressions, or advanced search syntax. Observe the following interface elements:

• The background of the search box
• The background and text in the result list
• The color of selected and unselected rows
• The color used to highlight matching text
• The menu bar, status bar, and column headers

If the window is mostly dark but matching filename characters are difficult to read, dark mode is probably active and the result highlight colors are the actual problem. If every area remains light, Everything may not be following the Windows theme, or saved custom colors may be overriding its defaults.

Success at this stage means you can describe the symptom precisely, such as “the interface is dark, but selected result text has insufficient contrast.” Once you identify the affected element, avoid changing unrelated index or service options.

1.2 Compare Everything with the active Windows theme

Open Windows Settings and check the current color mode under Personalization and Colors. Confirm whether Windows is set to dark, light, or a custom combination. A custom Windows mode can use one appearance for Windows itself and another for applications, so do not assume that a dark taskbar means applications have also been assigned dark mode.

If Everything is configured to follow the system or application theme, temporarily switch the Windows application mode to light, wait a few seconds, and then switch it back to dark. Fully exit and reopen Everything after the change. This safe test can reveal whether the application is receiving the current Windows theme preference.

Success means Everything changes consistently with the selected application mode. If it does, stop adjusting settings. If it does not, continue with Everything's own theme and color configuration.

2. Check Everything Theme and Color Settings

Open Everything's Options window and inspect the categories related to appearance, view, fonts, colors, or themes. The exact labels and available controls can differ between Everything builds, so use the labels displayed by your installed copy instead of following instructions intended for a different build.

2.1 Restore default theme colors first

Custom colors can survive Windows theme changes. A background, text, selection, or highlight color selected manually may continue to be used even when the rest of the interface follows dark mode. This often produces a mixed interface or makes result text appear invisible.

In the relevant appearance or color page, note your current settings or take a screenshot. Then choose the available default, automatic, system, or reset option for the affected colors. If there is a theme selector, select the appropriate dark or system-controlled choice rather than manually assigning every color.

Apply the settings and inspect an unselected result, a selected result, and highlighted matching text. Success means each state is readable and the interface uses a consistent palette. Stop there if the problem is fixed. Reintroduce custom colors only one at a time so you can identify the color responsible for the conflict.

2.2 Correct result highlight contrast

Everything can visually emphasize the part of a result that matches the current query. That highlight may use a different foreground or background color from ordinary result text. A color that worked on a light background may have almost no contrast on a dark background.

Test three states carefully:

1. Search for a short term that appears inside several filenames.
2. Inspect the highlighted characters on an unselected row.
3. Select that row and inspect the highlighted characters again.

If only the highlighted characters disappear, change the matching-text or highlighted-result color rather than the entire theme. If text becomes unreadable only when selected, inspect the selected text and selected background colors. Choose combinations with clear visual separation instead of relying on subtle shades.

Success means the full filename remains readable in both selected and unselected rows while the matching portion is still distinguishable. Once all three states are clear, no database or search troubleshooting is needed.

2.3 Check for custom color overrides

If Everything offers separate settings for normal text, selected text, backgrounds, highlights, alternating rows, or special result states, one custom value can override the expected dark-theme color. Reset the affected value to its default before choosing a new custom value.

Also check whether a customized font or display option is making text appear thin or unclear against a dark background. Theme problems are sometimes contrast problems rather than failures to activate dark mode. Test at normal Windows scaling before concluding that colors are not applying.

2.4 Restart Everything completely

Closing the main window may not always terminate the process if Everything is configured to continue running in the notification area or start in the background. After changing theme settings, use the application's Exit command. Confirm in Task Manager that the user-interface process has closed, and then launch it again.

Do not stop or remove the Everything service merely to refresh interface colors. The service and the desktop interface have different responsibilities. A service can help the client access NTFS volume information, but it does not normally control window colors.

Success means the selected appearance survives a complete exit and relaunch. If the theme works until restart and then reverts, investigate configuration persistence and startup behavior next.

3. Check Portable Settings, Startup Shortcuts, and Account Context

Everything can be used as an installed application or in a portable arrangement. It is possible to have multiple executable files, configuration files, or shortcuts on the same computer. You may therefore edit one copy's options and later open another copy with different colors.

3.1 Verify which executable is running

Open Task Manager, locate Everything, and inspect the executable location when Windows provides that option. Compare it with the shortcut you normally use. Check desktop shortcuts, Start menu entries, taskbar pins, scheduled tasks, and startup folders for older or portable copies.

If two copies exist, do not delete either one immediately. Close both, launch the intended executable directly, and change one harmless visual setting as a test. Exit and reopen that same executable.

Success means the change persists in the intended copy. You can then update stale shortcuts or unpin an obsolete taskbar entry.

3.2 Confirm that configuration changes can be saved

A portable copy may store its configuration beside the executable. If that folder is read-only, protected, on removable media, or located in a directory where the current user cannot write, Everything may accept a color change for the current session but fail to save it.

Use a normal user-writable test folder for a temporary portable test. Avoid changing ownership or weakening permissions on protected Windows folders merely to save theme preferences. If configuration files are managed by an administrator, deployment tool, or logon script, ask whether appearance settings are being replaced at startup.

Success means the chosen theme remains active after a complete exit, Windows sign-out, and relaunch. If settings revert only after sign-in, inspect startup scripts or managed configuration rather than repeatedly resetting the theme.

3.3 Compare elevated and standard-user launches

Running Everything under another account or with elevated credentials can load a different user context and configuration. If the theme appears correct when launched one way but not another, compare the shortcut properties and launch method.

For normal use, launch the interface consistently under your regular Windows account unless elevation is required for a specific administrative task. Do not assume that running as administrator is a general theme fix.

Success means the same user account loads the same appearance consistently. At that point, stop changing permissions.

3.4 Review command-line and startup options

A shortcut, script, launcher, or portable-app manager can supply command-line options or select a particular configuration location. Inspect the shortcut's Target field and any wrapper script used to launch Everything. Compare it with a direct launch of the intended executable.

If a direct launch uses the correct theme but the shortcut does not, the startup method is the source of the difference. Preserve any operationally necessary options, but remove obsolete appearance or configuration-location overrides only after documenting them.

4. Separate Theme Problems From Search and Index Problems

The phrase “Everything dark theme not working” sometimes accompanies reports that results are also missing. These are normally separate symptoms. Theme settings control appearance. Indexes, services, folder indexes, exclusions, filters, and servers control which filenames are available to search.

4.1 Use the status bar and a known-file search

Look at the status bar while running a simple search. If Everything reports results and known filenames appear, the search engine is functioning even if the colors are wrong. Do not rebuild the index just to repair a light background or unreadable highlight.

If no results appear, clear the search box and disable any active filter. Then search for a known filename using plain text. Remove regular-expression mode, whole-word restrictions, case matching, path matching, and result omissions temporarily.

Success means the known file appears after clearing search-specific restrictions. You can then restore filters one at a time.

4.2 Check indexes only when results are genuinely missing

If files are absent independently of the theme issue, inspect the relevant index settings. Confirm that the local volume is included, the folder index points to the correct path, and exclusions do not cover the missing location. For a mapped drive or network share, verify that the same Windows account can open the path outside Everything.

NTFS volumes, folder indexes, mapped drives, NAS shares, and server-fed results can have different indexing paths. A dark-theme change will not add or remove these sources. Likewise, changing Windows Search indexing locations will generally not repair Everything results because Everything and Windows Search are separate search systems.

4.3 Check service and server state only when relevant

If Everything reports access or indexing problems, verify that the configured Everything service is available and that the client is using the intended settings. For remote or server-based deployments, confirm that the client can reach the approved internal server and that firewall rules have not changed.

Do not expose an Everything server to the public internet as a troubleshooting shortcut. Do not permanently disable antivirus or firewall protection. If a security product appears to interfere, review its logs and create the narrowest approved exception only after verifying the executable and consulting organizational policy.

Success means results from the expected local or approved network source appear. This will not necessarily change the interface theme, so return to appearance settings if colors remain incorrect.

4.4 Treat Force Rebuild as a search repair, not a theme repair

A Force Rebuild can be useful when the index is demonstrably stale or inconsistent, but it does not reset interface colors. Before rebuilding, check filters, exclusions, indexed locations, folder availability, and the status bar. Rebuilding first can waste time and obscure the original cause.

If a rebuild is justified, allow it to finish and test a known filename. Stop when expected results return. Continue theme troubleshooting separately only if the visual problem remains.

5. Use Diagnostics Without Making Broad Changes

Diagnostics are most useful when settings do not persist or when two launch methods behave differently. The goal is to gather evidence, not to change every option at once.

5.1 Inspect the Options pages systematically

Review only the pages related to appearance, fonts, colors, view behavior, startup, configuration storage, and the specific result source that is missing. Take screenshots before changing values. This creates a simple rollback record and helps distinguish the fix from unrelated changes.

Apply one change, fully restart Everything when appropriate, and repeat the same small search. If the interface becomes correct, stop. Additional changes increase the chance of creating a second problem.

5.2 Use debug logging for persistence or launch problems

If Everything supports debug output in your build, use it temporarily to determine which executable, configuration, and startup options are active. Debug information is more relevant when settings revert, a managed shortcut behaves differently, or a server connection fails. It is rarely necessary for a straightforward custom-color conflict.

Review logs before sharing them because they may contain local paths, filenames, account details, or server names. Disable temporary debugging after collecting the required information.

5.3 Use the Index Journal only for result discrepancies

The Index Journal can help explain indexing changes or missing results in supported configurations, but it is not a theme diagnostic. Consult it only when a known file is absent after filters and exclusions have been ruled out.

If filenames are present and only their colors are wrong, return to the color controls. This boundary keeps Everything troubleshooting focused and prevents unnecessary index work.

6. Run a Clean Temporary Test Before Changing More Settings

A temporary clean profile can determine whether the cause is stored configuration or a broader Windows interaction. Use a separate test folder and a clean, trusted copy obtained from the official voidtools site. Do not overwrite your working configuration.

6.1 Create a controlled comparison

1. Record the path and build information of the copy you normally run.
2. Exit all Everything user-interface processes.
3. Place the temporary copy in a user-writable test folder.
4. Launch it without your usual shortcut, script, or portable-app wrapper.
5. Test its default colors before importing or copying any settings.
6. Switch the applicable Windows app theme and restart the test copy.

If the clean copy displays dark colors correctly, Windows can render the interface and the likely cause is a saved color, configuration file, launch option, or managed setting in the normal profile. Compare settings carefully rather than replacing the original configuration wholesale.

If the clean copy shows the same problem, check Windows application color mode, display contrast settings, and whether the behavior is limited to a particular interface element. Also compare the behavior using your normal account without compatibility settings or third-party theming utilities.

6.2 Know when to stop

Stop changing settings as soon as the main window, results, selected rows, and highlighted matches are readable and the appearance survives a complete restart. A successful fix does not require every Windows surface to use an identical shade. Native menus, title bars, and application-controlled result areas may be rendered through different Windows components.

If the remaining issue is cosmetic and reproducible in a clean profile, document the affected element, Windows version, display scaling, Everything build, and exact steps. That information is more useful for support than a heavily modified configuration.

7. Quick Fix Checklist

• Confirm whether the whole window or only result highlights have incorrect colors.
• Check the Windows application theme, especially when using Custom color mode.
• Open Everything's appearance, font, color, or theme options.
• Test default or automatic colors before creating a custom palette.
• Check normal, selected, and highlighted result text separately.
• Exit Everything completely and relaunch the intended executable.
• Verify that a portable configuration can save changes in its folder.
• Check whether an old shortcut opens a different Everything copy.
• Compare standard-user and elevated launches if they look different.
• Inspect shortcut or command-line options that select another configuration.
• Do not rebuild the index solely because dark mode looks wrong.
• Use a clean temporary profile before changing many settings.
• Stop once colors are readable and remain correct after restart.

8. Frequently Asked Questions

8.1 Why is Everything still light when Windows is in dark mode?

Windows may be using a custom color mode in which applications remain light, or Everything may have custom colors that override automatic behavior. Check the Windows application mode, reset Everything's appearance colors to their defaults, and completely exit and reopen the application.

8.2 Why are Everything search results unreadable only when selected?

The selected text color and selected background color probably have insufficient contrast. Inspect those colors separately from the normal result colors. Also test highlighted matching text on the selected row because it may have an additional color setting.

8.3 Does changing the theme require a restart?

Some visual changes may apply immediately, while others can require the user-interface process to restart. Use Everything's Exit command rather than merely closing the window, verify that the process has ended, and launch it again. Restarting the Everything service is generally unnecessary for a color change.

8.4 Will rebuilding the Everything index fix dark mode?

No. An index rebuild addresses filename database problems, not interface colors. Consider Force Rebuild only when known files are missing after you have checked filters, exclusions, index locations, and source availability.

8.5 Why does my custom theme reset every time Everything starts?

The application may be loading another configuration, launching from a different executable, or failing to write settings in a protected portable folder. A startup script or managed configuration may also restore predefined values. Test the intended executable directly from a user-writable location.

8.6 Is Everything Search the same as Windows Search?

No. voidtools Everything is a separate filename search application with its own settings, indexes, services, filters, and interface. Windows theme preferences can influence application appearance, but changing Windows Search indexing options does not normally repair Everything's theme or database.