Skip to content

Bring-Back-#3710#3809

Merged
ChrisTitusTech merged 5 commits intoChrisTitusTech:mainfrom
GabiNun:Bring-Back-#3710
Jan 7, 2026
Merged

Bring-Back-#3710#3809
ChrisTitusTech merged 5 commits intoChrisTitusTech:mainfrom
GabiNun:Bring-Back-#3710

Conversation

@GabiNun
Copy link
Contributor

@GabiNun GabiNun commented Dec 12, 2025

you close this pr because

This was how it used to be, but people ripped out system restore then would break their system running too many tweaks.

We added all these checks so people don't do stupid things without a backup.

but your code wouldn't even fix restore point if it was broken

you tried to Import-Module Microsoft.PowerShell.Management but if that module isn't loaded than the entire script wouldn't work

also the only way you could "break" restore point is if you disabled it or just stright up deleted system restore files which you couldn't fix

also people who break system restore point wouldn't run system restore

also fixes this warning

WARNING: The 'Microsoft.PowerShell.Management' module was not imported because the 'Microsoft.PowerShell.Management' snap-in was already imported.

@ChrisTitusTech
Copy link
Owner

Did you test this on PS5? I think I remember in the past Computer-Checkpoint didn't work on Windows Powershell and only did on the newer version. That is the only other reason why we added the repair on System Restore.

@GabiNun
Copy link
Contributor Author

GabiNun commented Dec 15, 2025

@ChrisTitusTech yes it dose work in powershell 5

@ChrisTitusTech ChrisTitusTech merged commit 158fabd into ChrisTitusTech:main Jan 7, 2026
1 check passed
@GabiNun GabiNun deleted the Bring-Back-#3710 branch January 7, 2026 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants