PowerShell 7.6.2 is now available for download, marking a significant update for the cross-platform automation and configuration framework. Built on the .NET 10.0.300 runtime, this release introduces native AppContainer isolation for enhanced script security and aligns telemetry data collection with Windows privacy settings.

.NET 10.0.300 Under the Hood

The move to .NET 10.0.300 provides PowerShell 7.6.2 with access to the latest runtime improvements. Users can expect faster startup times, reduced memory usage, and access to new .NET APIs. The upgrade also ensures compatibility with the latest .NET libraries, allowing administrators to leverage modern .NET features directly from their scripts.

The .NET 10 base includes numerous performance optimizations in the JIT compiler and garbage collection that translate directly into more responsive command-line experiences. For large-scale automation tasks, even milliseconds matter, and this release shaves off noticeable overhead.

AppContainer Support: A New Layer of Security

Perhaps the most impactful addition is AppContainer mode. First introduced in the Windows operating system for Universal Windows Platform (UWP) applications, AppContainer provides a sandboxed execution environment that restricts script capabilities to a tightly controlled set. When PowerShell is configured to run in AppContainer, scripts operate with significantly reduced privileges, protecting sensitive system areas from unintended access.

This feature is opt-in and configurable per session. Administrators can launch PowerShell with the -AppContainer flag to enable isolation. Inside the sandbox, scripts have limited network access, restricted file system visibility, and cannot interact with other processes outside the container. This is especially useful for running untrusted or third-party automation scripts without risking the host system's integrity.

Microsoft has been steadily improving AppContainer integration across its developer tools, and PowerShell’s adoption signals a broader strategy to harden scripting environments against supply chain attacks. By default, the feature is disabled, preserving backward compatibility while offering a new security lever for cautious IT environments.

Telemetry That Respects Your Privacy

PowerShell 7.6.2 changes how telemetry is handled on Windows. Previous versions of PowerShell 7.x collected basic usage data independently of the operating system's diagnostic settings. This update synchronizes PowerShell's telemetry behavior with the Windows privacy configuration.

If you have disabled optional diagnostic data in Windows Privacy Settings (Settings > Privacy & security > Diagnostics & feedback), PowerShell 7.6.2 will no longer send telemetry data to Microsoft. The change affects both the Windows MSI package and the Microsoft Store version. Users on Linux and macOS continue to have their own telemetry controls via environment variables.

For enterprise administrators managing fleets of Windows machines, this alignment means group policies that govern Windows telemetry now also apply to PowerShell without additional configuration. It simplifies compliance and reduces the overhead of managing separate privacy settings for different Microsoft products.

Microsoft has also updated the privacy statement for PowerShell to reflect this integration, noting that no script content or personal data is ever collected—only aggregated performance and usage metrics that help improve the tool.

Additional Improvements and Fixes

Beyond the headlining features, PowerShell 7.6.2 includes a collection of bug fixes and incremental enhancements. Cmdlet performance has been improved for Get-ChildItem when traversing large directory structures, and tab completion now handles nested module commands more reliably.

The release also patches several security vulnerabilities identified in the .NET base class libraries, ensuring that common scripting operations do not inadvertently expose systems to remote code execution risks. Users are strongly encouraged to upgrade from previous 7.6.x versions.

How to Get PowerShell 7.6.2

You can download the installers for Windows, macOS, and Linux from the official GitHub releases page. Windows users can also get it via winget:

winget install --id Microsoft.PowerShell --version 7.6.2.0

For those who prefer the ZIP package or global deployment with MSI, all standard installation methods remain. Microsoft’s official Docker images have also been updated to include this release.

What’s Next for PowerShell

With .NET 10 still in active development, PowerShell 7.6.2 serves as a stable anchor for this generation. Upcoming previews will continue to explore deeper AppContainer integration, possibly extending to constrained language mode defaults. The team is also working on improving remote session performance and expanding the secret management module’s capabilities.

For Windows enthusiasts, this release underscores Microsoft’s commitment to modernizing the command line while respecting user privacy and security. The combination of .NET 10, AppContainer, and telemetry alignment makes PowerShell 7.6.2 one of the most significant updates in the 7.x series.