Windows 10: Ayuda de Windows WinHlp32.exe para Windows 11

Buenos días, Tengo un programa, que deseo abrir la opcion de ayuda, sin embargo me muestra el siguiente mensaje:"Error al abrir la Ayuda en programas basados en Windows: "Característica no incluida" o "Ayuda no compatible"Dentro del centro de ayuda indica lo siguienteara ver los archivos de Ayuda de 32 bits con la extensión de archivo .hlp en Windows, tendrás que descargar e instalar WinHlp32.exe desde el Centro de descarga de Microsoft.4013443 WinHlp32.exe para versiones de Windows 8.1 basadas en x864013443 WinHlp32.exe para versiones de Windows 8.1 basadas en x644013443 WinHlp32.exe para W

:)

 

Winhlp32.exe and Windows 10

Enabling Winhlp in Windows 10

To enable Winhlp to work in Windows 10, follow these simple instructions.

• Download the updated Winhlp32 installation files, which are compressed into a zip file (winhlp32-windows-7-10-x86-64.zip) from the following link: https://drive.google.com/open?id=0B_tSrOg4FLp1T0dyTEppaW9SYm8
  
• Extract the contents of of the file you just downloaded (winhlp32-windows-7-10-x86-64.zip)
  
• Run the Install.cmd as Administrator by right-clicking on Install.cmd, then select Run as Administrator.
  
• Acknowledge any privilege warnings and allow Install.cmd to proceed.

That is all there is to it. You now you have Winhlp working in windows 10!

 

Winhlp32.exe on Windows 10

Subject: Winhlp32 (Help) in Windows 10 for Lotus 123 and other legacy programs

References

A. IBM Lotus SmartSuite Forum - Getting Lotus Help Files to Work in Windows 10, David Selby

-
http://www-10.lotus.com/ldd/ssforum.nsf/d6091795dfaa5b1185256a7a0048a2d0/fbba20da77553cc285257ee8001270c2?OpenDocument

B. MS Community - Thread by Alan Cope (9 Aug 2015): -

Redirecting

C. MS Community - Thread by SudsieMcSudFace (28 Aug 2017): -

Redirecting

D. Komeil Bahmanpour Website - Windows 8.1 & 7 Help Program (WinHlp32.exe) -, also - Alan on August 9, 2015 -

Windows Help Program (WinHlp32.exe) for Windows 8.1 and Windows 7 x64 and x86 - Komeil Bahmanpour

1. Introduction: Windows 10 does not provide the executable WinHlp32.exe to access HELP files and this causes a problem for MANY older programs, sometimes called legacy programs. As WinHlp32.exe has been part
of the historic Windows system, it can be considered both a legacy program and its absence is a problem. The following summarizes solutions to this problem that has been created by Microsoft Windows 10.

2. Specific Problem: While running Windows 10, I could not access HELP files for Lotus 123, Version 9.8. The Help files require WinHlp32.exe. Windows 10 does not include WinHlp32.exe. This is also the case
for many other legacy programs.

3. A search through several web communities shows that a solution has been found by numerous people. See the references.

4. The common solution is generously provided by Mr. Komeil Bahmanpour, see reference D. The solution eventually loads the executable in RAM memory where it resides for use by the legacy programs, including my Lotus 123.

5. I spent more than a day reading and working through this problem. There are several variations that can be found. (Microsoft has certainly made life difficult for a lot of people.)

6. In my first trial, the executable, WinHlp32.exe appears to be a problem. The executable is included in the compressed (zip) file downloaded from Mr. Bahmanpour's website. The zip includes 3 files, one of which is WinHlp32.exe. That executable file
has a size noted as 290 kB.

7. None of my trials worked with WinHlp32.exe as obtained from Bahmanpour's website.

8. In my last trials (which worked) I found a different executable, same name, thus WinHlp32.exe and with a size noted as 312 kB. The file has been obtained from a comment by SudsieMcSudFace, see Reference C. (also found at:

OneDrive
)

9. The following points present pertinent information for my trials which worked.

10. The Bahmanpour solution includes a download of a 3 compressed files. Those files are named:

• winhlp32.exe

• winhlp32.exe.mui

• Install.cmd

10.a. The files are unzipped and placed in a resident folder, user choice.

10.b. The file for winhlp.exe has been replaced per #8, above.

11. The Bahmanpour solution requires an edit of the file name Install.cmd. That edit can take at least two different forms. One form is per Alan, see Reference B, also D. The other form is per

JOQuantaman February 12, 2016, see Reference C. Both forms appear to work.

11.a. To edit the command file, right click on the file and select "edit". Save the file as *.cmd. (The * indicates a wildcard character for any name, i.e. Install.cmd.)

11.b. Bahmanpour via Cope recommends an edit (also others, see EricN1719, August 26, 2015 Reference C). That edit follows:

- edit the cmd file

• look for the area :: Settings

• after the two "set" lines for "MuiFile..." and "ExeFile...",

• add the two additional lines for "WindowsVer..." and ":Bypass...."

Thus, the excerpt:

...................

:: Settings

set MuiFileName=winhlp32.exe.mui

set ExeFileName=winhlp32.exe

set WindowsVersion=7

goto :BypassVersionError

:: ---------------------------------------------------------------------------

:: Displaying installer information

................

11.c. JOQuantaman recommends a different edit (Reference C). He recommends changing the version detection from Windows 7 to Windows 10. Thus, the excerpt reads:

..............

:: Windows version detection

echo Setup is detecting Windows version...

ver | findstr /il "10\.1\." > nul

if %errorlevel% equ 0 (

echo Microsoft Windows 7 [Version 6.1] detected.

set WindowsVersion=7

goto :BypassVersionError

)

ver | findstr /il "6\.0\." > nul

.................

11.d. Save and close the command (*.cmd) file and RUN IT AS ADMINISTRATOR (right click on file - Do not miss this instruction). A command (DOS) window will appear after the command file is run. The window will show that possible instances of WinHlp32 have
been terminated, and the Registry then updated with entries from the new copy of WinHlp32. Press any key to close the command window. (For readout of command window, see thread by One Iron, January 22, 2016, Reference B.)

11.e. The resident folder will be filled with supporting files.

11.f. WinHlp32 is now resident in your computer's RAM.

11.g. I am able to reboot and still access the HELP files in Lotus 123.

12. Comments by community participants make other suggestions. Before trying the Help in the legacy program, suggestions are offered to reboot, to close the internet browser, etc. Also, some participants had to re-install after Windows 10 does an upgrade.
Some participants offer the Install.cmd file as "already edited". You can find these suggestions in the referenced websites.

13. Warning is given by JOQuantaman, October 6, 2017, Reference B. Reboot your system to close the backdoor vunerability presented by WinHlp32. Do this after you use Winhelp in revcovering your legacy help
files.

14. Summary. The foregoing is information I gathered while not realizing my problem was due to a non-working WinHlp32 file. Hope this helps you and saves a lot of your time. All of this could have be avoided
if Microsoft would realize what people need when they do these revisions.

MGM

 

Winhlp32.exe on Windows 10

Please NOTE: When we sneak a working version of WINHLP32.EXE onto Windows 10, it will cause 1016 Errors upon Restarting. I suspect these errors can be ignored, especially if you don't activate WINHLP32.EXE by clicking on a HELP file or evoking it from
a legacy program. WINHLP32.EXE will remain in RAM, once it is called. That point may create a weakness or Backdoor for accessing the OS (Windows 10 build 1511). After you've finished using WINHLP32.EXE, I recommend rebooting to remove its stub from RAM.