My Daughter is 33, and a Mum of 9 months, and thankfully does not live here. I do not suspect my Wife, Siberian Husky, nor cats of being secret Windows 10 users. Nope I suspect Microsoft.
The 2 multiboot insider upgrades 17074 and 17063 on this machine appear to have lost Activation today (another older insider build installation on the same machine has not).
It seems weird.
installed eset premium 11.0.159.0
full heuristics, no green screens, cant notice a slow down opening apps quick as defender only.
and this PC with 21 drives in it has been updating since the 15000 builds (went from standard win10 to insider preview), haha! only had 1 build that didnt install (just used ISO upgrade install).
seriously for windows, thats pretty solid.
Take a look here if you haven't already. From the Blog:
For Insiders who reported that Windows needs activation after upgrading to Build 17063, this build includes the fix that caused the issue however you will need to use the Activation Troubleshooter to get your activation back into a good state once you’re on this build.
https://blogs.windows.com/windowsexperience/2018/01/11/announcing-windows-10-insider-preview-build-17074-pc/
Need to begin reading the release notes carefully. Struggled with the install and disabling virtualization is right there in known issues.
Had the problem from 17063. This time, I read the Blog first! All went fine. At 75% it booted and kept on going, instead of reverse rollback. Only problem I have is when I'm on my FCU, I can't run VMWare because it needs virtualization. I dual boot (actually, 6) and it's a PITA to have to walk thru the BIOS each time I switch around. Hopefully, that will be fixed before the Spring Creators Update, or whatever moniker they give it. :)
If anyone knows of any other "legacy filter drivers" creating a problem (or even not creating a problem--you can run "fltmc filters" to see what you have), such as ones used in Macrium Reflect and Mozy, here's a place to post about them:
17063 legacy file system filter - Microsoft Community
It's there where we'll find out if the problems are going to require driver rewrites or not. I have a feeling that there are probably dozens of programs that use this kind of driver, since they've been in use for a very long time.
Quote