Task automation and configuration management framework from Microsoft

Windows PowerShell (32-bit)

Windows PowerShell 6.0.2 (32-bit)

  -  45.2 MB  -  Freeware

Sometimes latest versions of the software can cause issues when installed on older devices or devices running an older version of the operating system.

Software makers usually fix these issues but it can take them some time. What you can do in the meantime is to download and install an older version of Windows PowerShell 6.0.2 (32-bit).


For those interested in downloading the most recent release of Windows PowerShell (32-bit) or reading our review, simply click here.


All old versions distributed on our website are completely virus-free and available for download at no cost.


We would love to hear from you

If you have any questions or ideas that you want to share with us - head over to our Contact page and let us know. We value your feedback!

  • Windows PowerShell 6.0.2 (32-bit) Screenshots

    The images below have been resized. Click on them to view the screenshots in full size.

    Windows PowerShell 6.0.2 (32-bit) Screenshot 1

What's new in this version:

Engine updates and fixes:
- Update PowerShell to use 2.0.6 dotnet core runtime and packages (d607f20). This change addresses the following vulenerabilities: Microsoft Security Advisory CVE-2018-0875: Hash Collision can cause Denial of Service

Build and Packaging Improvements:
- Add Ubuntu build without AppImage
- Add scripts to set and or update the release tag in VSTS
- Fix DSC Configuration compilation
- Fix errors in Start-PSBootStrap during release builds
- Fix spelling failures in CI
- Use PowerShell windowsservercore Docker image for release builds
- Use ADD instead of Invoke-WebRequest in nanoserver Docker file
- When doing daily/test build in a non-release branch use the branch name as the preview name
- Add Environment Variable override of telemetry
- Build: Remove two unneeded lines from 'Invoke-AppveyorFinish'
- MSI: Refactor New-MsiPackage into packaging.psm1 and various fixes to enable patching
- MSI: Use HKLM instead of HKCU registry keys since the current installation scope is perMachine