Times New Roman font will not print on HP Officejet Pro 8610

[TomComputer]

Thanks so much for the detailed reply.  I did, indeed, find the "print to file" options on both Microsoft Word and Microsoft Excel.  Microsoft Word created an empty file without error.  Microsoft Excel generated the same error as when I tried to send the file to the HP Officejet Pro 8610 printer.

So the hunt for the problem continues, but I think it will continue in places like the registry.

I had already in the process deleted ALL printers (with a re-boot after each printer deletion) and started fresh - several times.  I think I won't revisit that right away.

Stay tuned for another reply.

If anyone has any other tips, given this last piece of data, any response is GREATLY appreciated.

Tom

[TomComputer]

To Those Following this Thread:

    I have a very interesting data point.  I changed user accounts, from my priviledged account to the restricted account I set up for my granddaughter.

    I was able to get Times New Roman type in Microsoft Excel to print on my HP Officejet Pro 8610 just by switching to another user account on the same computer.

    Well, that should really narrow things down.

     Any suggestions as to what is wrong with the account I used to install the software?

Once again, any and all ideas welcome.

Respectfully submitted,

Tom 

[dansdaduk]

This is starting to get way out of my area of expertise.

Corrupt Wndows user profile?

Corrupt font cache?

[NotYetUsedName]

I have the same issue, dated back to April 2015 when I installed the new printer (HP deskjet 4515). Initially I had Windows 7, then upgraded to Windows 10, hoping to get the problem resolved. It did, to some extent: I can print from my admin account, but not from others. Converting "bad" accounts to administrator does not help. That is, in my case the problem also is account-specific; I suspect restricted rights for some file(s) or e.g. temporary directory that might be used by driver to process fonts.

Besides, while analysing the issue for the first time, I discovered some property (shown by standard Font viewer of Windows 7) that I believed was distinctive between 'good' and 'bad' fonts.  Alas, long and detailed message I was typing to describe that was lost due to power failure, so I gave up by the time. Now trying again....

Just my 2 cents...

[TomComputer]

I didn't think I would get any more replies after this long of a time.  The problem has gotten worse, not better, during all of my efforts.  Currently, the only way I can get things to print is to "print" them to .pdf using Primo, then opening the .pdf file and printing it.

I have built new accounts, reverted to old fonts from backup, replaced all the fonts from a working computer, re-installed the printer software a variety of ways, removed lots of software, used numerous cleanup utilities.

My next effort, when I get enough time, it to purchase an SSD and Windows 10, do a completely clean install, and only re-install the absolute essentials.

Sigh..

Tom

[NotYetUsedName · Accepted solution]

Finally I seem to have problem solved for me.

First, some observations, just for the record:

- in affected user accounts, "Print Test Page" fails from printer properties, but HP Printer & Scanner Doctor says everything is OK, and prints test page without any problem

- newly created user accouts work fine

At the end I recognized that my user accounts have non-default TEMP variable: I redirect it to HDD to avoid drilling main SSD disk by temporary files. Setting permissions on that directory for user Everyone  to "Full control" (not just "Modify"!) does the job: printer starts to print fine. Phew!

Hope this will help to you, Tom, and others getting this problem!

[TomComputer]

IT WORKS!!!!!   THAT FIXED IT!!!!!    THANK YOU, THANK YOU, THANK YOU.

I have been fighting with my computer since I purchased the new printer in July.

I have spent some time each day trying new things.

I do the same thing as the person providing the solution.  I have set my environment variables to place things on my 😧 drive in an attempt to distribute disk load across two drives on different controllers.  I have different temp and tmp variables for all occasions.

So, after changing permissions on all of my temp and tmp directories on all of my disks, and adding user "Everyone" and giving Everyone full control ... the problem went away.  ...  Along with a few other problems.

Thank you all so much for hanging in there with me.

Gratefully,

Tom