Every time I try to load willowtree, I am immediately presented with "WillowTree.exe has stopped working." I would like to clarify I have read up on every single thread on this site related to this issue, and it still hasn't been resolved for me. I am running Windows 10 and was previously able to use Willow Tree on Windows 8. If this is a .NET framework issue (it is possible my .NET framework 3.5 is corrupt), I understand this to be a whole other demon.
Any help would be greatly appreciated!
Last edit: Mick Tillson 2016-04-13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First off make sure you have installed WillowTree# properly. The entire contents of the ZIP file including WillowTree#.exe and its 'Data' folder be extracted somewhere that the current user has read and write access, such as in a subfolder of you downloads, desktop, or my documents folder. Typically a non-admin user does not have write access to Program Files or its subfolders, so you need to change the permissions to allow write access if you install in a folder there because WT# has to be able to write to its data folder. If you try to run WT# directly from a ZIP file without extracting it to a folder, it won't work properly.
If you have extracted WT# properly then I will need more information to try to figure out exactly why WillowTree# is crashing.
1) First off, which version of WillowTree# are you trying to run?
2) Secondly, I need more information about the crash to try to figure out what is causing it. To get this information you need to run the Windows event viewer. Look in the Windows Logs->Applications
1) Run WillowTree#.exe so it will crash. Shut down the window that says the application shut down.
2) Push and hold the Windows key and press the R key to open the Run dialog.
3) Type in 'eventvwr' (without the quotes) then push enter to run the Windows event viewer
4) When the event viewer pops up, expand the folder that says Windows Logs, then click on the subfolder of it that says Applications.
5) In the list of errors find the error where WillowTree# crashed. It should be the first one in the list since it just happened. That event will likely say either Application Error or .NET Runtime in the Source column.
6) Right click the error in the list of errors and click on Copy->Copy Details as Text. Paste the text from your clipboard here and I will try to help you figure out why it is not working.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Click start-Control Panel > Programs and Features.
Click Turn Windows features on or off.
Find NET Framework 3.5 in the list and uncheck it then click OK so Windows will uninstall it.
Restart your computer to make sure it is completely removed.
Go back to Programs and Features and turn NET Framework 3.5 back on and click OK so it will be reinstalled.
If NET Framework 3.5 SP 1 isn't installed and working properly then WT# won't work. The issue with the event viewer snap-in seems to suggest that might be the case.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Every time I try to load willowtree, I am immediately presented with "WillowTree.exe has stopped working." I would like to clarify I have read up on every single thread on this site related to this issue, and it still hasn't been resolved for me. I am running Windows 10 and was previously able to use Willow Tree on Windows 8. If this is a .NET framework issue (it is possible my .NET framework 3.5 is corrupt), I understand this to be a whole other demon.
Any help would be greatly appreciated!
Last edit: Mick Tillson 2016-04-13
First off make sure you have installed WillowTree# properly. The entire contents of the ZIP file including WillowTree#.exe and its 'Data' folder be extracted somewhere that the current user has read and write access, such as in a subfolder of you downloads, desktop, or my documents folder. Typically a non-admin user does not have write access to Program Files or its subfolders, so you need to change the permissions to allow write access if you install in a folder there because WT# has to be able to write to its data folder. If you try to run WT# directly from a ZIP file without extracting it to a folder, it won't work properly.
If you have extracted WT# properly then I will need more information to try to figure out exactly why WillowTree# is crashing.
1) First off, which version of WillowTree# are you trying to run?
2) Secondly, I need more information about the crash to try to figure out what is causing it. To get this information you need to run the Windows event viewer. Look in the Windows Logs->Applications
1) Run WillowTree#.exe so it will crash. Shut down the window that says the application shut down.
2) Push and hold the Windows key and press the R key to open the Run dialog.
3) Type in 'eventvwr' (without the quotes) then push enter to run the Windows event viewer
4) When the event viewer pops up, expand the folder that says Windows Logs, then click on the subfolder of it that says Applications.
5) In the list of errors find the error where WillowTree# crashed. It should be the first one in the list since it just happened. That event will likely say either Application Error or .NET Runtime in the Source column.
6) Right click the error in the list of errors and click on Copy->Copy Details as Text. Paste the text from your clipboard here and I will try to help you figure out why it is not working.
I recieve an error upon opening the event viewer:
I am running the most recent experimental version of WillowTree,
I found a thread where someone else had this snap-in issue with the MMC snap in due to having NET Framework 3.5.1 corrupted I think.
http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/event-viewer-mmc-could-not-create-the-snap-in/7c9aaea1-e0b7-42fd-adc0-f7d0b3f22c3d?auth=1
Try this to reinstall .NET Framework 3.5.
If NET Framework 3.5 SP 1 isn't installed and working properly then WT# won't work. The issue with the event viewer snap-in seems to suggest that might be the case.