The #1 Security Setting in Windows: Stop Using an Admin Account
Ten Seconds, One Decision
If you change one thing about a Windows machine today, change this: your everyday account should not be an administrator.
That is the whole tip. Everything below is why it matters and how to do it without locking yourself out, because the second part is where people give up and go back to running as admin.
The reason it matters is not abstract. When you browse the web, open an attachment or click a link as an administrator, every piece of code that runs has the keys to your machine. UAC prompts are not a real barrier to malicious code - they exist to make legitimate software ask permission, and malware routinely arrives as something you asked to run. The Microsoft Vulnerabilities Report has found for years that the large majority of critical Windows vulnerabilities are mitigated by simply removing admin rights. It is the cheapest mitigation available and most people never apply it.

The Correct Shape of a Windows Setup
Two accounts, not one.
A standard account is what you use daily: email, browser, documents, everything. It cannot install services, change system settings or write to protected locations without an elevation prompt and a password.
An administrator account exists but is not logged in. You use it when something genuinely needs elevation, and otherwise it sits there.
This is exactly how macOS and most Linux desktops are configured by default, which is why they do not have this conversation. Windows lets you run everything as admin because it is convenient, and convenient is what gets exploited.
Doing It With Commands
Open an elevated Command Prompt (right-click, Run as administrator) and check the current state first:
net localgroup Administrators
You will see your account listed. That is the problem.
Create a new local administrator. Pick a name that is obviously not your daily account, and write the password down somewhere physical before you continue:
net user SecAdmin P@ssw0rd-Change-This /add
net localgroup Administrators SecAdmin /add
Then remove your daily account from the administrators group:
net localgroup Administrators YourName /delete
Note that both commands reference the group Administrators and then the account. Getting those the wrong way round is the common error and it simply reports that the name was not found.
Verify:
net localgroup Administrators
whoami /groups | findstr /i administr
The group listing should now contain SecAdmin and not your daily account. whoami /groups in a normal shell should not show the Administrators group as enabled.

The Step That Prevents the Lockout
Before you demote your account, confirm the new admin actually works. Sign out, not just switch users, and sign in as SecAdmin. If that login succeeds and can open an elevated prompt, your daily account is safe to demote.
If you demote first and find the new account does not work, your only routes back are another admin account, a recovery drive, or reinstalling. I have watched someone do this at 11pm on a work laptop.
One more thing people miss: if the machine is domain-joined, net localgroup Administrators is not the whole picture. Domain group membership can re-grant admin rights at the next policy refresh, so this needs doing through your IT admin or it will silently undo itself.

Things That Will Feel Different
UAC prompts become more frequent for the first week, because installation and system settings now genuinely need elevation. That is the feature working.
Some older software assumes admin rights and will misbehave. The fix is per-application: right-click, Properties, Compatibility, "Run this program as an administrator" - that grants elevation for one program rather than the whole session.
Printers, VPN clients and hardware drivers are the usual offenders. Set the compatibility flag once and forget it.
If You Would Rather Not Type Commands
The same result is available in Settings: create a new account of type Administrator, sign into it once to confirm, then change your own account type to Standard. It takes about two minutes and does not require the command line.
There is also a small utility floating around that automates the create-and-demote sequence in one run. If you use one of those, the only thing worth checking is the same thing as above: that you wrote down the new admin credentials before it finished. A tool that demotes your account while the new password is only in your head is a tool that can lock you out of your own machine.
The Honest Caveat
This is not a substitute for updates, a password manager, or not clicking things. It removes one large class of damage - anything that runs as you now runs without the keys to the system - and it does nothing about the rest.
What it does do is change what a mistake costs. With admin rights, one bad installer can own the machine. Without them, the same mistake is usually contained to your user profile, which is recoverable.
Ten seconds to create an account, a minute to demote yours, and the machine that was one click from total compromise is no longer one click away.
Don't trust the download button. Trust the hash.
If this was useful, More hands-on tech guides at TechGeek. No pressure — read it whenever it's useful.