Fuslogvw.exe or the Assembly Binding Log Viewer is a program that helps you to view the log, that is generated when the .NET framework is unable to locate the assembly during its run time. This program belongs to the Visual Studio software alone and hence, you cannot get it from anywhere else.
Use of Fuslogvw.exe?
When the Visual Studio or Asp.net failed to start then it is important to check the log files in order to figure out what was the exact issue. And here Fuslogvw.exe comes into the picture. The Assembly Binding Log Viewer (Fuslogvw.exe) works as a troubleshooting tool when the asp.net throws an error message like “Could not load file or assembly”. This tool allows to figure out the exact issue and resolve it.
What is the File Location?
The Fuslogvw.exe process comes by default when someone installs ASP.net or Visual Studio on their system. The Fuslogvw.exe file is located under C:\Program Files (x86)\MicrosoftSDKs\Windows\v7.0A\Bin\ the directory in Windows 10 whereas it is located under C:\Program Files\MicrosoftSDKs\Windows\v6.0A\Bin\ folder in Windows 7 and older version.
However, if you are using Visual Studio 2010 then it will be located under
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0 Tools\x64\
How to Check the Logs?
When Asp.net failed to start or throw an error message then it is necessary to check the log files. For this, the user will have to enable the Fusion Logs. It can be done in two ways as shown below:
1. Via Registry Editor
- Go to the Start menu on the bottom left side of the screen.
- Type Registry Editor in the search field.
- Click to open the Registry Editor.
- In the Registry Editor, go to the below location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion
- Now, go to the right side and right-click on the DWORD Value – EnableLog.
- Select Modify from the right-click menu.
- It opens the Edit DWORD Value
Here, go to the Value data field and change the value to 1.
- Press the OK button to save the changes and return to the Registry Editor.
- Now, double-click on the DWORD Value – ForceLog.
- In the Edit DWORD Value dialogue box that opens, set the Value data field to 1.
- Hit OK to save changes and return to the Editor.
- <Now, double-click on the DWORD Value –LogResourceBinds.
- In the Edit DWORD Value window, go to the Value data field and set it to 1.
- Press OK to save changes and return to the Registry Editor
- This time, double-click on the LogPath
- In the String Value dialogue box that opens, set the Value data field toC:\FusionLog\ (folder for logs).
- Hit the OK button to save the changes and exit.
- Close the Registry Editor and restart your PC for the changes to be effective.
Now, close and re-launch the Excel sheet, and open the Fuslogvw.exe file to view the logs.
*Note – Just make sure to create a backup of the registry data before you make any changes, to ensure that if you lose any data during the process, you can recover it.
Learn how to fix error code 0xe0434352.
2. Via Command Prompt
You can run the fuslogvw.exe using Command Prompt and enable the fusion logs using the Fusion Log Viewer.
- Press the Win + R shortcut keys to open the Run command.
- Type cmd in the Run command window and press the Ctrl + Shift + Enter keys together. This will open the Command Prompt with administrator rights.
- In the Command Prompt console, execute the below command:
Fuslogvw
- This will launch the Fusion Log Viewer.
- Click on the Settings button on the right.
- In the list, click on Log bind failures to disk and check the box next to Enable custom log path.
- Now, create the path where you want to save the logs. For instance, you can create the logs folder in the C Drive and it should look like this – C:\FusionLogs.
- Copy this path and paste it in the Custom log path
- Press OK to save the changes and exit.
- Now that you have enabled the fusion logs, generate the issue.
- Press the Refresh button in the Fusion Log Viewer. It will now display the assembly binding failure in the list.
- You can press the View Log button to explore more details.
Once you are done diagnosing the error, make sure that you turn off the fusion log viewer, else it may end up slowing down the server.
Other similar files:
