I've really taken to using PowerShell, recently, having been a lifetime user of CMD until now. It's not that I need PowerShell as such, the commands I want to use work the same in both. It's the command history that I find so useful. In a command prompt the history is only available within that session and is forgotten on closing the window. In PowerShell it is persistent and is available whenever you open a new window. This is really convenient as it means that I have a history of my most used commands, such as
What is really annoying though is that whenever I mistype a command it will remain in the history too. It would be nice to edit the history. Well apparently you can, it's just a text file. To find where it is kept use the PowerShell command

Dism /Online /CleanUp-Image /StartComponentCleanup
. This saves having to type them out all over again and possibly making a mistake while doing so.What is really annoying though is that whenever I mistype a command it will remain in the history too. It would be nice to edit the history. Well apparently you can, it's just a text file. To find where it is kept use the PowerShell command
(Get-PSReadlineOption).HistorySavePath
and if you want to be really sneaky and not add that to the command history, then do it from a command prompt.
My Computers
System One System Two
-
- OS
- Windows 11 Home
- Computer type
- Laptop
- Manufacturer/Model
- Acer Aspire 3 A315-23
- CPU
- AMD Athlon Silver 3050U
- Memory
- 8GB
- Graphics Card(s)
- Radeon Graphics
- Monitor(s) Displays
- laptop screen
- Screen Resolution
- 1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
- Hard Drives
- 1TB Samsung EVO 870 SSD
- Browser
- Edge, Firefox
- Antivirus
- Defender
- Other Info
-
fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, supported device running Windows 11 Pro.
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 4GB RAM, 128GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro 22H2 Insider Beta as a native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 128GB NVMe ssd, supported device running Windows 11 Pro.
-
- Operating System
- Windows 11 Pro
- Computer type
- Laptop
- Manufacturer/Model
- Dell Lattitude E4310
- CPU
- i5 M 520
- Motherboard
- 0T6M8G
- Memory
- 8GB
- Screen Resolution
- 1366x768
- Hard Drives
- 500GB HDD
- Browser
- Firefox, Edge
- Antivirus
- Defender
- Other Info
-
unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, supported device running Windows 11 Pro.
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 4GB RAM, 128GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro 22H2 Insider Beta as a native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 128GB NVMe ssd, supported device running Windows 11 Pro.