I've upgraded four systems now to Windows 10, three of which had/have eset Smart Security installed. On my main PC, which I upgraded first, the upgrade process seemed to go well (albeit it took a lot longer than I expected it to).
However, on the first reboot following the completion of the upgrade, I had a bsod but the error flashed too quickly and the system rebooted, and subsequently went into the desktop without any additional issues.
At least it seemed so. I seemed to have *no* internet access, even though the taskbar's network icon showed I was connected just fine. Then I noticed most of the usual icons that appear down in the taskbar clock area were not there, either. It was only on a hunch that I went to the Start menu to load up eset, and I was shown the new network detected window, and I set it for the right access type, and suddenly all of the icons started loading like I'm used to.
Something that happens during the changeover to Windows 10 *must* include the networking feature, because not only did this quirk with eset appear, but my VMWare Workstation network also stopped working and telling me that I had no connection, even though everything seemed to be correct in the virtual adapters and VM settings. After a few hours of deep Googling, I finally located a how-to that got the VMWare network going again, but it was the first confirmation I found that Windows 10 either changes or reconfigures the network settings.
Others' mileage may vary, of course, and this experience may have been specific to my systems (on the second system upgrade, I was already prepared to start up eset from the Start menu to "activate" its core functions and identify the so-called "New Network Found."), but if this helps anyone who upgrades to Windows 10 and IS running the latest eSet Smart Security like I was, yet has internet issues or their system seems to be hanging---it's something worth trying.
For what it's worth,
Timothy Kline / ENVISIONocity