[TC 11.00rc1] Crash when using Help > Index > Keyword

[white]

21H2 because Windows Update never offered to upgrade to 22H2.

What is your Windows build version?

Have you tried to see if there are optional updates?
* Go to settings
* Start Windows Update
* Click Advanced settings
* Under Extra options, click on Optional updates

[JOUBE]

21H2 because Windows Update never offered to upgrade to 22H2.

that's strange.

Exception code: 0xc0000005 What is about that: "due to failed Windows update installation"? I found in the web.

[white]

Try direct run:
"C:\Windows\SysWOW64\hh.exe" C:\TotalCmd\TOTALCMD.CHM

You may want read the thread further back.

[AntonyD]

Btw Microsoft has abandoned this feature: .CHM files support.
So - if even we will be able to open those files - it does not guaranteed that all will be fine in that 'CALL hh.exe *.chm' process...

[AntonyD]

You may want read the thread further back.

I did not understand his answer - so that's why I asked it again.
Also at any system we must have 2 files hhctrl.ocx. But in some post back only
System32\ folder mentioned. And not SysWOW64. And in fault report we see only
System32\ folder. So it will be very interesting to see the NEW fault report when he
will try to run "C:\Windows\SysWOW64\hh.exe" chm file....

[JOUBE]

Btw Microsoft has abandoned this feature: .CHM files support.

That is ten(?) years ago now. They tried it. But the try failed...

[brahman]

Yes, AntonyD's suggestion was very helpful:
Direct run using hh.exe in SysWOW64 works, but direct run with hh.exe in c:\windows crashes as before.

hh.exe in SysWOW64 has different size - probably the 32 bit version, since it is only 16896 bytes (84034424e42017cf34897659e698c402fc42bf3339c1b3c3afe06fed54286820), vs 36864 bytes in c:\windows - file versions in TC both show the same "10.0.22000.1".

[AntonyD]

2brahman
Now all is much better)))
You system definitely allow to with easy run 32 bit CHM help subsystem.
C:\Windows\SysWOW64\hh.exe - exactly is an 32 bit app.
So problems you have only with 64 bit....
It remains to be seen - what exactly went wrong with this subsystem.

[brahman]

I am runnig sfc / scannow at the moment.
If that is clean, I will check the component store with "DISM /Online /Cleanup-Image /CheckHealth"

[AntonyD]

2brahman
what about
sfc /scannow
run command?
from admin's command prompt of course.
and after that
DISM /Online /Cleanup-Image /CheckHealth
and
DISM /Online /Cleanup-Image /ScanHealth
and
DISM /Online /Cleanup-Image /RestoreHealth

P.S.
Mamma mia)))))
I just typed this text and you are already doing it)))))))))

[brahman]

I learned in martial arts: "Never underestimate your opponent!" Lol

[brahman]

No component store corruption detected.

Scannow repaired file: C:\WINDOWS\System32\MsApoFxProxy.dll - but this has nothing to do with the CHM issue, it is a file that affects the audio system.

Just in case after the checking & repairing, I tried again and TOTALCMD.CHM still crashes.

I will now try 2white's last suggestions, in case you don't have any other ideas.

[brahman]

21H2 because Windows Update never offered to upgrade to 22H2.

What is your Windows build version?

Have you tried to see if there are optional updates?
* Go to settings
* Start Windows Update
* Click Advanced settings
* Under Extra options, click on Optional updates

OS Build 22000.2176

There are only 6 Driver updates: Intel Bluetooth and Intel net. My experiences with Intel upgrades have been so so, therefore I am procrastinating on those.

I will try what you suggested before now, but it will take a while, because I have to stop a lot of things and enter a lot of passwords.

[JOUBE]

There are only 6 Driver updates: Intel Bluetooth and Intel net. My experiences with Intel upgrades have been so so, therefore I am procrastinating on those.

These Intel updates come from microsoft, and not from intel itself. Intel only contributed. That's why they're okay. That's why you should install them. Probably the non-installation prevents an update to 2H22. Who knows? My experiences with driver updates from microsoft are good.

[white]

But in some post back only System32\ folder mentioned. And not SysWOW64. And in fault report we see only System32\ folder. So it will be very interesting to see the NEW fault report when he will try to run "C:\Windows\SysWOW64\hh.exe" chm file....

SysWOW64 was mentioned and it was mentioned that there was no crash when using that.