Hklm software microsoft fusion enablelog dword su 1

Enabling Remote Work. Small and Medium Business. Humans of IT. Green Tech. MVP Award Program. Video Hub Azure. Microsoft Business. Microsoft Enterprise. Browse All Community Hubs. Turn on suggestions. We can't guarantee quick solutions - Experts Exchange isn't a help desk.

We're a community of IT professionals committed to sharing knowledge. Our experts volunteer their time to help other people in the technology industry learn and succeed.

Plans and Pricing. Contact Us. Certified Expert Program. Credly Partnership. Udemy Partnership. I am trying to find alternatives ways to solve the problem without messing with the registers. I really don't know what to do here, your help and suggestions will be greatly appreciate.

You can enable assembly bind failure logging by setting register key value as log shows to trace detailed error information. This file can not load because there is a conflict with something else in the local server.

It may be the different version of asp. I know that for these simple reasons: First, I have never changed this assembly in years. Secondly, when I restart the computer everything work fine and the assembly as well, but this is only for a few hours until it crash again. So, for sure is not the assembly, is what I said before. You need to restart whatever program it is you're running for it to read those registry settings — Orion Edwards.

The Fusion Log Viewer does all that for you. In Settings you adjust the logging. Show 11 more comments. Make sure that the right level of logging is on I sometimes just select Log all binds to disk just to make sure things are working right Click OK Set the log location option to Custom Remember to turn of logging off once you're done!

I just posted this on a similar question - I think it's relevant here too. Phil 6, 2 2 gold badges 40 40 silver badges 66 66 bronze badges. Mike Goatly Mike Goatly 7, 1 1 gold badge 28 28 silver badges 29 29 bronze badges. Note that in cases where you are hosting the runtime yourself from a native application you will be required to use a custom log path for some reason otherwise you won't get anything logged.

At least in my situation, I didn't actually have to set the custom log paths. All I had to do was turn logging on, e. Run as Administrator was required in my case, otherwise all options were disabled. Note: create the folder as Admin! Make sure you are running fuslogvw not only as admin but also from the correct Windows SDK path the Visual Studio project throwing the exception is using. Using a non matching fuslogvw version seems to not catch the exceptions which makes sense Samuel Jack Samuel Jack Those buttons are disabled for me - why?

Tim, not seen that before - could it be to do with Admin privileges? Make sure the folder allows write access. Just as a note, if the buttons are disabled, re-run fusion log viewer with admin privileges. Show 2 more comments. Tereza Tomcova Tereza Tomcova 4, 2 2 gold badges 28 28 silver badges 27 27 bronze badges. I've allowed myself to put your commands into this gist.

Command line rules! I could quickly replay this using the best invented so far code reusability technology called "cut and paste". This answer is way more useful, I put it into my scripts last time. Now few months later, I came back here and saw the thread again. Remind me of how I use it last time.