Recently I have been rolling out Office 365 Click to Run to a number of pilot users and was having a lot of success until I come across two Windows 8 Machines. Strangely a Windows 8.1 Machine didnt experience the same issue and after a lot of reading of blogs and TechNet, there seems to be no real fix from Microsoft.
The error I was getting is;
Microsoft did release a “Fix IT” for this issue but sadly its doesnt resolve the issue at all. You can find the fix it tool at the following url http://support.microsoft.com/kb/2809219
So moving on too others that have experienced this issue, there was a lot disgruntled technical professionals complaining about the Fix IT tool and Microsoft. Some IT Professionals managed to fix the issue by doing the following;
- Running the Microsoft Fix it
- Uninstall Office traces by Fix it or Control Panel.
- Open Run Command Box
- Type Temp and Delete Contents in Folder
- Repeat process for %Temp% and Prefetch Folders
- Please go to back to Windows 8 Start Screen ( By Pressing Windows key on your keyboard )
- Type run on Start Screen ( Press run on start screen and windows will bring it for you )
- After Typing run on Start Screen you`ll got a run icon on your screen, please click on that run icon
- OK so now you got Run window at the left bottom of your screen, now in that window you need to type “REGEDIT“.
- Now in this registry editor you need to delete two files.
- HKEY_CURRENT_– USER\Software\Microsoft\Office\15.0
- OK now please close it and try for Installation.
In my case I tried the above actions and I was still having the same issues, so in the end I found the below worked as a workaround.
- Copy the Contents of the Office 365 Click to Run Deployment from the Network Share
- Copy to the Local Machine
- Reconfigure the UNC Paths in the Configuration.xml and Install.bat I was using to deploy to Office 365 Click to Run.
- Run the .bat as an Administrator
This process completed in the install successfully but its not workable if you have move than 10 machines on Windows 8, hopefully there will be a true fix for this issue but this is yet to be confirmed by Microsoft.