Thanks for posting.
I'm not shilling for KL or anything...
For the record, that KB article is > 1 month old (and predates patch (a), I think).
And lots of folks have upgraded to KIS/KAV/KTS 2017 under RS1 without issue.
BUT BUT Patch (b) has been in beta-testing for > 1 week, and is supposed to fix most of these issues:
I guess it's sort of like AU/RS1 itself: you'll have either no problems or some problems.
Having said that, I lean a bit closer to the cautious Luddite side than to the adventurous "bleeding edge" side of things.
So, I am still on Win10 1511 and KIS 2016 for a while longer.
At my age, I like to take things slow and steady....
That's been entirely weird of KL.I have KIS 2016 v22.214.171.1244(g)
You are on "MR0" (Maintenance Release 0), 126.96.36.1994(g).
For some reason, KL never shipped "MR1" (Maintenance Release 1) to the UK, even though it's available on the global site, in the US and in other locales.
I have been on 188.8.131.525(e) since I swapped KIS for OEM Crapafee when I bought this box in July.
It is true that they patched KIS 2016 for RS1 before they patched KIS 2017. This was done because there were many more users on 2016 than 2017 at that time. But they have patched and will continue to patch both 2016 (at least MR1, but I do not know about MR0) and 2017.
I know that they localize their builds and throttle the releases, but it looks as if they never shipped MR1 to UK.
Kaspersky Internet Security | Latest Versions | Kaspersky Lab UK
Either that, or you have the updates setting disabled to turn off automatic program updates (see screen cap)????
Ah, well. We'll probably never know.
One of the great mysteries.
My plan will be, when I am ready, to uninstall KIS 2016 (as they recommend) > update to AU/RS1/1607 > PROBABLY reinstall KIS 2016 for a while (because it is the more stable version) > and then eventually clean upgrade to KIS 2017, perhaps when they get to patch (c). Well, that's the plan...
I do have "Download & install new versions automatically" turned on. I'm also delaying upgrading to the AU until the missing drive/ RAW format bug is fixed since I have several internal drives. I've left a ticket with Kaspersky Support about which UK version to use. How can I find your version 184.108.40.2065(e) and would my licence work?
If you have a licence for a kasperksy product, it will be good for the next two years and the past year -- for instance, a 2015 licence will work for 2014, and for 2016-2017.
If you use this installer, it should update you to patch e. first you need to install, and then you need to let it update.
During installation, it might offer to download for you the newest version. It is 2017. if you don't want 2017, then decline new version during installation.
Hi, @Steve C:
Yes, a valid license for 2016 will work for either MR0 or MR1, as well as for 2015, 2017, 2018, 2019 versions.
The current policy for consumer licenses is -1 and +3.
So a 2016 license should work for 2015 2016 2017 2018 2019
MR0 vs. MR1:
You can get MR1 from the US site, or perhaps other regions that offer it.
(One needs to know how to find the "previous versions" links on the KL web site for a particular locale.)
And the installer will automatically update to patch (e) when you update it.
HOWEVER, I do not necessarily recommend doing that.
The major problem with running a version that is not officially offered in your locale is that KL support cannot/will not support it. They will not have been trained to do so. So, if you run into problems running MR1 on your system in the UK, where only MR0 is officially offered, your only support source will be the KL forums. The choice is up to you. But, especially now that 2017 has been released, you may run into issues getting official help from KL if you install MR1 in a region where it is not officially supported.
If you have the setting in my screenshot enabled, you WILL get version 2017 automatically when it is available to you via the auto-updater. As you know, KL, like other vendors, throttles their new version releases. So there's no way to know exactly when you will get it. This "new version auto-update" feature is relatively new for KL. And it has caught some users by surprise. So, if you prefer to do a clean upgrade and/or want to have control about when and how to update to 2017, I suggest disabling that feature. NOTE: it only applies to major new versions, e.g. 2017, not to patches. Patches come in with regular auto-updates, even if that particular setting is disabled.
I hope this helps,