Hi @lwmirkk 

Thanks for posting in our business forum.

If you disable firewall or anti-virus, will this still behave so?

If you try the program in compatibility mode by changing VSM.Dsicovery.Process.exe?

You have to find this .exe file and change it from there.

Hi @lwmirkk 

Thanks for posting in our business forum.

lwmirkk wrote

I tried what you told me and more things and the problem persists. =(

Looks like this is your computer issue. Or some software stops it. Simply try to install it on a different computer.

I am using Windows 10 Pro and I don't experience the issue. See the program was there and I have kept it running for more than 24 hours as I never turn off the computer.

And there has been no other report similar to this since 1.7.0 was released.

And I am using the enterprise Kaspersky.

Hi @lwmirkk 

Thanks for posting in our business forum.

lwmirkk wrote

Hi   @Clive_A ! :)

 

I use it on Windows 8.1, which I know isn't very good, but it works perfectly on version 1.6.96.

 

The problem only occurs on version 1.7.0

 

It's most likely a bug in this version with Windows 8.1, but is there any way I can prevent the application from checking for new updates? If so, I can continue with the previous version that doesn't have this problem.

 

Or if the development team checks what changed in the version from 1.6.96 to 1.7.0, so they can find out why this bug started...

It is not a bug. It is an issue and more accurately, a compatibility issue.

Second, we don't have an environment like yours. If there is a system compatibility issue, you should test it on Win 8.1 on another device.

Or you can create a virtual machine on your local computer and test it again.

There is no other feedback and mostly to be the problem on your local computer.

Third, you don't have any information about your system and anti-virus. I don't know if you actually turned it off. Even if we need to test, you should provide your Win 8.1 system version and Win update history.

And you can set the program .exe to the compatibility mode and see if there is an improvement.

Fourth, the VIGI and the architecture involves as it update its database and framework. We cannot guarantee the old system if the framework does not work with your system.

Fifth, the system shows the update but it is not every time. I have my VIGI running 24/7 but I don't always see the update notification. It would only pop at the launch. Not sure what that troubles you.