Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - HappyElderGeek

Pages: [1]
Program & Site Requests / Preserving Network Configurations
« on: February 06, 2018, 09:42:38 AM »
Many of us use Work Group networking, and it requires several settings to customize.  Unfortunately, I can't seem to find any option that would preserve that configuration...WR always creates a Home Group, which immediately makes the "Repaired" computer alien to the rest of the network (for some features).

Recently, the consequences of reverting to HomeGroup blew up one of my backup strategies:  I run backups on every system, every night.  After a recent WR session, I noticed that one computer (call it "M"), which launches a backup automatically at 5:30 pm, was ALSO triggering a second computer (say, "W") to run a backup at the same time...but, the latter computer is scheduled to run at 9:30, I started getting two backups every night from "W"!  That's one of the reasons I need to avoid "Home Group."

As it is, I now have to reset from "Home Group" to "Work Group" manually after every Windows Update (thru v4.13).

If you would just provide us the option to NOT change the network type, it would save a lot of us a lot of grief.  (And, if there IS such an option, can someone please inform me where it is?)


I've got a new tool, and its' called KB3125574, from Microsoft.  Attached is a document I wrote about using it to revive an old system...if it'll work there, it'll work anywhere!

Warning; my draft was not properly labelled, and it HAS ERRORS.  If you've tried my document, please read the new one.  Not all is wine and roses (even if you're not concerned about the telemetry issues).  I've updated some systems that have NO TRACE of the new KB3125574 having been installed, but the systems seem more stable.  It's never the wonder tool I thought we were provided, is it?

Feedback / Testimonial
« on: March 15, 2016, 09:16:20 AM »
 :teeth:  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...
 :cheesy: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.
 :smiley: Windows 7 SP1 is now working, is stable, and Outlook is rebuilding my IMAP email as I write and I have re-written my procedure for curing seemingly intractable Outlook 2013 problems, and everything is working exactly as it had when it was brand new.

It's time we started giving Shane public credit for what he has done with this suite of products.  All together now:

Hooray for Shane!

Feedback / Happy Customer...with a Request
« on: August 09, 2015, 03:35:55 PM »
 :cheesy:  Dear Shane:

I use Windows Repair a lot, and I tell my clients to buy it (I won't use the product on their computers until they do; for the value you give, the price is a pittance).  I'm using v3.4.0

One question:  The sole nagging problem I have with many Windows 7 systems is that the Task Scheduler was apparently written as a high-school class project, and tested by their brothers and sisters in grade-school.  It's buggier than an entomologists' laboratory.  If you dare touch it (e.g., inadvertently delete a key, or a file) it is broken and irreparable.

Is there any chance that you can add a rebuild of the "stock" Task Scheduler to your wonderful tool?  I don't have the Windows programming chops, but here's what I'd do:  I'd build a new, working, fully updated Windows 7 SP1 system, and then copy the program itself, all the files (three different places) and all the registry entries (again scattered across the registry), then copy the entire collection back to the Windows drive and registry.  That would completely replace all the "stock" tasks (albeit resetting any customizations), but restore the system to a fully working ab initio system without touching any of the users' own tasks or those loaded by other vendors (e.g., Adobe, Google, et. al. for periodic update checks).

To avoid the copyright implications, I would be quite happy if you required the user to provide the Windows 7 SP1 "Recovery" disk (unless they already have a Recovery Partition), so all you have to do is copy files without "distributing" any of M$'s code.

Curiously, the Upgrade/Repair install of Windows 7 from the DVD does NOT reinstall the Task Scheduler...I've tried, several times.

I'd make this another feature of the Pro edition, to increase the probability that you are more adequately compensated for your marvelous work.  Given the many, many users who've been pleading with M$ for years in their fora for some help, I'm confident it would be a money-maker.  I'll even volunteer, should you implement it, to go back to every forum on Task Scheduler I've ever visited and tell them you've got a solution they can use.

Thanks for considering the possibility.

   Happy Elder Geek

Pages: [1]