Since the update on August 29, the updater finishes with a message log4cxx: no appender could be found for logger. MikTeX remains functional, but the caching of fonts that usually happens at the end of the update process seems to be skipped.
This happens on four different machines, running both Windows 10 and 7. I installed months ago, from the Miktex web site. At the end of the update process, the following appears:
Copying C:\Users\mrenardy\AppData\Local\MiKTeX\2.9\pdftex\config\pdftex_dl14.map
to C:\Users\mrenardy\AppData\Local\MiKTeX\2.9\pdftex\config\pdftex.map...
log4cxx: No appender could be found for logger (mkfntmap).
log4cxx: Please initialize the log4cxx system properly.
Creating language.dat, language.dat.lua and language.def...
I have Comodo Firewall on all machines.
One has Comodo AV, the others have Symantec.
I have not filed a bug report, but have emailed this to Christian Schenk.
I know from surfing the web that others have seen the same message. Miktex so far has functioned normally for me, notwithstanding the error message. I note that the hundreds of lines that say fonts are being cached or that the existing cache is valid no longer appear during the update process. Being just a dumb user, I cannot tell whether the fonts are not being cached or just no message created.
log4cxx
about initializing it properly. (I suspect this has to do with the new/planned log file feature announced on the MikTeX page.) But I have yet to experience actual problems related to this. – moewe Sep 12 '15 at 9:33