Windows 10 stores the “Registered Owner” and “Registered Organization” text in the operating system metadata. It’s the same information you’ll often see in system property screens and in some inventory/reporting tools.
There’s no official Settings page to edit these fields, so the most reliable approach is to update the values in the Windows Registry and then verify the change.
As an Amazon Associate I earn from qualifying purchases.
What Registered Owner and Organization Name actually are
In Windows 10, the “Registered Owner” and “Registered Organization” are string values stored under the OS version key. Specifically, they live at:
Recommended Free Tools
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
The two most commonly used values are:
RegisteredOwnerRegisteredOrganization
These values are primarily informational. They do not replace your Microsoft account, product activation state, or licensing eligibility.
#1 Best Overall
Why you might want to change them
- Company or school rebranding (e.g., updating from a legacy department name).
- Fixing mislabeled assets after a reimage or deployment mistake.
- Aligning screenshots and hardware inventory reports with your internal naming conventions.
- Correcting an old owner/organization string left behind by a master image.
Prerequisites and safety checks
This change is straightforward, but you should treat Registry edits as a controlled operation. A mistake won’t usually brick Windows, but it can cause confusing metadata or deployment drift.
What you need
- Windows 10 with local Administrator rights.
- A current backup of the registry key you’ll modify.
- Clear target text for both fields (keep it short and consistent—spaces and punctuation are fine).
Make a backup before editing
- Press Win + R, type
regedit, press Enter. - In Registry Editor, navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion. - Right-click
CurrentVersion(or export the specific key) and choose Export. - Save a file with a recognizable name, such as
CurrentVersion_backup_YYYY-MM-DD.reg.
If something goes wrong, you can restore it by double-clicking the exported .reg file (or re-importing via Registry Editor).
Method 1: Change values with Registry Editor
This is the most common and most reliable method because it’s easy to see the current values and edit them safely.
Find the right registry keys
- Press Win + R, type
regedit, press Enter. - Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
Update RegisteredOwner and RegisteredOrganization
- In the right pane, locate
RegisteredOwner. - Double-click
RegisteredOwner. - Set Value data to your desired owner name (example:
Contoso IT). - Confirm the Value type remains REG_SZ.
- Repeat for
RegisteredOrganizationand set Value data to your organization name (example:Contoso Corporation). - Click OK after each change.
If one of the values doesn’t exist, you can create it:
Rank #2
- 15.6" diagonal, HD (1366 x 768), micro-edge, BrightView, 220 nits, 45% NTSC.
- Right-click an empty area in the right pane → New → String Value.
- Name it exactly
RegisteredOwnerorRegisteredOrganization. - Set the Value data and keep type as REG_SZ.
Triggering the refresh (restart vs. sign-out)
Windows doesn’t always redraw every system UI immediately after a registry change. For most machines, a restart is the most dependable way to ensure the new strings appear consistently.
- Recommended: Restart the PC.
- Sometimes enough: Sign out/in for a user-specific view, but restart is better for consistency.
Method 2: Change values with Command Prompt (reg.exe)
If you prefer automation (or you’re fixing multiple endpoints), you can set the same values via command line using reg.exe.
Run the commands as Administrator
- Press Win, type
cmd, right-click Command Prompt → Run as administrator. - Run these commands (replace values in quotes with yours):
reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v RegisteredOwner /t REG_SZ /d "Contoso IT" /f
reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v RegisteredOrganization /t REG_SZ /d "Contoso Corporation" /f
Verify the values
- Run:
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v RegisteredOwner
Rank #3
- 10th Generation Intel Core i5-1035G1 processor
- 12GB system memory for full-power multitasking
- 256GB Solid State Drive
- 15.6" Micro-edge touchscreen display
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v RegisteredOrganization
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Restart Windows to ensure UI/inventory tools reflect the updated strings.
Where the changes show up (and what won’t change)
After updating these values and rebooting, you should see the new text in places that read from CurrentVersion, such as system information dialogs and some inventory reports.
| Area | Will it update? | Why |
|---|---|---|
| System info / UI owner/organization text | Yes (typically after reboot) | These screens read the registry strings. |
| Activation status | No | Activation uses licensing channels and system IDs, not these display strings. |
| Microsoft account association | No | Account linkage is independent from RegisteredOwner metadata. |
| Windows product key | No | Key ownership isn’t tied to these values. |
Troubleshooting when the change doesn’t stick
If you update the strings but nothing changes, don’t assume the values are wrong—Windows tooling can be picky about where it displays from.
1) You edited the wrong hive or key name
Confirm you’re editing:
HKEY_LOCAL_MACHINE(notHKEY_CURRENT_USER)SOFTWARE\Microsoft\Windows NT\CurrentVersion(exact path)
Also ensure the value names are exact: RegisteredOwner and RegisteredOrganization.
2) Permissions prevented the write
Common symptom: you save the change, but Value data doesn’t actually update. In Registry Editor, verify the values after you click OK. For command line, check that reg add succeeded (it should not error).
Rank #4
- Latitude 7480 Laptop 14"
- Intel Core i7 6th Gen i7-6600U -Core Processor 2.6GHz (3.4GHz With Turbo Boost)
- 256 GB SSD Hard Drive & 16GB Memory
- 1920x1080 FHD resolution Non-Touch with Webcam and an integrated graphics chip
- Wireless Wifi & Bluetooth
Retry with an Administrator command prompt / elevated Registry Editor session.
3) You have policy or enterprise tooling overwriting it
In managed environments (Intune, Group Policy scripts, configuration management), an automation step may reset these fields after you change them.
- Wait for the next policy refresh cycle.
- Check your deployment scripts for any references to
RegisteredOwnerorRegisteredOrganization. - If machines are imaged, update the master image so the correct values ship by default.
4) You’re checking the wrong place
Some tools and dialogs show different fields (like “Registered to” or “Owner” pulled from cached/system-specific sources). Always verify using Registry itself:
- Open
regeditand confirm the Value data. - Use
reg queryto confirm what Windows sees.
5) Protected/merged images or custom deployments
If this PC was created from a sysprepped or specialized image, the metadata could be regenerated during a first-run task. In that case, edit the master image rather than patching each endpoint after the fact.
Free tools Windows power users keep installed
One-click scans. No signup required.
If you’re running in a lab, test your change after the first login and after any “Setup completion” tasks run.
Best Value
Common mistakes to avoid
- Editing the wrong value type: don’t change away from REG_SZ unless you know exactly what you’re doing.
- Using partial/inconsistent strings: inventory systems often compare exact text; keep naming consistent with your asset records.
- Forgetting the reboot: many UI surfaces update after restart, not instantly.
- Changing fields for the wrong machine state: if the device is under management, apply the change where the configuration is defined (often the image or deployment script).
- Assuming it affects activation: it won’t. Don’t use this to troubleshoot licensing.
Alternatives and admin-level considerations
On managed fleets, consider changing these values at the source (golden image) or via your configuration management pipeline so you don’t fight overwrites.
Fleet-friendly approach
- Build once: set
RegisteredOwner/RegisteredOrganizationin the master image. - Deploy as part of provisioning: run the
reg addcommands during OSD/Autopilot policy steps. - Verify post-deploy: script a registry query check and log the result.
FAQ
Will changing RegisteredOwner or RegisteredOrganization break Windows 10?
No, not in normal circumstances. You’re editing informational string values under CurrentVersion. Still, make a backup before you change anything.
Do I need to change both fields?
You don’t have to. You can change only RegisteredOwner or only RegisteredOrganization. For best consistency in inventory reports, changing both is common.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Why do I still see the old owner name after reboot?
Check the registry values with regedit or reg query. If they are correct, your viewer tool may be reading cached data or using a different field. If the registry values revert, something else (policy or scripts) is overwriting them.
Can I do this without admin rights?
Usually no. Writing to HKEY_LOCAL_MACHINE requires elevated privileges. You’ll need Administrator permissions.
Does this work on all Windows 10 versions?
Yes for supported builds because these values are longstanding within CurrentVersion. The UI surfaces that display the text can vary, but the registry location is the authoritative place to confirm.
Bottom Line
To change Registered Owner and Organization Name in Windows 10, update the string values RegisteredOwner and RegisteredOrganization under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion, then reboot.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If the change doesn’t show up, verify the registry values directly and check for policy or deployment scripts that may overwrite them.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
