Others have asked this question w/o any real answers. Time to get a real answer...
[I'm trying to open either a Word or Excel file on Windows Phone 10 Mobile but it says "Sign in to edit and save changes to this file".
I do not want to "sign in", (I don't know what I'm signing in to for a start, it doesn't tell you), I do not want my document on the cloud, I just want to edit and view it on my phone. And, when I try to sign in, it doesn't work anyway.
What good is MS Office when it does not allow file edits or updates, just read only? How stupid is that?
How do I do this without "signing in"?]
BTW, I am having this problem on my Windows 10 phone as we speak. FIRST OFF why should anyone have to sign in in order to be able to make updates to any Word or Excel files? I get so sick and tired of Microsoft screwing up my phone with all their updates.
I have complained about this very same problem before. The problem comes and goes away. And how is anyone supposed to sign in if (A) they do not happen to have a DATA plan with their carrier and/or (B) they are not someplace with a WiFi connection. Even
if you wanted to sign in and knew what the process was for doing so you would not be able to do it. A month ago my Office apps were able to do updates to .docx, .txt, and .xlsx files just fine... even if one had to allow the updates as part of "auto save"
which is also BS. There should be a manual save option as well. And any time I have tried to make changes to older .doc or .xls files the Win 10 Mobile OS seems to need the dang connection to convert the files to another format first... just to keep them
happy.
Anyway, WHY is this happening and WHAT must we do to fix the problem every time it starts happening again???
BTW... after posting this question I decided to shut off/reboot my phone. After it started back up again I went in to see if I could edit any MS Office files or not. Lo and behold, when I opened the first .docx file I got some strange message "You've been
upgraded..." now you can edit your file, or something to that effect. WTF? Then it started working OK on any .docx or .xlsx files.
Just in case nobody at MS ventures a real answer as to why this is happening, at least there is one clue that might help folks fix the problem... until it happens again anyway... which it will. When it comes to MS just about anything can happen now days.