InjectApplication throws "Attempted to write protected memory" — reproducible after first run, survives full reboot

[MateoValenciaPWB]

Steps to reproduce

1. Create a new project following the README exactly (Sdk="Nice3point.Revit.Sdk/6.2.3", <OutputType>Exe</OutputType>, <Configurations>Debug.R24</Configurations>), referencing:

   <PackageReference Include="Nice3point.Revit.Api.RevitAPI" Version="$(RevitVersion).*" />
   <PackageReference Include="Nice3point.TUnit.Revit" Version="$(RevitVersion).*" />
   <PackageReference Include="Polyfill" Version="11.0.1" PrivateAssets="all" />

2. Add the global executor registration exactly as shown in the README:

   [assembly: TestExecutor<RevitThreadExecutor>]

3. Add the exact ApplicationTests sample from the README / your own test project:

   public sealed class ApplicationSmokeTests : RevitApiTest
   {
       [Test]
       public async Task Create_XYZ_ValidDistance()
       {
           var point = Application.Create.NewXYZ(3, 4, 5);
           await Assert.That(point.DistanceTo(XYZ.Zero)).IsEqualTo(7).Within(0.1);
       }
   }

4. Run dotnet run -c Debug.R24 (also reproduced with -c Debug.R25; -c Debug.R26 fails separately/earlier with a RevitAPI, Version=26.4.0.0 FileNotFoundException, since the installed Revit 2026 update — RevitAPI.dll file version 26.5.0.55 — is newer than the latest published Nice3point.Revit.Api.RevitAPI package, 2026.4.10).

✔️ Expected Behavior

The test session initializes, InjectApplication() succeeds, and the test runs against the live Application.

❌ Actual Behavior

The first run on this machine succeeded (R24 and R25 both passed cleanly). Every run since — including after a full machine reboot — fails deterministically in BeforeTestSession with:

TUnit.Core.Exceptions.BeforeTestSessionException: BeforeTestSession hook failed: Attempted to write protected memory.
   at TUnit.Engine.Services.HookExecutor.ExecuteBeforeTestSessionHooksAsync(CancellationToken cancellationToken)
   at TUnit.Engine.TestExecutor.EnsureTestSessionHooksExecutedAsync(CancellationToken cancellationToken)
   at TUnit.Engine.TestExecutor.ExecuteAsync(AbstractExecutableTest executableTest, TestInitializer testInitializer, CancellationToken cancellationToken, Nullable`1 testTimeout)
 ---> System.InvalidOperationException: Attempted to write protected memory.
   at Nice3point.Revit.Injector.Injector.InjectApplication()
   at Nice3point.TUnit.Revit.RevitApplicationTest.InitializeRevitConnection()
   at TUnit.Generated.Hooks.Nice3point_TUnit_Revit_RevitApiTest_RevitSessionSetup_Before_TestSession.Nice3point_TUnit_Revit_RevitApiTest_RevitSessionSetup_Before_TestSessionInitializer.<>c.<global_Nice3point_TUnit_Revit_RevitApiTest_RevitSessionSetup_0Params_Body>b__0_0()

This reproduces identically whether invoked from a bash/MSYS shell or from native Windows PowerShell, ruling out a shell-specific process-creation quirk.

Environment

• OS: Windows, build 10.0.26200
• Revit 2024, RevitAPI.dll file version 24.3.40.26
• Nice3point.Revit.Sdk 6.2.3
• Nice3point.TUnit.Revit 2024.1.1 (resolved via $(RevitVersion).*)
• Nice3point.Revit.Injector / PolyHook2.NET 1.1.3 (transitive, PrivateAssets="all")
• dotnet SDK 10.0.400
• TUnit engine v1.44.0.0 (per the test-run banner)
• Ran via dotnet run -c Debug.R24 (dotnet test is refused outright on this SDK: "Testing with VSTest target is no longer supported by Microsoft.Testing.Platform on .NET 10 SDK and later")

Things I ruled out before filing

• No leftover Revit.exe or test-host processes from earlier runs (tasklist clean).
• No Attack Surface Reduction rules or Controlled Folder Access configured (Get-MpPreference).
• HVCI / Memory Integrity / Credential Guard all off (Win32_DeviceGuard: SecurityServicesRunning: {0}), CET/Shadow Stacks not forced at the system level.
• No named EDR agent (CrowdStrike/SentinelOne/etc.) running as a service.
• Not shell-specific (same failure from bash and native PowerShell).
• Not fixed by a full OS reboot.

Possible relevant environmental factor (unconfirmed)

This machine also has an unrelated, unrelated-vendor Revit add-in of ours deployed per-user under %AppData%\Autodesk\Revit\Addins\2024\2025\2026\ (from normal Nice3point.Revit.Sdk DeployAddin=true debug builds of a separate project). We haven't yet tested with that add-in's manifest temporarily removed, so we can't confirm or rule out an interaction between that add-in's normal (UI-expecting) OnStartup and the injector's restricted "database-level Application" bootstrap — flagging it in case it's a known interaction class.

Happy to gather more diagnostics (procmon trace, memory dump, etc.) if useful.

[Nice3point]

Version=26.4.0.0 FileNotFoundException :

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Revit--Requirements-for-products-affected-by-the-Microsoft--NET-10-transition.html

revit 2026 updated from .Net 8 to .Net 10. You need to update a target framework for your test project.

https://github.com/Nice3point/RevitTemplates/wiki/MsBuild-Sdk#configuration

<Project Sdk="Nice3point.Revit.Sdk/6.2.3">

    <PropertyGroup>
        <OutputType>Exe</OutputType>
        <AllowUnsafeBlocks>true</AllowUnsafeBlocks>
        <Configurations>Debug.R23;Debug.R24;Debug.R25;Debug.R26;Debug.R27</Configurations>
        <Configurations>$(Configurations);Release.R23;Release.R24;Release.R25;Release.R26;Release.R27</Configurations>
    </PropertyGroup>

    <PropertyGroup>
        <!-- SDK overrides -->
        <TargetFramework Condition="$(RevitVersion) == '2026'">net10.0-windows7.0</TargetFramework>
    </PropertyGroup>

   ...

SDK still uses .NET 8 for Revit 2026, because updating to .NET 10 for minor patch can breaks all add-ins that depends of this library

Run dotnet run -c Debug.R24 :

Revit 2024 broken? Try to open Revit 24 once in UI, need to accept the License. Also try to set TUnit version to latest explicitly. Attempted to write protected memory its a Revit core library level, usually need to open Revit once to accept something. On my my PC everything still works. If it cant help write more info. DeployAddin=true not needed for unit tests, only the project reference.

Create a new project following the README exactly

Better to use template for Unit tests: https://github.com/Nice3point/RevitTemplates