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 - OhForAWorkingWindows

Pages: [1]
1
Dear Tom / Boggin

We seem to be talking past each other. You've test run the program without (many) problems? That doesn't mean there won't be problems in particular circumstances. I said what I think one of those problems is. As to a repair install: yes, that's an option, but it is not the only option - if it were, the tweaking.com repair program would not exist. I can't see a reason, except perhaps for the effort involved, to not make that program better at its job - in the ways I've suggested.

Are you one of the developers of the program? They are the people who need to hear what I'm saying.

2
Thanks for the reply.

'One of the panes will also tell you which repair is running': my point about that was as follows. It does not show any progress *within a repair*.

'Can you try the repair program again in Safe Mode with Networking to see if there is any change?': thanks, but I managed by other means to fix things. The most serious, underlying problem with the repair program is, I believe, the following. Due to borkedness of my system - which is exactly what the program is meant to handle - some registry keys were readable only as administrator and this meant that some of the repairs, and/or the 'pre-repair operations' - hung. But also, and as I have been saying: progress within repairs needs always to be shown somewhere; the CPU usage indicator does not suffice for that because the usage could owe to other processes.

It seems to me that these are all problems that need fixing. And if the program does not get improved via feedback such as this, then how does it get improved?

3
Windows Repair 4.7.2 is fixing my Windows 10 registry at present. Or I hope it is. It tells me I can use CPU usage to tell whether it is carrying out the operation I requested. Well, there is CPU activity, between 1 and 30 and at one point 70%; but I came to think that it was other programs that were responsible. Your program does have a log window, but (1) it's blank initially (one has to think of looking in the drop-down), (2) the log for my operation just announces that it has started and does not even tell me whether I should see more once the operation is underway.

Admittedly I am not in Safe Mode but that is because in Safe Mode the CPU usage was very low (0.3%) and so I thought - rightly, it seems - that the repair was not working.

4
Thank you for your reply. However . .

1) I think you mean that there is an easier way of performing part of what those steps 1-3 accomplish. If that is what you mean: yes, I used a shortcut, in the form of a 'take ownership' context menu, for that.

2) I found that a repair install was offered only if I created an ISO. The other version of bootable media didn't offer it (and neither was it offered within Windows). This was a typical and grim Windows 'gotcha'.

5
Hello!

Edge would close as soon as opened and when I tried to install a 'feature' update I got locked into a temporary account. So: I used your Windows Repair, in Safe Mode, to fix file and registry permissions. Now Edge opens. (Goodness, though, that Microsoft continues to deeply embed a browser in the OS, despite the EU ruling and despite the problems caused when the program goes wrong!) However: now the 'Store' does not open, though, pre-repair, it did. I do not really care about the Store itself - and I have only a 'local account' - but the problem makes me think the next OS update, which I'll have to have at some point, will fail. (I have not tried that update - the feature update - since doing the repair.)

I suspect the Store problem is (itself) a permissions one. Any advice? Thanks.

Things I've tried to no avail: 'reset'ing the Store; a Powershell command to (I think) 're-register' Store components.

My level of knowledge: semi-advanced amateur (who is better on Linux, where things are easier to fix!).

EDIT: ah, steps 1-5 (inclusive) of this* seem to fix the Store problem! Perhaps you should incorporate those steps into your app (or, if they're in there already, something went wrong).

* Here is the link (for I can't see how to insert it into the post - do you use some sort of markdown? if so, what?): https://www.techtantri.com/windows-10-apps-not-working-download-apps-folder/

Pages: [1]