Main Forum > Tweaking.com Support & Help

Windows Repair not able to run on the Win 10 20H2

<< < (3/3)

Willy2:
- Ooops. Made a mistake in my previous post. I was in a hurry when I typed that reply. It should be (correction in bold characters):

"I reread the 1st post and it seems to be very straightforward. Having a MS account blocks the user from signing into Safe Mode. And then the user can't use WR anymore. But I think it also a matter of programs "interfering" with the MS account.

Willy2:
- I also experienced that programs behaved differently in different circumstances.
- One example was that there was a difference in behaviour beween Safe Mode and "Normal" mode.
- A second example was that one program showed behaviour (A). But a few days later the same program showed a slightly different behaviour (B). And 4 of 5 days later the program showed behaviour (A) again.
- My personal opinion is that A LOT OF these differrences in behaviour can be attributed to how well a program protects its own "(internal) variables".

Boggin:
What is behaviour (A) and behaviour (B) ?

Safe Mode is mainly a diagnostic mode as it isolates all third party programs from starting in the background.

The reason why it's advocated that WR is run in Safe Mode with Networking is to prevent antivirus programs interfering as they can do with programs it detects that can change the registry.

If a program is running fine in normal mode then there's no need to boot into Safe Mode to see how it runs.

Willy2:
- Behaviour A & B occurred in another program (not made by Tweaking.com).
- WR running in Safe Mode also has another advantage. It runs (much ??) faster than in "Normal Mode".

Navigation

[0] Message Index

[*] Previous page