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.

Messages - GLykos

Pages: [1] 2
One other thing for awareness - on those occasions when I have (re)installed Windows Repair and not yet deleted the WR tray icon from Task Scheduler where it is inserted by default, when I go to soft-restart the computer while up, the shutdown pauses to warn that (only) the WR Tray program is still running, then after a brief delay clears it and continues to shut down.  Dell laptop Win 7 32-bit.


Right - thanks.

Hello again, Boggin!  Uninstalling WR 4.16/installing WR 4.17 produces the same results as previously reported above on April 2 (other than it's now the WR 4.17 installation screen at step 1.

As a gentle reminder, am bringing forward your closing reply to the predecessor thread to this one based on WR 4.08 at the time:
Global Moderator
Hero Member
Re: Preservation of some installation option elections

Reply #6 on: October 21, 2017, 01:36:03 PM

Your suggestions have been taken on board and added to the queue for updates to the program.


Further to previous exchanges -

1. WR 4.16 installation screen at reinstallation.
2. Prompt overwriting existing user-specified program folder.
3. Prompt overwriting existing user-specified shortcut folder.
4. Run at installation, view of untouched Options:  run tray icon not checked.
5. Task Manager view showing unrequested task:  tray icon run at logon.


Installing Windows Repair causes its tray icon to be task-scheduled for Windows startup - there is no choice at installation nor is that default behavior mentioned anywhere.  Once running, the program Settings - WR Tray Icon - Start and Remove buttons then immediately create/delete that task - but there is no indication in that box as to what is currently selected.  I don't follow what is so "nifty" about all this.

"Start [Tray Icon] With Windows" (and strictly speaking, the utilized task option is at logon) alone, checked/unchecked (unchecked as default) in lieu of two buttons would be self-documenting and unambiguous.  Having said that, what's the difference between "**launching** the tray icon at program startup" and "**starting** it with Windows"?  If you start the Tray Icon with Windows, does it persist when the program runs even if the Launch Tray Icon With Program is unchecked?  C'mon, guys.

Separately, suggesting that program reinstallation maintain previously user-specified program and shortcut folder names is a universal standard convention.


Hello again.  May be operator error on my part, but started a thread on the captioned subject on 10/21, was last replied to by Boggin on same date advising that "Your suggestions have been taken on board and added to the queue for updates to the program."

It's now five months and maybe five program revisions later and the reported issues (to some of us) have not been addressed, it appears that this forum has very little activity, and I'm unable to reply to Boggin - it seems that topic, maybe all in this forum, are locked, hence this new posting to continue the existing thread.

The suggestions previously submitted were, effectively:  1.) when reinstalling Windows Repair, as in during an update, pay attention to where the user chose to install the previous version and associated menu folder and follow suit, and  2.) stop automatically scheduling a task during installation to run the program at computer startup.

Any news?


The installation closes with an option to run (or not) the just-installed program upon completion.  Not selected, the program still loads.  If you then restart the computer, the program (or at least its icon) loads again (even though not requested by the user to do so)  This is illogical, as you would say...

The program checks self-integrity every time it starts (and makes a show of it, all of which is fine), and if a related issue is detected and reported, the user can take appropriate action (if the program hasn't already done so).

Beyond that, your several replies are incomplete with respect to the two items originally enumerated for consideration.  I follow that you may not see a problem by the way that you do like to do things - thanks for sharing.

That said, please pass along the original request - thanks!

Sequence of operations here was different.  The updated program was downloaded and then installed on top of the previously-installed version, which was not running.  During that manual (re?)installation, these gaps come to light - lost previous user customized data and an indeterminate startup state.  Try it.

In my experience, preserving such configurable data across reinstallations (manual or automatic) is a de-facto standard convention of contemporary programs.  You'd expect that if you didn't elect to run the program at the conclusion of reinstallation, all would be ready for next time.  As it stands, manual intervention (read:  typing previously-entered data in again) is needed here during installation, and then a cleanup pass running the program is needed to synch the boot startup behavior.

As mentioned, this is a trivial matter, but an on-going nuisance, and seems inconsistent with the high standards that the author maintains (and whose dedication is clearly recognized and valued by the user community).  If you always use automatic program updating, I guess you wouldn't know - now you do.

Thanks for team's consideration.

Have very much appreciated having Windows Repair available to count on when needed.  Have likewise very much appreciated the author's dedication in continuing to revise and update the program.

A request that stems from needing to continually adjust the installation of updates to my preferences:
1. Please preserve the user's choice of program installation and menu group folders.
2. Please resolve whatever is causing the program to run at startup after installation even though that was specifically not requested during installation.  Settings | Remove from Startup (click with no visual success indication) seems to achieve that after the fact.  Perhaps changing the two buttons (are they in fact independent functions?) under WR Tray Icon to be presented the same as Launch Tray Icon would simplify the UI and make those elections self-documenting at a glance.

These are trivial matters, but would simplify the updating process.  Am seeing this on Win 7, if it matters.

Thanks, and best regards,

Thanks very much to you and your team for your interest and support!

Will mention to close off my earlier comment in this thread about hoping to view (and log) all WR run-time errors - happened to discover while poking around in WR that CMD-window supressed output is a default WR state, and an option is available and readily accessible on the Settings tab under CMD.exe Options to see the "whole story" if desired.  Have not gone back yet to see if it captures both the STDOUT and STDERR streams, hopefully chronologically merged.

Yes, if you're not using the Google search page, you won't see the problem.  I use Google as my IE search engine and my start-up screen.  Seems a lot of people do use the Google search page.  There are numerous postings with threads elsewhere from people experiencing the same problem but this was the first useful discussion I found.

The problem manifests itself as allowing initial user input into a data entry port on the page, then refusing to accept any more;  scroll down on the search page, click a selection, and the page jumps back to the top.

The problem appears to be with the current Google search page, or in its interaction with Java, as accessed via IE and has existed for some months at this point.  For me, while I could awkwardly (for me) go to another browser to avoid the problem, having a work-around that allows using Google search in IE is very much appreciated.  The article includes a link to go directly from a browser to the previous black-bar Google search page to see what this is about.

Am on IE 9 due to still on Vista, started encountering crazy Google search webpage behavior some weeks (?) back.  Attempted to run WR IE repair to see if it helped, but a junction problem in my NTFS appears to have prevented it from executing.

While resolving the junction issue is on a back burner, chased after the search page issue (again) and finally discovered a useful discussion about the problem:!topic/websearch/S0V3xNkjFEI/discussion.

Turns out that it's not just IE 9 that's affected but most/perhaps all of the IE's.  Google's current webpage has some sort of issue, perhaps in its interaction with Java JRE.  Of the various work-arounds mentioned in the discussion, the one I found to be immediately helpful, integrating seamlessly with normal operation while not involving peripheral software settings, is the one adding to to IE's Compatibility View Settings.  It causes Google to run as an earlier version described as the "black bar" search window (due to one being displayed across the top of the page).

This being the case, assume but can't (yet) verify that WR IE repair won't fix the Google search page issue, seemingly not an IE issue per se.


Re-examination suggests a corrupted junction point.  NTFS Links View (attached) suggests bad first junction, creating recursive situation that is consistent with DIR errors and Win Explorer directory structure display.

Simple dump of system-drive junctions via DIR, with erred paths following (attached) provided for context.  Those junctions created 7/2015 likely resulted from running then-current WR pre-scan.

Located a sample script file which appears suitable to manually fix the junction error(s).

Will reflect on this, poke around a bit more, then make NTFS adjustments.

Don't know that this has anything to do with the originally reported (and still existing) system save/restore checkpoint function getting broken, but am going to push ahead, attempting to fix and clean up as I go, see what happens.


In search of my unrecorded WMI repair run-time errors, turns out the DIR command (among others?) sends normal output to STDOUT and error output to STDERR.  The WMI repair command window errors that flashed by but didn't get logged appear to have resulted from a DIR (or DIR-like) command.  Running DIR from root-dir down, the errors are captured by doing an output redirect to 2> (rather than >, alternatively 1>).  Here's a brief related MS article:

Next step is to try to understand current situation and contemplate corrective action(s) while wondering how I got here in the first place.  The error output is attached for reference, if curious.

FYI, and regards.

Thanks for your reply.

Discovered NTFSLinksView, looked around a bit, don't see anything obviously untoward with the junctions.

Don't mind (with some level of confidence) throwing stuff against the wall to see what sticks, but would sure like to be able to capture the run-time errors encountered by a diagnostic routine, at least on request.  The errors may not be germane to the specific issue of interest, but can absolutely be of interest in detecting and perhaps later addressing other anomalies that happen to surface during the process.

Lessee, how does it go:  Why break it if it works?  To make it work better, right?

Just one person's viewpoint...

Pages: [1] 2