Version(s) 12 crashing constantly... 
Autor: Chris D.I see I am not alone in having problems with Website X5 version 12 crashing constantly. This only has occurred since the most recent update (which I did this week <GRR>). The program simply freezes - so no screenshot is relevant - but it universally seems to happen during page editing. I am on Evolution 12 but I see others are having the same problem with Pro 12. Suggestions regarding checking .NET configurations do not seem to work, nor those involving C+ etc. I see one user has even done a disk format... So, something is seriously wrong here and needs fixing ASAP. This is only since the most recent update. In the absence of a proper fix, is it possible to roll back to the previous version as this is unusable and I NEED TO GET A PROJECT FINISHED?
TIA, Chris
Autor
For info: Someone in another thread suggested running the prog in non-responsive mode to start with. This does seem to help - ie you can do about half a dozen edits before the (inevitable) crash - but it still not really viable.
It may be just me, but everything else on the computer seems to slow down as well. Does this suggest some memory misuse problem?
Hello Chris,
It is not possible to rollback to the previous version. Can you please tell me which windows version you are using?
Did you already tried to repair the .NET Frameworks and install the visual c++ libraries?
Which ones did you install?
Does the system slows down generally or when you use the program?
Can you please also try to run windows in safe mode to see if then you experience the same issue?
Many thanks!
Autor
Interestingly, I may have a solution. Before receiving the above message, I found I had my original installation file from last october (12.00.22?). I installed this over the top of my current installation and ran the program. It wouldn't open my existing project files - so I then did the upgrade using the newest version. Since then I have only had one crash.
So, I have gone straight from the october version to the latest one. If I remember rightly, there was at least one other update in between? In which case, maybe the problem lay there?
Hello Chris,
Yes there were different updates between them. It could depend on different things but if it would be an update to cause it also others would have the exact same issue.
Most probably the reinstall solved it.
Many thanks!