46 lines
4.1 KiB
Markdown
46 lines
4.1 KiB
Markdown
# Known driver, software and feature issues
|
|
|
|
Reviewed: **2026-09-15**. The executable list is
|
|
[config/diagnostics-watchlist.yaml](../config/diagnostics-watchlist.yaml). It flags documented
|
|
risks and compatibility conditions, not old release dates or vendor reputation.
|
|
Every match becomes a warning with an advisory link and an internal link to the
|
|
PDF's list. It adds no score penalty; independent event findings still do.
|
|
|
|
| Entry | Required evidence | Documented issue / source |
|
|
| --- | --- | --- |
|
|
| WinRing0 | `system_drivers.PathName` basename exactly `WinRing0.sys` or `WinRing0x64.sys` | Candidate vulnerable low-level driver; verify binary identity. [Microsoft advisory](https://support.microsoft.com/en-us/windows/security/threat-malware-protection/microsoft-defender-antivirus-alert-vulnerabledriver-winnt-winring0). |
|
|
| Dell dbutil | Basename exactly `dbutil_2_3.sys` | Candidate CVE-2021-21551 driver. [Dell advisory](https://www.dell.com/support/kbdoc/en-us/000186020/additional-information-regarding-dsa-2021-088-dell-client-platform-security-update-for-an-insufficient-access-control-vulnerability-in-the-dell-dbutil-driver). |
|
|
| GIGABYTE OC GURU II | Exact product alias and version `2.08` | Vendor-listed low-level driver vulnerabilities. Other/unknown versions do not match. [GIGABYTE advisory](https://www.gigabyte.com/uk/Support/Security/1801). |
|
|
| Intel wireless failures | `Netwtw10` inventory plus at least two events 5002/5005/5010/5032 | Observed malfunction warrants driver/firmware review. [Intel's related AX210 guidance](https://www.intel.com/content/www/us/en/support/articles/000089544/wireless.html) is context, not proof its specific fix applies to the captured AX200/version. |
|
|
| OBS and overlays | OBS Studio plus an exact listed overlay product name | Possible capture-hook conflict; installed does not mean concurrently running. [OBS conflict list](https://obsproject.com/kb/known-conflicts), [RTSS compatibility guidance](https://obsproject.com/kb/game-capture-troubleshooting). |
|
|
| OBS and audio enhancements | OBS Studio plus a listed Nahimic/Sonic product or `NahimicService` | Possible OBS interference. [OBS conflict list](https://obsproject.com/kb/known-conflicts). |
|
|
| SMBv1 | SMB1Protocol/Client/Server with `State=Enabled` or enum `2` | Protocol security risk. Disabled/unknown states and SMB Direct do not match. [Microsoft guidance](https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3). |
|
|
|
|
## Driver list and limitations
|
|
|
|
[Microsoft's recommended driver block rules](https://learn.microsoft.com/en-us/windows/security/application-security/application-control/app-control-for-business/design/microsoft-recommended-driver-block-rules)
|
|
are the broader driver reference linked from every report. The renderer does not
|
|
apply this list or equate its small name-based watchlist with Microsoft's binary,
|
|
signer, hash and version policy. Capture metadata cannot establish exploitation.
|
|
|
|
Stopped drivers still count as installed candidates, with their state displayed.
|
|
Only successful collection sections are searched. Missing sections remain in the
|
|
final coverage recap. Unknown versions do not satisfy exact-version constraints.
|
|
OBS alone, an Intel/NVIDIA vendor name, enabled virtualization, and a driver date
|
|
are not watchlist matches.
|
|
|
|
## Maintaining the list
|
|
|
|
1. Verify a primary vendor advisory and its affected products, versions and conditions.
|
|
2. Add a stable ID, category, precise `match` selectors, a scoped explanation,
|
|
supported review action and HTTPS reference in the YAML. Update the review date.
|
|
3. Use `requires` for co-installation conditions and `events` for observed failure
|
|
prerequisites. Exact `versions` are checked on the same matched record.
|
|
4. Add positive and negative assertions to `tools/check-diagnostics.typ`, including
|
|
unaffected/unknown versions, similarly named products, missing data and disabled states.
|
|
5. Render fixtures and all captures. Review updated vendor guidance when revising
|
|
the list; it is not refreshed during compilation.
|
|
|
|
Avoid generic substring matches, blanket vendor exclusions, claims that a
|
|
candidate caused a crash, and recommendations to bypass driver security.
|