<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Opening a file LO says it previously crashed, but fails to recover (win10 only?)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=127845#c36">Comment # 36</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Opening a file LO says it previously crashed, but fails to recover (win10 only?)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=127845">bug 127845</a> from <a class="email" href="mailto:tim@tim-passingham.co.uk" title="tim@tim-passingham.co.uk">tim@tim-passingham.co.uk</a> <pre>(In reply to vesper from <a href="show_bug.cgi?id=127845#c31">comment #31</a>) > (In reply to tim from <a href="show_bug.cgi?id=127845#c29">comment #29</a>) > > > Did you have any other OS (not .NET) updates around then? It may well be > > some form of fix being applied to several OS version. > > There were two updates applied on 9/26: the .NET one (KB4515842), and > KB4516045 which was the major OS build. As I mentioned previously, it MAY > turn out that on a system with this build LO could still function properly, > but since there are two of us reporting, the problem is larger than one > rogue user. I also note that the Bugzilla hurdle could be keeping others > from checking in... :) vesper, as a matter of interest, will Windows let you uninstall KB4516045? It does include an updated jscript.dll. I couldn't uninstall the version of the update on my system. If it doesn't let you uninstall it, you might be able to roll back to a windows restore point before the two updates. I tried and failed (for a variety of reasons of my own making), but you may be able to. If you do manage to roll back you may find that the 'update history' still includes the 2 new updates. This got me completely confused in the past. It turns out that the 'update history' in windows just lists entries from a log file, and that log is not rolled back in the restore. To see what updates are actually installed you have to do a proper check on what is installed (use cmd command systeminfo.exe).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>