Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.microsoft.com/en-us/powershell/scripting/powershell-support-lifecycle below:

PowerShell Support Lifecycle - PowerShell

PowerShell follows the Microsoft Modern Lifecycle Policy. Support dates follow the .NET Support Policy. In this servicing approach, customers can choose Long Term Support (LTS) releases or current releases.

An LTS release of PowerShell is built on an LTS release of .NET. Updates to an LTS release only contain critical security updates and servicing fixes that are designed to minimize impact on existing workloads.

A current release is a release that occurs between LTS releases. Current releases can contain critical fixes, innovations, and new features. Microsoft supports a current release for six months after the next LTS release.

Both LTS and current versions of PowerShell receive security updates and bug fixes. Microsoft only supports the latest update version of a release.

Microsoft provides support for PowerShell on a best-effort basis. Support for Windows PowerShell 5.1 is provided through Windows support channels. You can use the standard paid support channels to get support for PowerShell.

• Support for business
• Contact support

There are many free support options available from the PowerShell community. The most active community support channels are available through Discord or Slack. The discussion channels are mirrored on both platforms, so you can choose the platform that you prefer. These channels can help you troubleshoot issues, answer questions, and provide guidance on how to use PowerShell.

If you think that you found a bug, you can file an issue on GitHub. The PowerShell team can't provide support through GitHub, but they welcome bug reports. The community support page provides links to the most popular community support channels.

PowerShell runs on multiple operating systems (OS) and processor architecture platforms. The platform must meet the following criteria:

• The target platform (OS version and processor architecture) is supported by .NET.
• Microsoft has tested and approved PowerShell on the target platform.
• The OS version is supported by the distributor for at least one year.
• The OS version isn't an interim release or equivalent.
• The OS version is currently supported by the distributor.

Support for PowerShell ends when either of the following conditions are met:

• The target platform reaches end-of-life as defined by the platform owner
• The specific version of PowerShell reaches end-of-life

After a version of PowerShell reaches end-of-life, no further updates, including security updates, are provided. Microsoft encourages customers to upgrade to a supported version of PowerShell to continue receiving updates and support.

Microsoft supports PowerShell until PowerShell reaches end-of-support or the version of Windows reaches end-of-support.

The Docker images for the .NET SDK contain the latest versions of PowerShell. These images are available from the Microsoft Artifact Registry.

These images may not have the latest security updates. Microsoft recommends that you update the OS packages to the latest version to ensure the latest security updates are applied.

These images are provided for testing purposes. If you need a Docker image for a production workload, you should build and maintain your own.

Microsoft supports PowerShell until PowerShell reaches end-of-support or the version of macOS reaches end-of-support.

• macOS 15 (Sequoia) x64 and Arm64
• macOS 14 (Sonoma) x64 and Arm64
• macOS 13 (Ventura) x64 and Arm64

Apple determines the support lifecycle of macOS. For more information, see the following:

• macOS release notes
• Apple Security Updates

Microsoft supports PowerShell until PowerShell reaches end-of-support or the version of Alpine reaches end-of-life.

The Docker images for the .NET SDK contain the latest versions of PowerShell. These images are available from the Microsoft Artifact Registry.

These images are built from official operating system (OS) images provide by the OS distributor. These images may not have the latest security updates. Microsoft recommends that you update the OS packages to the latest version to ensure the latest security updates are applied.

These images are provided for testing purposes. If you need a Docker image for a production workload, you should build and maintain your own.

Microsoft supports PowerShell until PowerShell reaches end-of-support or the version of Debian reaches end-of-life.

Install package files (.deb) are also available from https://packages.microsoft.com/.

The Docker images for the .NET SDK contain the latest versions of PowerShell. These images are available from the Microsoft Artifact Registry.

These images are built from official operating system (OS) images provide by the OS distributor. These images may not have the latest security updates. Microsoft recommends that you update the OS packages to the latest version to ensure the latest security updates are applied.

These images are provided for testing purposes. If you need a Docker image for a production workload, you should build and maintain your own.

Microsoft supports PowerShell until PowerShell reaches end-of-support or the version of RHEL reaches end-of-support.

Install package files (.rpm) are also available from https://packages.microsoft.com/.

• RHEL 10 - OS support ends on 2035-05-31
• RHEL 9 - OS support ends on 2032-05-31
• RHEL 8 - OS support ends on 2029-05-31

PowerShell is tested on Red Hat Universal Base Images (UBI). For more information, see the UBI information page.

Microsoft supports PowerShell until PowerShell reaches end-of-support or the version of Ubuntu reaches end-of-support.

Install package files (.deb) are also available from https://packages.microsoft.com/.

The Docker images for the .NET SDK contain the latest versions of PowerShell. These images are available from the Microsoft Artifact Registry.

These images are built from official operating system (OS) images provide by the OS distributor. These images may not have the latest security updates. Microsoft recommends that you update the OS packages to the latest version to ensure the latest security updates are applied.

These images are provided for testing purposes. If you need a Docker image for a production workload, you should build and maintain your own.

The support lifecycle for PowerShell doesn't cover modules that ship outside of the PowerShell release package. For example, using the ActiveDirectory module that ships as part of Windows Server is supported under the Windows Support Lifecycle.

Experimental features aren't intended to be used in production environments. We appreciate feedback on experimental features and we provide best-effort support for them.

PowerShell is released under the MIT license. Under this license, and without a paid support agreement, users are limited to community support. With community support, Microsoft makes no guarantees of responsiveness or fixes.

The PowerShell support lifecycle follows the support lifecycle of .NET. The following table lists the end-of-support dates for the current versions of PowerShell:

The following table lists the end-of-support dates for retired versions of PowerShell:

The following table contains a historical timeline of the major releases of Windows PowerShell. Microsoft no longer supports Windows PowerShell versions lower than 5.1.

Run the following command to see the full version number of .NET used by the version of PowerShell you're running:

[System.Runtime.InteropServices.RuntimeInformation]::FrameworkDescription

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4