MS 4.7.1 Update wipes out Font Choice...
Howdy,
Yesterday afternoon I chose to install the .NET Framework 4.7.1 with Windows updates, and now when I opened Logos in the wee hours this morning, the fonts are off...and you can't make a choice as to Default Font. The graphic attached shows the empty choice slot that comes up when you try.
I right-clicked on the "Installed Windows Update" list to copy the information listed below. I had no clue how much I enjoyed my default font! :-)
Thought your technicians ought to know.
Paul L. White
Satisfied Logos User since 1.6
Microsoft .NET Framework 4.7.1 for Windows 7 and Windows Server 2008 R2 for x64 (KB4033342)
Installation date: 1/9/2018 4:03 PM
Installation status: Successful
Update type: Recommended
The Microsoft .NET Framework 4.7.1 is a highly compatible, in-place update for all the previous versions of .NET Framework 4.X. After you install this update, you may have to restart your computer.
More information: http://support.microsoft.com/kb/4033342
Help and Support: http://support.microsoft.com
Comments
-
Same issue.
Also Logos 7.12 won't accept any of my previous layouts. If I load an old layout, Logos stops working. This is the first major hiccup I've had in Logos since 1.6 twenty-something years ago.
0 -
Removed .NET update KB4055532, back to .NET 4.7.02558. Fonts and layouts working again.
0 -
Andrew BN said:
Same issue.
Also Logos 7.12 won't accept any of my previous layouts. If I load an old layout, Logos stops working. This is the first major hiccup I've had in Logos since 1.6 twenty-something years ago.
Andrew,
When you say Logos stops working, do you mean that it becomes unresponsive or does it crash? Also do you have any screenshots of the layouts you were trying to load?
Also just to clarify you are running Windows 7 SP 1, correct?
0 -
Andrew BN said:
Same issue.
Also Logos 7.12 won't accept any of my previous layouts. If I load an old layout, Logos stops working. This is the first major hiccup I've had in Logos since 1.6 twenty-something years ago.
Andrew,
I also want to clarify that you are running Logos 7.12 (7.12.0.0027) and not an earlier version. Did you ever update to 7.11 SR-2? If you are running 7.12 do you remember what version you update from?
0 -
Philana,
I can verify that the font issue is a direct result of the MS .Net update to 4.7.1.
When I opened Logos before downloading 7.12, the font was changed.
And I will echo that I also have Windows 7 SP 1.
Paul
0 -
I can verify that the issue is with Microsoft .Net update.
Yesterday, before downloading 7.12, and after updating .Net, the font was an issue. I thought maybe the download would correct that. But it didn't.
Also, I too am using Windows 7, SP1.
Paul
0 -
Philana,
Sorry for the late reply but I'm in South Africa and we're ten hours apart.
I'm running Win 7 SP1, 32 bit, fully updated to yesterday morning when it added the .NET update (KB4055532).
The crash was with a Windows message "Logos has stopped working" and an option to close or to look for a solution online. The crash log files were uploaded to Microsoft.
I was running 7.9 when the first crash happened. Logos has not automatically updated it.
I tried reinstalling 7.9 but same problem.
I eventually did a fresh full install of 7.12.0.0027 (32 bit) from the logos web site. This worked except I could not change the resource font as Paul described in his original post.
I then replaced the User, Data and Documents folders with my backups.
Worked well but still no font option and crash every time I tried one of my custom layouts.
I open Logos to a custom layout on startup. With the reinstall I initially left it at the default startup to open at the home page.
After seeing Paul's post I uninstalled the .NET update. Since then I have had no problems and I start with a custom layout and can set resource fonts.
Do you want me to upload crash logs?0 -
I think I only replaced the Data and Documents folders, not Users.
0 -
Andrew BN said:
Do you want me to upload crash logs?
Yes (see the Diagnostic Logging link in Philana's posts). They could be useful if they came from v7.12. Event Viewer Logs would also be useful - the ones that apply to Logos 7.12 (upload as files - don't paste contents here)
Dave
===Windows 11 & Android 13
0 -
-
Sorry for the double entry above. The first one didn't post on the page after submitting, so I wrote the second and it did. Now both appear.
I have to acknowledge, after reading posts from Andrew BN, that I'm using 64-bit Windows. My Layouts, personally designed, do work. Thanks.
0 -
KB4055002 has similar problem with fonts.
0 -
Pavel said:
KB4055002 has similar problem with fonts.
As per the comments on that post (search for “Windows7SP1”), it appears that the latest Microsoft update is breaking a lot of WPF programs on Windows 7 SP1.
At the moment I think all we can do is wait for Microsoft to release a fix for this issue.
0 -
Thank you, Mr. Grainger. For what it's worth, I did just do Windows Update on my Laptop, and did *not* download that particular one. And then I updated Logos, and the fonts work just fine. So your analysis is right on target, no doubt.
Um, since y'all have a connection with Microsoft, are you planning to let them know about this? If we call, they may not answer the phone! [:D]
And will there be a way for Logos to inform us of any notification they receive from Microsoft? Thanks.
Paul
0 -
Microsoft has released an official support article: https://support.microsoft.com/en-us/help/4074906/typeinitializationexception-or-fileformatexception-error-in-wpf-apps-t
Anyone having this crash on Windows 7 SP1 should follow the workarounds in that article (Method 1 is preferred).
0 -
And that's not all. Microsoft.NET Framework update KB4055002 causes problems with Canon's "My Image Garden" which is used to edit DVD labels prior to printing them onto printable DVDs and Blu-rays. After I installed that update yesterday, I was unable to load, edit or do anything with the label programs for my Canon Pixma MG7720 printer. Re-installing the Canon software after removing it and everything on the computer and registry with a "Canon" or "My Image Garden" did nothing. I was going to restore a computer backup from last month when I discovered that removing update KB4055002 solved the problem! I don't have or use Logos, but if you have problems with it, suspect that update. By the way, that update is included in Microsoft's rollup KB4055532, which you might also want to avoid. I have notified both Microsoft and Canon. The updates are easily removed, requiring a reboot afterward.
0 -
I came back to thank Mr. Grainger for his post with the Microsoft link, and to verify that following the steps he pointed to works. I now have my Times New Roman font back! :-)
You know, this little incident was a graphic reminder (pun intended) of how powerful Logos is (compared to other software). To have our choice of fonts, and so many of them...that is something we take for granted. And yet it's rare, and part of what makes Logos the premiere product that it is. I didn't realize how much I would miss it.
Blessings.
0 -
From Microsoft support: On January 18, 2018, update 4055532 was re-released ...
Has anyone been brave enough to try it?
0 -
Update KB4055532, January 18, 2018 re-release, installed. Logos seems happy with it, custom layouts and font selections working.
0
