New
#11
Exactly. That is in the nature of an OS that is in active development. And that is why Symantec and other developers of AV software are probably doing little about compatibility at this stage. When the OS attains the stability of consumer preview Symantec and others will look into this, but only to be prepared when the OS is officially released. Then the product will be extensively tested with the new OS and any necessary changes made. Then a new version will be released and advertised as compatible with Windows 10.
Modern operating systems are designed to give the illusion to applications that they are running alone on the computer. Most applications have no knowledge of what other processes are running and what they might be doing. For normal applications that is all good.
But AV applications are not "normal". Their purpose is to detect and deal with malicious software that is using every dirty trick in the book (and probably a few new ones) to evade detection. Modern malware has invaded system address space, normally the exclusive domain of device drivers and the operating system kernel. This address space is strictly off limits to normal applications and enforced by the OS.
Simple file scanning is no longer adequate to detect modern malware. AV products must use highly advanced techniques and go into system address space where malware resides. To do this the AV product will require detailed internal knowledge of the specific OS it is running under. Doing that with an OS under active development is almost impossible and at the least highly impractical. That an AV product might crash while attempting this in an unknown OS is hardly surprising.