This is really cool, but also pretty complex. At first, I thought maybe it was Steve's system being too outdated. After all, while the rest of us have icons on our desktop, Steve's apparently has knobs. Very old fashioned.
I suppose you could do a _FILEEXISTS() routine for the font files, but for really good error checking, a compare with the font files used in development would be needed, paired with an alert to the user the font file, in the user's system, is not compliant. It gets a bit iffy to do an overwrite, and I believe in Windows, fonts involve the Registry. Again, this could get quite complicated, but a simple error trap, to inform the user of what to do when Steve's situation comes up, well that would be fairly easy to include.
Nice work on the file recover from the .net site! It's like an Easter Egg hunt, over there.
Pete