Microsoft Office Crashes When Openingfasrreport



If your Office package is crashing please refer to the below.

  1. Microsoft Office Crashes When Opening Fastreport Today
  2. Microsoft Office Crashes When Opening Fastreport 2017

Microsoft Office Crashes When Opening Fastreport Today

Microsoft Office 2016 applications may crash or cannot start. The applications that have been seen to be affected are Excel, Outlook, Skype for Business, Word, Access, Publisher, Project and OneNote. Additionally, in the Application Event log, you may find a crash signature similar to. I have an end user who's installation of office is crashing. The installation is fresh from today. When you launch any of the office 2016 apps they bring up the standard first things first window however regardless the option you select it closes the app. Presumably because it crashes.

Microsoft Office Crashes When Openingfasrreport

Are you having Problems with Office hanging, freezing or not responding? The below are common issues which may cause this.

  • This issue can occur if you have not installed the latest updates.
  • Office may be in use by another process.
  • A previously installed add-in may be interfering with Office.
  • You may need to repair your Office programs.
  • Antivirus software may be outdated, or conflicting.

The first thing you will want to do is run Windows Update to make sure office is fully up to date. Please refer to the below links on how to do this on your operating system.

Windows 7

Windows 10

Apple Mac

If you have recently install High Sierra then you need to install the latest Microsoft Office updates for it to function correctly. This can be done by opening Word or Outlook and clicking 'Help' at the top and clicking 'Check for Updates'.

If running the updates do not fix the problem then you may need to reinstall or repair your Office programs - please close down all of your Office programs and refer to the below link on how to do this.

Please contact us via your homepage if you still need technical support which is located here.

Microsoft Office Crashes When Openingfasrreport -->

Note

Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. For more information about this change, read this blog post.

Note

This article only addresses the crash scenario where mso30win32client.dll is the module name in a crash signature.

For other scenarios, see the following articles:

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.

Symptoms

Microsoft Office 2016 applications may crash or cannot start. The applications that have been seen to be affected are Excel, Outlook, Skype for Business, Word, Access, Publisher, Project and OneNote.

Additionally, in the Application Event log, you may find a crash signature similar to the following in event ID 1000:

Note

  • The Application Name will be the name of the executable of the application, such as excel.exe, outlook.exe, lync.exe, winword.exe, msaccess.exe, mspub.exe, winproj.exe, or onenote.exe.
  • The Application Version, Module Version and Offset will vary.

Workaround

Important

Crashes

Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.

To work around this issue, follow these steps:

WhenMicrosoft Office Crashes When Openingfasrreport

Microsoft Office Crashes When Opening Fastreport 2017

  1. Exit all Office 2016 applications.

  2. Start Registry Editor. To do this, use one of the following procedures, as appropriate for your version of Windows.

    • Windows 10, Windows 8.1 and Windows 8:Press Windows Key + R to open a Run dialog box. Type regedit.exe and then press OK.
    • Windows 7: Click Start, type regedit.exe in the search box, and then press Enter.
  3. Locate and then select the following registry key:

    HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0CommonGeneral

  4. Locate the ShownFirstRunOptin registry value in the key that is specified in step 3. If you do not find ShownFirstRunOptin, go to step 5. If you do find it, go to step 7.

  5. If you do not find the ShownFirstRunOptin registry value, point to New on the Edit menu, and then click DWORD (32-bit) Value.

  6. Type ShownFirstRunOptin, and then press ENTER.

  7. Right-click ShownFirstRunOptin, and then click Modify.

  8. In the Value data box, type 1, and then click OK.

  9. On the File menu, click Exit to exit Registry Editor.