New
#60
For some odd reason, Build 16296 has reverted to Home, rather than Pro!
WHAT?
That should not even be possible (according to MS information available when working with Windows images and files). I would understand if it was the other way around (HOME became Pro), but it still would not make any sense during a standard build upgrade.
Interesting issue you have. :)
This was not any ones intention.
Just try to keep relevant information where it belongs. Some antimalware online scanner on a 3rd-party tool has nothing to do with this build. Just like an Ubuntu or other Linux installation on a VMWare or Linux KVM stand alone Hypervisor booted from a 3rd computer where the insider build isn't installed on, has nothing to do with this build.
Only possible thing I can think of is it crashed during late stages of install, and did a "reset my pc" , detected an embedded bios home key and reinstalled Home.
Easy enough to get back to PRO by entering this generic key, and it will activate automatically:
VK7JG-NPHTM-C97JM-9MPGT-3V66T
Well I upgraded to this but had not run disk cleanup from previous upgrade, and got a windows.old(1) folder. Used disk cleanup but it did not entirely delete windows.old(1) leaving oddly enough the windows\sotwaredistribution folder which I could not delete due to permissions. Deleted from a Macrium Rescue Drive.