Store Desktop Office

18

FWIW, and this may be more appropriate on reddit than here, I’ve come across one deficiency of the Store version of desktop Office.

Using File Explorer, select a text file (.TXT extension). Usually it’s associated with Notepad. If you’ve installed a more powerful text editor, like Notepad++, .TXT files would be associated with that. However, if you wanted to open the .TXT file in Word, it’s not so easy.

Store desktop Word doesn’t appear in the default Open With submenu of the pop-up/right-click menu. Nor can a usable Word .EXE be found using Look for another app on this PC.

Comments (19)

19 responses to “Store Desktop Office”

  1. Paul Thurrott

    Yeah, this is an issue with a number of things. Add-ins, I think. It's amazing that something like this can be so half-assed.

  2. skane2600

    Perhaps it would be better just to call it "The Store version of Office". Or is there another version of Office in the Store such that an additional qualifier is needed?

    • hrlngrv

      In reply to skane2600:

      Yup, there's Mobile/UWP Office also in the MSFT Store. Mobile Store Office and Immobile Store Office?

      I suppose MSFT still bothers with Mobile Office for the legions of remaining Windows phone users running Windows 10 Mobile and the hordes of Xbox users wanting to run Office on game consoles. There are virtually no small tablets running Windows 10 Mobile, and all larger tablets + all PCs running full Windows 10 can run desktop Office and require Office 365 licenses to run Mobile Office.

      tl;dr -- there may be hundreds of people using Mobile/UWP Office from the MSFT Store.

  3. StudBen

    I didn't realize this was an issue, given I never use Windows Store apps, I figured their must be a way from the registry I found this from 2016 https://superuser.com/questions/1071323/cannot-set-a-windows-10-store-app-as-default-program-to-open-a-file assuming it should still work. Basically you have to find office in the RegisteredApplications to identify a few things then make the file association in the registry for the .txt file. Honestly though given the registry has a list of the RegisteredApplications you would think in selecting the default app Microsoft would put in a means to enumerate ALL registered Windows Store applications. I mean to me that sounds like a simple solution.

    • hrlngrv

      In reply to StudBen:

      This is not going to be simple for the home users many MSFT fans speculate would be well served by MSFT Store software. FWLIW, excel and winword on command lines still launch Excel and Word, so a 1-line batch file is all it takes. But if that's all it takes, even that shouldn't be necessary. Packaged desktop software through the Store ain't ready for prime time.

  4. gregsedwards

    I haven't played with the store versions of the Office apps yet, but my hunch would be that's because instead of being stored in the c:Program Files folder(s) like other Win32 apps, these apps are actually stored under the c:ProgramData folder. They're also probably not registered like their non-store counterparts. Remember that store apps are "containerized" to prevent their ability to interact with the system as a security measure. It turns out there are a lot of challenges to changing paradigms. I'd imagine there's still a way to do this (after all, other store apps do show up in the Open With menu). Guessing it'll be fixed in a future release.

    • hrlngrv

      In reply to gregsedwards:

      All removable Store apps are stored under C:\Program Files\WindowsApps. Bundled UWP apps that can't be removed are stored under C:\Windows\SystemApps.

      Whether they're registered or not I can't tell. I had had standard Office 365 installed before. I removed that in order to install the Store version. It's possible the removal didn't clear out registry keys. OTOH, typing winword or excel at a command prompt or in the Run dialog starts Word or Excel, respectively, so the new installed locations are in the registry.

      As for containerized, VBA macros in Store Excel can automate the other Store Office apps, and outside scripting facilities like VBScript running through Windows Script Host can automate Store Office apps. Further, VBA in the Store Office apps can make Windows API calls (calls which require Declare statements and name the system DLL in which to find the given function). VBA macros can also modify and delete any files for which the user account has read-write permission. Not clear what the containers are doing. AFA I can tell, the only security provided by Store Office is that C:\Program Files\WindowsApps by default doesn't allow any user account or even Administrator accounts to browse inside it or modify any files inside it.

      As for Store apps which show up in Open With menus, they're usually ones with file associations. Thus I have Code Writer which shows up in Open With for .TXT, .LOG, .INI files but not for Unicode text or exotica like _vimrc.

  5. Lauren Glenn

    I still can't get the store office to install without it going off to a website for the install. The same website where I do the desktop install..... makes no sense. Someone told me to uninstall the desktop one and then it gives you the store one. OK, but the store one is supposedly only 32bit? And it offers nothing new over the desktop one which is 64-bit....... why am I doing this?

Leave a Reply