{"id":1993,"date":"2017-04-27T20:09:54","date_gmt":"2017-04-27T20:09:54","guid":{"rendered":"http:\/\/salientsoft.co.uk\/?p=1993"},"modified":"2018-10-10T17:15:57","modified_gmt":"2018-10-10T17:15:57","slug":"webstorm-2017-1-update-failure-due-to-kaspersky-false-detections","status":"publish","type":"post","link":"https:\/\/salientsoft.co.uk\/?p=1993","title":{"rendered":"Webstorm 2017.1 update failure due to Kaspersky false detections"},"content":{"rendered":"

1\/ I took the latest 2017.1 upgrade when offered by Webstorm. This upgrade results in the following version:-<\/p>\n

\n

WebStorm 2017.1.2
Build #WS-171.4249.40, built on April 25, 2017
Licensed to Steve Woodley
You have a perpetual fallback license for this version
Subscription is active until April 9, 2018
JRE: 1.8.0_112-release-736-b21 x86
JVM: OpenJDK Server VM by JetBrains s.r.o
Windows 7 6.1<\/p>\n<\/blockquote>\n

During the upgrade, Kaspersky complained that E:\\Program Files (x86)\\JetBrains\\WebStorm 2017.1\\jre32\\bin\\unpack200.exe <\/em>contained a trojan malware virus. This caused the upgrade to fail.<\/p>\n

I checked this online and discovered that Webstorm often gets cited as giving false malware positives, all of which are false. I was happy to allow this to proceed as a Kaspersky exception.<\/p>\n

This Kaspersky forum post gives details on what to do (including disabling file antivirus). It then says to add a file exception rule for the file – the instructions for doing this may be found here<\/a>. Whilst the link is for a 2014 version of Kaspersky, it is similar enough to be correct with the current version as at 2017, with just a few textual prompt\/description differences. Note that I added the full file name, but did not enter a value for the file\/folder name mask ref the \u201cvirus encyclopedia\u201d quoted in the instructions. (I wouldn\u2019t have known what to enter there anyway!). These 2 fields are an either\/or \u2013 this is not quite made clear in the UI prompts, and is not enforced e.g. via a radio button choice or similar.<\/p>\n

Once I did this I checked for updates in Webstorm, retried the new update, and it completed OK.<\/p>\n

 <\/p>\n

2\/ Having done this, I restarted Webstorm and reloaded my Ionic project. Whilst loading the project, Kaspersky complained that \u201cServer-side JavaScript run by a program with restrictions is attempting to create an embedded key or parameter in a protected registry key\u201d<\/strong><\/em><\/p>\n

Effectively, Node.js was attempting to create a new subkey in the registry under TCP\/IP Settings (not sure why it would do this, but I was confident that this was not Malware). Whilst Node.js was a trusted program, it was doing  it as instructed via an ionic batch script.<\/p>\n

I tried to keep allowing the action but this did not work. The solution in the end came when I noticed that the component hierarchy mentioned in the Kaspersky error consisted of a series of green hyperlinks for each level. I was able to click on the green links, and this immediately took me to a Kaspersky settings screen for that component. I was able to see that the script component calling Node.js did not have permissions to create a security registry key. I was able to easily click on the relevant \u201c?\u201d entries to create a security registry subkey, and set the option to Yes.<\/p>\n

So in all a plus for Kaspersky in making it easy to fix, but a minus as I had to work it out for myself and had not been able to find any online or other help on it.<\/p>\n

Note for the future \u2013 any errors etc. from Kaspersky may have clickable links in them which take you to a place where you can add a rule to stop the error \u2013 this is always worth looking into. In my case the clickable links were not underlined but were green in colour.<\/em><\/strong><\/p>\n

Once I had done this, restarting Webstorm and opening the project went without any errors from Kaspersky.<\/p>\n","protected":false},"excerpt":{"rendered":"

1\/ I took the latest 2017.1 upgrade when offered by Webstorm. This upgrade results in the following version:- WebStorm 2017.1.2 Build #WS-171.4249.40, built on April 25, 2017 Licensed to Steve Woodley You have a perpetual fallback license for this version Subscription is active until April 9, 2018 JRE: 1.8.0_112-release-736-b21 x86 JVM: OpenJDK Server VM by […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[200,206,205],"tags":[13,40,16],"_links":{"self":[{"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/1993"}],"collection":[{"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1993"}],"version-history":[{"count":3,"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/1993\/revisions"}],"predecessor-version":[{"id":1997,"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/1993\/revisions\/1997"}],"wp:attachment":[{"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1993"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1993"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/salientsoft.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1993"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}