Windows 10: Toolbars: Rename broken.

Win 10 16100 /14393 32 bit
I keep 2 toolbars on my taskbar: "Progs" and "System." Each contains shortcuts to my available programs. When I rt click and select Rename a little "Rename" window pops up with the present name shown, ready for editing. However, it's impossible to actually edit the string because the mouse click causes the window to momentarily show a red "X" for close. Nothing else happens. The close button does not work but "cancel" does.

I can change the name by opening Properties. I can also rename files in Explorer, which does not use a special window. It's not a huge inconvenience but clearly something is wrong.

tcebob

Well, resetting the toolbars hardly needs a special batch file. Anyway, I did use the batch and reinstalled the toolbars. No change. The problem is with Windows, not the toolbar itself. It is either a bug or something amiss on my installation. I hesitate to repair the system for such a minor irritation but if that will help I'll reconsider. Thanks for your help.
tcebob

Already had that selected. Still convinced it's a bug. I appreciate the suggestions.
tcebob

Thanks, I'll give it a try later.
tcebob

Update: I found other windows with the same problem: refusal to accept or edit entries. These are windows Class #32770.

In preparation for a repair I ran

C:\WINDOWS\system32>sfc /scannow


Beginning system scan. This process will take some time.


Beginning verification phase of system scan.
Verification 100% complete.


Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

I can provide CBS.log (5.2 meg) if it will help.

tcebob

Further update: I made an iso from my present system and booted it. After a couple of hours the system was repaired. (I do NOT recommend doing this; the repaired system placed all of my installed files in C:\Program Files and in the process screwed up my python installation.) All is (sorta) normal now, but the windows mentioned still don't work. It seems these windows were written in pre-XP days and never properly ported to newer Windows. Why my installation can't handle them, I don't know. My last resort would be to completely install Win 10 from scratch on a new hard drive and try to import as much as possible from the present one.

I'd really appreciate any advice or comments.

tcebob