Garbled Event Log Entry

[Dave-H]

Just updated to version 1903, and seeing this on every boot in the Windows Event Log!
What's all that about?!

[UCyborg]

Does FullEventLogView show them the same way?

[Dave-H]

Thanks, sorry for the delay in replying.
The event log message looks exactly the same in FullEventLogView.
That message has been in Windows 10 on every boot on my system for several versions now, but it has never looked like that before!
Some further investigation seems to indicate that the garbled text effect is something to do with something called "Pseudo-Localization", and has been seen before in many places on Windows 10 Insider builds.
It surely shouldn't be in a release version though!

Edited June 11, 2019 by Dave-H
Amendment

[UCyborg]

Wow! Might not be related, but:

 

[Dave-H]

That looks a lot more drastic a problem than I'm seeing!
So far that one event log message is the only place I've seen that garbled font.
The article I found is here.
I guess what's happened is that MS forgot to change the font back from the development font for that particular message, strange though that would seem!
I'm using UK English on my system, I guess from what the article says that it would come good if I changed the system to US English.
I don't actually want to do that of course, so I guess I'll just put up with it unless I find that it appears in loads of other places as well, and hope they fix it with a future update.

 

[UCyborg]

I see, that other problem is not related.

Here's a working link to Raymond Chen's blog post about this:

https://web.archive.org/web/20190218192651/https://blogs.msdn.microsoft.com/oldnewthing/20120726-00/?p=7043

Probably best to wait until some more updates have already been pushed.

[Dave-H]

Thanks!
Well it wasn't fixed with this week's update, and it certainly wouldn't surprise me at all if it isn't actually now fixed until version 1909 later in the year!

[xpclient]

Well they broke the Event Viewer: https://www.zdnet.com/article/windows-latest-patches-crash-event-viewer-but-microsoft-has-temporary-fix/ Maybe they corrupted the Event log too.