Task automation and configuration management framework from Microsoft

Windows PowerShell (32-bit)

Windows PowerShell 7.0.11 (32-bit)

  -  79.8 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 7.0.11 (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 7.0.11 (32-bit) Screenshots

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

    Windows PowerShell 7.0.11 (32-bit) Screenshot 1

What's new in this version:

- Add explicit job name for approval tasks in Snap stage
- Update to use mcr.microsoft.com
- Update global.json and wix
- Put Secure supply chain analysis at correct place
- Partial back-port of: Update a few tests to make them more stable in CI (Internal 20648)
- Replace . in notices container name
- Add an approval for releasing build-info json
- Release build info json when it is preview
- Add a major-minor build info JSON file
- Update release instructions with link to new build
- Add condition to generate release file in local dev build only
- Removed old not-used-anymore docker-based tests for PS release packages
- Publish global tool package for stable releases
- Update to use windows-latest as the build agent image
- Don't upload dep or tar.gz for RPM build because there are none.
- Update to vPack task version 12
- Make RPM license recognized
- Ensure psoptions.json and manifest.spdx.json files always exist in packages