Windows 10: Narrator

Well, although the procedure went well, the patient is still sick?

1. Narrator now automatically turns itself on upon restart.
2. System still freezing on restart, (approx 3/4 of the way through, (compensating with the 'Slide' shutdown feature).
3. Still have no "Left" click response on the Win 10 Start Button, (compensating with "Start Menu 8").
4. Still have no "Right" click response on any 'Task Bar' icons. (no compensating method).

I am wondering if any of these problems are 'Registry' or 'Program' related?

 

Try running SFC/scannow once or twice more. Sometimes it won't get it all the first time. What you are looking for now is no integrity violations found.

 

1st run:
C:\WINDOWS\system32>sfc/scannow
Beginning system scan.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.

2nd run:
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.

 

Unfortunately, no change.

Apparently MS hasn't afforded us a true repair tool other than, "Repair Install Windows 10 with an In-place Upgrade", at the risk of perhaps losing some programming. (XP and 7 much easier to fix).

 

Well, if windows is still messed up it's time to repair install/ in place upgrade. Sorry, plenty of times what you did will solve the problem. The disk from tech bench would be the one to use. Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums . I went through much the same thing with win 8.1 about a year ago. Turned out Norton was the culprit.

 

John, I cannot believe that for all the knowledge out there that is available to us that we cannot seem to understand the basics of win 10?

How does something like narrator turn itself on automatically at boot up when it is set to off?

What components are involved with a 'left click' function on the Win 10 Start Button?

What components are involved with a 'right click' function on the system tray buttons?

How would you monitor the 're-start' shutdown sequence to find which function or program was causing the error?

As you know, it can take weeks to rebuild a system that has many component programs and what about the loss of factory or vendor installed programming or purchased programs with their respective legitimate key codes?

There must be a better way!