How to fix the failure "[FAIL] Traffic was unexpectedly blocked" in the HLK test--AppContainers_Tests

Question

All ipv6 test variation failure.

Variation:

        Address         : fe80::x:x:x:xx
        Protocol        : Tcp
        Capabilities    : InternetClient
        Network Profile : Public
        IsProxy         : No
        Expected Result : Allowed

[FAIL]  Traffic was unexpectedly blocked.
Starting test "Traffic test variation 11"

Variation:

        Address         : fe80::x:x:x:xx
        Protocol        : Tcp
        Capabilities    : InternetClientServer
        Network Profile : Public
        IsProxy         : No
        Expected Result : Allowed

[FAIL]  Traffic was unexpectedly blocked.

Answer 1

Hello,

The error "[FAIL] Traffic was unexpectedly blocked" failure in the HLK (Windows Hardware Lab Kit) test for AppContainers_Tests usually is related network-related issues and ensuring that your AppContainer is configured correctly. I would recommend the next checks:

• Firewall rules: Check if you have set up specific "Allow" rules in your firewall for your application/process
• Group Policy configuration: By running "GPRESULT.EXE /H result.html" you can generate a HTML report of the applied policies to both machine and user, where you can check if any are applying to network restrictions

-Check you AppContainer configuration:

You can use PowerShell to list and view the AppContainer configuration:

Open PowerShell as an administrator.

To list all AppContainers, you can run the following command:

Get-AppxPackage -AllUsers | Select-Object -Property Name, PackageFamilyName, InstallLocation

This command will list installed AppContainers along with their names, package family names, and install locations.

To view the capabilities and permissions associated with a specific AppContainer, you can use the Get-AppxPackageManifest cmdlet along with the package family name:

Get-AppxPackageManifest -Package <PackageFamilyName> | Select-Object -ExpandProperty Capabilities

*Replace <PackageFamilyName> with the actual package family name of the AppContainer you want to inspect.

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer–

Answer 2

I solved this problem because a new network port was added, ensuring that the HLK Client has and only has one network port is no problem.