Person who can't get it to show up: You usually don't have the correct file and folder layout if it doesn't show up at all as a port/device-type.
If you have a look in your computer at C:\Users\<youruser>\Documents\Ableton\User Library\Remote Scripts\Launchpad95 there should be a bunch of .py files and some subfolders. If you just unpacked stuff and didn't pay precise attention to the unpacked content, and copied another folder into launchpad95 or the name isn't Launchpad95, then it won't work. ie if you have C:\Users\<youruser>\Documents\Ableton\User Library\Remote Scripts\Launchpad95\LaunchPad95 then you are not yet used to the wonders of Zip and Unzipping files and folders yet.
I just discovered LaunchPad95, on my first actual day with a used Novation LaunchPad MK1 that I obtained on reverb.com for not much. The utility of this thing is truly fantastic.
One confusing thing for me as a new Ableton live user, when a track is armed in the session view there is a lighter or darker red way of tracks being armed. If no tracks are armed and I go to the User1-instrument-mode and use the left/right Page buttons to change active tracks (so great!) it arms the active track for me, if and only if no other track has an arm on it. What I would like is for my livesets/session-state not to have these "brighter red" armed states on some tracks, because that messes up the ability to actually use the push-like workflow where I could select a track, and then record a clip into a row on one of my tracks.
Screenshot
Anyone who has spent more than one day with Ableton Live will probably know what the deal is with this bright red and dark red stuff.
If the scripts could always ensure that all tracks are NOT armed and then the track I select is ALWAYS armed, I would find that incredibly useful.
I actually know a little python, I could try a fork and make my own mods to this awesome thing.