DEV Community: Bryz︱🦾

📬 "My Mailbox Is Full!" Find What's Eating the Space Before You Delete Anything

Bryz︱🦾 — Sun, 01 Nov 2026 14:13:02 +0000

"I can't send email. Outlook says my mailbox is full!" 😩

It's one of the most common help desk tickets out there. The lazy fix is "just delete some old stuff." The better fix takes five minutes and actually solves it. Let's go. 🚀

🔍 Step 1: Find the real space hog

Don't guess. Measure.

In classic Outlook for Windows:

Right-click your mailbox name in the folder pane.
Choose Data File Properties.
Click Folder Size.

You'll see every folder and how big it is. Usually one or two folders (Sent Items, Deleted Items, or an old project folder) are doing all the damage.

If you're the admin, you can check from Exchange Online PowerShell:

Connect-ExchangeOnline
Get-EXOMailboxStatistics -Identity user@contoso.com | Select-Object DisplayName, TotalItemSize, ItemCount
Get-EXOMailboxFolderStatistics -Identity user@contoso.com | Select-Object Name, FolderSize, ItemsInFolder

📎 Step 2: Go after the big stuff

Empty Deleted Items first (right-click > Empty Folder).
Open your biggest folders and sort by Size.
Delete or save off the giant attachments you don't need anymore.

A handful of old emails with huge attachments can free up gigabytes. Deleting 2,000 tiny newsletters barely moves the needle. 💡

🗑️ Step 3: Don't forget Recoverable Items

Here's the one most people miss. Mail you "permanently" delete can still sit in the Recoverable Items folder, and in many setups that space still counts against you.

In classic Outlook:

Select Deleted Items.
Click Recover Deleted Items (Folder tab or the link at the top).
Select what you don't need and choose Purge.

Note: if the mailbox is on a litigation hold or retention policy, items may not purge. That's by design, so loop in your admin.

📦 Step 4: Stop it from coming back

Cleaning up once is nice. Never getting the ticket again is better. ✅

Turn on the online archive so older mail moves out of the main mailbox.
Apply an archive policy that moves mail after a set number of years.

Admins can enable the archive like this:

Enable-Mailbox -Identity user@contoso.com -Archive

🧠 The takeaway

Measure first, delete the big stuff, purge Recoverable Items, then set up an archive. That's a fix the user won't have to call you about next month. 🙌

What's the biggest mailbox you've ever had to clean up? Drop it in the comments 👇

🖥️ Second Monitor Went Black? Try These Fixes Before You Replace It

Bryz︱🦾 — Sat, 31 Oct 2026 13:16:41 +0000

"My second monitor just stopped working." 😩

It's one of the most common help desk calls, especially after someone docks a laptop, wakes it from sleep, or gets a Windows update. The good news: the monitor is usually fine. Here's the order I'd work through before anyone orders new hardware.

⚡ Step 1: Check the projection mode

Windows can quietly flip to "PC screen only." Press:

Win + P

Pick Extend (or Duplicate if they want a mirror). If the screen comes back, you're done.

🔄 Step 2: Restart the graphics driver

This shortcut resets the display driver without a reboot:

Win + Ctrl + Shift + B

The screen flickers and you may hear a beep. Open apps stay open, so it's safe to try mid-call.

🔍 Step 3: Make Windows look again

Go to Settings > System > Display > Multiple displays and click Detect.

Want to see what Windows actually sees? Run this in PowerShell:

Get-PnpDevice -Class Monitor | Select-Object Status, FriendlyName

If the monitor shows up with an Unknown or Error status, Windows sees it but something is off with the driver or connection.

🔌 Step 4: Go physical

Make sure the monitor is powered on and set to the right input source (HDMI 1 vs HDMI 2 vs DisplayPort catches lots of people).
Reseat both ends of the cable.
Swap the cable or try a different port.
Using a dock? Unplug the dock's power for 30 seconds, then reconnect. Docks get stuck more often than monitors die.

🛠️ Step 5: Then look at drivers

Still nothing? Open Device Manager:

devmgmt.msc

Expand Display adapters, then update the driver, or use Roll Back Driver if this started right after an update.

✅ The takeaway

Software first (Win + P, driver restart, Detect), then cables and input source, then drivers. Hardware replacement is the last step, not the first.

What's your go-to fix when a monitor goes blank? 👇

🎧 "Nobody Can Hear Me!" Fix Meeting Audio Before You Reinstall Teams

Bryz︱🦾 — Fri, 30 Oct 2026 13:12:37 +0000

It's 8:59. The meeting starts at 9:00. And the ticket says: "Nobody can hear me!" 😱

The tempting move is to uninstall and reinstall Teams (or Zoom). Hold on. Most "no audio" tickets aren't a broken app at all. They're the wrong device selected somewhere along the chain. Here's the three-step check I'd run first. 👇

🎯 Step 1: Check the device inside the app

Meeting apps keep their own device settings, separate from Windows.

Teams: Settings > Devices
Zoom: Settings > Audio

Look at Microphone and Speaker. Docking stations, monitors with speakers, webcams and Bluetooth headsets all show up as audio devices, and any of them can quietly become the selected one. Pick the right device and use the built-in test call or "Test Mic" button.

🪟 Step 2: Check Windows

If the app looks right, go one layer down.

Open Settings > System > Sound.
Under Output, choose the right speaker or headset.
Under Input, choose the right microphone, then talk and watch the input volume bar move.
Open Settings > Privacy & security > Microphone and make sure microphone access is on, and that desktop apps are allowed to use it.

You can also list what Windows sees from PowerShell:

Get-PnpDevice -Class AudioEndpoint | Select-Object Status, FriendlyName

A device showing Error or Unknown points you toward the driver or the cable instead of the app.

⚡ Step 3: Restart the audio service

Still silent? The Windows Audio service can get stuck. From an elevated PowerShell window:

Restart-Service -Name Audiosrv -Force
Get-Service -Name Audiosrv, AudioEndpointBuilder

Both should show Running. Then unplug and replug the headset (or reconnect Bluetooth) and test again. If that doesn't do it, a full restart (not just closing the lid) is the next cheap step.

✅ The order matters

App device ➡️ Windows device + privacy ➡️ audio service ➡️ restart.

Each step takes about a minute, and together they clear most audio tickets before you ever touch a reinstall. Only when all of those check out is it time to look at drivers or reinstalling the app.

What's your go-to first check when someone says "they can't hear me"? 👇

🔄 Windows Update Stuck at 0%? Reset the Cache Before You Reimage

Bryz︱🦾 — Thu, 29 Oct 2026 13:05:06 +0000

Picture it: a user says "my updates have been stuck for two days" 😩. The progress bar sits at 0%, or the same update fails, retries, and fails again.

Before you reach for the reimage button, try this. A very common cause is a corrupted or half-downloaded update cache, and Windows can rebuild it in minutes.

🔍 Step 0: Note the error code

Go to Settings > Windows Update > Update history and write down any error code (for example 0x80070002). If the reset below doesn't fix it, that code is your best clue.

🛑 Step 1: Stop the update services

Open Command Prompt as administrator and run:

net stop wuauserv
net stop bits

wuauserv is the Windows Update service and bits handles background downloads. They need to be stopped so the cache folder isn't locked.

📁 Step 2: Rename the cache folder

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

Renaming (instead of deleting) keeps a backup. Windows creates a brand-new, empty SoftwareDistribution folder the next time the service starts.

▶️ Step 3: Start the services again

net start bits
net start wuauserv

🔁 Step 4: Restart and check again

Restart the PC, then go back to Settings > Windows Update > Check for updates. Expect the first check to take a little longer, since Windows has to re-download what it needs.

🧰 Still failing?

💾 Check free disk space. Updates need room to unpack.
🛠️ Run DISM /Online /Cleanup-Image /RestoreHealth and then sfc /scannow to repair system files.
🔎 Search the error code you saved in Step 0.

Once updates are working again, you can delete SoftwareDistribution.old to free up space.

✅ Quick recap

Stop wuauserv and bits
Rename SoftwareDistribution
Start the services
Restart and check for updates

Simple, safe, and way faster than a reimage. 🚀

What's your go-to move when Windows Update won't cooperate? Drop it below 👇

🌐 "This Website Is Broken!" Test an InPrivate Window Before You Escalate

Bryz︱🦾 — Wed, 28 Oct 2026 13:21:54 +0000

"The website is down!" 😩 It's one of the most common help desk tickets out there. But a lot of the time the website is fine. The problem lives inside the user's browser.

Here's a quick routine that tells you in about two minutes whether it's the browser, the device, or something bigger. ⚡

🔍 Step 1: Try an InPrivate / Incognito window

A private window starts without the user's saved cookies and cache, and most extensions stay off by default.

Edge: Ctrl + Shift + N
Chrome: Ctrl + Shift + N
Firefox: Ctrl + Shift + P

You can also launch one from the Run box (Win + R):

msedge --inprivate https://example.com
chrome --incognito https://example.com

✅ Site works in private mode? The problem is almost always cached data, a bad cookie, or an extension in the normal profile.

❌ Still broken? Skip to Step 3.

🍪 Step 2: Clear that site's data (not everything!)

Wiping the whole browser history signs the user out of everything, and they won't thank you for it. Target just the problem site:

Click the padlock / site info icon next to the address bar.
Open Cookies and site data (Edge) or Site settings (Chrome).
Remove the data for that site, then reload with Ctrl + F5.

Still acting up? Check extensions:

edge://extensions
chrome://extensions

Turn them off one at a time and retest. Ad blockers and old password managers are frequent culprits. 🧩

🖥️ Step 3: Widen the test

If private mode failed too, find out how far the problem reaches:

Try a different browser on the same PC.
Try the same site on another device (or a phone on cellular data).
Check name resolution and connectivity from PowerShell:

Resolve-DnsName example.com
Test-NetConnection example.com -Port 443

If DNS fails or port 443 can't connect, you're looking at a network, DNS, proxy, or VPN issue, not a browser one. 🌐

🎯 Why this matters

Those few tests tell you who should own the ticket:

Result	Likely cause
Works in InPrivate	Cache, cookies, or extension
Fails in every browser on one PC	Device, proxy, or local network setting
Fails on every device	Network, DNS, or the site itself

Write down what you tested in the ticket notes. If you need to escalate, the next tier won't have to start from zero. 📝

What's your first move when a user says a site won't load? Drop it in the comments 👇

🛠️ Windows Acting Broken? Run DISM and SFC Before You Reimage

Bryz︱🦾 — Tue, 27 Oct 2026 13:19:12 +0000

Apps crash for no reason. Windows Update keeps failing. The Start menu won't open. Your first instinct might be "let's just reimage it." 😩

Hold on. A lot of these weird problems come from corrupted system files, and Windows ships with two built-in tools that can repair them in about 15 to 30 minutes. Try them first. 🚀

🔑 Step 1: Open an elevated Command Prompt

Both tools need admin rights. Search for Command Prompt (or Terminal), right-click it, and pick Run as administrator.

If you skip this, SFC tells you that you must be an administrator, and DISM fails with an elevation error.

🩺 Step 2: Repair the Windows image with DISM

DISM /Online /Cleanup-Image /RestoreHealth

Why run this first? SFC repairs files by copying good versions from the Windows component store. If that store is damaged too, SFC can't fix anything. DISM checks and repairs the component store itself, using Windows Update as its source by default.

Heads up: it can sit at 20% or 62.3% for a while. That's normal. Let it finish. ⏳

Want a quick check before the full repair?

DISM /Online /Cleanup-Image /ScanHealth

🔍 Step 3: Fix system files with SFC

sfc /scannow

System File Checker scans protected Windows files and replaces corrupted ones. You'll get one of these results:

✅ "Windows Resource Protection did not find any integrity violations." System files are fine, so look elsewhere (drivers, apps, user profile).
🔧 "...found corrupt files and successfully repaired them." Restart and test again.
⚠️ "...found corrupt files but was unable to fix some of them." Run DISM again, restart, then run SFC again.

📄 Step 4: Check the log if you need details

SFC writes its results to the CBS log:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"

That pulls just the SFC lines into a text file on your desktop, so you can see which files it couldn't fix.

🔁 Step 5: Restart and retest

Always reboot after repairs, then reproduce the original problem. If it's gone, write down what fixed it in the ticket. 📝

🧭 When to escalate

If DISM and SFC both run clean and the problem stays, the system files probably aren't the cause. Now an in-place repair install or a reimage makes sense, and you can show you ruled out the easy fix first.

Your turn: do you run DISM before SFC, or SFC first? 👇

🗂️ Mapped Drive Showing a Red X? Test the Path Before You Remap

Bryz︱🦾 — Mon, 26 Oct 2026 13:22:41 +0000

"My S: drive has a red X and I can't open my files!" 😩

It's one of the most common help desk tickets out there. The quick reflex is to delete the drive and map it again. Sometimes that works. But often the drive letter was never the problem.

Here's the thing: a mapped drive is just a shortcut to a network path. If the path behind it is broken, remapping won't help. So test the path first. 🔍

📋 Step 1: Find the real path

Open Command Prompt and run:

net use

You'll see every mapped drive, its status, and the UNC path it points to, something like \\fileserver\shared. Note the server name and share name.

If you prefer PowerShell:

Get-SmbMapping

📂 Step 2: Open the path directly

Copy the UNC path and paste it into the File Explorer address bar. You can also test it in PowerShell:

Test-Path "\\fileserver\shared"

✅ It opens (or returns True)? The share is healthy. The mapping is just stale. Remove it and map it again:

net use S: /delete
net use S: \\fileserver\shared /persistent:yes

❌ It fails? Then remapping won't fix anything. Move on to Step 3.

🌐 Step 3: Check the network path

Now find out where the connection breaks:

ping fileserver
Test-NetConnection fileserver -Port 445

Port 445 is SMB, the protocol Windows file sharing uses. Here's how to read the results:

Name doesn't resolve? That's a DNS issue. Try nslookup fileserver.
Name resolves but port 445 fails? Check whether the user is off-site and needs the VPN connected, or whether a firewall is blocking the path.
Everything connects but access is denied? Look at permissions or saved credentials for that share.

⏰ Bonus: the "red X at login" trick

Sometimes the drive shows a red X right after sign-in but opens fine when you double-click it. Windows often tries to reconnect drives before the network (or VPN) is fully up. If it opens on click, the user is usually fine, and you've saved yourself a pointless remap.

⚡ The takeaway

Fix the path, and the drive letter fixes itself. Test the UNC path, then the network, then remap only when you know the share is reachable.

What's your first check when a mapped drive goes missing? Drop it in the comments 👇

📶 Wi-Fi Keeps Dropping? Read the WLAN Report Before You Blame the Router

Bryz︱🦾 — Sun, 25 Oct 2026 13:04:13 +0000

"My Wi-Fi keeps dropping!" 😩

It's one of the most common help desk tickets, and the usual reply is "restart the router." Sometimes that works. Often it doesn't, and the ticket comes right back.

Here's the thing: Windows already keeps a detailed log of every wireless connect and disconnect. One command turns it into a readable report. Let's use it. 🧾

🛠️ Step 1: Generate the report

Open Command Prompt or PowerShell as administrator and run:

netsh wlan show wlanreport

Windows builds an HTML report from roughly the last few days of wireless activity and saves it here:

C:\ProgramData\Microsoft\Windows\WlanReport\wlan-report-latest.html

Open it in any browser:

start C:\ProgramData\Microsoft\Windows\WlanReport\wlan-report-latest.html

🔍 Step 2: Read the chart

At the top you'll see a timeline of sessions. Red marks are errors, and gaps show where the connection dropped. Click into a session to see the disconnect reason, like the device going to sleep, the network becoming unavailable, or the user disconnecting.

Now you have when and why, not just "it drops sometimes." 🎯

⚡ Step 3: Match the pattern to a fix

😴 Drops when the laptop sleeps or sits idle? Open Device Manager, go to your Wi-Fi adapter's Properties, and on the Power Management tab uncheck "Allow the computer to turn off this device to save power."
📍 Drops only in one room or desk? Probably weak signal or interference. Check signal strength with:

  netsh wlan show interfaces

Look at the Signal percentage while standing in the problem spot.

💻 Drops everywhere, but only on this one PC? Update the Wi-Fi driver from the laptop maker's site or Windows Update.
👥 Drops for everyone at the same time? Now it's worth looking at the router or access point. 📡

✅ The takeaway

Don't guess. Pull the report, find the pattern, and fix the actual cause. You'll close the ticket faster, and it won't bounce back next week.

What's your go-to first check when Wi-Fi keeps cutting out? Drop it below 👇

☁️ OneDrive Stuck on "Sync Pending"? Fix It Before You Reinstall

Bryz︱🦾 — Sat, 24 Oct 2026 13:06:59 +0000

A user calls: "My files aren't syncing." The spinning arrows have been spinning since Tuesday. 😩

The temptation is to uninstall OneDrive and start fresh. Don't. Most sync problems come down to three things: the client is paused or signed out, one problem file is blocking the queue, or the local sync state is confused. Here's the order I check them in.

🔍 1. Read the status first

Click the OneDrive cloud icon in the taskbar notification area (you may need the ^ arrow to find it). Look for:

Paused: someone paused sync (or it auto-paused on battery saver / metered network). Click Resume.
Signed out / grey cloud: the account isn't signed in. Sign back in.
Red X or "sync issues": click it. OneDrive usually lists the exact file it's stuck on.
Storage full: the OneDrive quota is used up. Nothing new uploads until space is freed.

This one click solves a surprising number of tickets.

📄 2. Hunt down the problem file

One bad file can hold up everything behind it. Common culprits:

File or folder names with characters OneDrive doesn't allow, like " * : < > ? / \ |
Very long paths (deeply nested folders with long names)
Files that are open and locked by another app, like an Excel workbook someone left open
Huge files or temp files that keep changing

Rename, shorten, or close the file, and watch the queue start moving again.

🔄 3. Reset the client (files stay put)

Still stuck? Reset OneDrive. This doesn't delete your files; it clears the local sync state and resyncs.

Press Win + R and run:

%localappdata%\Microsoft\OneDrive\onedrive.exe /reset

If you get a "Windows cannot find..." message, OneDrive may be installed per-machine instead. Try:

"C:\Program Files\Microsoft OneDrive\onedrive.exe" /reset

Wait a minute or two. If OneDrive doesn't reopen on its own, start it manually:

%localappdata%\Microsoft\OneDrive\onedrive.exe

Expect a full resync to take a while on big libraries. ⏳

✅ The takeaway

Check the status. Fix the problem file. Reset the client. Only after all three should a reinstall even be on the table.

What's the weirdest file you've ever seen block a OneDrive sync? Drop it in the comments 👇

⏰ Weird Sign-In Errors? Check the Clock Before You Reset the Password

Bryz︱🦾 — Fri, 23 Oct 2026 13:15:44 +0000

A user can't sign in. You reset their password. Still can't sign in. 😩

Before you go further down the rabbit hole, look at the clock in the corner of their screen. Seriously. A wrong time is one of the sneakiest causes of "nothing makes sense" tickets.

🤔 Why the clock matters

On a Windows domain, sign-in uses Kerberos, and Kerberos tickets are time-stamped. By default, if a computer's clock is more than 5 minutes off from the domain controller, authentication fails. The error messages rarely say "your clock is wrong," so it looks like a password or account problem.

A wrong clock can also break HTTPS: certificates have "valid from" and "valid to" dates, so a PC living in the wrong year can throw certificate errors on perfectly good websites.

1️⃣ Check the time AND the time zone

Compare the PC's clock with your phone. Then check the time zone in Settings > Time & language > Date & time. A laptop that traveled (or a fresh install) can have the right "local" time with the wrong time zone, which still adds up to the wrong actual time.

2️⃣ See where the PC gets its time

Open Command Prompt or PowerShell and run:

w32tm /query /status

Look at Source and Last Successful Sync Time. A domain-joined PC normally syncs from a domain controller. A home or workgroup PC usually syncs from an internet time server like time.windows.com. If the source says Local CMOS Clock or the last sync was ages ago, you've found your suspect. 🔍

3️⃣ Force a resync

From an elevated (Run as administrator) prompt:

w32tm /resync

If it complains that the time service isn't running, start it first:

net start w32time
w32tm /resync

Now try the sign-in again. ✅

🔋 Then ask: why did it drift?

Fixing the time is great, but find the cause so the ticket doesn't come back:

Dead CMOS battery on an older desktop: the time resets after every power loss.
PC offline for a long time and can't reach a time source.
Wrong time zone set manually.

Note it in the ticket so the next tech knows the history. 📝

🎯 The takeaway

When sign-ins or certificates fail for no clear reason, spend 10 seconds on the clock before you spend 30 minutes on the account.

What's the strangest problem you've ever fixed just by correcting the time? 👇

🐢 PC Running Slow? Check the Disk Before You Reimage

Bryz︱🦾 — Thu, 22 Oct 2026 13:08:03 +0000

"My computer is SO slow." 😩

Every help desk tech hears this daily. And it's tempting to jump straight to a reimage. But one of the most common (and easiest) causes is hiding in plain sight: a nearly full C: drive.

When the system drive runs low, Windows has less room for temp files, the page file, and updates. Things get sluggish, and Windows Update can start failing. Here's a quick 3-step check that takes a few minutes. 👇

🔍 Step 1: Check How Much Space Is Left

The fast way: open File Explorer > This PC. If the C: bar is red, you've likely found a big part of the problem.

Or check it in PowerShell:

Get-PSDrive C

Look at the Used and Free columns. Want it in GB?

Get-PSDrive C | Select-Object @{n='FreeGB';e={[math]::Round($_.Free/1GB,1)}}, @{n='UsedGB';e={[math]::Round($_.Used/1GB,1)}}

🧹 Step 2: Clean the Safe Stuff First

Start with what Windows can safely remove itself.

cleanmgr

In Disk Cleanup, pick the C: drive, then click "Clean up system files". That reopens the tool with extra options like Windows Update Cleanup and temporary files. Tick the boxes and let it run.

Prefer set-and-forget? Turn on Storage Sense in Settings > System > Storage. It clears temp files and the Recycle Bin automatically on a schedule.

📂 Step 3: Find the Space Hogs

Go to Settings > System > Storage. Windows breaks down what's using space by category (Apps, Temporary files, Other, and more).

The usual suspects:

📥 Downloads full of old installers and duplicate files
🗂️ Big media files sitting on the desktop
☁️ OneDrive files stored locally. Right-click a folder and choose "Free up space" to make files online-only. They stay in the cloud and download again when opened.

Want to see the biggest folders in a user's profile? Try:

Get-ChildItem $env:USERPROFILE -Directory | ForEach-Object {
  [pscustomobject]@{
    Folder = $_.Name
    SizeGB = [math]::Round((Get-ChildItem $_.FullName -Recurse -File -ErrorAction SilentlyContinue | Measure-Object Length -Sum).Sum/1GB,2)
  }
} | Sort-Object SizeGB -Descending

Always check with the user before deleting their personal files. 🙏

✅ The Takeaway

Check. Clean. Find the hog. Freeing up disk space won't fix every slow PC, but it's a quick, low-risk win you should rule out before reinstalling anything.

What's your go-to first check when someone says their PC is slow? Drop it in the comments 👇

🛑 Group Policy Not Applying? Refresh, Verify, Then Check the OU

Bryz︱🦾 — Wed, 21 Oct 2026 13:09:44 +0000

You pushed a new Group Policy. The user swears nothing changed. 😩

Before you reimage the machine or blame Active Directory, slow down. Most "GPO not applying" tickets come down to one of three things: the PC hasn't refreshed yet, the GPO is being filtered out, or the user or computer is sitting in the wrong OU.

Here's the quick routine I use. 👇

🔄 Step 1: Force a refresh

Group Policy refreshes in the background every 90 minutes or so (with a random offset). If you just made the change, the machine may simply not have it yet.

Open Command Prompt or PowerShell on the affected PC and run:

gpupdate /force

Some settings (like software installs or folder redirection) only apply at sign-in or startup. If it asks to log off or restart, say yes.

🔍 Step 2: See what actually applied

Now check what the machine really received:

gpresult /r

Look at two sections:

Applied Group Policy Objects: your GPO should be listed here.
The following GPOs were not applied because they were filtered out: if your GPO is here, the reason is shown next to it (for example, security filtering or a WMI filter).

Want only the computer side or the user side?

gpresult /r /scope computer
gpresult /r /scope user

For a full, readable report you can share with your team:

gpresult /h C:\Temp\gpreport.html

Run it from an elevated prompt to include computer settings.

🗂️ Step 3: Check the OU

A GPO only applies to objects in the OU it's linked to (and child OUs, unless inheritance is blocked).

Remember the golden rule:

⚙️ Computer Configuration settings follow the computer object.
👤 User Configuration settings follow the user object.

So a user setting in a GPO linked to a computers-only OU won't reach the user. You can check where a computer lives with PowerShell (RSAT AD module needed):

Get-ADComputer $env:COMPUTERNAME | Select-Object DistinguishedName

✅ The takeaway

Refresh with gpupdate /force.
Verify with gpresult /r.
Confirm the user or computer is in the right OU.

Three checks, a couple of minutes, and you'll usually know exactly why the policy didn't land. No reimage required. 🙌

What's your first move when a GPO won't stick? Drop it in the comments 👇