Microsoft Office Error Code 5fcl8

The error code 5fcl8 appears on Microsoft Office applications like MS Word, MS Excel. This particular Office Error Code 5fcl8 appears when there is some sort of problem with the Office applications. So, if you have also experienced this problem and your search has led you here, you are in the correct place. These solutions will help you resolve the problem for sure.

Table of Contents

Fix 1 – Delete notifications registry keys

There are some problems with the Notification entry in the system registry.

NOTE – You should create a registry backup before proceeding to the main part of the solution. This otherwise a very simple process can save your computer in case if anything goes wrong.

Step 1 – Quickly, press the Windows key and perform a search for Registry Editor and open it up.

Step 2 – Later, head on this Notifications point ~

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Notifications

Step 3 – Delete the Notifications key from there.

After deleting the Notifications entries, you must quit the Registry Editor and restart your system.

After restarting the system, you won’t get the 5fcl8 error code again.

Fix 2 – Remove Shared Access registry entries

[For Server 2019 Remote Desktop Service users]

If you are experiencing this problem with any applications running on Windows Server 2019 or 2022, this particular solution will sort it out for you.

Step 1 – Search for “cmd” and open up the “Command Prompt” with administrative rights.

Step 2 – In the Command Prompt terminal, execute these lines of codes one after the other to delete several registry entires from your system ~

reg delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules /va /f

reg delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\RestrictedServices\Configurable\System /va /f

reg delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\RestrictedServices\AppIso\FirewallRules /va /f

Step 3 – Once you have removed these registry entries, open up a new Server 2019 or 2022.

Step 4 – Now, open up the Registry Editor from the taskbar.

Step 5 – Reach the following registry address from there –

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Notifications

Step 6 – Then, tap the “File” menu and tap “Export“.

Step 7 – Choose a location of your choice and export the backup of this key.

Step 8 – Later, load up a CMD terminal and run this command to remove the previous registry entry from there.

reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Notifications" /va /f

Step 10 – Finally, reach the location where you have exported the Notifications key earlier.

Step 11 – Merge that backup to your system registry.

Restart the server. This time, you won’t face this issue.

Fix 3 – Change the startup type of Microsoft Account service

It seems that the problem is directly linked to the startup of the Microsoft Account Sign-in Assistant service on your machine.

Step 1 – Search for services and open up Services utility from the taskbar.

Step 2 – Then, find the Microsoft Account Sign-in Assistant service. Double-tap it to open the service.

Step 3 – Set the ‘Startup type:’ to Automatic or Automatic (Delayed Start) mode.

Step 4 – Save the changes to that service.

After this, close the Services window and restart your computer. The error code 5fcl8 won’t show up again.

Fix 4 – Empty up the authentication-related folders

Sometimes the corruption in the authentication folder can cause this problem.

Step 1 – At first, press the Win+R buttons together to load up the Run window.

Step 2 – Then, paste this there and click OK.

%appdata%

Step 3 – Locate the “OneAuth” folder and “IdentifyCache” folders and delete them.

Later, close all the File Explorer windows and restart the system.

Fix 5 – Mend the WAM particulates

The Web Account Manager components ease the connection between the Windows applications and Microsoft services. Repairing them should fix the issue.

Step 1 – Search for PowerShell from the search box. Then, launch the PowerShell with administrative rights.

Step 2 – Execute these two codes to repair the WAM services.

add -appxpackage -register $env:windir\systemapps\microsoft.aad.brokerplugin_cw5n1h2txyewy\appxmanifest.xml -disableDevelopmentMode -forCeapplicationsHutdown

add -appxpackage -register $env:windir\systemapps\microsoft.windows.cloudexperienceHost_cw5n1h2txyewy\appxmanifest.xml -disableDevelvementMode -forceapplicationshutdownhutdown

After executing these commands, the WAM components will be repaired on your machine. You must restart your computer once to complete the task.

Check if this works.

Fix 6 – End Office processes

The origin of this issue lies in the Office processes from the Task Manager console to fix the problem.

Step 1 – You can just right-click the Windows icon and tap Task Manager to load it up.

Step 2 – Later, look for the Office processes or any other Office app sub-processes and end it from there.

After this, close the Task Manager console. This should help you resolve the issue on your system.

Microsoft Office Error Code 5fcl8 – How to fix