Is there a way to disable checkdisk for encrypted volumes or volumes that do not have a letter

Question

Is there a way to disable checkdisk for encrypted volumes or volumes that do not have a letter

Microsoft User 66

I am booting from multiple systems with Bitlocker volumes and they always pop up with checkdisk /volume classid and such and such. Does anyone know how to take out the whole checkdisk I do not need it. I am on an SSD.

Arun Kumar 0 Reputation points

2026-10-25T13:02:21.2866667+00:00
You can bypass the automatic startup check using the built-in chkntfs utility, which supports both drive letters and volume GUIDs for encrypted volumes.

1. Find your volume GUIDs Open Terminal (Administrator) or Command Prompt (Run as administrator) and run:

DOS

mountvol

This lists your volumes in the format \\?\Volume{GUID}\ even if they don't have a drive letter assigned.

2. Exclude the volumes Run chkntfs /x specifying all the volumes you want to skip. For example:

DOS

chkntfs

Note: /x replaces your previous exclusion list, so make sure to include all drives you want suppressed in a single command.

3. Check the dirty bit (Optional) If you want to check why a volume keeps triggering a scan, you can query its status using:

DOS

fsutil dirty query D:

(Or use the GUID format without the \\?\ prefix for unassigned volumes).

1 answer

Your answer

Arun Kumar 0 Reputation points

2026-10-25T13:02:21.2866667+00:00

You can bypass the automatic startup check using the built-in chkntfs utility, which supports both drive letters and volume GUIDs for encrypted volumes.

1. Find your volume GUIDs Open Terminal (Administrator) or Command Prompt (Run as administrator) and run:

DOS

mountvol

This lists your volumes in the format \\?\Volume{GUID}\ even if they don't have a drive letter assigned.

2. Exclude the volumes Run chkntfs /x specifying all the volumes you want to skip. For example:

DOS

chkntfs

Note: /x replaces your previous exclusion list, so make sure to include all drives you want suppressed in a single command.

3. Check the dirty bit (Optional) If you want to check why a volume keeps triggering a scan, you can query its status using:

DOS

fsutil dirty query D:

(Or use the GUID format without the \\?\ prefix for unassigned volumes).

Answer 1

Exclude each affected volume from startup checking with chkntfs /x, using its volume GUID name when it has no drive letter.

Exclude the volumes

Open Terminal (Administrator) or Command Prompt (Run as administrator).
List the volume GUID names:
```
   mountvol
```
mountvol displays names in the form \\?\Volume{GUID}\ and any associated drive letters or mounted folders. It can identify volumes without assigning them a drive letter.^1^
Correlate the volumes with BitLocker, if necessary:
```
   manage-bde.exe -status
```
This reports each volume’s encryption status, encryption method, and volume type.^2^
Put all volumes to exclude in one command, using either drive letters or the exact GUID names returned by mountvol:
```
   chkntfs /x D: E: \\?\Volume{11111111-2222-3333-4444-555555555555}\
```
Replace the example GUID with the actual value. chkntfs accepts drive letters, mount points, and volume names; /x prevents startup autochk from checking those volumes even if they are marked as requiring chkdsk.^3^ Important: /x is not cumulative. Running it again replaces the previous exclusion list, so every excluded volume must appear in the latest command.
Restart and verify that those volumes are no longer checked.

Run the exclusion from every Windows installation that performs the unwanted startup check, because each installation controls its own startup configuration.

Check why the scan is being triggered

Before leaving the exclusion permanently, query the volume’s dirty bit:

fsutil dirty query D:
fsutil dirty query volume{11111111-2222-3333-4444-555555555555}

Use the GUID syntax shown above for fsutil, without the \\?\ prefix. A dirty bit means the file system may be inconsistent because changes were outstanding, shutdown occurred before they were committed, or corruption was detected. When it is set, Windows runs autochk during restart.^4^

Exclusion suppresses the automatic check; it does not repair or clear an underlying file-system problem. Back up important data and investigate repeated dirty states rather than assuming an SSD makes checking unnecessary. chkdsk checks file-system integrity and logical errors, not only physical disk damage.^5^

Undo the exclusion

To restore the default startup-check configuration:

chkntfs /d

This restores the default settings except for the startup countdown time; by default, dirty volumes are checked at startup.^3^

Do not edit the BootExecute registry value or remove autochk.exe. Microsoft documents chkntfs as the supported way to configure whether autochk runs for specific volumes.^6^

References