PowerShell 7.3.4 and 7.2.11 has been released


v7.3.4 Release of PowerShell​


Engine Updates and Fixes
  • Add instrumentation to AmsiUtil and make the init variable readonly (#18727)
  • Fix support for NanoServer due to the lack of AMSI (#18882)
  • Adding missing guard for telemetry optout to avoid NullReferenceException when importing modules (#18949) (Thanks @powercode!)
  • Fix VtSubstring helper method to correctly check chars copied (#19240)
  • Fix ConciseView to handle custom ParserError error records (#19239)
Build and Packaging Improvements

Bump to use .NET 7.0.5
  • Update ThirdPartyNotices.txt
  • Update cgmanifest.json
  • Fix the template that creates nuget package
  • Update the wix file
  • Update to .NET SDK 7.0.203
  • Skip VT100 tests on Windows Server 2012R2 as console does not support it (#19413)
  • Improve package management acceptance tests by not going to the gallery (#19412)
  • Fix stage dependencies and typo in release build (#19353)
  • Fix issues in release build and release pipeline (#19338)
  • Restructure the package build to simplify signing and packaging stages (#19321)
  • Test fixes for stabilizing tests (#19068)
  • Add stage for symbols job in Release build (#18937)
  • Use reference assemblies generated by dotnet (#19302)
  • Add URL for all distributions (#19159)


v7.2.11 Release of PowerShell

Build and Packaging Improvements

Bump .NET version to 6.0.16
  • Update ThirdPartyNotices.txt
  • Update cgmanifest.json
  • Fix the template that creates nuget package
  • Update the wix file
  • Update .NET SDK to 6.0.408
  • Fix the build script and signing template
  • Fix stage dependencies and typo in release build (#19353)
  • Fix issues in release build and release pipeline (#19338)
  • Restructure the package build to simplify signing and packaging stages (#19321)
  • Skip VT100 tests on Windows Server 2012R2 as console does not support it (#19413)
  • Improve package management acceptance tests by not going to the gallery (#19412)
  • Test fixes for stabilizing tests (#19068)
  • Add stage for symbols job in Release build (#18937)
  • Use reference assemblies generated by dotnet (#19302)
  • Add URL for all distributions (#19159)
  • Update release pipeline to use Approvals and automate some manual tasks (#17837)
 
Click to expand...
Almighty1 said:
You are right, I was reading this:
learn.microsoft.com

Installing PowerShell on Windows - PowerShell

Information about installing PowerShell on Windows
learn.microsoft.com
where it says:
" PowerShell 7.3 is an in-place upgrade that replaces PowerShell 7.0 and lower." since and lower would mean something less than 7.0.
Click to expand...
It also recommends to install PowerShell via winget. Well it has been now :-)
 

My Computers

System One System Two

  • OS
    Win 11 Home & Pro
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook
    CPU
    AMD Ryzen™ 7 7730U
    Motherboard
    M1605YA
    Memory
    15.0GB Dual-Channel DDR4 @ 1596MHz (22-22-22-52)
    Graphics Card(s)
    512MB ATI AMD Radeon Graphics (ASUStek Computer Inc)
    Monitor(s) Displays
    Generic PnP Monitor (1920x1200@60Hz) - P1 PLUS (1920x1080@59Hz)
    Screen Resolution
    1920 X 1200
    Hard Drives
    953GB Western Digital WD
    PSU
    45 Watts
    Mouse
    Lenovo Bluetooth.
    Internet Speed
    500 Mbps
    Browser
    Edge
    Antivirus
    Defender
  • Operating System
    Windows 11
    Computer type
    Laptop
    Manufacturer/Model
    ACER NITRO
    CPU
    AMD Ryzen 7 5800H / 3.2 GHz
    Motherboard
    CZ Scala_CAS (FP6)
    Memory
    32 GB DDR4 SDRAM 3200 MHz
    Graphics card(s)
    NVIDIA GeForce RTX 3060 6 GB GDDR6 SDRAM
    Sound Card
    Realtek Audio. NVIDIA High Definition Audio
    Monitor(s) Displays
    15.6" LED backlight 1920 x 1080 (Full HD) 144 Hz
    Screen Resolution
    1920 x 1080 (Full HD)
    Hard Drives
    Samsung 970 Evo Plus 2TB NVMe M.2
    PSU
    180 Watt, 19.5 V
    Mouse
    Lenovo Bluetooth
    Internet Speed
    500 Mbps
    Browser
    Edge
    Antivirus
    Defender
Fabler2 said:
It also recommends to install PowerShell via winget. Well it has been now :-)
Click to expand...
LOL, I used to use the store version until reading that page saying the store version is run in a sandbox compared to the regular version so I did the winget this time. I still wonder if the winget also does these:

  • The $env:ProgramFiles\PowerShell\7 folder is added to $env:PATH
  • Folders for previously released versions are deleted
 

My Computer

System One

  • OS
    Windows XP/7/8/8.1/10/11, Linux, Android, FreeBSD Unix
    Computer type
    Laptop
    Manufacturer/Model
    Dell XPS 15 9570
    CPU
    Intel® Core™ i7-8750H 8th Gen Processor 2.2Ghz up to 4.1Ghz
    Motherboard
    Dell XPS 15 9570
    Memory
    32GB using 2x16GB modules
    Graphics Card(s)
    Intel UHD 630 & NVIDIA GeForce GTX 1050 Ti with 4GB DDR5
    Sound Card
    Realtek ALC3266-CG
    Monitor(s) Displays
    15.6" 4K Touch UltraHD 3840x2160 made by Sharp
    Screen Resolution
    3840x2160
    Hard Drives
    Toshiba KXG60ZNV1T02 NVMe 1024GB/1TB SSD
    PSU
    Dell XPS 15 9570
    Case
    Dell XPS 15 9570
    Cooling
    Stock
    Keyboard
    Stock
    Mouse
    SwitftPoint ProPoint
    Internet Speed
    Comcast/XFinity 1.44Gbps/42.5Mbps
    Browser
    Microsoft EDGE (Chromium based) & Google Chrome
    Antivirus
    Windows Defender that came with Windows
You must log in or register to reply here.

Similar threads

  • Article Article
PowerShell 7.5.0 and 7.4.7 (LTS) has been released
Replies
3
Views
538
Cliff S
Cliff S
  • Article Article
PowerShell 7.4.6 and 7.2.24 (LTS) has been released
Replies
3
Views
2K
Warre1
Warre1
  • Article Article
PowerShell 7.5.0-rc.1 has been released
Replies
3
Views
695
HRPuffnstuff
HRPuffnstuff
  • Article Article
PowerShell 7.4.5 and 7.2.23 (LTS) has been released
Replies
0
Views
460
Brink
Brink
  • Article Article
PowerShell 7.4.4 and 7.2.22 (LTS) has been released
Replies
3
Views
1K
Warre1
Warre1

Latest Support Threads

Latest Tutorials

Back
Top Bottom