Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, October 19, 2015 8:21 PM
I have Office 2016-32 running on Windows 10-64 Professional. When I open Windows Explorer and select any Office file (Word, Excel, etc), I get an error message, saying that the application tries to recreate the information.The Application- and System Event-log show always error messages:
..............................................................................................................................
System Event Error:
Distributed COM event 10010;
Server "{84F66100-FF7C-4FB4-B0C0-02CD7FB668FE}" could not be registered by DCOM within the timelimit.
Application Event Error:
Application Error 1000
Name der fehlerhaften Anwendung: WINWORD.EXE, Version: 16.0.4266.1003, Zeitstempel: 0x55ceb2b2
Name des fehlerhaften Moduls: mso30win32client.dll, Version: 16.0.4266.1003, Zeitstempel: 0x55ceaf45
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00097033
ID des fehlerhaften Prozesses: 0x25dc
Startzeit der fehlerhaften Anwendung: 0x01d10aa4db6d4073
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Microsoft Office\Root\Office16\WINWORD.EXE
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso30win32client.dll
Berichtskennung: 618c3fac-6472-4427-a6ac-0dc762bb7094
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
..........................................................................................................
Any idea how to solve this issue?
Joachim
Joachim Claus
All replies (12)
Tuesday, October 27, 2015 11:03 AM ✅Answered
I like to give an update on this issue.
Its source is based on an uncomplete Window 10 installer process. During the Office 2016 public test phase, I had the 64-bit test version installed. When I bougght the final version, the installation process recommended to install the 32-bit version for compatibility reasons. However the 32-bit version could not be installed prior to an uninstallation of the 64-bit version. So I uninstalled the test version of Office 2016-64, and then I installed the final version of Office 2016-32bit. All went fine with the installation, except the error I reported in this thread.
The problem was, that the uninstallation process left a number of registry entries present under HKCR\CLSID and the installation process installed the previewers under HKCR\Wow6432Node\CLSID with faulty entries of the keys "DisplayName" for the CLSID's of Word, Excel, PowerPoint and Visio.
I have solved the problem with the help of my laptop. I compared the registry entries of my laptop with those of my workstation (which had the problems). The entries for Microsoft Office preview handlers were fundamentally different, even when both computers run the 32-bit Office version on a 64-bit Windows 10 system.
Laptop
There are no registry entries for Microsoft Office previews under the key HKCR\CLSID. They are registered under the key HKCR\Wow6432Node\CLSID.
Workstation
There are registry entries of Microsoft Office Previews under the key HKCR\CLSID. However the entries have no values registered for the keys InprocHandler32 and for LocalServer32.
Under HKCR\Wow6432Node\CLSID I find entries for Microsoft Office previews, however with a totally wrong key entry for DisplayName: "@C:\Program Files (x86)\Microsoft Office\Root\VFS\ProgramFilesCommonX86\Microsoft Shared\Office16\oregres.dll,-487"
I made a manual registry correction as follows:
1. I deleted the entries of Microsoft Office previews for Word, Excel, PowerPoint, and Viseo under HKCR\CLSID.
2. I corrected the entries of Microsoft Office previews under HKCR\Wow6432Node\CLSID with correct DisplayName settings, e.g. "Microsoft Word previewer" for Word, etc.
Having done these manual corrections, Windows Explorer displays correct previews in the preview pane, and no error is reported.
Joachim
Joachim Claus
Tuesday, October 20, 2015 2:19 AM
Please post your question in Office 2016 forums L https://social.technet.microsoft.com/Forums/en-US/home?forum=Office2016setupdeploy
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Thursday, October 22, 2015 6:33 AM
Hi,
Besides that, please also refer to this thread to see if it's helpful to you:
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Thursday, October 22, 2015 12:28 PM
I followed the above links and tried to understand and perform the proposed measures. However, so far no success.
Joachim
Joachim Claus
Tuesday, October 27, 2015 9:36 AM
JC
Any other version of Office in your computer?
You may consider ask this question in Office forum.
Tuesday, October 27, 2015 9:43 AM
I followed the above links and tried to understand and perform the proposed measures. However, so far no success.
Joachim
Joachim Claus
After change its permission, it still give the same error message?
Run SFC /scannow command to scan and fix the corrupted system file:
Use the System File Checker tool to repair missing or corrupted system files
https://support.microsoft.com/en-us/kb/929833
After that, repair your office installation to have a try.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Thursday, September 29, 2016 11:45 AM
I have been facing this issue for the last few months and the only solution I have got is to switch the Explorer preview off :(
Could you provide a more detailed step by step guide which registry keys to modify and how to do it?
Thursday, September 29, 2016 1:50 PM | 2 votes
Hi Alexander,
I can tell you what I did in my case. The registry keys in my description may not necessarily the same in your system. So please check carefully their content before modifying any key. In addition, make a backup-copy of the related branch of the registry, so that you have a fall-back available to re-set the former state.
1. Start "regedit": Type "regedit" (without the hyphons) in the search field in W10 and press enter.
You will be asked, whether you allow modifications by the program. Answer with: YES.
2. In regedit go to HKEY_CLASSES_ROOT and look for CLSID in the left pane.
3. Under CLSID you will find lots of entries beginning with
HKEY_CLASSES_ROOT\CLSID\0000002F-0000-0000-C000-000000000046}
Now look for the following entries:
Microsoft Excel previewer: {00020827-0000-0000-C000-000000000046}
Microsoft Visio previewer: {21E17C2F-AD3A-4b89-841F-09CFE02D16B7}
Microsoft PowerPoint previewer: {65235197-874B-4A07-BDC5-E65EA825B718}
Microsoft Word previewer: {84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}
Delete all four entries completely (after making a back-up). For back-up right-click the entry and select "Export", define a location where to export, e.g. desktop, and give the export a name, e.g. "Excel".
4. Now go to key HKEY_CLASSES_ROOT\Wow6432Node\CLSID
5. Look for each of the four key-names given above. They should have the entries for previewer.
Example:
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\00020827-0000-0000-C000-000000000046}
"Microsoft Excel previewer"
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\00020827-0000-0000-C000-000000000046}\InprocHandler32
"ole32.dll"
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\00020827-0000-0000-C000-000000000046}\LocalServer32
"C:\Program Files (x86)\Microsoft Office\Root\Office16\EXCEL.EXE"
6. Check the entries, whether they seem to be appropriate, the LocalServer32 must point to a process (here: excel.exe), which are present under the cited location in your system (check location with Windows-explorer).
7. If necessary, make corrections to the entries for all four programs.8. Close registry and reboot your system.
8. If all above was correct, you should have previews of office files in the explorer.
I hope this is precise enough to follow the procedure. I do not guarantee for any incorrectness. This were the modifications I made in my system.
Good luck,
Joachim
Joachim Claus
Wednesday, May 15, 2019 2:59 PM
You are the MAN! Thanks so much for posting this.
We changed all Office versions of a customer from 64 bit to 32. Preview stopped working.
In our case we saw the keys in the HKCR\CLSID. The name of the keys were wrong.
Used this beneeth reg file to fix:
Once again THANKS!!
Best regards Frank
Windows Registry Editor Version 5.00
[-HKEY_CLASSES_ROOT\CLSID\84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}]
[-HKEY_CLASSES_ROOT\CLSID\84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}\InprocHandler32]
[-HKEY_CLASSES_ROOT\CLSID\84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}\LocalServer32]
[-HKEY_CLASSES_ROOT\CLSID\00020827-0000-0000-C000-000000000046}]
[-HKEY_CLASSES_ROOT\CLSID\00020827-0000-0000-C000-000000000046}\InprocHandler32]
[-HKEY_CLASSES_ROOT\CLSID\00020827-0000-0000-C000-000000000046}\LocalServer32]
[-HKEY_CLASSES_ROOT\CLSID\21E17C2F-AD3A-4b89-841F-09CFE02D16B7}]
[-HKEY_CLASSES_ROOT\CLSID\65235197-874B-4A07-BDC5-E65EA825B718}]
[-HKEY_CLASSES_ROOT\CLSID\65235197-874B-4A07-BDC5-E65EA825B718}\InprocHandler32]
[-HKEY_CLASSES_ROOT\CLSID\65235197-874B-4A07-BDC5-E65EA825B718}\LocalServer32]
Sunday, September 15, 2019 5:50 PM
You are the MAN! Thanks so much for posting this.
We changed all Office versions of a customer from 64 bit to 32. Preview stopped working.
In our case we saw the keys in the HKCR\CLSID. The name of the keys were wrong.Used this beneeth reg file to fix:
Once again THANKS!!
Best regards Frank
Windows Registry Editor Version 5.00
[-HKEY_CLASSES_ROOT\CLSID\84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}]
[-HKEY_CLASSES_ROOT\CLSID\84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}\InprocHandler32]
[-HKEY_CLASSES_ROOT\CLSID\84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}\LocalServer32]
[-HKEY_CLASSES_ROOT\CLSID\00020827-0000-0000-C000-000000000046}]
[-HKEY_CLASSES_ROOT\CLSID\00020827-0000-0000-C000-000000000046}\InprocHandler32]
[-HKEY_CLASSES_ROOT\CLSID\00020827-0000-0000-C000-000000000046}\LocalServer32]
[-HKEY_CLASSES_ROOT\CLSID\21E17C2F-AD3A-4b89-841F-09CFE02D16B7}]
[-HKEY_CLASSES_ROOT\CLSID\65235197-874B-4A07-BDC5-E65EA825B718}]
[-HKEY_CLASSES_ROOT\CLSID\65235197-874B-4A07-BDC5-E65EA825B718}\InprocHandler32]
[-HKEY_CLASSES_ROOT\CLSID\65235197-874B-4A07-BDC5-E65EA825B718}\LocalServer32]
Finally thats work for me, thanks
Thursday, October 10, 2019 10:19 PM
Over three years later, thanks!! This just helped me out. Appreciate that you shared it!
Brian
Friday, February 21, 2020 4:11 PM
Five years later, thank you!!! I was going mad with this problem and among dozens of answers I found yours is the one that worked. Thanks again.