Jump to content
IObit Forum
Top Free Driver Updater Tools Best 25 PC Optimization Software Best 22 Antimalware Best 22 Uninstaller Software IObit Coupons & Discount Offers PC Optimizer Mac Boost Advice IObit Coupons A Good Utility Program From IObit IObit Promo Codes IObit Coupon Codes IObit Coupons and Deals FAQs Driver Booster Pro Review

HELP - How to revert or UNDO the changes made by ASC ?


Recommended Posts



Since I installed ASC13 and made some of its optimizations, my computer (win10) is behaving weirdly, like:


- Rebooting itself.


- Freezing completely (I have to brute-force shutdown).


- Slower than before.


- Internet disconnecting often (after applying Internet connection optimization)



Does this program have the option to revert back or undo the changes made??




Link to comment
Share on other sites

Yes it has some options to revert changes. Also you should always have recent restore points available so you can undo issues.

Also, it is totally unnecessary to run every available function of ASC. Only run functions which may resolve problems.

Read the Product Manual....https://www.iobit.com/en/product-manuals.php

Link to comment
Share on other sites

What if you realize that you don’t want to keep your changes to the CONTRIBUTING.md file? How can you easily unmodified it — revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)? Luckily, git status tells you how to do that, too. In the last example output, the unstaged area looks like this:


Changes are not staged for commit:

(use "git add <file>..." to update what will be committed)

(use "git checkout -- <file>..." to discard changes in working directory)


modified: CONTRIBUTING.md

It tells you pretty explicitly how to discard the changes you’ve made. Let’s do what it says:


$ git checkout -- CONTRIBUTING.md

$ git status

On branch master

Changes to be committed:

(use "git reset HEAD <file>..." to unstage)


renamed: README.MD -> README

You can see that the changes have been reverted.



It’s important to understand that git checkout — <file> is a dangerous command. Any local changes you made to that file are gone — Git just replaced that file with the most recently-committed version. Don’t ever use this command unless you absolutely know that you don’t want those unsaved local changes.


If you would like to keep the changes you’ve made to that file but still need to get it out of the way for now, we’ll go over stashing and branching in ch03-git-branching.asc; these are generally better ways to go.


Remember, anything that is committed in Git can almost always be recovered. Even commits that were on branches that were deleted or commit that were overwritten with an --amend commit can be recovered (see ch10-git-internals.asc for data recovery). However, anything you lose that was never committed is likely never to be seen again.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...