04-23-2012 05:14 AM
mjcon and livesoftware,
I don't know the cause of the crash in TVSU 4.03 but I have a beta version of TVSU 5.0 that I would like for you to try, and then you can tell me if the same issue happens in TVSU 5.0 or not. Would you please contact me by private message if you are willing to try it? Thanks and sorry for this trouble with TVSU 4.03
04-25-2012 06:41 PM
Mind sharing v5 beta with another poor soul who has the same issue? W510 Win7Ent N with SP1 installed. Get the exact same error. I have enabled .NET on the macine (v3 i think) in add/remove programs-turn windows features on/off and still fails.
04-25-2012 07:00 PM
Since you posted in multiple threads that are about different issues, I really have no idea exactly what issue you are having with TVSU. So I don't know if the v5 beta will solve your issue or not.
Exactly what problem are you having with TVSU?
04-25-2012 07:38 PM - edited 04-25-2012 07:40 PM
After starting the application i recieve an error message that states
TVSU Application has stopped working
Windows can check online for a solution to the problem
When viewing the problem details it states.
Problem Event Name: APPCRASH
Application Name: tvsu.exe
Application Version: 220.127.116.11
Application Timestamp: 4f630917
Fault Module Name: tvsutil.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4f63091a
Exception Code: c0000005
Exception Offset: 0000906b
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: 2ac3
Additional Information 2: 2ac3e0a5a88496a511e3fb7db5121704
Additional Information 3: 5c3e
Additional Information 4: 5c3ed15125777e7d8f7d3dd45fc8f6dd
The other posts were in response to the the request "If you are having problems with System Update..please post your Model number here"
04-26-2012 05:36 AM
OK, now I understand you are having the same issue described by this thread. Thanks for clarifying.
Check your private messages, look near the top-right of your screen for an envelope icon and (1 New) or something like that.
05-01-2012 11:30 AM
I am also experiencing this same error on Windows 7 64b SP1, and would be very grateful to receive this v5 beta that may fix this issue!