Windows 10: Office 2010 excel.exe cannot access protected folder after Win10 updates KB5044273,...

Opened an Excel file, that I use daily. Made changes and when I tried to save it got an error from Win 10 "Protection History" stating "Protected folder access blocked". The folder is my documents folder.I allowed access to get by this. I went back back into Excel and changed anotther spreadsheet and it worked fine. Looked at protected folder and my documents folder is still protected.Any idea what might have happened? Thanks- Steve

:)

 

Updates to Windows 10 Pro seem to remove any files pinned to the recent list for access an excel in office 2010. How can I stop this

Updates to Windows 10 Pro seem to remove any files pinned to the recent list for access an excel in office 2010. How can I stop this

***Post moved by the moderator to the appropriate forum category.***

 

Excel Starter 2010

Your subject line reads "Excel Starter 2010" but in your most recent post you mention "Excel Starter 2000". Which one is it?

Regardless of this, I think your installation is damaged. If this was my machine then I would do this:

1. Download & install the free version of Macrium Reflect.
2. Use it to create an image of drive C:. In this way, you are fully protected against anything.
3. Create a Macrium Reflect rescue disk on a USB flash disk.
4. Press Windows key+I
5. Click "Update and Security"
6. Click "Recovery"
7. Click "Get started"
8. Select "Keep my files"

 

Win 10 1803 update - Thesaurus on MS office 2010 not working

Since updating Win10 Pro to 1803 (17134.285) , my Office 2010 has lost the ability to use the Thesaurus.When I click review and then Thesaurus it defaults to 'Research' and the response is " No results found. Please search again". This is the response whether I use the UK English or US English Thesaurus. I have repaired the Office Word, Excel and Outlook. I have looked online and made any other changes suggested to Language choice etc but nothing I have done works.It was fine before this Win10 update. Is it a coincidence and possibly an Office 2010 update that happened at the same time?