I have a number of older programs that use hlp help files that are still being downloaded and used so I would like to have a way  for the folks downloading them to use the old hlp file format.

I used to be able to direct them to the MS site where they could download  a Win32Hlp.exe program for their operating system.

At that site I have downloaded and installed  windows 8.1 KB917607 x64.msu and still get an error message saying I need to download Win32Hlp.exe.

I did a forum search and found posts saying that MS had fixed this but other posts saying the fix didn't work.

Is there a solution for this issue?

I am using Win 8.1 64 bit on an HP ENVY m6  laptop.

At that site I have downloaded and installed  windows 8.1 KB917607 x64.msu and still get an error message saying I need to download Win32Hlp.exe.

Are you sure the install worked?   Check the ReportingEvents.log  for clues.  Also, it may not be the obvious module which is not being updated.  FWIW I would run ProcMon, filtering on Operation Is WriteFile  to find out what is going on.  Perhaps you should try installing both versions--32 and 64 bit.

WTH?  It looks like mine is running out of  %windir% and I have only the 32-bit version plus updates.  But I have not tried to do anything special with this module.

Try this Powershell pipeline so we can compare what we have:

PS C:\windows> ls -Re -Fi *winhlp* | sort LastWriteTime | ft Length, FullName -AutoSize

Note that I am giving the full command line, including my prompt, to show the starting point of this recursive search.  You should use the Administrator: Windows Powershell to minimize warnings and error messages.  AutoSize is specified to try to ensure the whole path will be displayed but that ultimately depends on the size of the window.

 

HTH

It said it installed and it shows up in the list of updates as installed. I uninstalled it and re-installed it but that made no change. I did try to install Windows8.1-KB917607-x86.msu but it says it isn't compatible - I suppose because I have a 64 bit OS.

I have never used PowerShell and would have to learn to use it, however since I want non technical people to use the fix, it needs to something as easy as downloading and installing the proper WinHlp32.exe.

Reading related posts it appears that other folks are having the same problem with the Win8.1 version of  WinHlp32.exe so it doesn't appear to be restricted to my computer.

Have you had an occasion to open one of the old hlp files in a Win8.1 OS?

Have you had an occasion to open one of the old hlp files in a Win8.1 OS?

Why can't I get Help from this program?

The Help for this program was created in Windows Help format, which depends on a feature that isn't included in Windows 8.1 or  Windows RT 8.1. For more info, go to the Microsoft Support website.

Hi ClayL,

I downloaded the 64 bit of Windows Help program (WinHlp32.exe) and installed it successfully on Windows 8.1 Enterprise 64 bit.

From this link: http://www.microsoft.com/en-us/download/details.aspx?id=40899

For more information, please check: Error opening Help in Windows-based programs: "Feature not included" or "Help not supported"

Best regards

I downloaded the 64 bit of Windows Help program (WinHlp32.exe) and installed it successfully on Windows 8.1 Enterprise 64 bit.

Me too.  So why am I still getting the same message when I try to open

%Downloads%\SysinternalsSuite\DISKMON.HLP

FWIW here is the result from my Powershell pipeline

Length FullName
------ --------
  2560 C:\windows\WinSxS\x86_microsoft-windows-winhstb.resources_31bf3856ad364e35_6.3.9600.16384_en-us_66fa9c274977a4e2\winhlp32.exe.mui
285696 C:\windows\WinSxS\x86_microsoft-windows-winhstb_31bf3856ad364e35_6.3.9600.16398_none_bd9f041c2504e85c\winhlp32.exe
285696 C:\windows\WinSxS\amd64_microsoft-windows-winhstb_31bf3856ad364e35_6.3.9600.16398_none_19bd9f9fdd625992\winhlp32.exe
 30720 C:\windows\WinSxS\x86_microsoft-windows-winhstb.resources_31bf3856ad364e35_6.3.9600.16398_en-us_66f3cd63497c262f\winhlp32.exe.mui
 30720 C:\windows\en-US\winhlp32.exe.mui
 30720 C:\windows\WinSxS\amd64_microsoft-windows-winhstb.resources_31bf3856ad364e35_6.3.9600.16398_en-us_c31268e701d99765\winhlp32.exe.mui
  9728 C:\windows\WinSxS\x86_microsoft-windows-winhstb_31bf3856ad364e35_6.3.9600.17415_none_bdf26dbc24c6d397\winhlp32.exe
  9728 C:\windows\winhlp32.exe
  1013 C:\windows\WinSxS\x86_microsoft-windows-winhstb_31bf3856ad364e35_6.3.9600.16384_none_bda5d2e02500670f\winhlp32.exe
 19142 C:\windows\Prefetch\WINHLP32.EXE-50DA0E57.pf

Notice that the only full size  winhlp32.exe that I have are in WinSxS only.

I'll see what ProcMon says is happening...  and apparently now there is a performance issue with it that I always need to start it elevated?  YMMV...  ICIM this is being done via my Administrator: Windows PowerShell...  Invoke-Item  (just executing it didn't work?). 

So, essentially, filtering with Operation Begins with Process, the winhlp32.exe in %windir% root is being executed and then helppane.exe (also in root?) is giving its unwanted "help".

what do you see in that scenario?

AFAIK I have had a reboot (Restart) since installing this

I installed one of my programs on my wife's Asus desktop. It has Win 8.1 64 bit. Clicking on Help generated the error and I downloaded the WinHlp.exe 64 bit again and installed it. Now hlp files run on hers.

So my problem is computer specific, not general as I thought.

 

Now hlp files run on hers.

How?

Just for grins I pointed  HLPFILE  at the X64 update version (since it wasn't installed properly) and got a new symptom.  9009.

C:\windows>assoc .hlp
.hlp=hlpfile

C:\windows>ftype hlpfile
hlpfile=%SystemRoot%\winhlp32.exe %1

C:\windows>ftype hlpfile=C:\windows\WinSxS\amd64_microsoft-windows-winhstb_31bf3856ad364e35_6.3.9600.16398_none_19bd9f9fdd625992\winhlp32.exe
hlpfile=C:\windows\WinSxS\amd64_microsoft-windows-winhstb_31bf3856ad364e35_6.3.9600.16398_none_19bd9f9fdd625992\winhlp32.exe

C:\windows>net helpmsg 9009

DNS server not authoritative for zone.

But how do we know whether  %SystemRoot%  contains the 64-bit version or the 32-bit version?  Also, why are they both the same length?

I suppose for completeness I should try pointing HLPFILE at the 32-bit version too?  Same thing.  ProcMon indicates that it is not winhlp32.exe which is generating this?  So where's it coming

So my problem is computer specific, not general as I thought.

So now you have two cases which you can trace and compare for their essential differences.

FWIW I just used ProcMon on mine and decided to find out where that  helppane.exe  was being invoked.

It was right here:

	winhlp32.exe	RegOpenKey	NAME NOT FOUND	HKCR\Wow6432Node\CLSID\{8CEC58E7-07A1-11D9-B15E-000D56BFE6EE}\TreatAs	Desired Access: Read	
	winhlp32.exe	RegCloseKey	SUCCESS	HKCR\Wow6432Node\CLSID\{8CEC58E7-07A1-11D9-B15E-000D56BFE6EE}		
	winhlp32.exe	CreateFile	SUCCESS	C:\Windows\SysWOW64\HelpPaneProxy.dll	Desired Access: Read Attributes, Dis, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened	

So, what does your wife's do at that point?  E.g. looks like we need to find out what  TreatAs  should be set to.

I ran promon as I opened a program - Wire Size Calculator - and clicked on Help. The file activity was in the pic below. The help file did not open -a "Failed to open help "error was generated - but success was indicated. Registry list showed no failures either. 

I ran promon as I opened a program - Wire Size Calculator - and clicked on Help.

Turn off the Profiling and turn on Registry events.  In order to navigate to the ones that I saw just do a Find (e.g. Ctrl-f) from the top for helppane.  Those registry events (e.g. the RegQueryValue) will have occurred just before that process is "created".

Okay I ran procmon on my laptop checking the registry when I clicked on Help in the program and got the following.

 

when I clicked on Help in the program and got the following.

Can you try just opening that file using normal file extension file type association?  That's what I am doing with the SysInternals HLP files.  Then as soon as the HelpPane.exe app opens, stop the trace. Also, it looks like you had File Access events only filtered for your screen shot. The UI is not particularly clear because its tooltip is always the same regardless of the actual state of the button you are checking.  However, it looks like one way of looking at it is that when it is in a patch of blue the exclusion filter for that Event class is not present.  E.g. compare the Filter list at the bottom with Event Class Profiling to see this.  (Ctrl-L Backtab (from the OK button), End)

In any case, the idea would be to trace both yours and your wife's instances of that scenario.  Then, in the Registry trace find out what the difference is that causes yours to diverge to HelpPane.exe

BTW I don't think you will actually have to filter just Registry events because usually they completely swamp any of the others.  So, I would leave them all enabled for context.

FWIW while I am here I took a different tack on the trace.  Finding the first instance of the CLSID which is involved {8CEC58E7-07A1-11D9-B15E-000D56BFE6EE}.  These occur just a bit before the first HelpPane Find, so probably all 3 NOT FOUND events if changed could significantly alter the flow

winhlp32.exe	RegOpenKey	NAME NOT FOUND	HKLM\SOFTWARE\Microsoft\WindowsRuntime\CLSID\{8CEC58E7-07A1-11D9-B15E-000D56BFE6EE}	Desired Access: Read
winhlp32.exe	RegOpenKey	NAME NOT FOUND	HKCR\ActivatableClasses\CLSID\{8CEC58E7-07A1-11D9-B15E-000D56BFE6EE}	Desired Access: Read
winhlp32.exe	RegOpenKey	NAME NOT FOUND	HKCR\Wow6432Node\CLSID\{8CEC58E7-07A1-11D9-B15E-000D56BFE6EE}\TreatAs	Desired Access: Query Value

The last one is the same as one I have already shown.

 

HTH

 I have been out of pocket - grandsons in from Denver.

I tried to start a hlp file by clicking on it and still the error.

On my wife's computer clicking on either one opens the help file.

A search yields no results for helppane.

Winhpl32.exe gives the results below. 

Although I have been writing programs since 1967 (Fortran IV) was my first language - I have not had to get into the guts of an operating system since the days of DOS and as you can tell I am just not knowledgeable. I do appreciate your help. 

A search yields no results for helppane.

Of course.  You could regard that as the error condition on your system that you are trying to diagnose.  So, at that point in your trace how far do you have to go back to find the starting point of that divergence?  For this part of the analysis you could filter very coarsely.  Try it with Operation Begins with Process  for example.  Then you can suppress both Registry and File access events, leaving just Process and Thread.  You already know what the divergence will be then, the helppane.exe in your trace and comparison between the two should be pretty simple from before that.  Then I would add perhaps Operation Is RegQueryValue (and allowing Registry events again).  E.g. see if her version was able to take some branches that yours couldn't.  Etc.

Good luck

There is now an update available for this which works in W8.1.2

C.f.

https://social.technet.microsoft.com/Forums/en-US/9db52e81-e5c1-49fe-8a87-ecbbf79b2e81/i-installed-the-package-that-this-site-says-contains-winhlp32-but-cant-find-it?forum=w8itprogeneral#c26dfa90-de78-4e54-a8a7-005fa9435ea8

BTW the first time I tried to use the Download link in the KB article as is I got a "not found" condition.  I used right-click Copy Shortcut to actually get it.  YMMV.

FYI

Thank you very much Robert !!! That worked. It took an unusually long time to install for some reason but my hlp files load now. :)