There is no requirement to use a MS Account in W10 (or W8 either). I run all my Win 8 and Win 10 machines using local accounts.
From my experience with Windows 8 after the 8.1 upgrade it is then that the default that Microsoft wants you to use is the Windows Live Account, and you then have to manually change it back to a normal local password that is not a Windows Live Account. I didnt see that they made it a choice to deselect the Windows Live Authentication with Windows 8.1 when upgrading.
As far as Windows 10, I didnt see any choice to use a normal user name and password on the system that was connected to the internet while installing 10. It seems like only the offline system automatically chose to go the route of local username and password, but that because an Internet connection was found with the other, it went the path of a mandatory Windows Live Account authentication.
So maybe with Windows 8 to 8.1 upgrade as well as Windows 10, if a live internet connection is found its the default to make you create a Windows Live Account or use an already created Windows Live Account, but if you upgrade from 8 to 8.1 or install 10 clean with a system with no internet connection, it then defaults to a local "classic mode" username password.
Now I want to be home on my test system to connect that Offline Pentium D to the internet and see if it then wants to upgrade the authentication to Windows Live or if it will stick with a normal username password. Very Curious if they are forcing it upon people to instead use the Windows Live Account for authentication.
I also want to see if Windows 10 will install to Pentium III 1000Mhz Laptop with 768MB RAM even though the RAM doesnt meet the minimum requirements of 1GB and the GPU might also be missing from supported graphics chips given its age.
System requirements
Basically, if your PC can run Windows 8.1, you’re good to go. If you're not sure, don't worry—Windows will check your system to make sure it can install the preview.
Processor: 1 gigahertz (GHz) or faster
RAM: 1 gigabyte (GB) (32-bit) or 2 GB (64-bit)
Free hard disk space: 16 GB
Graphics card: Microsoft DirectX 9 graphics device with WDDM driver
A Microsoft account and Internet access
Here is the link to the info:
http://windows.microsoft.com/en-us/windows/preview-faq#faq=tab1I like testing the hardware limitations of Windows OS's. Even if its not realistic to run a specific OS on such a slow CPU and limited RAM, its neat to know if it will work or not. I started doing this back in Windows 95 when installing Windows 95 to an old Everex 80386 SX 16Mhz with 4MB RAM, 512k VRAM Oakes Technology ISA VGA Card, and 80MB HDD that was a loud drive when the arm was moving inside with the heads on it. Windows 95 on this old beast tested around 1999 would just groan with hard drive activity for a good 3 minutes to load Windows 95 mainly because it was likely using a chunk of the drive as virtual memory for 95 to function with just 4MB RAM...LOL This curiosity also pushes the limits of older hardware with newer games etc... such as lets see if a specific game will run with a very weak CPU, but powerful enough graphics card to render the games graphics etc in which the most common issue you run into is either the game pukes stating you need a better CPU or the BUS bandwidth limitations of a weak CPU are slowing the GPU down too much to function, etc.