Windows Guest still exists, but a visitor needs a standard account
Borrowing a family computer raises two separate questions: whose files are exposed, and who gets permission to change the machine.
Someone needs your computer for ten minutes. Your signed-in desktop contains a considerably longer autobiography.
Windows still has a built-in account named Guest. Microsoft’s local-account documentation describes its limited permissions and disabled default. The company calls anonymous access a “security risk” and recommends leaving Guest disabled unless its use is necessary. That old account name has survived longer than its usefulness as casual household advice.
A visitor needs a place to work without borrowing your identity. Creating a regular local user lets the owner choose that place deliberately. Naming it Visitor makes its purpose obvious; the name itself grants no special protection. A label on the cookie jar has never stopped anyone reaching into it.
Microsoft’s account-management instructions put the starting point in Settings, under Accounts and Other users. Add account begins the process. The local route uses I don’t have this person’s sign-in information, followed by “Add a user without a Microsoft account.” A visitor checking a travel reservation hardly needs to become part of your synchronized digital family.
The important choice comes after creation. The account should be Standard User, rather than Administrator. In the account’s options, Change account type shows the setting. Microsoft recommends standard accounts for everyday use because administrators can install software, change system settings and access files across the machine.
Giving someone your normal sign-in and opening a private browser window leaves the Windows session yours. The operating-system account is the boundary for this job. A fresh browser window sitting on your own desktop is an awfully small curtain to put in front of the rest of your computing life.
A separate account also gives the visit a clear ending. Microsoft’s Remove option removes that person’s sign-in information and data from the device. Anything the visitor wants to keep needs to leave with them first. Removing a Windows profile should never be the surprise souvenir from a weekend stay.
On a work-managed PC, the company that owns the device gets to decide whether another person may use it. An account you can technically create doesn’t settle that permission. For a household computer, the useful arrangement is much simpler: a named visitor account, limited privileges and a clear decision about what happens to its files afterward.
More shared devices could benefit from making this path easier to find. The ordinary need is still sitting right there beside the keyboard, waiting for an account that doesn’t start with your email address.
Guest has overstayed its welcome.