This issue has only been seen when you are running Microsoft Office 2016 and Windows 10 on a system that is configured to use a touchscreen LCD. On the File menu, click Exit to exit Registry Editor. The issue will usually happen when you are opening a large file and start using the Autofilter function, working with filters - especially clearing filters causes Excel to crash. In the Value data box, type 1, and then click OK. Right-click ShownFirstRunOptin, and then click Modify. Type ShownFirstRunOptin, and then press ENTER. If you do not find the ShownFirstRunOptin registry value, point to New on the Edit menu, and then click DWORD (32-bit) Value. If you do not find ShownFirstRunOptin, go to step 5. Locate the ShownFirstRunOptin registry value in the key that is specified in step 3. HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\General Locate and then select the following registry key:
Windows 10, Windows 8.1 and Windows 8:Press Windows Key + R to open a Run dialog box.To do this, use one of the following procedures, as appropriate for your version of Windows. To work around this issue, follow these steps:
Before you modify it, back up the registry for restoration in case problems occur. Serious problems might occur if you modify the registry incorrectly. exeįollow the steps in this section carefully. The applications that have been seen to be affected are Excel, Outlook, Skype for Business, Word, Access, Publisher, Project and OneNote.Īdditionally, in the Application Event log, you may find a crash signature similar to the following in event ID 1000: Application Name. Microsoft Office 2016 applications may crash or cannot start. If you still couldn't find a solution with Office Applications crashing or not starting, you might check the Microsoft Community Office Commercial Admin Center Forums. Help protect your files in case of a crash.I get a "stopped working" error when I start Office applications on my PC.PowerPoint isn't responding, hangs, or freezes.Excel not responding, hangs, freezes, or stops working.This article only addresses the crash scenario where mso30win32client.dll is the module name in a crash signature.įor other scenarios, see the following articles:
0 kommentar(er)
