Show Posts
1
Tweaking.com Support & Help / Re: V4.3.0 fails even before "Permissions" repairs on stable Windows 7
« on: November 12, 2018, 03:12:47 pm »
I had lots of problems trying to use WR V4.3.xxx, but was able to use V4.2.0 to recover a system that had to be rolled back from a backup made about 9 days ago. That all worked. Some key points:
#1 Wherever I can, I use C: (for Code; executables, Windows, apps, etc.) and D: (for Data), which allows me to roll a version of the Windows 7 O.S. without losing any data (e.g., Quicken accounting database).
#2 I make 100% backups (C: and D:, in toto) of the every system to a central computer once every day (one computer does it at 7:00 am, all the rest are staggered from 6:30 pm to 1:30 am, to avoid slowing regular LAN speeds. I have three Terabyte disks, and I "rotate" them every Sunday morning. Each computer has C: and D: backups made every day, each week. That allows me to "roll back" a poorly running Windows and Apps (C:) without losing important data for local computer apps.
#3 Customarily, after rolling back an O.S. (e.g., for poor performance, intrusive errors, etc.) to an earlier edition (usually a couple of days; sometimes as much as 15 days) I run the latest stable (according to my own standards) version of Windows Repair. Recently, I tried that with WR 4.3.0, and it was a catastrophe...so, I went even further back, to WR 4.2.0, which worked like a charm.
#4 I would encourage the owners of this domain to have a specific forum for user feedback about how Tweaking.com's editions of specific products are actually working, so that the founder can know how his products are working in real environments. Some of us have enough experience that we can make better-informed decisions from that information. For me, the ability to decide whether to apply the absolute LATEST edition of WR, or to use an older edition, is a critical decision point, when I (or a client) are having problems. When I can see other customers' feedback about their experience, it helps me make that "use the newest-or-prior edition" decision. That means more exposure for you, I know, but flying blind with a powerful product like WR is scary, even to some of us who've been using these kinds of tools for a long time (I've been in the trenches since 1962...on an IBM 1401, IBM 709, and even a vacuum-tube RCA 301!). My own estimate is that it would materially improve confidence when something like 50 early-bird users can inform the rest of us about how stable and reliable a powerful and complex product from Tweaking.com has performed over the past month or so. I cede to you the responsibility of how to sort through the responses for those that are productively informative (vs. the novices, and those who don't cotton to things like "Safe Mode").
I have a habit of only returning food in a restaurant to which I intend to return...I trust you'll accept my feedback in the spirit that's attended. If the situation was so bad that I'd rather never return, I don't even bother.
Ye Old Bit-Slinger.
--Carol Anne (aka "Happy Elder Geek")
#1 Wherever I can, I use C: (for Code; executables, Windows, apps, etc.) and D: (for Data), which allows me to roll a version of the Windows 7 O.S. without losing any data (e.g., Quicken accounting database).
#2 I make 100% backups (C: and D:, in toto) of the every system to a central computer once every day (one computer does it at 7:00 am, all the rest are staggered from 6:30 pm to 1:30 am, to avoid slowing regular LAN speeds. I have three Terabyte disks, and I "rotate" them every Sunday morning. Each computer has C: and D: backups made every day, each week. That allows me to "roll back" a poorly running Windows and Apps (C:) without losing important data for local computer apps.
#3 Customarily, after rolling back an O.S. (e.g., for poor performance, intrusive errors, etc.) to an earlier edition (usually a couple of days; sometimes as much as 15 days) I run the latest stable (according to my own standards) version of Windows Repair. Recently, I tried that with WR 4.3.0, and it was a catastrophe...so, I went even further back, to WR 4.2.0, which worked like a charm.
#4 I would encourage the owners of this domain to have a specific forum for user feedback about how Tweaking.com's editions of specific products are actually working, so that the founder can know how his products are working in real environments. Some of us have enough experience that we can make better-informed decisions from that information. For me, the ability to decide whether to apply the absolute LATEST edition of WR, or to use an older edition, is a critical decision point, when I (or a client) are having problems. When I can see other customers' feedback about their experience, it helps me make that "use the newest-or-prior edition" decision. That means more exposure for you, I know, but flying blind with a powerful product like WR is scary, even to some of us who've been using these kinds of tools for a long time (I've been in the trenches since 1962...on an IBM 1401, IBM 709, and even a vacuum-tube RCA 301!). My own estimate is that it would materially improve confidence when something like 50 early-bird users can inform the rest of us about how stable and reliable a powerful and complex product from Tweaking.com has performed over the past month or so. I cede to you the responsibility of how to sort through the responses for those that are productively informative (vs. the novices, and those who don't cotton to things like "Safe Mode").
I have a habit of only returning food in a restaurant to which I intend to return...I trust you'll accept my feedback in the spirit that's attended. If the situation was so bad that I'd rather never return, I don't even bother.
Ye Old Bit-Slinger.
--Carol Anne (aka "Happy Elder Geek")
It was scarey, trusting a valued Latitude E6420, to Windows Repair (v3.8.4)...but it was so abused, so corrupted, we were on the verge of wiping the disk and donating it. So, I tried one last thing...
Windows Repair. But, this time, instead of trying to shortcut, I did ALL the steps: Even though I make 100% daily backups of every computer in the shop, every day (overnight), I followed every step. And, I ran the actual "Windows Repair" final step twice, as recommended. Then I did a "repair install" of Office 2013 (H&B), and had to remove, root & branch, some Outlook add-ons, to get back to a working, stable system.