System Restore Is a Feature in Microsoft Windows That Allows the User to Revert Their Computer's State (Including System Files

Total Page:16

File Type:pdf, Size:1020Kb

System Restore Is a Feature in Microsoft Windows That Allows the User to Revert Their Computer's State (Including System Files System Restore is a feature in Microsoft Windows that allows the user to revert their computer's state (including system files, installed applications, Windows Registry, and system settings) to that of a previous point in time, which can be used to recover from system malfunctions or other problems. First included in Windows ME, it has since been included in all following desktop versions of Windows released since, excluding the Windows Server[1] An updated version of System Restore introduced by Windows Vista uses the Shadow Copy service as a backend (allowing block-level changes in files located in any directory on the volume to be monitored and backed up regardless of their location.) and allows System Restore to be used from the Windows Recovery Environment in case the Windows installation no longer boots at all. Resources monitored Starting with Windows Vista, System Restore takes a snapshot of all volumes it is monitoring. However, on Windows XP, it only monitors the following:[6][7] Windows Registry Files in the Windows File Protection folder (Dllcache) Local user profiles COM+ and WMI databases IIS metabase Specific file types monitored[5] -------------------- Implementation differences There are considerable differences between how System Restore works under Windows XP and later Windows versions. Configuration UI - In Windows XP, there is a graphical slider to configure the amount of disk space allotted to System Restore. In Windows Vista, the GUI to configure the disk space is not available. Using the command-line tool Vssadmin.exe or by editing the appropriate registry key, [11][12] the space reserved can be adjusted. Starting with Windows 7, the slider is available once again. Maximum space - In Windows XP, System Restore can be configured to use up to a maximum of 12% of the volume's space for most disk sizes;[7] however, this may be less depending on the volume's size. Restore points over 90 days old are automatically deleted, as specified by the registry value RPLifeInterval (Time to Live - TTL) default value of 7776000 seconds. In Windows Vista and later, System Restore is designed for larger volumes.[13] By default, it uses 15% of the volume's space.[9] File paths monitored - Up to Windows XP, files are backed up only from certain directories. On Windows Vista and later, this set of files is defined by monitored extensions outside of the Windows folder, and everything under the Windows folder.[14][dead link] File types monitored - Up to Windows XP, it excludes any file types used for users' personal data files, such as documents, digital photographs, media files, e-mail, etc. It also excludes the monitored set of file types (.DLL, .EXE etc.) from folders such as My Documents. Microsoft recommends that if a user is unsure as to whether certain files will be modified by a rollback, they should keep those files under My Documents.[7] When a rollback is performed, the files that were being monitored by System Restore are restored and newly created folders are removed. However, on Windows Vista and later, it excludes only document file types; it does not exclude any monitored system file type regardless of its location. Configuring advanced System Restore settings - Windows XP supports customizing System Restore settings via Windows Registry and a file at %windir%\system32\restore\Filelist.xml.[15][8] Windows Vista and later no longer either.[16] FAT32 volume support: On Windows Vista and later, System Restore no longer work on FAT32 disks and cannot be enabled on disks smaller than 1 GB. ==================== The quick, simple explanation is that System Restore backs up and restores the Registry, important Windows files, and the programs you've installed into Windows. It has no effect whatsoever on documents, photos, and so forth. But that isn't quite accurate. If it was, you'd be able to reliably create a restore point, uninstall an application, restore the point, and have the application back. That might actually work in some cases, but it won't in most. That's because System Restore might not protect all of the files that the uninstall deletes. System Restore chooses what to protect based on file type, not folder location. It backs up .exe files, .dlls, batch files, and shortcuts. I couldn't obtain a full list, so there may be others, but having just tested the XP and Vista versions of System Restore, I can verify those. Many people assume that System Restore backs up everything in certain locations, such as Program Files and the Desktop, while leaving the Documents folder alone. (After all, you don't want that project you've been working on to revert to last Sunday's version just because Windows was misbehaving.) But that isn't the case. I deleted an program file and a .wav sound file from a folder within Program Files, then restored from a point created before the deletions. I got the program file back, but not the .wav. I got similar results with different file types on the desktop and in my Documents folder. It's best to see System Restore as an imperfect system whose main advantage is that it's there and creates its backups automatically. When it works (and there's no guarantee of that), it does a pretty good job protecting Windows, a mediocre one on your applications, and leaves your data alone. Sometimes installing a program or driver can make Windows run slowly or unpredictably. System Restore can return your PC's system files and programs to a time when everything was working fine, potentially preventing hours of troubleshooting headaches. It won't affect your documents, pictures, or other data. ====================== What is System Restore? System Restore helps you restore your computer's system files to an earlier point in time. It's a way to undo system changes to your computer without affecting your personal files, such as e-mail, documents, or photos. Sometimes, the installation of a program or a driver can cause an unexpected change to your computer or cause Windows to behave unpredictably. Usually, uninstalling the program or driver corrects the problem. If uninstalling doesn't fix the problem, you can try restoring your computer's system to an earlier date when everything worked correctly. System Restore uses a feature called system protection to regularly create and save restore points on your computer. These restore points contain information about registry settings and other system information that Windows uses. You can also create restore points manually. For information about creating restore points, see Create a restore point. System image backups stored on hard disks can also be used for System Restore, just like the restore points created by system protection. Even though system image backups contain both your system files and personal data, your data files will not be affected by System Restore. For more information about system images, see What is a system image? System Restore isn't intended for backing up personal files, so it cannot help you recover a personal file that has been deleted or damaged. You should regularly back up your personal files and important data using a backup program. For more information about backing up personal files, see Back up your files. Open System Restore by clicking the Start button Picture of the Start button. In the search box, type System Restore, and then, in the list of results, click System Restore.‌ Administrator permission required If you're prompted for an administrator password or confirmation, type the password or provide confirmation. ============= How does System Restore work? System Restore uses restore points to return your system files and settings to an earlier point in time without affecting personal files. Restore points are created automatically every week, and just before significant system events, such as the installation of a program or device driver. You can also create a restore point manually. For more information about System Restore, What files are changed during a system restore? System Restore affects Windows system files, programs, and registry settings. It can also make changes to scripts, batch files, and other types of executable files created under any user account on your computer. System Restore does not affect personal files, such as e-mail, documents, or photos, so it cannot help you restore a deleted file. If you have backups of your files, you can restore the files from a backup. How long are restore points saved? Restore points are saved until the disk space System Restore reserves is filled up. As new restore points are created, old ones are deleted. If you turn off system protection (the feature that creates restore points) on a disk, all restore points are deleted from that disk. When you turn system protection back on, new restore points are created. For more information about system protection, What if System Restore doesn't fix the problem? If System Restore doesn't fix the problem, you can undo the restore operation or try choosing a different restore point. If System Restore doesn't display any restore points to choose from, make sure you have system protection turned on and that you have at least 300 MB of free space left on your hard disk if it is 500 MB or larger, or have at least 50 MB of free space if your hard disk is smaller than 300 MB. If System Restore doesn't fix the problem, you can also try an advanced recovery method. For more information.
Recommended publications
  • Solve Errors Caused by Corrupt System Files
    System File Corruption Errors Solved S 12/1 Repair Errors Caused by Missing or Corrupt System Files With the information in this article you can: • Find out whether corrupt system files could be causing all your PC problems • Manually replace missing system files using your Windows installation CD • Use System File Checker to repair broken Windows system files • Boost the memory available to Windows File Protection for complete system file protection Missing or corrupt system files can cause many problems when using your PC, from cryptic error messages to mysterious system crashes. If one of the key files needed by Windows has gone missing or become corrupt, you may think that the only way to rectify the situation is to re-install Windows. Fortunately, nothing that drastic is required, as Microsoft have included several tools with Windows that allow you to replace corrupt or missing files with new, fresh copies directly from your Windows installation CD. Now, whenever you find that an important .DLL file has been deleted or copied over, you won’t have to go to the trouble of completely re-installing your system – simply replace the offending file with a new copy. Stefan Johnson: “One missing file can lead to your system becoming unstable and frequently crashing. You may think that the only way to fix the problem is to re-install Windows, but you can easily replace the offending file with a fresh copy from your Windows installation CD.” • Solve errors caused by corrupt system files ................... S 12/2 • How to repair your missing system file errors ..............
    [Show full text]
  • IIS Security and Programming Countermeasures
    IIS Security and Programming Countermeasures By Jason Coombs ([email protected]) Introduction This is a book about how to secure Microsoft Internet Information Services for administrators and programmers whose work includes a requirement for information security, a computer industry specialty field commonly referred to as infosec. In this book the terms information security and infosec are used interchangeably with the more friendly term data security. This is not a book about hacking, cracking, and the tools and techniques of the bad guys, the so-called black hat hackers. This book teaches computer professionals and infosec specialists how to build secure solutions using IIS. It is your duty to secure and defend networked information systems for the benefit of the good guys who are your end users, clients, or less technical coworkers. There is nothing you can do that will transform a programmable computer running Microsoft Windows from its vulnerable condition to an invulnerable one. Every general purpose programmable computer is inherently vulnerable because it is controlled by software and is designed to allow new software to be installed or executed arbitrarily. Network computing based on programmable general purpose computers will never be safe from an information security perspective. Eliminating the feature of general purpose programmability from a networked computer and replacing its software with firmware reduces but does not eliminate vulnerabilities. These are immutable realities of present day computing and, as always, reality represents your biggest challenge. Microsoft is in business to get as much of your money as possible using whatever means will work at a given moment and in this respect they know virtually no equal in the software business.
    [Show full text]
  • WAF/CDP V3.7.1 User Guide
    WAFS/CDP v3.7.1 User Guide GlobalSCAPE, Inc. (GSB) 4500 Lockhill-Selma Road, Suite 150 Address: San Antonio, TX (USA) 78249 Sales: (210) 308-8267 Sales (Toll Free): (800) 290-5054 Technical Support: (210) 366-3993 Web Support: http://www.globalscape.com/support/ © 2004-2010 GlobalSCAPE, Inc. All Rights Reserved July 21, 2010 Table of Contents GlobalSCAPE Replication Software ............................................................................................................. 7 What's New? .............................................................................................................................................. 7 For the Best WAFS/CDP Experience .................................................................................................... 8 Getting Started .............................................................................................................................................. 9 WAFS Quick Start ..................................................................................................................................... 9 CDP Quick Start ...................................................................................................................................... 11 Quick Reference ...................................................................................................................................... 13 File-Naming Conventions ........................................................................................................................ 13 WAFS/CDP
    [Show full text]
  • Microsoft Windows Common Criteria Evaluation Security Target
    Microsoft Common Criteria Security Target Microsoft Windows Common Criteria Evaluation Microsoft Windows 10 version 1809 (October 2018 Update) Microsoft Windows Server 2019 (October 2018 Update) Security Target Document Information Version Number 0.05 Updated On June 18, 2019 Microsoft © 2019 Page 1 of 126 Microsoft Common Criteria Security Target Version History Version Date Summary of changes 0.01 June 27, 2018 Initial draft 0.02 December 21, 2018 Updates from security target evaluation 0.03 February 21, 2019 Updates from evaluation 0.04 May 6, 2019 Updates from GPOS PP v4.2.1 0.05 June 18, 2019 Public version Microsoft © 2019 Page 2 of 126 Microsoft Common Criteria Security Target This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. This work is licensed under the Creative Commons Attribution-NoDerivs- NonCommercial License (which allows redistribution of the work). To view a copy of this license, visit http://creativecommons.org/licenses/by-nd-nc/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.
    [Show full text]
  • Windows Intruder Detection Checklist
    Windows Intruder Detection Checklist http://www.cert.org/tech_tips/test.html CERT® Coordination Center and AusCERT Windows Intruder Detection Checklist This document is being published jointly by the CERT Coordination Center and AusCERT (Australian Computer Emergency Response Team). printable version A. Introduction B. General Advice Pertaining to Intrusion Detection C. Look for Signs that Your System may have been Compromised 1. A Word on Rootkits 2. Examine Log Files 3. Check for Odd User Accounts and Groups 4. Check All Groups for Unexpected User Membership 5. Look for Unauthorized User Rights 6. Check for Unauthorized Applications Starting Automatically 7. Check Your System Binaries for Alterations 8. Check Your Network Configurations for Unauthorized Entries 9. Check for Unauthorized Shares 10. Check for Any Jobs Scheduled to Run 11. Check for Unauthorized Processes 12. Look Throughout the System for Unusual or Hidden Files 13. Check for Altered Permissions on Files or Registry Keys 14. Check for Changes in User or Computer Policies 15. Ensure the System has not been Joined to a Different Domain 16. Audit for Intrusion Detection 17. Additional Information D. Consider Running Intrusion Detection Systems If Possible 1. Freeware/shareware Intrusion Detection Systems 2. Commercial Intrusion Detection Systems E. Review Other AusCERT and CERT Documents 1. Steps for Recovering from a Windows NT Compromise 2. Windows NT Configuration Guidelines 3. NIST Checklists F. Document Revision History A. Introduction This document outlines suggested steps for determining whether your Windows system has been compromised. System administrators can use this information to look for several types of break-ins. We also encourage you to review all sections of this document and modify your systems to address potential weaknesses.
    [Show full text]
  • Hands-On Ethical Hacking and Network Defense
    Hands-On Ethical Hacking and Network Defense Chapter 6 Enumeration Modified 1-11-17 Objectives Describe the enumeration step of security testing Enumerate Microsoft OS targets Enumerate *NIX OS targets Introduction to Enumeration Enumeration extracts information about: – Resources or shares on the network – Network topology and architecture – Usernames or groups assigned on the network – Information about users and recent logon times Before enumeration, you use Port scanning and footprinting – To Determine OS being used Intrusive process NBTscan NBT (NetBIOS over TCP/IP) – is the Windows networking protocol – used for shared folders and printers NBTscan – Tool for enumerating Microsoft OSs Enumerating Microsoft Operating Systems Study OS history – Knowing your target makes your job easier Many attacks that work for older Windows OSs still work with newer versions Windows 95 The first Windows version that did not start with DOS Still used the DOS kernel to some extent Introduced the Registry database to replace Win.ini, Autoexec.bat, and other text files Introduced Plug and Play and ActiveX Used FAT16 file system Windows 98 and ME More Stable than Win 95 Used FAT32 file system Win ME introduced System Restore Win 95, 98, and ME are collectively called "Win 9x" They run Windows 98 Use plaintext passwords – Research from Billy K Rios, published 2-11-14 Windows NT 3.51 Server/Workstation No dependence on DOS kernel Domains and Domain Controllers NTFS File System to replace FAT16 and FAT32 Much more secure and stable than Win9x Many companies still use Win NT Server Domain Controllers Win NT 4.0 was an upgrade Windows 2000 Server/Professional Upgrade of Win NT Active Directory – Powerful database storing information about all objects in a network Users, printers, servers, etc.
    [Show full text]
  • The Defintive Guide to Windows Desktop
    realtimepublishers.comtm The Definitive Guidetm To Windows Desktop Administration Bob Kelly Chapter 2 Chapter 2: OS Deployment............................................................................................................23 The Workstation Baseline..............................................................................................................23 Benefits ..............................................................................................................................23 Increased Reliability ..............................................................................................23 Increased Deployment Speed.................................................................................23 Ease of Troubleshooting ........................................................................................24 Drawbacks..........................................................................................................................24 Baseline Components.........................................................................................................24 What to Leave In....................................................................................................25 What to Leave Out.................................................................................................25 Common Pitfalls to Avoid .................................................................................................25 MSI Source Resiliency ..........................................................................................25
    [Show full text]
  • Microsoft Windows Common Criteria Evaluation Security Target
    Microsoft Common Criteria Security Target Microsoft Windows Common Criteria Evaluation Microsoft Windows 10 (Creators Update) Security Target Document Information Version Number 0.06 Updated On June 14, 2018 Microsoft © 2017 Page 1 of 102 Microsoft Common Criteria Security Target This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. This work is licensed under the Creative Commons Attribution-NoDerivs- NonCommercial License (which allows redistribution of the work). To view a copy of this license, visit http://creativecommons.org/licenses/by-nd-nc/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. The example companies, organizations, products, people and events depicted herein are fictitious.
    [Show full text]
  • The Definitive Guide to Windows Installer Technology for System
    realtimepublishers.comtm The Definitive Guidetm To Windows Installer Technology for System Administrators Darwin Sanoy and Jeremy Moskowitz Chapter 4 Chapter 4: Best Practices for Building Packages...........................................................................82 Best Practices Formulation ............................................................................................................82 Best Practice Is Not Optional.............................................................................................84 Darwin’s Law of Technology Sophistication ....................................................................84 Repackaging Best Practice Recommendations..............................................................................85 Do Not Repackage All Types of Setup Programs .............................................................86 Have a Documented Desktop Reference Configuration....................................................87 Use Clean System Reloads for Testing and Packaging .....................................................87 Why Clean Machines? ...........................................................................................88 Additional Management Data for Packaging.....................................................................89 Windows Installer Best Practices...................................................................................................90 Invest in Training...............................................................................................................91
    [Show full text]
  • Windows File Protection Switcher Download Windows File Protection Switcher Download
    windows file protection switcher download Windows file protection switcher download. Completing the CAPTCHA proves you are a human and gives you temporary access to the web property. What can I do to prevent this in the future? If you are on a personal connection, like at home, you can run an anti-virus scan on your device to make sure it is not infected with malware. If you are at an office or shared network, you can ask the network administrator to run a scan across the network looking for misconfigured or infected devices. Another way to prevent getting this page in the future is to use Privacy Pass. You may need to download version 2.0 now from the Chrome Web Store. Cloudflare Ray ID: 67ab2b6599ac16a1 • Your IP : 188.246.226.140 • Performance & security by Cloudflare. Stay protected with Windows Security. Windows 10 includes Windows Security, which provides the latest antivirus protection. Your device will be actively protected from the moment you start Windows 10. Windows Security continually scans for malware (malicious software), viruses, and security threats. In addition to this real- time protection, updates are downloaded automatically to help keep your device safe and protect it from threats. Windows 10 in S mode. Some features will be a little different if you're running Windows 10 in S mode. Because this mode is streamlined for tighter security, the Virus & threat protection area has fewer options. But don't worry—the built-in security of this mode automatically prevents viruses and other threats from running on your device, and you'll receive security updates automatically.
    [Show full text]
  • Outlook Security
    E-mail Security in the Wake of Recent Malicious Code Incidents By: Trent Pitsenbarger and Paul Bartock of the Systems and Network Attack Center (SNAC) [email protected] Acknowledgments: The authors would like to acknowledge Neal Ziring and Dave Albanese, NSA and Sean Finnegan, Microsoft for their contributions. Dated: Jan 29, 2002 Version 2.6 UNCLASSIFIED Warnings Do not attempt to implement any of the settings in this guide without first testing in a non-operational environment. This document is only a guide containing recommended security settings. It is not meant to replace well-structured policy or sound judgment. Furthermore this guide does not address site-specific configuration issues. Care must be taken when implementing this guide to address local operational and policy concerns. SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. IN NO EVENT SHALL THE CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Please keep track of the latest security patches and advisories at the Microsoft security bulletin page at http://www.microsoft.com/technet/security/current.asp. This document contains possible recommended settings for the system Registry.
    [Show full text]
  • Microsoft Windows Common Criteria Evaluation Security Target
    Microsoft Common Criteria Security Target Microsoft Windows Common Criteria Evaluation Microsoft Windows 10 (Fall Creators Update) Microsoft Windows Server (Fall Creators Update) Security Target Document Information Version Number 0.04 Updated On March 23, 2018 Microsoft © 2018 Page 1 of 104 Microsoft Common Criteria Security Target Version History Version Date Summary of changes 0.01 January 27, 2018 Initial draft 0.02 February 24, 2018 Updates from security target evaluation 0.03 March 23, 2018 Updates from assurance activity evaluation 0.04 April 19, 2018 Prepared copy for publication Microsoft © 2018 Page 2 of 104 Microsoft Common Criteria Security Target This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. This work is licensed under the Creative Commons Attribution-NoDerivs- NonCommercial License (which allows redistribution of the work). To view a copy of this license, visit http://creativecommons.org/licenses/by-nd-nc/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.
    [Show full text]