Today, I installed Windows 10 Professional (x64) Version 1709 (build 16299.19).
When I started FrameMaker, the program hangs when it is loading Fonts.
I have uninstalled and reinstalled with the same results.
I had a startup problem many years ago that was due to corrupt data in the users/appdata area. The kind of thing that a reinstall would not fix. I don't know if this is the exact same problem, but it might be worth a try, and perhaps it might give you some additional ideas to try.
Here is an update!
I uninstalled the Windows 10 Fall Creator Update and FrameMaker 2017 works normally!
So it looks like FrameMaker itself does not work with Windows 10 Fall Creator Update.
Thanks for the information!
I did uninstall FrameMaker and reinstall but it does not startup!
Looks like we're waiting on Microsoft to fix this issue.
Well, since rolling it back seems to have solved the OP's issue, there must be something in that Win10 1709 build that FM2017 doesn't like. I'm just in the process of upgrading a test machine to see if it behaves after 1709 is installed. It's already got FM2017 patch 2 installed.
Jeff, If everything goes well with your upgrade, I will try once more.
Nuts, the upgrade to 1709 keeps erroring out - no test of that coming soon.
Ok, was able to get my test machine updated to 1709 16299.125 build & FM2017 patch 2 starts up fine. Just applying patch 3 to it right now.
I have just updated to Windows 10 1709 as well. And both FM 2015 and 2017 start and work just fine. So, maybe it's related to something else on your machine? Like e.g. the virus scanner also updated on the same day and decided to not like FrameMaker anymore?
I'll ping the support team to this discussion and ask them to get into contact with you.
Would like to let you guys know what caused our crashing. We found out that after Win10 1709 the company took in use OneDrive Files on Demand and that caused FrameMaker to crash constantly, also after we found that we have found that there have been similar issues with illustrator, photoshop etc. After untapping the OneDriver Files on Demand setting and letting the computer sync for a moment, Framemaker started working normally again.
Hope someone finds this useful.