As far as I can tell, that’s the whole story.
Create a local account
Microsoft really, really wants you to use a Microsoft account. Over the years, the company has made it increasingly difficult to create a local account -- one that isn’t hooked into Microsoft’s stuff in the sky. (It’s an open point of debate as to whether using a local account also curtails Microsoft’s snooping, given the ever-present Advertising ID, but that’s another story.)
Here’s how to create a new local account:
- Click Start, Settings, Family & other users, Add someone else to this PC. (Note that you can’t “Add a family member” with a local account. Presumably that is tied in to parental controls.)
- In the box marked “How will this person sign in?” down at the bottom, click “The person I want to add doesn’t have an email address.”
- In the “Let’s create your account” dialog, at the bottom, click “Add a user without a Microsoft account.”
- At that point, finally, you can type in a user name, password and password hint. Click Next and you suddenly have a local account ready to use on your machine.
And you thought creating a local account would be easy.
Your programs don’t appear on the Start menu’s All Apps list
If you have more than 512 programs on your machine, Windows 10 gives up -- the apps don’t appear on your Start all apps list. Although the apps are still installed, you can’t get to them through the Start menu. Your system may freeze, it may become very lethargic, and links might not work.
The 512 limit applies not only to programs. It’s the total of all the programs, folders, files, and shortcuts that you have in your Start menu, on the left and right (tiled) sides.
It’s a bug -- nothing you can do about it. In later builds, Microsoft apparently fixed the bug, but it isn’t clear when/if the fix will roll out to the Windows 10 build 10240 masses.
Windows 10 Store won’t start
A lot of people report that they can’t get in to the Windows Store: Click on the tile or on the icon in the taskbar, and nothing happens.
There must be hundreds of posts on various forums about this problem. The Windows 10 forum has a thread where the original poster -- after trying a PowerShell command, a DISM and an SFC command, re-registering the Store -- only solved the problem by performing a Refresh. You can delete the local cache. Chris Snyder has a lengthy description of the problem he encountered and its solution -- for reasons unknown! -- on his Common Ground Software Solutions blog. There’s a troubleshooter for Windows apps that may dislodge the problem.
Sign up for CIO Asia eNewsletters.