WorkVisual - Closes without warning

Lookup WorkVisual.log in WoV installation folder and send it to KUKA with a description what goes wrong. What should we do about it? We do not write the software. If it is unstable there is only one natural destination for your problems: KUKA.

In the meantime you could try a different version.

Fubini

How do You installed WoV on this machine?

Running WorkVisualSetup.msi, or Setup.exe?

The right way is using Setup.exe, and I saw WoV behaving strangely in the past because it was installed with WorkVisualSetup.exe.

MSI installer only installs WoV ... without any of several required dependencies, hence use EXE installer.

another thing worth checking is crash report folder (if something got recorded).

it is not clear what exactly you are doing. i guess you are trying to install different versions on same machine but it is not known what the target OS is, compatibility with WoV, type of install, the way install is performed, if and what options are integrated, if and what crash report is generated, etc.

in other words there are way too many unknowns to offer any concrete advice.

doing same thing over and over and expecting different results is not ... efficient.

my suggestion is to try things differently. over the years i had many complain about WorkVisual install. in the end, 99% were user errors.

so here is a short list of tips:

1. make sure to extract downloaded WoV into a folder, then run installer. do not try to run installer that is not extracted yet.

2. make sure to install using Setup.EXE and not MSI file. MSI only installs WoV but not dependencies (which are required).

3 make sure that path where installation files are extracted is short. normally things would arrive on CD/DVD and setup.exe would be in the root of that drive (something like D:\Setup.exe). in this case dependencies (also compressed files or self-extracting archives) will be ok despite using long names.

for example D:\DotNetFX461LanguagePack\NDP461-KB3102436-x86-x64-AllOS-DEU.exe will be extracting bunch of files too - and directories (all of which will make path even longer), before they are copied to target folder C:\Program Files\...

and if the total path length exceeds 260char limit for ANY file, your installation will fail and you may not even know it. then you get to see weird results when you least expect it. and in some cases there are no warnings if this happens. i have seen this and mentioned it before. So do NOT try to install from something like

C:\Users\MyItAssigmendVerlyLongUSerName\Desktop\My Files\KUKA Downloads\2021\WorkVisual Installations\6.x\00311617;03;KUKA.WorkVisual 6.0;WorkVisual_V6.0.2_Build0287\workVisual\Setup.exe

that is "only" 186 characters but .Net the language pack (just an example) is already at some 240 characters and that is before anything is extracted yet. guess what happens if that language pack contains something like, i don't know... \Languages\1033\64-bit\SetupResources.dll

suddenly that 240 is grown to 280 characters and would definitely exceed the Windows limits.

so if you want to install software, install it from a short path, so that installer executable is close to root. I use something like:

C:\Installs\WOV6.0.2\Setup.exe

C:\Installs\WOV6.0.9\Setup.exe

C:\Installs\WOV6.0.12\Setup.exe

etc.

i guess you are getting the point. Just ask yourself, why Microsoft always installs the operating system into folder that follows DOS 8.3 naming convention? it's been 30 years since DOS. but they will happily let you have your documents in a folder using long file names...

4. maybe everything so far is all fine but something is simply not right with your machine. maybe something got corrupted so reinstalling different version of WoV6.x does not make any difference. did you consider installing it as a portable version? that should isolate good deal of resources and potentially reduce chance of running into same problem. Or try installing it in a virtual machine.

Have you checked the application.evt?