cargo test --workspace failed with App Control Policy

[westerdaled]

I am trying set upmxc on Windows 11.

During the setup I have successfully run:
.\build.bat --with-wslc

A this stage , I was hoping to spin off a mxc container, say for an openclaw_dev install, but as shown below, I think I need configure my App Control Policy. As shown below. Also do I need to upgrade WSL beyond 2.7.8.0 ?

cargo test --workspace

Compiling windows v0.62.2
Compiling memoffset v0.9.1
Compiling crc32fast v1.5.0
Compiling libc v0.2.186
error: failed to run custom build command for generic-array v0.14.7

Caused by:
could not execute process D:\mcxhost\mxc\src\target\debug\build\generic-array-0094dd08cedfbcab\build-script-build (never executed)

Caused by:
An Application Control policy has blocked this file. (os error 4551)
warning: build failed, waiting for other jobs to finish...

[westerdaled]

Looks like this a setting issue not doc issue .

Windows Security → App & Browser Control → Reputation-based protection → Disable Potentially unwanted app blocking.
This seems to resolve the issue

[craigloewen-msft]

What does wsl --version show as the output? wslc isn't yet released so to use it in MXC you have to compile and install it from source which could add complications here.

Building it from source and installing it instructions are here: https://github.com/microsoft/wsl

We are also releasing WSLc very soon which might fix this.

[westerdaled]

wsl --version
WSL version: 2.7.8.0

I am inclined to agree with you. Maybe I should wait for the released version of wslc, rather keep hitting issues, such as my other one: #553

[craigloewen-msft]

I think that might be wise

I can tell from your WSL version that you are on one that doesn't support WSL container (You can always verify with wslc --version).

[westerdaled]

I have tried updating wsl a few times but I unless there is preview channel I can access, I won't be able to reach the magic v 2.8.1 that Copilot tells me I need .

[craigloewen-msft]

WSLc is now available!

You can just run wsl --update --pre-release to get it and then you should be able to do all the WSLc commands you want :)

[westerdaled]

Yes, thanks. I did that earlier, restarted the terminal session and now able to start wslc..Not sure what I will do with it yet.. Maybe OpenClaw-dev ,,🤔. Sent from Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________