text stringlengths 0 4.23k |
|---|
ver |
If you want to get the operating system version number through Windows PowerShell, type: |
$PSVersionTable.BuildVersion |
If you want to get the operating system version number through PowerShell 7.x.x, type: |
$PSVersionTable.OS |
verifier |
Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012 |
Driver Verifier monitors Windows kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject Windows drivers to a variety of stresses and tests to find improper behavior. You can configure which tests to run, which allows you to put a d... |
Important |
You must be in the Administrators group on the computer to use Driver Verifier. |
Running Driver Verifier can cause the computer to crash, so you should only run this utility on computers used for testing and debugging. |
Syntax |
verifier /standard /all |
verifier /standard /driver NAME [NAME ...] |
verifier /flags <options> /all |
verifier /flags <options> /driver NAME [NAME ...] |
verifier /rules [OPTION ...] |
verifier /query |
verifier /querysettings |
verifier /bootmode [persistent | disableafterfail | oneboot] |
verifier /reset |
verifier /faults [Probability] [PoolTags] [Applications] [DelayMins] |
verifier /faultssystematic [OPTION ...] |
verifier /log LOG_FILE_NAME [/interval SECONDS] |
verifier /volatile /flags <options> |
verifier /volatile /adddriver NAME [NAME ...] |
verifier /volatile /removedriver NAME [NAME ...] |
verifier /volatile /faults [Probability] [PoolTags] [Applications] [DelayMins] |
verifier /domain <types> <options> /driver ... [/logging | /livedump] |
verifier /logging |
verifier /livedump |
verifier /? |
verifier /help |
Parameters |
Parameter |
Description |
/all |
Directs the Driver Verifier utility to verify all installed drivers after the next boot. |
/bootmode [persistent \| disableafterfail \| oneboot \| resetonunusualshutdown] |
Controls whether the settings for the Driver Verifier utility are enabled after a reboot. To set or change this option, you must reboot the computer. The following modes are available:persistent - Ensures that the Driver Verifier settings persist (stay in effect) over many reboots. This is the default setting.disableaf... |
/driver <driverlist> |
Specifies one or more drivers that will be verified. The driverlist parameter 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, aren't supported. |
/driver.exclude <driverlist> |
Specifies one or more drivers that will be excluded from verification. This parameter is applicable only if all drivers are selected for verification. The driverlist parameter 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, aren't suppo... |
/faults |
Enables the Low Resources Simulation feature in the Driver Verifier utility. You can use /faults in place of /flags 0x4. However, you can't use /flags 0x4 with the /faults subparameters. You can use the following subparameters of the /faults parameter to configure the Low Resources Simulation:Probability - Specifies th... |
/faultssystematic |
Specifies the options for Systematic Low Resources simulation. Use the 0x40000 flag to select the Systematic Low Resources simulation option. The following options are available:enableboottime - Enables fault injections across computer reboots.disableboottime - Disables fault injections across computer reboots (this is... |
/flags <options> |
Activates the specified options after the next reboot. This number can be entered in decimal or in hexadecimal (with an 0x prefix) format. Any combination of the following values is allowed:Value: 1 or 0x1 (bit 0) - Special pool checkingValue: 2 or 0x2 (bit 1) - Force IRQL CheckingValue: 4 or 0x4 (bit 2) - Low Resource... |
/flags <volatileoptions> |
Specifies the the Driver Verifier utility options that are changed immediately without rebooting.This number can be entered in decimal or in hexadecimal (with an 0x prefix) format. Any combination of the following values is allowed:Value: 1 or 0x1 (bit 0) - Special poolValue: 2 or 0x2 (bit 1) - Force IRQL CheckingValue... |
<probability> |
Number between 1 and 10,000 specifying the fault injection probability. For example, specifying 100 means a fault injection probability of 1% (100/10,000).if this parameter isn't specified, the default probability of 6% is used. |
<tags> |
Specifies the pool tags that will be injected with faults, separated by space characters. If this parameter is not specified, then any pool allocation can be injected with faults. |
<apps> |
Specifies the image file name of the apps that will be injected with faults, separated by space characters. If this parameter isn't specified, then low resources simulation can take place in any application. |
<minutes> |
A positive number specifying the length of the period after rebooting, in minutes, during which no fault injection will occur. If this parameter isn't specified, then the default length of 8 minutes is used. |
/iolevel <level> |
Specifies the level of I/O Verification. The value of [level] can be 1 - Enables Level 1 I/O Verification (default) or 2 - Enables Level 1 I/O Verification and Level 2 I/O Verification. If I/O Verification isn't enabled (by using /flags 0x10), /iolevel is ignored. |
/log <logfilename> [/intervalseconds] |
Creates a log file using the specified name. The Driver Verifier utility periodically writes statistics to this file, based on the interval you optionally set. The default interval is 30 seconds. If a verifier /log command is typed at the command line, the command prompt doesn't return. To close the log file and return... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.