Join Workgroup in Windows 11: Full Setup & Fix Guide

If you’re staring at an empty Network Explorer window or hitting "Access Denied" every time you try to access a printer or folder on another PC, you aren't alone. It’s a frustrating blind spot in modern Windows design. To join workgroup windows 11 effectively, you need to understand that file sharing isn’t just about putting computers on the same router anymore; it’s about configuring the right permissions and discovery settings.

In this guide, I’ll walk you through the setup process—from the basic Settings app tweaks to advanced PowerShell commands—and, crucially, how to fix the common issues that prevent your devices from seeing each other.

Understanding Workgroup vs. Domain in Windows 11

Why Workgroups Are Still Relevant

Let’s clear up some confusion right away. Many users assume that because Active Directory is the gold standard for enterprise IT, "Workgroups" are dead. They aren't. In fact, for home networks, small offices, and peer-to-peer environments, the default WORKGROUP is still the native way Windows 11 handles non-domain devices.

When you buy a PC today, it likely comes pre-configured in the standard WORKGROUP. This is a flat network model: every computer is equal. There is no central server granting permissions. You manage access locally. This is distinct from a Windows 11 domain vs workgroup setup. In a domain (like Active Directory), a central controller manages users and policies. In a workgroup, each computer manages its own users.

Since Microsoft removed HomeGroup in Windows 11 (it was deprecated in Windows 10), Workgroups are now the only built-in option for simple, centralized-free file sharing. If you’re running a small business with 10-15 users and don’t want to pay for a domain controller license or manage a server, Workgroup is your default. But if you have 50+ users, the lack of centralized authentication in a workgroup will become a management nightmare.

Step-by-Step: Joining a Workgroup via Windows 11 Settings

Prerequisites and Admin Credentials

Before you touch any settings, verify your account type. Changing the workgroup is a system-level modification. You must be logged in as a local Administrator. If you’re on a laptop that requires a domain account to sign in, ensure you have a local admin backup account ready; otherwise, you might be locked out if the domain connection drops during the change.

Also, be prepared to enter credentials. If you are changing from one workgroup to another, or if your network has password-protected sharing enabled, Windows 11 will ask for the username and password of an account that has the right to join the target workgroup. For most home setups, this is just your local admin user and password on the PC you’re configuring.

Navigating to Computer Name Settings

The interface for this has moved around a bit in Windows 11, which trips up a lot of users looking for the old Control Panel. Here is the direct path:

1. Click the Start button and select Settings (or press Win + I).
2. On the left sidebar, ensure System is selected.
3. Scroll down the right pane to find the Rename this PC section.
4. Click the Change button located under "Advanced computer name settings."

This action opens the legacy System Properties dialog box. It feels a bit dated, but it’s where the actual switch happens. You’ll see tabs for Computer Name, Network ID, etc.

In the Computer Name tab, look at the bottom section labeled "Member of." It will currently say "Workgroup: WORKGROUP." Click the Change... button.

Type the name of the workgroup you want to join into the box. If you are setting up a new home network, you might want to keep it as WORKGROUP to avoid extra hassle, or create a custom name like HOME-LAN to distinguish it from other networks. I personally prefer custom names for client work because it’s easier to debug if a device falls off the grid.

Click OK. If prompted, provide the credentials. Then, click OK again to close the window.

Advanced Methods: PowerShell and Command Line

Using PowerShell for Automation

Sometimes the GUI locks up, or you’re deploying a script to update multiple machines. This is where join workgroup windows 11 pro features shine. PowerShell offers a clean, scriptable way to handle this.

You need to run PowerShell as an Administrator. Use the Add-Computer cmdlet. Note that unlike domains, joining a workgroup often just requires the local admin credentials or, in some configurations, the guest password if that’s enabled on the target.

$wg = "HOME-LAN"
$cred = Get-Credential -Credential "AdminUser"

Add-Computer -Workgroup $wg -Credential $cred -Restart

Note: The -Restart parameter is critical. I’ve seen instances where the command reports success but the network stack doesn’t update until a manual reboot.

Legacy Netdom Commands

For those who prefer the command prompt or are working in environments where PowerShell execution policies are restricted, netdom is still the reliable tool. This command is particularly useful in headless server scenarios or when scripting in batch files.

Open Command Prompt as Administrator and run:

netdom join %COMPUTERNAME% /workgroup:HOME-LAN /userd:AdminUser /passwordd:*

When you see the asterisk (*), type your admin password. You won’t see characters as you type—that’s normal. Hit Enter.

If the output says "SUCCESS," your computer has joined the new workgroup. However, the change won’t apply to network services until you restart the computer. I always restart immediately to clear any cached DNS or NetBIOS entries that might cause "ghost" visibility of the old workgroup.

Configuring Network Discovery and File Sharing

Enabling Network Discovery

Here is the catch-22 that frustrates 80% of users: You successfully change workgroup name windows 11, you restart, but your other PC still doesn’t show up. Why? Because being in the same workgroup is only half the equation. If Windows 11 workgroup network discovery is off, the devices are essentially deaf and blind to each other.

Windows 11 often disables Network Discovery for public networks by default. If your Wi-Fi profile is marked "Public," discovery is off.

To fix this:

1. Go to Settings > Network & internet > Advanced network settings > Advanced sharing settings.
2. Ensure your network profile is set to Private.
3. Expand the Private networks section.
4. Turn ON "Network discovery."
5. Also, ensure "Turn on automatic setup of network connections" is ON.

If you skip this, you are shouting into the void. The devices are on the same "room" (workgroup), but they don’t have permission to look for neighbors.

SMB Protocol and Sharing Settings

Underneath all this, the magic happens via the SMB (Server Message Block) protocol. SMB is the backbone of Windows file sharing.

It’s worth noting a technical detail: SMB1 was disabled by default in recent Windows updates due to security vulnerabilities (like the WannaCry ransomware exploit). If you are trying to share a file with an ancient NAS or a very old printer, you might face compatibility issues. However, for standard Windows 11-to-Windows 11 or 10 sharing, SMB3 is active and highly efficient.

In the same Advanced Sharing Settings menu, check Password protected sharing.

• On: Everyone must have a local user account on the host PC to access files.
• Off: Allows guests to access shared folders without a password (less secure, but easier for family devices).

For a home workgroup, I often leave it "On" for security but create a local user account on the "server" PC for each person in the house who needs access.

Troubleshooting: Fix Common Workgroup Errors

Device Not Appearing in Network Explorer

If you’ve joined the workgroup and enabled discovery, but the PC is still missing, the Windows 11 workgroup not showing issue is likely a subnet or firewall problem.

First, verify you are on the same subnet. If one PC is on 192.168.1.x and the other is on 192.168.0.x (perhaps due to multiple routers or VLANs), they cannot see each other via standard discovery.

Second, check Windows Defender Firewall. SMB traffic uses TCP ports 135, 139, and 445. Ensure the "File and Printer Sharing" rule is enabled for your Private profile.

If you suspect a corrupted network stack, I recommend a hard reset of the IP configuration. Open PowerShell as Admin and run:

Reset-NetProfile
ipconfig /flushdns
ipconfig /release
ipconfig /renew

Restart the computer afterward. This clears out any stale ARP table entries that might be pointing to the wrong MAC address.

"Access Denied" or Credential Prompts

This is where the modern identity shift bites. Windows 11 tries to use "Windows Hello" or your Microsoft account for everything. But workgroups are built on Local Accounts.

If you see a credential prompt even though you are on the same workgroup:

1. Check the Account Type: The user trying to access the file might not have a corresponding local account on the host PC. If John@Hotmail.com is trying to access a folder on a PC where John is not a local user, it will prompt for credentials.
2. Guest Access: If you want to bypass this, disable "Password protected sharing." Caution: This is risky if your Wi-Fi is open.
3. Nuance on "Join workgroup windows 11 without admin": You generally cannot join a workgroup without admin rights on the PC you are configuring. However, once joined, a standard user can access shared folders if their permissions are set correctly on the host. Don’t confuse "joining" (system change) with "accessing" (file permission).

To fix permission mismatches, go to Settings > Accounts > Other users and ensure the user exists on both machines with the same password.

Changing Workgroup Name and Restarting

Renaming the Default WORKGROUP

If you’ve decided to move from the generic WORKGROUP to something specific like OFFICE-LAN, here is the process. As mentioned earlier, you do this via Settings > System > About > Rename this PC > Change.

Critical Warning: This is not a one-sided action. If you rename your workgroup to OFFICE-LAN, every single computer on that network must also be renamed to OFFICE-LAN. If PC-A is in OFFICE-LAN and PC-B is in WORKGROUP, they are on different "planets." They will not see each other in the Network Explorer, even if they are connected to the same switch.

I always advise my clients to schedule a downtime window for this. You will need to update 5-10 machines, restart them, and test connectivity. There will be brief periods where shared printers or files will be inaccessible.

Post-Change Verification

Before you call it done, run through this checklist:

• Open System Properties (Win + Pause on the desktop icon) and verify the new Workgroup name is displayed.
• Restart the PC.
• Open File Explorer and click "Network."
• Verify that other devices in the new workgroup appear.
• Try to access a shared folder on a peer device.
• Check that Windows Firewall is configured for "Private" network profile, not "Public."

If any of these fail, you’ve likely missed a device that is still in the old workgroup, or your discovery settings have been reset to Public.

FAQ

Does Windows 11 still use workgroups?

Yes. Workgroups remain the native method for peer-to-peer file sharing in Windows 11. Microsoft removed HomeGroup, so for non-enterprise environments, Workgroup is the default and only built-in alternative to a Domain.

Why does Windows 11 ask for workgroup credentials?

Windows 11 will prompt for credentials if "Password protected sharing" is enabled (the default) and the user accessing the file does not have a matching local user account on the host machine. To disable this, you can turn off password protected sharing in Advanced Sharing Settings, though this is less secure.

Do I need to restart my PC after joining a workgroup in Windows 11?

Yes. The system registry entries for the computer name and workgroup membership are cached. A reboot is required to flush these caches and allow the network stack to properly announce the new workgroup identity to neighbors.

Can I join a workgroup without a password in Windows 11?

You can join the default WORKGROUP without a password in most home scenarios because it’s a local operation. However, if you are joining a custom workgroup that has specific security policies or if you are moving from a Domain, you may need admin credentials. For file access, you can enable guest access by disabling "Password protected sharing."

Conclusion

Successfully configuring a network in Windows 11 is less about a single "join" command and more about aligning three elements: Workgroup Membership, Network Discovery, and Firewall Rules.

1. Settings GUI: Best for one-off changes. Easy to navigate but easy to miss the "Network" vs "Public" profile settings.
2. PowerShell/Netdom: Best for consistency and scripting. Allows you to automate the process for multiple machines.
3. Troubleshooting: If it’s not working, 90% of the time it’s a Firewall issue or a mismatched subnet, not the workgroup join itself.

Keep your firewall rules consistent across all devices, and don’t mix "Public" network profiles with your home office setup. If you’re still stuck, grab the Windows 11 Network Diagnostics Checklist to systematically isolate whether the issue is SMB, Discovery, or Subnetting.