Thanks Bernd, that was very helpful. I tried installing FM2019 onto another PC, a Win10 laptop and hit the same update problem. I then went back to installing it (15.0.6.956) on my desktop and followed Bernd's advice and pulled the plug on the internet. This solved the 'not installing' problem but I still hit the 'Update required' problem and it crashed my working FM document with a 15084 error message. This apparently can arise for a large number of reasons (and so is pretty useless) but does produce a dump file. I then followed the 15084 discussions which recommended the latest version (Update 8, 15.0.8.979) which I installed (I thought I had the latest version earlier but did not). Update 8 is from https://helpx.adobe.com/uk/framemaker/kb/framemaker-downloads.html It installed Ok and the 'Update required' message disappeared. But I am still left with a 15084 error when I try to produce a pdf - it fails midway through producing the pdf. So Bernd's suggestion that there is an Adobe server problem seems correct. It is not a Windows 11 problem as I originally thought. However, something must have changed with FM over the period I updated to Win11 to cause the new problem. So at the moment, I'm not sure whether my 15084 error is due to a server error or something else - though why a working fm document and a formerly working fm.exe should now cause a problem is a mystery.   ... View more

I had FM2019 (perpetual license)-Windows installed and working properly. I do not use FM very often but it is important to me. I updated from Win10 to Win11 and now FM does not work properly - it would crash. Ichecked the Updates and got the 'Update required' message. I have the latest OS updates installed. I read the answers below from Be.em and installed the updated AASIapp.exe. I've also updated the registry as suggested.  I uninstalled FM2019 so as to be able to reinstall it. I re-downloaded the Framemaker_15_x64_LREFDJ file. But now when I run the FM2019 Set-up.exe it immediately goes to the 'Update required' page with the only option to 'Quit'. So now I have nothing with no way forward. Any ideas please?   PS I am also confused by the Adobe web pages which talk about 'Internet Explorer 11' being important - I thought this browser was out of date, superceded by Windows Edge/Bing. Also there is mention of Windows 10 but not Windows 11. https://helpx.adobe.com/uk/x-productkb/global/update-operating-system-and-browser.html   ... View more

Just an update. Thanks everyone above for trying to help me. After going round in circles on the web trying to find Adobe FrameMaker support (no reply from tcssup@adobe.com), I eventually found the support I needed at techcomm@adobe.com. I got an instant response from Shivang and he guided me through various tests. Eventually he tested the 'bad' file himself and found it OK so I concluded that there was something wrong with my PC. Reluctantly I re-installed Windows 10 and then FM2019 and everything else. FM then read the files OK but refused to produce a pdf. I could not get the Adobe pdf printer to install. Again Shivang was very helpful and yesterday, a colleague of his did a remote logon to my PC and solved the problem, albeit after an hour or so of furious typing and head scratching. I think the problem was another pdf printer instance (from ABBYY FineReader) which was interfering with Adobe's efforts to install, a problem somewhat reminiscent of years ago when installing FrameMaker with other pdf generators including Adobe's very own Acrobat.   So it is all working well now. FM is a great program and Adobe Support has been really excellent (when I found it), the best I've had from a large software company. Of course, we'd all like better diagnostics when things go wrong. Such is life. ... View more

I uninstalled FM2019-8 and installed FM2019-7 (it is now 'up to date').   I could open all the documents and scroll through them with the graphics off on two of the original documents but unlike before with 2019-8, it crashed on making the book pdf. This time the crash was 'Postprocessing pdf document' after it seemed to have gone through all the documents.   The error number was 15074 which is somewhat similar to the error number from vsn 8 (15084) and suggests the same underlying problem (error number 4?)   So this seems to have been a step backwards as I could get a pdf before, albeit without many graphics. ... View more

Thanks very much for that suggestion - I was not aware of it, or had forgotten it.   So turning off the graphics via the Options tab has made scrolling the entire document work well.   I have 6 documents in this book. I then tried to generate the book pdf and it sailed through the original bad document but then failed on a later one, again with error 15084.   So I turned the graphics off on that one, and then the whole book generated the pdf but obviously without lots of graphics.   Doing the binary search is tedious on large docments especially given the scrolling with FM. Is there a short cut to highlight a range of pages to cut/copy?  At present, I scroll slowly down with the  shift-down arrow.   ... View more

Interesting. I can't really remember but I'm pretty sure it would have been through the official update mechanism. I didn't go through any devious means to get it for sure. Maybe it was a mistake on Adobe's part or they have pulled it. I certainly would like to go back to a stable version. Is that possible? ... View more

Another update on my original comment:   This document is important to me so I have spent some time trying to recover it for my purchased version of FM (i.e. FM2019).   Since I could open it in FM2020, I decided to track down the offending item using a binary search, splitting the 250 page document in two and exporting from FM2020 to FM2019 format then attempting to open the 2019 format doc in FM2019. One half would fail and the other one would succeed. I kept doing this with the failed half until I found the problem. It turned out to be a frame with some graphic (eps) inserts. I deleted this and then opened the whole document bar the insert with no problem (so far).   I then thought that the eps might be a problem (from Ghostscript) so replaced that with a pdf. I recompiled both FM2019 and 2020 formats. Both opened. I remade the FM2020 pdf file with distiller with no problem.   However, while scrolling through the FM2019 document  it would suddenly crash (near where the old problem was) and it refused to distil the whole document to pdf, again giving the 15084 internal error.   My conclusion is that FM2020 is working fine but that FM2019 is fundamentally broken. I don't know what it is but it may have something to do with inserting graphic images, surely the bread-and-butter of FM. ... View more

Thanks for your reply. I saved from FM2020 to .fm(2019) and to .mif and to .mif(7.0). None of these worked - they all gave the same internal error 15084. So yes, I did save to mif and opened in 2019.   I get the following message in the console when opening both 2020 and 7.0 mif files:   <filename>.mif (13519) Invalid opcode: DFNoteKeepWithAnchor - Skipping these characters: 0>---Done skipping.   With the 2020 mif file, the above error number changes from 13519 to 14004 but the message is otherwise the same. ... View more

Update on the above. I installed a trial version of FM2020 and read in the offending document OK with that. I saved as FM2019 format but got the same error as above when I tried to open it in FM2019. ... View more