During installation you will be asked for your version of MiKTeX since MiKTeX 2.4 requires bug fixes, and MiKTeX 2.5 beta 7 or earlier requires different bug fixes. If you have the latest version of MiKTeX, and at least 2.5, just select item 4 and no bug fixes are done. Otherwise, in either case the bug fix involves forcing dvips to also look through the next higher folder for figures. It just must be done in different ways in the two versions. The fix should be of little further consequence, and is undone on uninstall.
During testing, running latex on the document has nothing to do with LaTeX2HTML, just with your MiKTeX installation, except for the presence of html.sty. The installation script should have copied html.sty, with or without your assistance, into a suitable location, and refreshed MiKTeX to be aware of the file. But Murphy rules. In case of problems, you can search for html.sty to see whether it is in a suitable location and refresh the FNDP/File name data base using the MiKTeX settings or options program available from the Windows Start menu. (Different versions of MiKTeX use different names for this, do not ask me why.)
The small MiKTeX installations do not have the epsf.sty package installed, and installing it from a random depository is not always reliable. Complain, but not to me. However, to just conduct the test of your LaTeX2HTML installation, it should be enough to simply copy the epsf.sty into the check subfolder with the index.tex file. A copy of the file is here; right-click and select "Save Link/Target as." Then save epsf.sty in the subfolder check of folder l2hsup on the C:\ drive. During the makel2h command, the package manager may still want to install epsf.sty; just abort that and you should be OK.
For problems with makel2h; is perl.exe in the bin subfolder of the perl folder on the C: drive? Is ghostscript's gswin32c.exe in a subfolder of the gs folder on the C: drive? If you have ghostscript or Perl installed elsewhere, either reinstall them or follow the manual configuration procedure on the web page.
Otherwise this installation is not supposed to fail unless you do something like logging in without administrative privileges or your disk is full/broke. If you cannot figure it out, contact me at l2h@dommelen.net with info what is wrong and what error messages have shown up. Make sure to note that you used the MiKTeX script.
Press the "Back" button on your browser to return to the general instructions.