Friday, June 05, 2026

Windows recovery points

Windows update could cause some problems with device drivers, video, USB etc.

That can cause corrupted system files, including PowerShell.

Possible ways to fix them:

Repair Windows components

Run from elevated cmd.exe:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

DSIM may take LONG time to run, don't interrupt it! Prevent windows sleep, restart etc.


Note: PowerShell is NOT one product!

  1. Windows PowerShell 5.1

    • Built into Windows
    • Lives under C:/Windows/System32/WindowsPowerShell/v1.0/powershell.exe
    • Uses the old .NET Framework-based stack
    • Repaired through Windows servicing, not normal uninstall/reinstall
  2. PowerShell 7+

    • Separate product installed independently
    • Usually launched with pwsh
    • Uses the newer .NET stack
    • Can be installed, updated, or removed like a normal application
this is "native" 5.1
    powershell.exe -NoProfile

this is "portable" 7.x
    pwsh -NoProfile


WSL2 is used by Docker, and sometimes can get damaged

  • wsl --status
  • wsl -l -v

If WSL is broken but Windows is now stable, repair WSL first.
Reinstall Docker only after WSL is confirmed healthy.

wsl --shutdown
wsl --updateIf needed, reinstall Docker Desktop

docker version
docker context ls
docker ps

On Windows 11, the quickest way is through System Protection.

  1. Press Win.
  2. Type restore point.
  3. Open Create a restore point.
  4. In the System Protection tab, select your system drive, usually ..
  5. If Protection says Off, click Configure, turn on System Protection, and apply.
  6. Click Create.
  7. Enter a name like After_SFC_Docker_Recovery.
  8. Wait for the confirmation.

If you prefer the longer route:

  1. Open Control Panel
  2. System
  3. System Protection
  4. Then the same steps above

A few practical notes:

  • Restore points are not full backups.
  • They mainly protect system files, drivers, registry, and some installed app state.
  • They are still worth creating right now, especially before any more AMD, Docker, or Windows updates

No comments: