Excellent.

I do not know much about this feature of GitHub but it looks promising.

And anything to move tech support questions out of Issues is good.

Hi guys!

I very much like good old forums! ;-)

First question: I noticed this morning when I launched PowerShell 7.1.0 that 7.1.1 was available. I made the update but I cannot find any release notes anywhere. Furthermore 7.1.1 is not released yet on PowerShell's the Github landing page.

Is that normal? Where can I find the release notes?

Thanks
Arnaud

Is there a command line to update to the latest version of powershell or is the only way to download and install an updated MSI/ZIP? I've tried searching but all I can find are commands to upgrade to 7 from older pre-installed versions of powershell.

How can I find out which version I have?

I do not want to see this starting info every time I open the this shell. How to disable/customize this

Hi, Can I access AWS EC2 through PowerShell? (like gitbash)

Do you know when the PS 5.1 will be completely replaced by the PS 7 in Windows 11? In other words, when will the PS 7 be integrated into the Windows base build?

PS 7 has so many advantages and features that simply don't exist in PS 5.

In terms of automation, it would help us enormously if all newer Windows systems had the PS7 integrated by default.

Are there any plans yet? :)

Dear Microsoft Learn and PowerShell Teams,

I am writing to propose a comprehensive idea that addresses a recurring gap in how users learn, understand, and safely adopt PowerShell and Windows command-line tools.

This proposal is not about adding more documentation—Microsoft already excels at that—but about transforming learning into an interactive, guided experience that lives inside the tools themselves.

1. The underlying problem

PowerShell is one of Microsoft’s most powerful technologies, yet it is frequently misunderstood, underused, or misused.

From my experience—and from countless community discussions—the typical learning path looks like this:

• Users copy commands from forums or documentation
• Commands are executed without understanding objects, pipelines, or side effects
• Mistakes occur that can damage system configurations
• Users become frustrated or afraid of PowerShell

The core issue is not lack of documentation, but lack of guided comprehension.

Microsoft Learn and Docs explain what commands do, but not always how users should think while using them.

2. The current learning gap

At present, learning PowerShell involves:

• Reading documentation
• Manually experimenting
• Debugging errors after they happen

This creates a steep learning curve, especially for:

• Beginners
• Career switchers
• Non-developers
• Power users transitioning from GUI tools

As a result:

• Users memorize commands instead of understanding concepts
• Pipelines feel “magical” rather than logical
• PowerShell is perceived as dangerous instead of empowering

3. Proposed solution: an interactive PowerShell learning mode

I propose an interactive, guided learning environment for PowerShell, conceptually similar to mobile learning apps like MIMO, but technically aligned with Microsoft Learn and Windows.

Core characteristics:

• Runs inside PowerShell or Windows Terminal
• Structured as progressive lessons (Lesson 1, Lesson 2, etc.)
• Requires users to type commands themselves
• Validates results and outputs in real time
• Explains why a command works or fails
• Uses real PowerShell objects, not simulations

Example interactions:

• Explaining what Get-Location returns and its object type
• Demonstrating how Get-Member reveals object capabilities
• Showing how pipelines transform objects step by step
• Explaining parameters through cause-and-effect, not syntax lists

4. Educational benefits for users

Such a system would:

• Build correct mental models from day one
• Reduce fear of the command line
• Encourage exploration instead of copy-paste
• Prevent common beginner mistakes
• Make PowerShell approachable for a wider audience

It would also naturally guide users through:

• Command Prompt basics
• PowerShell fundamentals
• Advanced scripting concepts
• Eventually, automation and DevOps workflows

5. Technical and operational benefits for Microsoft

From Microsoft’s perspective, this approach could:

• Reduce support incidents caused by incorrect command usage
• Decrease configuration errors on Windows systems
• Improve overall PowerShell adoption and reputation
• Strengthen Microsoft Learn as a best-in-class learning platform
• Create a safer, more educated user base

In short: better-trained users create fewer problems and greater trust.

6. Why PowerShell is uniquely suited for this

PowerShell already includes:

• A rich object-oriented pipeline
• Built-in discovery tools (Get-Help, Get-Member)
• Deep Windows integration
• A strong open-source ecosystem

What it lacks is a didactic layer—a way for the shell to actively teach while being used.

This proposal does not replace documentation; it activates it.

7. Potential challenges and drawbacks (acknowledged)

No proposal is without trade-offs. Potential concerns include:

• Development and maintenance cost
• Risk of oversimplifying advanced concepts
• Need for careful sandboxing to avoid system damage
• Ensuring lessons stay aligned with evolving PowerShell versions

However, these challenges are manageable:

• Lessons can run in constrained environments
• Advanced features can be opt-in
• Content can be modular and versioned
• Community feedback can guide iteration

8. Why this is worth doing

PowerShell is not just a tool—it is a gateway to understanding Windows itself.

By turning PowerShell into a teacher, Microsoft would:

• Lower the barrier to entry
• Increase long-term adoption
• Reduce misuse
• Empower users instead of intimidating them

This aligns perfectly with Microsoft’s broader goals of education, accessibility, and developer empowerment.

Closing

I believe an interactive PowerShell learning experience—built on top of Microsoft Learn and Docs and integrated directly into Windows—would be a meaningful and forward-looking addition to the ecosystem.

Thank you for taking the time to read this proposal. I hope it contributes to ongoing discussions about how users learn and grow with Microsoft technologies.

Kind regards,
Ken

Hola equipos de Microsoft Learn y PowerShell,

Os escribo para proponer una idea que aborda un problema recurrente en la forma en que los usuarios aprenden, entienden y utilizan PowerShell y las herramientas de línea de comandos de Windows.

No se trata de añadir más documentación—Microsoft ya destaca en eso—sino de transformar el aprendizaje en una experiencia interactiva y guiada integrada en las propias herramientas.

El problema de fondo

PowerShell es una de las tecnologías más potentes de Microsoft, pero a menudo se aprende mal:

• Copiando comandos sin entenderlos
• Ejecutándolos sin conocer los efectos reales
• Provocando errores de configuración
• Generando miedo o rechazo a la consola

El problema no es la falta de información, sino la falta de comprensión guiada.

La brecha actual de aprendizaje

Hoy en día aprender PowerShell implica:

• Leer documentación
• Probar a ciegas
• Corregir errores después del daño

Esto crea una barrera grande para principiantes, usuarios no técnicos o personas que vienen del entorno gráfico.

La solución propuesta

Un modo de aprendizaje interactivo de PowerShell, integrado con Microsoft Learn, que:

• Se ejecute dentro de PowerShell o Windows Terminal
• Esté estructurado por lecciones
• Obligue al usuario a escribir comandos
• Valide resultados en tiempo real
• Explique por qué algo funciona o falla
• Enseñe objetos, pipelines y lógica, no solo sintaxis

Beneficios para los usuarios

• Aprendizaje real, no memorización
• Menos miedo a romper cosas
• Menos errores graves
• Mejor comprensión del sistema
• Evolución natural hacia scripting y automatización

Beneficios para Microsoft

• Menos incidencias de soporte
• Menos errores por uso incorrecto
• Mejor adopción de PowerShell
• Usuarios más capacitados
• Refuerzo de Microsoft Learn como plataforma educativa

Riesgos y desventajas (reales)

• Coste de desarrollo
• Necesidad de sandboxing
• Riesgo de simplificación excesiva
• Mantenimiento de contenidos

Pero todos estos riesgos son gestionables y asumibles frente a los beneficios.

Por qué merece la pena

PowerShell no es solo una consola: es una forma de entender Windows.

Convertirlo en un entorno que enseña mientras se usa reduciría errores, frustración y barreras de entrada, y empoderaría a los usuarios.

Un saludo y gracias por vuestro tiempo,
Ken