As I understand it, it should perform the same secedit-based fix that is applicable to 2013. It might work, it might not. But its an easy test/fix. The FixIt itself (I already ran it to check) does not specify a specific version of Office.
To perform a tradition Office "repair", you would need to do that via *Programs and Features* control panel. Perform a *change *of the install, and then choose to *repair *it. If you want to go the route of preventing product re-registrations: - reg add HKCU\Software\Microsoft\Office\<build.#>\Word\Options /v NoReReg /t REG_DWORD /d 1 - reg add HKCU\Software\Microsoft\Office\<build.#>\Excel\Options /v NoReReg /t REG_DWORD /d 1 - reg add HKCU\Software\Microsoft\Office\<build.#>\Access\Options /v NoReReg /t REG_DWORD /d 1 - reg add HKCU\Software\Microsoft\Office\<build.#>\Powerpoint\Options /v NoReReg /t REG_DWORD /d 1 - reg add HKCU\Software\Microsoft\Office\<build.#>\Outlook\Options /v NoReReg /t REG_DWORD /d 1 IIRC, the build number is 15.0 for Office 2013. -- Espi On Mon, Sep 21, 2015 at 12:39 PM, J- P <[email protected]> wrote: > Does this apply to 2013, the article only says 2010 ? > > > > > ------------------------------ > From: [email protected] > Date: Mon, 21 Sep 2015 12:12:34 -0700 > Subject: Re: [NTSysADM] Multiple office installs > To: [email protected] > > Have you tried fixing the install? > > https://support.microsoft.com/en-us/kb/2528748 > > > -- > Espi > > > On Mon, Sep 21, 2015 at 11:41 AM, J- P <[email protected]> wrote: > > Hi all, > > The site has a mix of outlook 2010, access runtime 2010, and now office > 2013 > > Due to a custom access fe they need to stay on outlook 2010, however now > whenever word is launched you get the "please wait while office is > configured..." likewise when the Access runtime is launched the same occurs. > > I recall if you had multiple versions of WORD there is a reg hack to > prevent this from occurring, > (HKCU\Software\Microsoft\Office\14.0\Word\Options /v NoReReg /t REG_DWORD > /d 1) > > But these pc's do not have multiple word version, does anyone if these > hacks can be applied to Access runtime? > > Or provide another work around? > > tia > > > >
