Upgrade from v1909 to v2004 - - Questions on Existing Software

Win10-Pro, v1909, Build 18363

Found this:

Beginning with Windows 10, version 2004, all new Windows 10 systems will be required to use 64-bit builds and Microsoft will no longer release 32-bit builds for OEM distribution. This does not impact 32-bit customer systems that are manufactured with earlier versions of Windows 10; Microsoft remains committed to providing feature and security updates on these devices, including continued 32-bit media availability in non-OEM channels to support various upgrade installation ....

Re: The above.
I have a lot of old 32 bit software and a number of VB6 programs I've written.
I believe the old VB6 programs will run under a 64 bit OS if recompiled since I have source.
My question relates to all my other old 32 bit software (e.g Office 97), that I did not write.
---------------
Questions
-----------------
1) Any pluses / minuses from using v2004 ISO versus using Windows upgrade (if one can do this through upgrade) to v2004?
2) Will the v2004 install AUTOMATICALLY ensure (be seamless) the old software will run (e.g. move needed files from System32 to WOW if needed, --or-- set the old software so it runs in compatability mode without me having to reinstall or do a bunch of tweaks?
3) Microsoft already killed the HLP files associated with some of this software, any suggestions on best / easiest way to upgrade these HLP files to CHM or PDF, and hopefully get them to run from the old software instead as a separate file?

dw85745 said:

Win10-Pro, v1909, Build 18363....

1) Any pluses / minuses from using v2004 ISO versus using Windows upgrade (if one can do this through upgrade) to v2004?
2) Will the v2004 install AUTOMATICALLY ensure (be seamless) the old software will run (e.g. move needed files from System32 to WOW if needed, --or-- set the old software so it runs in compatability mode without me having to reinstall or do a bunch of tweaks?

Macboatmaster is quite correct, Microsoft have decided that OEMs will no longer be supplied with a 32-bit version of W10 to install on their new machines starting with version 2004. That does not mean MS won't update existing 32-bit machines to 2004, or that the MCT will no longer make 32-bit install media, it just means you will no longer see any new machines supplied with 32-bit Windows 10. That has no bearing on your questions.

All 32-bit software that was installed and running in 1909 will still be installed and running after upgrading to 2004. There is nothing that needs 'moving'.

3) Microsoft already killed the HLP files associated with some of this software, any suggestions on best / easiest way to upgrade these HLP files to CHM or PDF, and hopefully get them to run from the old software instead as a separate file?

the .HLP file format was a security risk, so MS replaced it with the .chm format.

Microsoft: Beware of .HLP files | ZDNet

HLP and CHM are functionally similar, in fact the project source files from which they are compiled are nearly identical. But you cannot directly convert a .hlp to a .chm. To make a .chm you need to have access to the project files so you can recompile. It is possible, with a lot of effort, to decompile a .hlp file and generate the source files. Then you can compile a .chm equivalent. However that doesn't help much, as the .exe is hard-coded to open its .hlp when you hit F1. At best you will have a standalone .chm file.

A simpler solution, if you are prepared to take the security risks, is to replace Winhlp32.exe with one from an earlier version of Windows that will allow you to continue using .hlp files. See this post:

Can't read older *.hlp files on Windows-10 - post #46

See also post #57 later on in that thread.

Thanks all for responding. Lot good information in each post.

------------------------
Macboatmaster
-------------------------
Picked up on the OEM issue. Since I do my own builds, the issue for me ->>

Am I going to be able to get a 32bit copy of Windows (whatever version) in the future for a new build, or is M$ only going to be supplying 64 bit Windows?

I am currently using 64 bit processors (4). While 64bit processors allow one to reference a larger address space -- and the old 32 bit software currently runs fine under Windows and these 64 bit processor -- my concern is that M$ may do something with Windows which will deprecate that 32 bit software. So far they have been pretty good at living up to their word regarding compatability (HLP files is an example of one exception), but it appears M$ is coming full circle back to the old main frame days where they will control everything and users are just renters of their software. While that may be great for M$, for those of us who want to write/use their own software it has major implications especially if their language (VB6 for example) is not supported (no 64 bit compiler).

---------------
Bree / Dalchina
----------------
Have tried various HLP file workarounds since upgrading to Win-10 in January 2020. Windows keeps breaking those workarounds. Thought I'd once and for all try and convert, but so any far conversion seems to be a major effort rather than simple reference to HLP file of interest with a button push and new file CHM/PDF generated. Thanks for the link and see if any different than what I've tried.

Betron: I get -- VB6 for example -- is licensed to M$. The problem, like with Windows is that it is the stumbling block for all the software created using that particular program (VB6 in this case). I guess one can argue that the user should have known that from the get go. However, this industry (PC) has changed from the 1980 wild west of software days to where we are today. For example I can't tell you how many databases I learned that were "here today gone tomorrow". That was part of Microsofts selling point for using their software (VB6, Office, etc.). So a lot of commitments were make, lot of manhours expended, and then new M$ management decides to upend the apple cart. Personally at an age that I just want the things that I use to keep functioning. Yes, I know that is my problem / issue. Sorry for the rant, just believe I see where M$ is going and potential issues involved.

dw85745 said:

Have tried various HLP file workarounds since upgrading to Win-10 in January 2020. Windows keeps breaking those workarounds.....

Yes, if you just replace Winhlp32.exe with an older one then an upgrade or SFC /ScanNow will 'repair' the 'damage' you have done.

The way to avoid that is described in Can't read older *.hlp files on Windows-10 - post #57