Dr. Memory failed to start the target application, perhaps due to interference from invasive security software. - Visual Studio Interference

**Describe the bug**

Dr. Memory fails to start the target application (`explorer.exe`) on a Windows 11 Pro 24H2 system (OS build 26100.3323) after installing the Windows 11 SDK (10.0.26100.0) as part of Visual Studio Community 2022 (version 17.13.2). The error indicates an issue with locating the results file and potential interference from invasive security software. This issue persists even when running Dr. Memory in light mode, with specific options to limit its functionality, or with debug options enabled. However, running DynamoRIO directly with the command `C:\Program Files (x86)\Dr. Memory\dynamorio\bin64\drrun.exe -- explorer.exe` successfully starts `explorer.exe` without any error messages.

**To Reproduce**

1. Install Visual Studio Community 2022 (version 17.13.2) with only the Windows 11 SDK (10.0.26100.0) and no additional workloads.
2. Open a command prompt.
3. Run the command: `drmemory -- explorer.exe`.
4. Observe the error message indicating that Dr. Memory is unable to locate the results file and fails to start the target application.
5. Run the command with the light mode option: `drmemory -light -- explorer.exe`.
6. Observe the same error message indicating that Dr. Memory fails to start the target application.
7. Run the command with additional options: `drmemory -leaks_only -no_count_leaks -no_track_allocs -- explorer.exe`.
8. Observe the same error message indicating that Dr. Memory fails to start the target application.
9. Run the command with debug options: `drmemory -debug -dr_debug -pause_at_assert -- explorer.exe`.
10. Observe the same error message indicating that Dr. Memory fails to start the target application.
11. Run the command under plain DynamoRIO: `C:\Program Files (x86)\Dr. Memory\dynamorio\bin64\drrun.exe -- explorer.exe`.
12. Observe that `explorer.exe` starts correctly without any error messages.

**Expected behavior**

Dr. Memory should successfully start the target application (`explorer.exe`) and begin monitoring it without errors, regardless of the Windows 11 SDK installation or the mode in which Dr. Memory is run. Running DynamoRIO directly should not be necessary to start `explorer.exe`.

**Screenshots or Pasted Text**

When the Windows SDK is not installed, Dr. Memory works correctly and produces the following output:

```
~~Dr.M~~ Dr. Memory version 2.6.20133
~~Dr.M~~ Running "explorer.exe"
~~Dr.M~~ Using system call file C:\Users\antoine\AppData\Roaming\Dr. Memory\symcache\syscalls_wow64.txt
~~Dr.M~~ ERROR: Failed to find "main" for limiting memory dump
~~7192~~ WARNING: application is missing line number information.
~~Dr.M~~
~~Dr.M~~ NO ERRORS FOUND:
~~Dr.M~~ 0 unique, 0 total unaddressable access(es)
~~Dr.M~~ 0 unique, 0 total uninitialized access(es)
~~Dr.M~~ 0 unique, 0 total invalid heap argument(s)
~~Dr.M~~ 0 unique, 0 total GDI usage error(s)
~~Dr.M~~ 0 unique, 0 total handle leak(s)
~~Dr.M~~ 0 unique, 0 total warning(s)
~~Dr.M~~ 0 unique, 0 total, 0 byte(s) of leak(s)
~~Dr.M~~ 0 unique, 0 total, 0 byte(s) of possible leak(s)
~~Dr.M~~ ERRORS IGNORED:
~~Dr.M~~ 162 potential error(s) (suspected false positives)
~~Dr.M~~ (details: C:\Users\antoine\AppData\Roaming\Dr. Memory\DrMemory-explorer.exe.4552.000\potential_errors.txt)
~~Dr.M~~ 41 potential leak(s) (suspected false positives)
~~Dr.M~~ (details: C:\Users\antoine\AppData\Roaming\Dr. Memory\DrMemory-explorer.exe.4552.000\potential_errors.txt)
~~Dr.M~~ 631 unique, 1140 total, 1575883 byte(s) of still-reachable allocation(s)
~~Dr.M~~ (re-run with "-show_reachable" for details)
~~Dr.M~~ Details: C:\Users\antoine\AppData\Roaming\Dr. Memory\DrMemory-explorer.exe.4552.000\results.txt
~~Dr.M~~ WARNING: application exited with abnormal code 0x1
```

When the Windows SDK is installed, Dr. Memory produces the following error output:

```
~~Dr.M~~ WARNING: unable to locate results file: can't open C:\Users\antoi\AppData\Roaming\Dr. Memory/resfile.12576 (code=2).
Dr. Memory failed to start the target application, perhaps due to
interference from invasive security software.
Try disabling other software or running in a virtual machine.
WARNING: Examine the following unusual libraries in this process to help identify
invasive software that may have affected the target application:

C:\WINDOWS\system32\fltlib.dll
C:\WINDOWS\system32\version.dll
C:\Windows\System32\guard32.dll
C:\WINDOWS\System32\msvcp_win.dll
C:\WINDOWS\System32\ole32.dll
C:\WINDOWS\System32\IMM32.DLL
C:\WINDOWS\System32\win32u.dll
C:\WINDOWS\System32\combase.dll
C:\WINDOWS\System32\gdi32full.dll

Please file a bug about this at [http://drmemory.org/issues](http://drmemory.org/issues)
~~Dr.M~~ WARNING: application exited with abnormal code 0xffffffff
```

**Versions**

- **Dr. Memory Version:** 2.6.20133
- **Latest Build Tested:** Yes
- **Operating System:** Windows 11 Pro 24H2 (OS build 26100.3323)
- **Application Bitwidth:** 64-bit
- **Visual Studio Version:** Community 2022 (version 17.13.2)
- **Windows SDK Version:** 10.0.26100.0