the system creates restore points when it is running at its peak. restore points by user should be created before deleting or adding new software or changes to operating system. this way you can restore to old settings if conflicts exist when changes take place.
System creates Automatic Users Create Manual
Restore points are created, by the system, before every update. Restore points are created, by the user, whenever the user chooses too make an restore point.
the system creates restore points when it is running at its peak. restore points by user should be created before deleting or adding new software or changes to operating system. this way you can restore to old settings if conflicts exist when changes take place.
the system creates restore points when it is running at its peak. restore points by user should be created before deleting or adding new software or changes to operating system. this way you can restore to old settings if conflicts exist when changes take place.
System creates Automatic Users Create Manual
Restore points are usually generated when you install a program or change an important computer setting. e.g. if you change what services to load on computer start up
System creates Automatic Users Create Manual
The answer is very hard to answer
The System Restore function in Windows XP is one defense line against file corruption or loss but it is far from a complete backup. System Restore monitors certain parts of Windows XP known as the "system state". The system state includes the Registry, COM+ Class Registration database, boot files, and certain file types. The file types that are monitored are listed at this Microsoft page and include EXE and DLL files. If you can read XML, you can also see the list on your computer at %windir%\system32\restore\Filelist.xml. Note, however, that these file types are not necessarily protected if they are placed directly on the desktop.Periodically (usually once a day) System Restore takes a snapshot of the system state and stores the various files in a condensed form. At some later time, the system can then be rolled back to a previous system state. By no means, however, does that include all your files.By default, System Restore will set aside 12% of each of your drives for saving restore points. Although you may have a big hard drive and no need of the space, a lot of extra restore points can slow down processes such as virus checking, disk defragmenting, and other procedures. I discuss the details of the procedure for changing the amount of space that is reserved on another page. Also discussed there is how to turn off System Restore for drives or partitions that do not need to be monitored. If you use a separate drive for a dual-boot system or if you have partitions for data, turn off System Restore for these volumes. There is no benefit from monitoring non-system or non-XP files.
Restore points are based on the operational system environment, which includes the BIOS on the motherboard, partitions and drivers. Furthermore, a certain operational system licence can be stored in the BIOS, causing mismatches and malfuctionings. On the other hand, most types of restore points do not copy the entire disk image, what would take a significant ammount of space. Instead, they take a 'snapshot' of the actual configuration. So restoring a completely different operational system environment in that case will not install programs or copy personal documents, while making the current system configuration pretty much useless and unrecoverable.
System Restore's purpose is to return your system to a workable state without requiring a complete reinstallation and without compromising your data files. The utility runs in the background and automatically creates a restore point when a trigger event occurs. Trigger events include application installations, AutoUpdate installations, Microsoft Backup Utility recoveries, unsigned- driver installations, and manual creations of restore points. The utility also creates restore points once a day by default. System Restore requires 200MB of free hard disk space, which the utility uses to create a data store. If you don't have 200MB of free space, System Restore remains disabled until the space becomes available, at which point the utility enables itself. System Restore uses a first in/first out (FIFO) storage scheme: The utility purges old archives to make room for new ones when the data store reaches a set limit. The file types that System Restore monitors are many but include most of the extensions that you typically see when you install new software (e.g., .cat, .com, .dll, .exe, .inf, .ini, .msi, .ole, .sys). Note that only application installations that use a System Restore restorept.api-compliant installer will trigger the creation of a restore point. Typically, system recoveries are easiest when you know *or think you know* what caused the problem (e.g., a recently installed device driver). In some cases, System Restore might not be the best choice for correcting a problem you're experiencing. System Restore changes many different files and registry entries, and in some cases might replace too much and actually cause more problems than it solves. For example, say you install Office XP, which triggers System Restore to create a restore point, and the software suite works great. Later in the day, you download and install an updated video driver, and because the driver is signed, the installation doesn't trigger System Restore to create a restore point. Now your system hangs on occasion, and you believe that the video driver is the culprit. In this case, you should use the Device Driver Rollback utility because it will address the device-driver problem only and not change anything else on your system. System Restore would roll your computer back to a preOffice XP state, and you would have to reinstall the entire software suite after you resolved the driver problem.
System Restore's purpose is to return your system to a workable state without requiring a complete reinstallation and without compromising your data files. The utility runs in the background and automatically creates a restore point when a trigger event occurs. Trigger events include application installations, AutoUpdate installations, Microsoft Backup Utility recoveries, unsigned- driver installations, and manual creations of restore points. The utility also creates restore points once a day by default. System Restore requires 200MB of free hard disk space, which the utility uses to create a data store. If you don't have 200MB of free space, System Restore remains disabled until the space becomes available, at which point the utility enables itself. System Restore uses a first in/first out (FIFO) storage scheme: The utility purges old archives to make room for new ones when the data store reaches a set limit. The file types that System Restore monitors are many but include most of the extensions that you typically see when you install new software (e.g., .cat, .com, .dll, .exe, .inf, .ini, .msi, .ole, .sys). Note that only application installations that use a System Restore restorept.api-compliant installer will trigger the creation of a restore point. Typically, system recoveries are easiest when you know *or think you know* what caused the problem (e.g., a recently installed device driver). In some cases, System Restore might not be the best choice for correcting a problem you're experiencing. System Restore changes many different files and registry entries, and in some cases might replace too much and actually cause more problems than it solves. For example, say you install Office XP, which triggers System Restore to create a restore point, and the software suite works great. Later in the day, you download and install an updated video driver, and because the driver is signed, the installation doesn't trigger System Restore to create a restore point. Now your system hangs on occasion, and you believe that the video driver is the culprit. In this case, you should use the Device Driver Rollback utility because it will address the device-driver problem only and not change anything else on your system. System Restore would roll your computer back to a preOffice XP state, and you would have to reinstall the entire software suite after you resolved the driver problem.
Computers that have been so completely destroyed that they look like something an abstract artist would paint are the computers that must be built using the Bare Metal Restore system. This system is basically the way to create a computer from scratch starting with installing the OS and software applications, and then if possible your data and settings.
The answer is very hard to answer