Per Build Notes/Announcement Blog regarding release of this build from Microsoft
[u][b]Known issues for PC[/b][/u]
If you have 3rd party antivirus products such as Bitdefender, Kaspersky Antivirus, F-Secure Antivirus and Malwarebytes installed on your PC – your PC might not be able to complete the update to this build and roll-back to the previous build.
Although Avast is not listed, I suspect the issue might be the same. I am uninstalling Avast as the new insider build is being downloaded. I really need the new fast ring update due to the recent features that they added in Windows Subsystem for Linux.
I agree, this build seems to affect a majority of AV’s.
I would imagine there will be a new build sometime this week, so I’ll await and see if AV issues fixed in that build.
Yes, the same problem with web browsing does also seem to be affecting build 14951 which I updated to today. Disabling the web shield allows it to work but obviously isn’t an ideal solution…
That is not necessarily an option if you need a fix/feature in the later builds of Windows. I actually opted for fast ring builds after the antivirus issue was introduced, because they added features in WSL (Windows Subsystem for Linux) which I needed for work. In fact I uninstalled Avast as I was opting for the Windows Preview Program Fast Ring builds. My alternate was dealing with a virtual Ubuntu session with limited system resources or working over VNC with a 2nd computer and dealing with its related restrictions and limits and extra costs.
So for the time being, goodbye Avast, I need my computer to do what I need it to do so I can pay rent.
If Avast employees haven’t done so yet, they should reach out to Microsoft to find out if this is a temporary bug that is going to be fixed in MS’s Nov bug bash or if changes to Avast is needed to get it to work again.
I’m not so sure it’s not a MS new feature (changing svchost processes) or the way antivirus interact with MS services/drivers/processes.
I think it’s a combination that, most probably, will require adjustments from the antivirus providers (and not only MS).
I have a feeling it may be awhile until this is fixed, just like last time. I’m on Build 14955 now, and the issue still persists. Unfortunately my only option has been to disable Avast to even have internet access…
According to Microsoft, there is also a known issue with upgrading to the latest build if you have a third-party AV program installed. I’m beginning to see more and more that they are going to dump this on the software makers to resolve instead of doing it themselves.
A better solution is to use a build that still supports your third party AV till MS fixes their attempt
to force you to use Defender.
Build 14936 is the last build that works with third party AV’s
Сегодня купил лицензию и не могу установить на windows 10
Построение ос 10586.122 , как мне использовать купленный продукт и если продукт не работает могу ли вернуть потраченные деньги ?
Today I bought a license and can not install on windows 10
The build OS 10586.122 , how can I use the purchased product and if the product doesn’t work can you return the money spent ?
Figured out can help someone else.
My problem was that I couldn’t install antivirus on Windows 10 build OS 10586.122
During installation, any time asked to restart the operating system and try again , it lasted indefinitely.
Solution : first you need to remove other antivirus applications. then go through start, settings , then select defender Windows there disable everything you can , then enable it , reboot and install avast safely . hope it will help someone else !
