What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Microsoft Execution Containers (MXC) is a policy-driven runtime for running AI agents and other untrusted, dynamically generated workloads inside an independently enforced boundary. You declare which files, processes, network destinations, credentials, and user-interface resources an agent may use; MXC maps that policy to a process container, Windows session container, WSL environment, or (experimentally) a microVM. If generated code requests an operation outside the policy, the containment layer is designed to block it regardless of what the model decides.
That separation is the essential security property. As Logan Iyer, Microsoft’s Corporate Vice President for Windows Platform + Developer, wrote on October 7, 2026: “An agent cannot be its own security authority. It must run within a boundary defined by the developer or organization and enforced independently of the agent itself.”
What is Microsoft Execution Containers (MXC)?
MXC is an execution and containment layer for model-generated code, plugins, tools, agent harnesses, or a complete agent. Instead of trusting an agent to follow a prompt such as “do not access production,” a developer or organization declares the allowed resources and lets the operating system enforce those rules outside the workload.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsThe policy travels with the execution request. MXC selects an appropriate backend and applies controls to the covered process and its children. This makes the same policy model usable for a short coding task, a long-running desktop automation job, a Linux-first toolchain, or a higher-risk workload that merits hardware-backed virtualization.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Microsoft described MXC as generally available in its October 7, 2026 announcement. Availability of individual integrations and management features can differ, so check the release status of the agent, Windows edition, and organizational service you intend to use.
Why must the policy be outside the AI agent?
An agent can generate or execute code that is buggy, manipulated by untrusted input, or simply wrong about its own permissions. If the agent is the only component deciding whether an action is safe, a prompt-injection attack or model error can turn a prohibited action into an approved one.
MXC moves that decision to a boundary the workload cannot rewrite. A process attempting an undeclared file read, network connection, or UI operation should receive a denial even if the model explicitly asks for it. This is containment, not a promise that the code is correct: the policy still has to cover every relevant process and resource.
Which resources can an MXC policy control?
MXC policies are multidimensional. A useful policy specifies not only where the agent runs, but also the exact operations it may perform there.
| Policy area | What you define | Questions to answer |
|---|---|---|
| Containment type | Process, session, WSL, or microVM backend | Do you need a desktop, Linux compatibility, low latency, or the strongest available boundary? |
| Process and environment | Command to launch, child-process behavior, and environment variables | Which executable is the entry point? Which helpers are required, and which variables could expose secrets? |
| Files | Read, write, and deny rules for paths | Which project directories are writable? Are source, credentials, system folders, and build artifacts separated? |
| Network | Inbound and outbound destinations, ports or services, and loopback behavior | Does the task need package downloads, an API, a local service, or no network at all? |
| User interface | Desktop, clipboard, input, and UI access | Can the workload run headlessly, or must it interact with a visible application? |
| Identity and credentials | Which credentials are injected and where they are available | Can the task use short-lived, least-privilege tokens instead of a user’s full profile? |
Start with explicit denies for sensitive locations and services, then add the smallest grants that make the task work. A broad writable home directory or unrestricted outbound network can erase much of the benefit of an otherwise well-designed container.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Which MXC containment option should you choose?
Choose the lightest backend that satisfies the workload’s boundary and compatibility requirements. The options differ in startup overhead, desktop behavior, Linux support, and isolation strength.
| Option | Best fit | Boundary and trade-offs |
|---|---|---|
| Process container | Responsive coding agents and tool execution | Lightweight process-level file and network controls using platform primitives. It favors low latency, but it covers the selected command and child processes rather than an entire independent operating-system instance. |
| Session container (Windows 11) | Long-running automation that needs a desktop | Separates the Windows account and session, desktop, clipboard, UI, and input. Use it when graphical state must be isolated from the operator’s normal session. |
| WSL container (Windows 11) | Linux-first agent toolchains | Provides a Linux environment through Windows Subsystem for Linux. It is a compatibility choice for Linux tools, not automatically a stronger security boundary than every other option. |
| MicroVM (Windows 11 and Linux, experimental) | Higher-risk workloads needing stronger isolation | Uses a hardware-enforced virtualized boundary and supports a full Linux workload. Its experimental status means you should validate supported features and operational behavior before relying on it in production. |
When is a process container enough?
Use a process container for a narrowly scoped compiler, test runner, formatter, or coding agent that can work without a separate desktop. It is usually the simplest way to keep file and network permissions close to the task. Make sure every helper process is launched under the same containment policy; starting a tool through an unsandboxed fallback changes the effective boundary.
When should you use a session container?
A session container is appropriate when automation must open windows, send input, use a clipboard, or preserve a desktop session for hours. Its separate account and session reduce accidental interaction with the operator’s desktop, but UI permissions still need to be granted deliberately.
When does WSL make sense?
Choose WSL when the agent’s dependencies are Linux-oriented or its scripts assume Linux filesystem and command behavior. Keep file sharing narrow: mounting broad Windows paths can give a Linux toolchain more access than the project requires.
What does the experimental microVM option add?
A microVM places the workload behind hardware-enforced virtualization and offers full Linux compatibility. That is useful for untrusted code with a higher potential impact, but experimental components may have feature, performance, or management gaps that your deployment team must test.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
How do you author and roll out an MXC policy?
Use an iterative rollout. Begin with known requirements, observe real accesses, grant only what is needed, and finish in enforcement before production use.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute- Map the task. Identify the launch command, child tools, project paths, package registries or APIs, local services, UI actions, and credentials. Separate read-only inputs from writable outputs.
- Write the narrow initial policy. Declare the containment type, process and environment, file read/write/deny rules, inbound and outbound network destinations, loopback behavior, and UI permissions. Do not start with an unrestricted filesystem or open internet.
- Observe with Permissive mode. Permissive mode records operations that would have been denied while allowing them, subject to other operating-system or organizational restrictions. Use the resulting observations to discover hidden dependencies, not to justify permanent broad access.
- Probe safely with Learning mode. Learning mode blocks ungranted operations and records the denied attempts. Run representative tasks, including failure paths, so required resources appear in the activity data without being silently allowed.
- Review every attempted access. Grant a specific file path, destination, or executable only when the task genuinely needs it. Investigate unexpected domains, writes outside the workspace, credential requests, and attempts to launch an unlisted helper.
- Switch production workloads to Enforcement. Enforcement blocks operations outside the policy. It runs without an activity report, so complete discovery and review before making this the normal operating mode.
- Make denials visible to the agent and operator. The harness should explain that an organizational policy blocked a resource and identify the required approval path. A clear denial is safer than silently retrying through an unsandboxed tool.
Policies should be versioned with the agent or project configuration. Re-run Learning after dependency upgrades, because a new package manager, compiler, or plugin can introduce a previously unseen access requirement.
How should you handle files, networking, and credentials?
Files
Give source trees read access when possible and restrict writes to a dedicated workspace, build directory, or temporary directory. Deny credential stores, system directories, unrelated user profiles, and deployment locations unless the task has a documented reason to use them. Treat generated archives and logs as outputs that may contain secrets; control where they can be written and who can retrieve them.
Networking
Prefer an allowlist of required hostnames or services over unrestricted outbound access. Package installation often needs a registry, while tests may need only loopback to a service launched inside the boundary. Decide explicitly whether inbound connections are needed, and test loopback separately because a local service can still expose sensitive data if its binding and policy are too broad.
Credentials
Isolation does not make an injected credential safe by itself. A token explicitly exposed to the workload can be copied to an allowed file or network destination. Use short-lived credentials with the smallest scope, avoid placing them in general environment variables when a narrower mechanism is available, and revoke them after the run.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
What happens when an agent is blocked?
A denial usually means the policy is doing its job, but the response depends on the resource requested. Diagnose the denied operation rather than disabling containment.
| Symptom | Likely cause | Safer correction |
|---|---|---|
| Build fails while reading a dependency | The dependency cache or registry path is not granted | Grant the specific cache directory or registry destination, preferably read-only where practical, then retest in Learning mode. |
| Tests cannot reach a local service | Loopback or the service port is outside the network policy | Declare the required loopback behavior and port; do not open all inbound or outbound traffic. |
| Desktop automation sees the wrong screen | The workload is in a separate session or lacks UI/input permission | Use a session container and grant only the required desktop, clipboard, and input operations. |
| Agent asks for a secret repeatedly | The credential was not injected, is unavailable in the selected backend, or is blocked by organizational policy | Use an approved, least-privilege credential path and surface the policy denial to the operator instead of copying a secret into the workspace. |
| Tool appears to escape the policy | A helper was launched outside the covered command, or a fallback path is unsandboxed | Trace the process tree and ensure every child and fallback remains under MXC; treat any uncovered process as outside the boundary. |
How does MXC fit into Microsoft’s Windows control plane?
Microsoft describes MXC as part of a broader control plane rather than a standalone sandbox switch. Planned and named connections include Entra identity, Intune policy, Agent 365 governance, Defender, and Purview. Windows 365 support is intended to let agents run on Cloud PCs while using the same containment model.
These connections can help organizations apply identity, device, data-protection, and threat-response rules consistently. They do not remove the need to define resource-level permissions in MXC. Management features and integrations may be forthcoming, and Microsoft’s named agent integrations—including GitHub Copilot, OpenAI Codex, OpenClaw, Replit, LM Studio, NVIDIA OpenShell, and Unsloth AI—can have different release stages. Verify the current support matrix for the exact version and service you deploy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What can MXC not protect you from?
MXC is a runtime containment layer, not a replacement for endpoint security, identity governance, code review, or least-privilege design. Its boundary applies only to covered processes and granted resources.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Uncovered execution: A process started outside MXC, or an unsandboxed fallback, is not protected by the policy you wrote.
- Overbroad grants: Read/write access to an entire profile, unrestricted network access, or broad UI permissions can let a compromised task cause substantial damage while technically staying inside the boundary.
- Injected credentials: Secrets deliberately exposed to the agent can be exfiltrated through any destination the policy allows.
- Platform limitations: Backend differences, Windows edition requirements, experimental microVM support, and integration maturity can affect which controls are available.
- Application flaws: A sandbox cannot validate business logic, detect every malicious instruction, or replace review of code that will later run in production.
Use defense in depth: isolate the workload, restrict identity and data access, monitor the endpoint and network, review generated code, and keep a recovery path for credentials and files.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
How can an organization choose a default policy?
Most teams can standardize a small set of profiles and require an exception for broader access.
| Workload profile | Default choice | Exception trigger |
|---|---|---|
| Local coding, formatting, or tests | Process container; project read access and a dedicated writable build directory; no inbound network | Needs a desktop, privileged compiler, or external service |
| Desktop workflow automation | Session container with a separate account and narrowly granted UI/input access | Requires Linux-only tooling or stronger hardware isolation |
| Linux build or data pipeline | WSL container with explicit Windows path sharing and network allowlist | Processes untrusted archives or high-impact secrets |
| High-risk untrusted code | Evaluate the experimental microVM and keep credentials and network access minimal | Production dependence on a feature not yet supported by the microVM backend |
Record the owner, policy version, granted resources, expiration date for exceptions, and evidence from Learning runs. This turns a one-time sandbox configuration into an auditable operating practice.
Frequently Asked Questions
Does MXC replace antivirus or endpoint detection software?
No. MXC limits the resources available to covered processes, while endpoint security tools detect and respond to threats across the device. Run both, and keep telemetry and response policies active on the host and any Cloud PC.
Can an MXC container safely run code from an untrusted repository?
It can reduce the repository’s access to files, services, and networks when the policy is narrow and all child processes remain covered. Review archive handling, package-install behavior, injected credentials, and any step that launches an external or unsandboxed helper before treating the run as low risk.
Is a WSL container automatically more secure than a Windows process container?
No. WSL primarily addresses Linux tool compatibility. Effective security depends on the declared paths, network rules, credentials, and whether additional processes or shared Windows directories fall outside the intended boundary.
What should I test before enabling Enforcement mode?
Exercise normal, error, update, and recovery paths with representative projects. Confirm that required package registries, local services, UI actions, logs, and credential flows work, and inspect denied operations from Learning mode for unexpected dependencies.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →
