PowerShell 2.0 removed from Windows 11 and Windows Server from August 2025
Windows without PowerShell 2.0: Microsoft removes the version still included for compatibility for good. It has long been considered obsolete.

PowerShell 2.0 removed from Windows 11 and Windows Server from August 2025
Windows without PowerShell 2.0: Microsoft removes the version still included for compatibility for good. It has long been considered obsolete.
I've published a significant update to my PSReminderLite module to the #PowerShell Gallery. https://github.com/jdhitsolutions/PSReminderLite
PowerShell 2.0 ab August 2025 aus Windows 11 und Windows Server entfernt
Windows ohne PowerShell 2.0: Microsoft entfernt die noch zur Kompatibilität enthaltene Version endgültig. Als veraltet gilt sie schon lange.
Microsoft Removes PowerShell 2.0 From Windows To Clean Up Legacy Code https://cybersecuritynews.com/microsoft-removes-powershell-2-0-from-windows/ #CyberSecurityNews #cybersecuritynews #CyberSecurity #cybersecurity #PowerShell #Microsoft #Windows
Microsoft will remove PowerShell 2.0 from Windows starting in August, eight years after announcing its deprecation and keeping it around as an optional feature.
New Open-Source Tool Spotlight
BlackCat is a PowerShell module tailored for analyzing Microsoft Azure configurations. It detects potential security vulnerabilities while adhering to best practices. A vital tool for Azure security audits. #Azure #PowerShell
Project link on #GitHub
https://github.com/azurekid/blackcat
#Infosec #Cybersecurity #Software #Technology #News #CTF #Cybersecuritycareer #hacking #redteam #blueteam #purpleteam #tips #opensource #cloudsecurity
— P.S. Found this helpful? Tap Follow for more cybersecurity tips and insights! I share weekly content for professionals and people who want to get into cyber. Happy hacking
Phew! This little #powershell gem saved my ass today when I tried to migrate a #Signal Desktop install to another Windows PC.
(Not a thing officially supported by @signalapp)
The database encryption key itself is device-specifically encrypted using the „Data Protection API“ (haha) #DPAPI, so signal can't decrypt it on the new machine.
Using a legacy parameter, you can put the unencrypted key on the old machine, transfer it to the new one and have it re-encrypted.
Hackers Exploit ClickFix Technique to Compromise Windows and Run PowerShell Commands https://gbhackers.com/hackers-exploit-clickfix-technique-to-compromise-windows/ #CyberSecurityNews #cybersecurity #PowerShell #Windows
Here is what readers of my premium #PowerShell newsletter read about last month. https://jdhitsolutions.com/yourls/newsletter Premium subscribers have access to the entire archive.
Ich hab mit Gemini programmiert. Also ich hab das, was ich am besten kann, gemacht: ich hab herumkommandiert.
Ich wollte ein Symbol auf dem Desktop haben. wenn ich da doppelt raufklicke, bekomme ich ein Menü mit:
Herunterfahren
Neustart
Energiesparen
Abbrechen
ich wollte das erst in vbs haben, aber offensichtlich lief das auf meinem Rechner nicht mehr. Also haben wir das mit der Powershell umgesetzt. Ich spare mir die ganzen Schritte, hier das Ergebnis:
```
# Lädt die notwendigen Bibliotheken für eine grafische Oberfläche
Add-Type -AssemblyName System.Windows.Forms
Add-Type -AssemblyName System.Drawing
# Erstellt das Hauptfenster
$form = New-Object System.Windows.Forms.Form
$form.Text = "Power-Menue"
$form.Size = New-Object System.Drawing.Size(220, 230)
$form.StartPosition = "Manual"
$form.Location = [System.Windows.Forms.Cursor]::Position
$form.FormBorderStyle = 'None'
$form.MaximizeBox = $false
$form.BackColor = 'Magenta'
$form.TransparencyKey = $form.BackColor
# Erstellt den "Herunterfahren"-Knopf
$btnShutdown = New-Object System.Windows.Forms.Button
$btnShutdown.Location = New-Object System.Drawing.Point(20, 20)
$btnShutdown.Size = New-Object System.Drawing.Size(160, 30)
$btnShutdown.Text = "Herunterfahren"
$btnShutdown.BackColor = 'Gainsboro' # Eine Standard-Button-Farbe
$btnShutdown.ForeColor = 'Black' # Schwarze Schrift
$btnShutdown.Add_Click({
Start-Process "shutdown.exe" -ArgumentList "/s"
$form.Close()
})
$form.Controls.Add($btnShutdown)
# Erstellt den "Neustart"-Knopf
$btnRestart = New-Object System.Windows.Forms.Button
$btnRestart.Location = New-Object System.Drawing.Point(20, 55)
$btnRestart.Size = New-Object System.Drawing.Size(160, 30)
$btnRestart.BackColor = 'Gainsboro' # Eine Standard-Button-Farbe
$btnRestart.ForeColor = 'Black' # Schwarze Schrift
$btnRestart.Text = "Neustart"
$btnRestart.Add_Click({
Start-Process "shutdown.exe" -ArgumentList "/r"
$form.Close()
})
$form.Controls.Add($btnRestart)
# Erstellt den "Standby"-Knopf
$btnStandby = New-Object System.Windows.Forms.Button # Variable umbenannt für Klarheit
$btnStandby.Location = New-Object System.Drawing.Point(20, 90)
$btnStandby.Size = New-Object System.Drawing.Size(160, 30)
$btnStandby.BackColor = 'Gainsboro'
$btnStandby.ForeColor = 'Black'
$btnStandby.Text = "Energie sparen" # Text geändert auf den offiziellen Windows-Begriff
$btnStandby.Add_Click({
# WICHTIG: Dies ist der neue Befehl für den Standby-Modus
[System.Windows.Forms.Application]::SetSuspendState('Suspend', $false, $false)
$form.Close()
})
$form.Controls.Add($btnStandby)
# Erstellt den "Abbrechen"-Knopf
$btnAbort = New-Object System.Windows.Forms.Button
$btnAbort.Location = New-Object System.Drawing.Point(20, 140)
$btnAbort.Size = New-Object System.Drawing.Size(160, 30)
$btnAbort.BackColor = 'Gainsboro' # Eine Standard-Button-Farbe
$btnAbort.ForeColor = 'Black' # Schwarze Schrift
$btnAbort.Text = "Aktion abbrechen"
$btnAbort.Add_Click({
Start-Process "shutdown.exe" -ArgumentList "/a"
$form.Close()
})
$form.Controls.Add($btnAbort)
# Zeigt das Fenster an
$form.ShowDialog()
```
War cool. Hat den ganzen langweiligen Coding-Kram gespart.
Ich musste mich also nur um das kümmern, was mich interessiert, also Funktion, Aussehen, Optimierung.
Und das eigentliche Coden hab ich ausgelagert.
hier die Verknüpfung auf dem Desktop, die das Script dann aufruft:
```
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -WindowStyle Hidden -File "\\Lala\Dokument\User\Ron\Entwicklung\Beenden.ps1"
```
iX-Workshop: Windows Server absichern und härten
Lernen Sie, wie Sie Ihren Windows Server effektiv absichern und härten, Schutzmaßnahmen integrieren, Konfigurationen optimieren und Angriffsszenarien bewerten.
Have you ever needed to time your #powershell scripts and see what is slowing them down? Or even need to find out what is the fastest process between multiple options?
Here’s a few ways you can do that.
CVE-2025-53786 – Anatomía de una escalada de privilegios silenciosa en entornos híbridos de Microsoft Exchange https://www.hackplayers.com/2025/08/cve-2025-53786-exchange-entornos-hibridos.html #vulnerabilidades #powershell #amenazas #Exchange #hibrido #redteam #Windows #cloud
Here's a chance to save a bundle on a bundle. https://jdhitsolutions.com/yourls/masterbundle #PowerShell
Why is #powershell on #homebrew mac only?
#PowerShell #AI Introducing MCP Support in AI Shell Preview 6 http://dlvr.it/TMKCPG
Finally got to play with #ublueAurora, overall quite neat, although setting things up for developing with #dotnet took some work; the #devcontainers idea is interesting, but both #vscode and #JetbrainsRider could use some polish on it.
Also a bit sad I haven't found a way to install #powershell on it yet.
heise+ | Microsoft-365-Audits mit Maester automatisch sichern
Um Tenant und Dienste in Microsoft 365 abzusichern, müssen Unternehmen die Konfiguration überprüfen. Hier kommt das PowerShell-Framework Maester ins Spiel.
Here is what readers of my premium #PowerShell newsletter read about last month. https://jdhitsolutions.com/yourls/newsletter Premium subscribers have access to the entire archive.
New Attack Uses Windows Shortcut Files to Install REMCOS Backdoor – Source:hackread.com https://ciso2ciso.com/new-attack-uses-windows-shortcut-files-to-install-remcos-backdoor-sourcehackread-com/ #1CyberSecurityNewsPost #CyberSecurityNews #cybersecurity #CyberAttack #PowerShell #backdoor #Hackread #security #malware #Windows #Remcos #RAT