Well, that 's sort of the problem. There are no error messages, anywhere... The printer has no errors displayed on the control panel of the printer, and no errors are displayed when printing inside of Windows 10 (regardless of whatever 'app' I try), such as from MS Word 2013). It is as if both Windows and MS Word 'believes' the document has printed properly since no errors are (for lack of a better term) 'bounced back' to the computer from the printer.
Graphics of any form WILL print properly, whether from an image editor application or from a document where a graphic image is placed in a MS Word document. Alsmost as if there is a setting someplace that allows "graphics only" and no text of any form.
The last time I saw anything like this was when I was running Windows 7 and a newer version of print driver software was required, and that 'driver update' dealt with that problem back then. But the drivers currenty installed are directly from Canon and are the latest version available. Of note: the installation of drivers and software has been done more than once, and even though I've done a full un-install when troubleshooting this (and a reboot after each uninstall attempt), and even the subsequent removal of all folders related to Canon are removed, this is the same indication everytime: No text - graphics only...
Potentially 'forcing' the PC to upgrade to Windows 10 ver. 20H2 might address this, but I have heard of some 'potential issues' with this newest release of Windows 10 so I'm maybe a bit hesitant.
But then since I'm allowed up to - what it is it? Up to like 10 days to 'rollback' to the previous version..? - potentially I should just give this a try and hope for the best. The update to Windows 10 ver 2004 was seemingly what caused this, but the 'allotted time' to accomplish a rollback has now expired, so I'm 'trapped' where I am unless I try this 20H2 update, I suppose....
On another note: I am one of those 'lucky' ones who seem to recurrenty have 'Windows 10 update issues' with several of the past 'feature and version' updates, so ostenstibly this was simply a failure related to this last update.
Just as 'per norm', I guess...
