Calc would not open ODS files after Win 10 update

I know this kind of question has been around for some time now, but all answers/solutions I’ve read about didn’t help.
(I’ve tried to install/reinstall all LO versions starting from 4 and to 5.1, tried to reset user profile, nothing works).
Here is how this happened to me:
I use the latest LO 5.1.0.3 installed on Hp DV6-7014 Notebook PC. I’ve been using Win 10 for about couple months now after upgrade.
Two days ago my Win 10 installed the following updates:

  1. Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3140743)
  2. Update for Windows 10 Version 1511 for x64-based Systems (KB3139907)

After that I can not open any ODS file. Calc just hangs and all I see is grey empty LO window. When I try to close it, Win opens dialog box saying it is trying to find a solution and then it closes, but not the LO window. I even can not remove it with Task Manager - have to reboot to get rid of it. (though it may finally go away after several minutes)
I still can open XLS/XLSX files with LO.
I can also create new file and save it as ODS, but after closing the file I can not open it again.
Moreover, I’ve discovered, that I can open ODS files after I boot Win 10 in Safe Mode.
So my guess is some (most likely Microsoft) service is preventing LO from opening ODS files.
The only thing I don’t know is how to track the service which causes LO to freeze.

As far as ODT and ODG files - no problem there.
Whoever have faced with this kind of trouble please help! Any advice will be greatly appreciated.

OK, I think I’ve figured it out. There was similar question several years ago:

And also there is related bug , filed for LO 3.4.3, which apparently has not been fixed until today:

https://bugs.documentfoundation.org/show_bug.cgi?id=42673&redirected_from=fdo

In my situation I have network printer attached to my other computer at home, which I set as default about a week ago. The printer was not available when I boot my notebook, while the computer it is attached to, was on.
I fixed the problem by switching default printer to “Microsoft Print to PDF”.

Hope this will be helpful to anyone who will face similar problem.