SMB2 is supported on Windows Vista, Windows Server 2008 R2, Windows 7. Windows computer, you will need to modify your computer's registry settings. Registry Hack to Disable Writing to USB Drives Lowell Heddings @lowellheddings Updated July 12, 2017, 10:38pm EDT A common security concern at organizations is allowing users to plug in a usb flash drive, because they could so easily copy corporate data.
-->The following syntax is used when running the Verifier utility in a Command Prompt window.
You can type several options on the same single line. For example:
Windows 10
You can use the /volatile parameter with some Driver Verifier /flags options and with /standard. You cannot use /volatile with the /flags options for DDI compliance checking, Power Framework Delay Fuzzing, Storport Verification, or SCSI Verification. For details, see Using Volatile Settings.
Windows 8.1
You can use the /volatile parameter with some Driver Verifier /flags options and with /standard. You cannot use /volatile with the /flags options for DDI compliance checking, Power Framework Delay Fuzzing, Storport Verification, or SCSI Verification. For details, see Using Volatile Settings.
Windows 8, Windows 7, Windows Vista Syntax
You can use the /volatile parameter with some Driver Verifier /flags options and with /standard. You cannot use /volatile with the /flags options for DDI compliance checking, Power Framework Delay Fuzzing, Storport Verification, SCSI Verification or with /disk. For details, see Using Volatile Settings.
Windows Server 2003 Syntax
Parameters
Verifier Command-Line Syntax
/all
Directs Driver Verifier to verify all installed drivers after the next boot.
/bootmodemode
Controls whether the settings for Driver Verifier are enabled after a reboot. To set or change this option, you must reboot the computer.
| Boot mode | Description |
|---|---|
persistent | Ensures that the Driver Verifier settings persist (stay in effect) over many reboots. This is the default setting. |
disableafterfail | If Windows fails to start, this setting disables Driver Verifier for subsequent reboots. |
oneboot | Only enables the Driver Verifier settings for the next time the computer starts. Driver Verifier is disabled for subsequent reboots. |
resetonunusualshutdown | (Introduced in Windows 10, build 1709) Driver Verifier will persist until an unusual shutdown occurs. Its abbrevation, 'rous', can be used. |
/disk
(Introduced in Windows Server 2003. Not available in Windows 7 and later versions of Windows.) Activates the Disk Integrity Checking option after the next boot. You cannot use /disk with /volatile on any version of Windows.
/driverDriverList
Specifies one or more drivers that will be verified. DriverList is a list of drivers by binary name, such as Driver.sys. Use a space to separate each driver name. Wildcard values, such as n*.sys, are not supported.
/driver.excludeDriverList
Specifies one or more drivers that will be excluded from verification. This parameter is applicable only if all drivers are selected for verification. DriverList is a list of drivers by binary name, such as Driver.sys. Use a space to separate each driver name. Wildcard values, such as n*.sys, are not supported.
/faults
(Windows Vista and later) Enables the Low Resources Simulation feature in Driver Verifier. You can use /faults in place of /flags 0x4. However, you cannot use /flags 0x4 with the /faults subparameters.
You can use the following subparameters of the /faults parameter to configure Low Resources Simulation.
| Subparameter | Description |
|---|---|
Probability | Specifies the probability that Driver Verifier will fail a given allocation. Type a number (in decimal or hexadecimal) to represent the number of chances in 10,000 that Driver Verifier will fail the allocation. The default value, 600, means 600/10000 or 6%. |
Pool Tags | Limits the allocations that Driver Verifier can fail to allocations with the specified pool tags. You can use a wildcard character (*) to represent multiple pool tags. To list multiple pool tags, separate the tags with spaces. By default, all allocations can fail. |
Applications | Limits the allocations that Driver Verifier can fail to allocations for the specified program. Type the name of an executable file. To list programs, separate the program names with spaces. By default, all allocations can fail. |
DelayMins | Specifies the number of minutes after booting during which Driver Verifier does not intentionally fail any allocations. This delay allows the drivers to load and the system to stabilize before the test begins. Type a number (in decimal or hexadecimal). The default value is 7 (minutes). |
/faultssystematic
Specifies the options for Systematic low resources simulation. Use the 0x40000 flag to select Systematic low resources simulation option.
| OPTION | Description |
|---|---|
enableboottime | Enables fault injections across computer reboots. |
disableboottime | Disables fault injections across computer reboots (this is the default setting). |
recordboottime | Enables fault injections in what if mode across computer reboots. |
resetboottime | Disables fault injections across computer reboots and clears the stack exclusion list. |
enableruntime | Dynamically enables fault injections. |
disableruntime | Dynamically disables fault injections. |
recordruntime | Dynamically enables fault injections in what if mode. |
resetruntime | Dynamically disables fault injections and clears the previously faulted stack list. |
querystatistics | Shows the current fault injection statistics. |
incrementcounter | Increments the test pass counter used to identify when a fault was injected. |
getstackid COUNTER | Retrieves the indicated injected stack identifier. |
excludestack STACKID | Excludes the stack from fault injection. |
/flagsOptions
Activates the specified options after the next reboot. In Windows 2000, this number must be entered in decimal format. In Windows XP and later, this number can be entered in decimal or in hexadecimal (with an 0x prefix) format. Any combination of the following values is allowed.
| Decimal | Hexadecimal | Standard Setting | Option |
|---|---|---|---|
1 | 0x1 (bit 0) | X | |
2 | 0x2 (bit 1) | X | |
4 | 0x4 (bit 2) | ||
8 | 0x8 (bit 3) | X | |
16 | 0x10 (bit 4) | X | |
32 | 0x20 (bit 5) | X | Deadlock Detection (Windows XP and later) |
64 | 0x40 (bit 6) | Enhanced I/O Verification (Windows XP and later) (In Windows 7 and later, this option is automatically activated when you select I/O Verification) | |
128 | 0x80 (bit 7) | X | DMA Verification (Windows XP and later) |
256 | 0x100 (bit 8) | X | Security Checks (Windows XP and later) |
512 | 0x200 (bit 9) | Force Pending I/O Requests (Windows Vista and later) | |
1024 | 0x400 (bit 10) | IRP Logging (Windows Server 2003 and later) | |
2048 | 0x800 (bit 11) | X | Miscellaneous Checks (Windows Vista and later) |
8192 | 0x2000 (bit 13) | Invariant MDL Checking for Stack (Starting with Windows 8) | |
16384 | 0x4000 (bit 14) Nbbi code. | Invariant MDL Checking for Driver (Starting with Windows 8) | |
32768 | 0x8000 (bit 15) | Power Framework Delay Fuzzing (Starting with Windows 8) | |
65536 | 0x10000 (bit 16) | Port/miniport interface checking (Starting with Windows 10) | |
131072 | 0x20000 (bit 17) | X | DDI compliance checking (Starting with Windows 8) |
262144 | 0x40000 (bit 18) | Systematic low resources simulation (Starting with Windows 8.1) | |
524288 | 0x80000 (bit 19) | DDI compliance checking (additional) (Starting with Windows 8.1) | |
2097152 | 0x200000 (bit 21) | NDIS/WIFI verification (Starting with Windows 8.1) | |
8388608 | 0x800000 (bit 23) | Kernel synchronization delay fuzzing (Starting with Windows 8.1) | |
16777216 | 0x1000000 (bit 24) | VM switch verification (Starting with Windows 8.1) | |
33554432 | 0x2000000 (bit 25) | Code integrity checks (Starting with Windows 10) |
You cannot use this method to activate the SCSI Verification or Storport Verification options. For information, see SCSI Verification and Storport Verification.
/flagsVolatileOptions
Specifies the Driver Verifier options that are changed immediately without rebooting in Windows 2000, Windows XP, and Windows Server 2003. (In Windows Vista, you can use the /volatile parameter with all /flags values.)
In Windows 2000, enter a number in decimal format. In Windows XP and Windows 2003, enter a number in decimal or in hexadecimal format (with an 0x prefix).
Any combination of the following values is permitted.
| Decimal | Hexadecimal | Option |
|---|---|---|
1 | 0x1 (bit 0) | Special Pool |
2 | 0x2 (bit 1) | Force IRQL Checking |
4 | 0x4 (bit 2) | Low Resources Simulation |
/iolevelLevel
(Windows 2000 only) Specifies the level of I/O Verification.
The value of Level can be 1 or 2. The default value is 1.
| Level value | Description |
|---|---|
1 | Enables Level 1 I/O Verification (default) |
2 | Enables Level 1 I/O Verification and Level 2 I/O Verification |
If I/O Verification is not enabled (by using /flags 0x10), /iolevel is ignored.
/logLogFileName [/intervalSeconds]
Creates a log file with name LogFileName. Driver Verifier periodically writes statistics to this file. For details, see Creating Log Files.
If a verifier /log command is typed at the command line, the command prompt does not return. To close the log file and return a prompt, use the CTRL+C key. After a reboot, to create a log, you must submit the verifier /log command again.
| Option | Description |
|---|---|
/intervalSeconds | Specifies the interval between log file updates. The default is 30 seconds. |
/rulesOption
Options for rules that can be disabled (advanced).
| Option | Description |
|---|---|
query | Shows current status of controllable rules. |
reset | resets all rules to their default state. |
defaultID | Sets rule ID to its default state. For the supported rules, the rule ID is the Bug Check 0xC4 (DRIVER_VERIFIER_DETECTED_VIOLATION) parameter 1 value. |
disableID | Disables specified rule ID. For the supported rules, the rule ID is the Bug Check 0xC4 (DRIVER_VERIFIER_DETECTED_VIOLATION) parameter 1 value. |
/standard
(Windows XP and later) Activates the 'standard' or default Driver Verifier options after the next boot. The standard options in Windows XP are Special Pool, Force IRQL Checking, Pool Tracking, I/O Verification, Deadlock Detection, and DMA Verification. This is equivalent to /flags 0xBB. Starting with Windows Vista, the standard options also include Security Checks and Miscellaneous Checks. This is equivalent to /flags 0x9BB. Starting with Windows 8, the standard options also include DDI compliance checking. This is equivalent to /flags 0x209BB.
Note
Starting in Windows 10 versions after 1803, using /flags 0x209BB will no longer automatically enable WDF verification. Use the /standard syntax to enable standard options, with WDF verification included. See Driver Verifier Command Syntax for more information.
/volatile
Changes the settings without rebooting the computer. Volatile settings take effect immediately.
On Windows Vista and later versions of Windows, you can use the /volatile parameter with the /flags parameter to enable and disable some options without rebooting. You can also use /volatile with the /adddriver and /removedriver parameters to start or stop the verification of a driver without rebooting, even if Driver Verifier is not already running.
On versions of Windows prior to Windows Vista, the /volatile parameter can be used only with the options listed in VolatileOptions and it can be used to start or stop the verification of a driver without rebooting only if Driver Verifier is already running and the computer has been rebooted.
For details, see Using Volatile Settings.
| Option | Description |
|---|---|
/adddriverVolatileDriverList | (Windows XP and later) Adds the specified drivers to the volatile settings. To specify multiple drivers, list their names, separated by spaces. Wildcard values, such as n.sys, are not supported. See Using Volatile Settings for details. |
/removedriverVolatileDriverList | (Windows XP and later) Removes the specified drivers from the volatile settings. To specify multiple drivers, list their names, separated by spaces. Wildcard values, such as n.sys, are not supported. See Using Volatile Settings for details. |
/reset
Clears all Driver Verifier settings. After the next boot, no drivers will be verified.
/querysettings
(Windows XP and later) Displays a summary of the options that will be activated and drivers that will be verified after the next boot. The display does not include drivers and options added by using the /volatile parameter. For other ways to view these settings, see Viewing Driver Verifier Settings.
/query
Displays a summary of Driver Verifier's current activity. The Level field in the display is the hexadecimal value of options set with the /volatile parameter. See Monitoring Global Counters and Monitoring Individual Counters for explanations of each statistic.
/domainTypes **** Options
Controls the verifier extension settings. The following verifier extension types are supported.
| Types | Description |
|---|---|
wdm | Enables verifier extension for WDM drivers. |
ndis | Enables verifier extension for networking drivers. |
ks | Enables verifier extension for kernel mode streaming drivers. |
audio | Enables verifier extension for audio drivers. |
The following extension options are supported.
| Options | Description |
|---|---|
rules.default | Enables default validation rules for the selected verifier extension. |
rules.all | Enables all validation rules for the selected verifier extension. |
/logging
Enables logging for violated rules detected by the selected verifier extensions.
/livedump
Enables live memory dump collection for violated rules detected by the selected verifier extensions.
/?
Sia move your body zippyshare. Displays command-line help.
For more information about the use of these commands, see Controlling Driver Verifier and Monitoring Driver Verifier.
/help
Displays command-line help.
For more information about the use of these commands, see Controlling Driver Verifier and Monitoring Driver Verifier.
Return Codes
The following values are returned after driver verifier has run.
| 0 | EXIT_CODE_SUCCESS |
| 1 | EXIT_CODE_ERROR |
| 2 | EXIT_CODE_REBOOT_NEEDED |
The Gflags Special Pool feature directs Windows to request memory allocations from a reserved memory pool when the memory is allocated with a specified pool tag or is within a specified size range.
For detailed information about this feature, see Special Pool.
In Windows Vista and later versions of Windows, you can configure the Special Pool feature as a system-wide registry setting or as a kernel flags setting that does not require a reboot. In earlier versions of Windows, Special Pool is available only as a registry setting.
In Windows Vista and later versions of Windows, you can also use the command line to request special pool by pool tag. For information, see GFlags Commands.
This section includes the following topics.
Note Use Driver Verifier to request special pool for allocations by a particular driver. For more information, see the 'Special Pool' topic in the 'Driver Verifier' section of the Windows Driver Kit (WDK).