Microsoft Windows is a computer operating system developed by Microsoft. It was first launched in 1985 as a graphical operating system built on MS-DOS. The initial version was followed by several subsequent releases, and by the early 1990s, the Windows line had split into two separate lines of releases: Windows 9x for consumers and Windows NT for businesses and enterprises. In the following years, several further variants of Windows would be released: Windows CE in 1996 for embedded systems; Pocket PC in 2000 (renamed to Windows Mobile in 2003 and Windows Phone in 2010) for personal digital assistants and, later, smartphones; Windows Holographic in 2016 for AR/VR headsets; and several other editions.
Windows MultiPoint Server was an operating system based on Windows Server. It was succeeded by the MultiPoint Services role in Windows Server 2016 and Windows Server version 1709. It was no longer being developed in Windows Server version 1803 and later versions.
In 2012 and 2013, Microsoft released versions of Windows specially designed to run on ARM-based tablets; these versions of Windows, named "Windows RT" and "Windows RT 8.1," were based on Windows 8 and Windows 8.1, respectively. Upon the release of Windows 10 in 2015, the ARM-specific version for large tablets was discontinued; large tablets (such as the Surface Pro 4) were only released with x86 processors and could run the full version of Windows 10. Windows 10 Mobile had the ability to be installed on smaller tablets (up to nine inches);[26] however, very few such tablets were released, and Windows 10 Mobile primarily ended up only running on smartphones until its discontinuation. In 2017, the full version of Windows 10 gained the ability to run on ARM, thus rendering a specific version of Windows for ARM-based tablets unnecessary.
Beginning with Windows 10, version 21H2, feature updates for Windows 10 release are released annually, in the second half of the calendar year, to the General Availability Channel. They will be serviced with monthly quality updates for 18 or 30 months from the date of the release, depending on the lifecycle policy.
We recommend that organizations begin deployment of each General Availability Channel release immediately as a targeted deployment to devices selected for early adoption and ramp up to full deployment at your discretion. This will enable you to gain access to new features, experiences, and integrated security as soon as possible.
The Visual C++ Redistributable installs Microsoft C and C++ (MSVC) runtime libraries. Many applications built using Microsoft C and C++ tools require these libraries. If your app uses those libraries, a Microsoft Visual C++ Redistributable package must be installed on the target system before you install your app. The Redistributable package architecture must match your app's target architecture. The Redistributable version must be at least as recent as the MSVC build toolset used to build your app. We recommend you use the latest Redistributable available for your version of Visual Studio, with some exceptions noted later in this article.
Unlike older versions of Visual Studio, which have infrequent redist updates, the version number isn't listed in the following table for Visual Studio 2015-2022 because the redist is updated frequently. To find the version number of the latest redist, download the redist you're interested in using one of the following links. Then, look at its properties using Windows File Explorer. In the Details pane, the File version contains the version of the redist.
Some of the downloads that are mentioned in this article are currently available on my.visualstudio.com. Log in using a Visual Studio Subscription account so that you can access the download links. If you're asked for credentials, use your existing Visual Studio subscription account. Or, create a free account by choosing the No account? Create one! link.
Visual Studio versions since Visual Studio 2015 share the same Redistributable files. For example, any apps built by the Visual Studio 2015, 2017, 2019, or 2022 toolsets can use the latest Microsoft Visual C++ Redistributable. However, the version of the Microsoft Visual C++ Redistributable installed on the machine must be the same or higher than the version of the Visual C++ toolset used to create your application. For more information about which version of the Redistributable to install, see Determining which DLLs to redistribute. For more information about binary compatibility, see C++ binary compatibility between Visual Studio versions.
These links download the latest supported en-US Microsoft Visual C++ Redistributable packages for Visual Studio 2013.You can download other versions and languages from Update for Visual C++ 2013 Redistributable Package or from my.visualstudio.com.
These links download the latest available en-US Microsoft Visual C++ Redistributable packages for Visual Studio 2012 Update 4. You can download other versions and languages from Microsoft Visual C++ Redistributable Packages for Visual Studio 2012 Update 4 or from my.visualstudio.com.
The installation commands in this article are for the latest stable release of PowerShell. Toinstall a different version of PowerShell, adjust the command to match the version you need. Thefollowing links direct you to the release page for each version in the PowerShell repository onGitHub.
Winget, the Windows Package Manager, is a command-line tool enables users to discover, install,upgrade, remove, and configure applications on Windows client computers. This tool is the clientinterface to the Windows Package Manager service. The winget command-line tool is bundled withWindows 11 and modern versions of Windows 10 by default as the App Installer.
Windows Server 2025 Preview Build 26085 and later includes winget for Windows Server withDesktop Experience only. For more information, seeAnnouncing Windows Server Preview Build 26085.
On Windows systems using X86 or X64 processor, winget installs the MSI package. On systems usingthe Arm64 processor, winget installs the Microsoft Store (MSIX) package. For more information,see Installing from the Microsoft Store.
PowerShell 7.4 installs to a new directory and runs side-by-side with Windows PowerShell 5.1.PowerShell 7.4 is an in-place upgrade that removes previous versions of PowerShell 7. Previewversions of PowerShell can be installed side-by-side with other versions of PowerShell.
PowerShell 7.2 and newer has support for Microsoft Update. When you enable this feature, you'll getthe latest PowerShell 7 updates in your traditional Microsoft Update (MU) management flow, whetherthat's with Windows Update for Business, WSUS, Microsoft Endpoint Configuration Manager, or theinteractive MU dialog in Settings.
Enabling updates may have been set in a previous installation or manual configuration. UsingENABLE_MU=0 doesn't remove the existing settings. Also, this setting can be overruled by GroupPolicy settings controlled by your administrator.
MSI packages can be installed from the command line allowing administrators to deploy packageswithout user interaction. The MSI package includes the following properties to control theinstallation options:
Depending on how you download the file you may need to unblock the file using the Unblock-Filecmdlet. Unzip the contents to the location of your choice and run pwsh.exe from there. Unlikeinstalling the MSI packages, installing the ZIP archive doesn't check for prerequisites. Forremoting over WSMan to work properly, ensure that you've met the prerequisites.
The dotnet tool installer adds $HOME\.dotnet\tools to your $env:PATH environment variable.However, the currently running shell doesn't have the updated $env:PATH. You can start PowerShellfrom a new shell by typing pwsh.
By default, Windows Store packages run in an application sandbox that virtualizes access to somefilesystem and registry locations. Changes to virtualized file and registry locations don't persistoutside of the application sandbox.
This sandbox blocks all changes to the application's root folder. Any system-level configurationsettings stored in $PSHOME can't be modified. This includes the WSMAN configuration. This preventsremote sessions from connecting to Store-based installs of PowerShell. User-level configurations andSSH remoting are supported.
Beginning in PowerShell 7.2, the PowerShell package is now exempt from file and registryvirtualization. Changes to virtualized file and registry locations now persist outside of theapplication sandbox. However, changes to the application's root folder are still blocked.
For best results when upgrading, you should use the same install method you used when you firstinstalled PowerShell. If you aren't sure how PowerShell was installed, you can check the value ofthe $PSHOME variable, which always points to the directory containing PowerShell that the currentsession is running.
When upgrading, PowerShell won't upgrade from an LTS version to a non-LTS version. It onlyupgrades to the latest version of LTS, for example, from 7.2.3 to 7.2.19. To upgrade from anLTS release to a newer stable version or the next LTS, you need to install the new version withthe MSI for that release.
Windows 10 IoT Core adds Windows PowerShell when you include IOT_POWERSHELL feature, which we canuse to deploy PowerShell 7. The steps defined above for Windows 10 IoT Enterprise can be followedfor IoT Core as well.
Microsoft supports the installation methods in this document. There may be other third-party methodsof installation available from other sources. While those tools and methods may work, Microsoftcan't support those methods.
Note : If you are using a user account created by your company, please contact your company's IT help desk or system administrator to know the required setup information and your company specific version requirement.
Citrix Workspace app can be used on domain and non-domain joined PCs, tablets, and thin clients. Provides high performance use of virtualized Skype for Business, line of business and HDX 3D Pro engineering apps, multimedia, local app access.
b37509886e