Apache OpenOffice (AOO) Bugzilla – Issue 126482
files open in read only
Last modified: 2015-08-21 23:43:48 UTC
went to windows 10 now all files open in read only
There is already an issue with problems that maybe results from an upgrade to Windows 10. So, I'm closing this one. *** This issue has been marked as a duplicate of issue 126464 ***
** NOTE ** This is not necessarily the only way that a Windows 10 Upgrade may interfere with use of OpenOffice (and other applications). There are two prospective remedies when documents suddenly become read-only after upgrade to Windows 10. These cases have nothing to do with OpenOffice directly, but appear to be side-effects of the update in the case of Windows 10 Home. We want you to be a successful user and are interested in providing the resolution for those who notice this problem in conjunction with their use of Apache OpenOffice. TRY THIS FIRST This is the simplest case. 1. In Windows 10, go into "Settings" a. At the end of the desktop task bar, next to the Window icon, enter "Settings" into the search entry field. (If you do not have a search entry field in the task bar, click the round icon next to the Window icon, then use the field at the bottom of the pane that pops open.) b. The top search result should be "Settings" with a gear icon. c. Click Enter 2. In the Settings Window, click Accounts. 3. Under your account or anywhere else, see if it says your account needs to be authenticated. If so, click on the option to do that now and follow the instructions. 4. See if your previously-writable files are now writable. 5. If that doesn't work, Restart your system, and see if that makes the difference. Please report if that succeeds or fails by replying to this comment.
(In reply to Marcus from comment #1) > There is already an issue with problems that maybe results from an upgrade > to Windows 10. So, I'm closing this one. > > *** This issue has been marked as a duplicate of issue 126464 *** I am re-opening this issue since it is specifically about the read-only case. The circumstances described for issue 126464 do not appear to be the same. (We need to find out what the separate cases are because the repair may be different.)