<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Ashampoo Backup Pro: Easy Backup and Restore software for Windows	</title>
	<atom:link href="https://reviews.thewindowsclub.com/ashampoo-backup-pro-review/feed/" rel="self" type="application/rss+xml" />
	<link>https://reviews.thewindowsclub.com/ashampoo-backup-pro-review/</link>
	<description>Software, Services &#38; Hardware Reviews by TheWindowsClub</description>
	<lastBuildDate>Thu, 02 Nov 2017 04:57:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>
		By: paladyn		</title>
		<link>https://reviews.thewindowsclub.com/ashampoo-backup-pro-review/#comment-22</link>

		<dc:creator><![CDATA[paladyn]]></dc:creator>
		<pubDate>Thu, 02 Nov 2017 04:57:00 +0000</pubDate>
		<guid isPermaLink="false">http://reviews.thewindowsclub.com/?p=223#comment-22</guid>

					<description><![CDATA[&quot;Creating a System Restore Point first before installing a new software is always recommended, he feels&quot; 

Always? Really? I am seriously curious if this is &quot;always&quot; a sine qua non for system security when installing software, because I maintain a dedicated USB Recovery Drive, updated whenever I add or replace hardware, as well as a Windows 10 system image, updated regularly, on an external 1 TB hard drive, in addition to which I use Ashampoo Uninstaller, which launches automatically whenever I install software. 

My experience goes back to DOS 3.3, MASM, Turbo Pascal, etc., so I know how to access the boot sequence recovery options (having had to do so about three months ago). I am trying, and failing, to imagine a failure scenario from which I cannot recover. 

The reason that I am SERIOUSLY curious is that Windows only maintains a few System Restore points,depending upon how much drive space is allocated in the Control Panel&#124;System Properties&#124;Configure dialog, beyond which new ones replace the oldest. When I experienced that system boot failure a few months ago, I found, to my considerable chagrin, that every one of my most recent restore points abended and failed to complete the restore operation. Without much hope I tried the oldest one I had, and you may imagine my relief when it completed successfully!

Consequently, it is VERY important to me to understand why &quot;Creating a System Restore Point first before installing a new software is always recommended,&quot; since my experience has demonstrated dramatically that creating a restore point is NOT without consequences. In my case, had I created a new restore point for every software installation, I might not have had a viable restore point when I needed it.

So, I would be most pleased if Mr. Thakkar would kindly propose to me a failure mode (not involving a hardware failure, of course ;-) from which I could not recover. Creating a new restore point is a piece of cake using Ashampoo Uninstaller&#039;s Tools&#124;Administration&#124;Manage Restore Points, or even the built in system dialog, for that matter, so that&#039;s not the issue. But I would be loath to create new restore points needlessly unless it can be demonstrated that there is a failure scenario from which I could not recover given my current recovery preparations. So, please explain what that might be, if you will. Thank you.]]></description>
			<content:encoded><![CDATA[<p>&#8220;Creating a System Restore Point first before installing a new software is always recommended, he feels&#8221; </p>
<p>Always? Really? I am seriously curious if this is &#8220;always&#8221; a sine qua non for system security when installing software, because I maintain a dedicated USB Recovery Drive, updated whenever I add or replace hardware, as well as a Windows 10 system image, updated regularly, on an external 1 TB hard drive, in addition to which I use Ashampoo Uninstaller, which launches automatically whenever I install software. </p>
<p>My experience goes back to DOS 3.3, MASM, Turbo Pascal, etc., so I know how to access the boot sequence recovery options (having had to do so about three months ago). I am trying, and failing, to imagine a failure scenario from which I cannot recover. </p>
<p>The reason that I am SERIOUSLY curious is that Windows only maintains a few System Restore points,depending upon how much drive space is allocated in the Control Panel|System Properties|Configure dialog, beyond which new ones replace the oldest. When I experienced that system boot failure a few months ago, I found, to my considerable chagrin, that every one of my most recent restore points abended and failed to complete the restore operation. Without much hope I tried the oldest one I had, and you may imagine my relief when it completed successfully!</p>
<p>Consequently, it is VERY important to me to understand why &#8220;Creating a System Restore Point first before installing a new software is always recommended,&#8221; since my experience has demonstrated dramatically that creating a restore point is NOT without consequences. In my case, had I created a new restore point for every software installation, I might not have had a viable restore point when I needed it.</p>
<p>So, I would be most pleased if Mr. Thakkar would kindly propose to me a failure mode (not involving a hardware failure, of course 😉 from which I could not recover. Creating a new restore point is a piece of cake using Ashampoo Uninstaller&#8217;s Tools|Administration|Manage Restore Points, or even the built in system dialog, for that matter, so that&#8217;s not the issue. But I would be loath to create new restore points needlessly unless it can be demonstrated that there is a failure scenario from which I could not recover given my current recovery preparations. So, please explain what that might be, if you will. Thank you.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
