Windows 11 Troubleshooting Guide 2026

Introduction: Why Windows 11 Troubleshooting Is a Core Helpdesk Skill

If you work on an IT helpdesk, Windows 11 issues are the bread and butter of your ticket queue. Whether it's a user who can't print after an update, a laptop stuck on a BitLocker recovery screen, or a machine that's slowed to a crawl since last month's patch — these problems land on your desk every single day.

And honestly? With Microsoft's aggressive update cadence (monthly security patches, feature updates, and the recent rollout of Windows 11 25H2), the variety and complexity of issues just keeps growing.

This guide is designed to be your go-to reference for the most common Windows 11 support scenarios you'll encounter in 2026. We'll walk through practical, step-by-step troubleshooting workflows for update failures, Blue Screen of Death (BSOD) errors, performance degradation, printer problems, BitLocker recovery lockouts, driver issues, and system file corruption. Every section is written from a helpdesk perspective — meaning we focus on what you can actually do when a user calls in or submits a ticket, not just the theory behind it.

Bookmark this page. You're going to need it.

1. Windows Update Failures: The January and February 2026 Saga

Understanding the Current Update Landscape

The January 2026 Security Update (KB5074109) for Windows 11 versions 24H2 and 25H2 introduced a wave of issues that helpdesk teams across the globe have been dealing with ever since. Microsoft confirmed that this update can trigger UNMOUNTABLE_BOOT_VOLUME stop errors on some devices, effectively bricking them. The February 2026 update (KB5077181) addressed many of these problems, but not before a significant number of machines were already affected.

Here are the key known issues from the January and February 2026 update cycle that you need to know about:

Boot failures with Black Screen of Death: Some devices crash during startup with an UNMOUNTABLE_BOOT_VOLUME error after installing KB5074109.
Remote Desktop Connection failures: Credential prompts fail in remote connection applications, including the Windows App on Azure Virtual Desktop and Windows 365.
Cloud storage application hangs: Apps become unresponsive when opening or saving files to OneDrive or Dropbox.
Outlook POP account issues: Outlook Classic won't open with POP accounts because a background process blocks the main window.
Virtual Secure Mode restart loop: Systems running VSM restart instead of shutting down or entering hibernation.
WPA3 Wi-Fi connectivity: Some devices can't connect to WPA3-Personal Wi-Fi networks (this one was fixed in the February update, thankfully).

Troubleshooting Update Installation Failures

When a user reports that Windows Update is failing, here's the systematic approach I'd recommend:

Step 1: Check the error code. Open Settings > Windows Update and note the specific error code. Common ones include:

0x800f0922 — Insufficient disk space in the System Reserved partition or failure to connect to the update server.
0x80073712 — A file needed by Windows Update is damaged or missing.
0x800705b4 — Timeout error during download or installation.
0x80070002 — Windows Update component store corruption.

Step 2: Run the Windows Update Troubleshooter. It doesn't always fix things, but it's a quick first step.

Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run

Step 3: Reset Windows Update components manually. If the troubleshooter doesn't resolve it, open an elevated Command Prompt and run:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Step 4: Use DISM to repair the component store.

DISM /Online /Cleanup-Image /RestoreHealth

Wait for this to complete (it can take 15-30 minutes — go grab a coffee), then run:

sfc /scannow

Step 5: If KB5074109 caused a boot failure, the user will need to uninstall the update from the Windows Recovery Environment (WinRE). They won't be able to reach the desktop, so walk them through this:

Force-restart the device three times to trigger automatic repair.
Select Troubleshoot > Advanced options > Uninstall updates.
Choose Uninstall latest quality update.
Once the device boots, pause updates for 7 days while you validate the next cumulative update.

Proactive Update Management for IT Teams

To prevent update disasters (and trust me, you want to prevent them), use Group Policy or Microsoft Intune to configure Windows Update for Business settings. Key policies include:

Defer quality updates by 7-14 days to let early adopters discover issues first.
Use update rings in Intune to create a pilot group that receives updates before the general population.
Enable Known Issue Rollback (KIR) via Group Policy so Microsoft can remotely disable a specific fix within an update without requiring a full uninstall.

One thing that trips up a lot of teams: when using Intune alongside Active Directory Group Policy, MDM Wins Over GPO does NOT apply to Windows Update policies. If conflicting GPOs exist, the update ring in Intune may not take effect. Always audit both channels.

2. Blue Screen of Death (BSOD) Diagnosis and Resolution

The Most Common BSOD Stop Codes in 2026

Blue screens are one of the most intimidating problems users bring to the helpdesk, but they're surprisingly systematic to diagnose once you know what to look for. Here are the stop codes you'll see most often:

UNMOUNTABLE_BOOT_VOLUME (0x000000ED): Disk or file system corruption. Frequently triggered by bad updates or failing storage devices.
CRITICAL_PROCESS_DIED (0x000000EF): A critical system process terminated unexpectedly. Often caused by corrupted drivers or system files.
IRQL_NOT_LESS_OR_EQUAL (0x0000000A): A driver or kernel-mode process accessed a memory address it shouldn't have. Usually points to a driver issue.
SYSTEM_SERVICE_EXCEPTION (0x0000003B): An exception occurred while executing a system service routine. Commonly triggered by antivirus software or corrupted drivers.
DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1): A driver accessed an improper memory address at an elevated IRQL. Almost always a driver problem.
KERNEL_SECURITY_CHECK_FAILURE (0x00000139): The kernel detected corruption of a critical data structure. Can indicate hardware failure or software bugs.

Step-by-Step BSOD Troubleshooting Workflow

Step 1: Collect the dump file. Windows writes a minidump to C:\Windows\Minidump\ after every BSOD. If the user can boot (even in Safe Mode), grab this file for analysis.

Step 2: Analyze with WinDbg. Install WinDbg from the Microsoft Store or Windows SDK. Open the dump file and run:

!analyze -v

This command gives you the faulting module, the bugcheck code, and a stack trace. Look for the module name — it'll tell you whether the crash was caused by a specific driver (e.g., nvlddmkm.sys for NVIDIA, ataport.sys for storage, tcpip.sys for networking).

Step 3: Check Event Viewer. If WinDbg isn't available (or you need a quicker look):

eventvwr.msc > Windows Logs > System

Filter for "Error" and "Critical" events around the time of the crash. Look for BugCheck entries and any driver or service failures that happened right before.

Step 4: Update or roll back the faulting driver. If the analysis points to a specific driver:

devmgmt.msc > Right-click the device > Properties > Driver tab > Roll Back Driver

If rollback is grayed out, you'll need to download the previous driver version from the manufacturer's website and install it manually.

Step 5: Run memory diagnostics. BSOD errors with memory-related stop codes should prompt a hardware check:

mdsched.exe

Choose "Restart now and check for problems." Review results in Event Viewer under Windows Logs > System after the test completes.

Step 6: Check disk health.

wmic diskdrive get status
chkdsk C: /f /r

For NVMe drives, also check the SMART data using CrystalDiskInfo or the manufacturer's utility. I've personally caught a few drives that were reporting "OK" through basic checks but showed concerning reallocated sector counts in SMART data.

3. Performance Degradation: When Windows 11 Slows Down

Common Causes of Slow Performance After Updates

The January 2026 update (KB5074109) was specifically reported to cause systems to freeze within minutes of sign-in, with Task Manager showing 0% CPU usage — a particularly confusing symptom, right? But even outside of specific buggy updates, Windows 11 machines slow down for pretty predictable reasons:

Background indexing after updates: Windows Search rebuilds its index after major updates, consuming significant disk I/O for hours.
Startup program bloat: Users accumulate startup applications over time without realizing the impact.
Antivirus conflicts: Multiple security products running simultaneously create severe performance overhead.
Insufficient RAM for modern workloads: With Windows 11 25H2 and Copilot features, 8 GB is the minimum; 16 GB is the practical baseline for productivity workers.
Disk fragmentation on HDDs: Still relevant for organizations that haven't fully migrated to SSDs (and there are more of these than you'd think).
Corrupted Windows component store: Accumulated update residue and broken components drag down system performance.

The Helpdesk Performance Troubleshooting Checklist

So, let's dive into the actual checklist.

1. Check Task Manager for resource hogs.

Ctrl + Shift + Esc > Processes tab > Sort by CPU, Memory, or Disk

Look for any process consuming more than 30% of any resource continuously. Common offenders include SearchIndexer.exe, MsMpEng.exe (Windows Defender), OneDrive.exe, and Teams.exe.

2. Disable unnecessary startup programs.

Task Manager > Startup apps tab > Disable items with "High" impact that the user doesn't need at boot

3. Run Disk Cleanup with system files.

cleanmgr /sageset:1

Select all options including "Windows Update Cleanup," "Delivery Optimization Files," and "Previous Windows installations." Then run:

cleanmgr /sagerun:1

4. Repair system files. Always run DISM before SFC — this is important because DISM restores the component store that SFC uses as its source:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

5. Check power plan settings. Laptops often default to "Balanced" or "Power saver" mode, which throttles CPU performance significantly:

powercfg /list
powercfg /setactive 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

That GUID sets the "High Performance" power plan. For desktops on AC power, this should be the default.

6. Defragment HDDs or optimize SSDs.

dfrgui.exe

Windows automatically TRIMs SSDs, but if the scheduled optimization has been disrupted, running it manually can help. And a quick reminder: never defragment an SSD — only optimize it.

7. Check for malware. Even with Windows Defender active, run a full offline scan:

Start-MpScan -ScanType FullScan

Or for an offline scan that runs before the OS fully loads:

Start-MpWDOScan

4. Printer Problems: The Eternal Helpdesk Nemesis

Ah, printers. If you've been on a helpdesk for more than a week, you already know.

The 2026 Printer Driver Deprecation

A major change landed in 2026 that every helpdesk tech needs to understand: Microsoft has officially ended support for V3 and V4 printer drivers, following the deprecation announcement from September 2023. Here's what this means in practice:

Existing printers with V3/V4 drivers will continue to function, but they won't receive future updates through Windows Update.
New printer installations may default to Microsoft's IPP Class Driver instead of manufacturer-specific drivers.
Some legacy printers — particularly older network multifunction devices — may lose advanced features like duplex printing, stapling, or secure print release.

You can check which driver a printer is using with PowerShell:

Get-PrinterDriver | Select-Object Name, MajorVersion | Format-Table -AutoSize

A MajorVersion of 3 or 4 means it's a legacy driver. Contact the manufacturer for an updated IPP-compatible driver or Universal Print driver.

Common Printer Troubleshooting Scenarios

Scenario 1: Printer not found after Windows Update.

Open Services (services.msc) and restart the Print Spooler service.
If the printer was USB-connected, try a different USB port and cable.
Remove and re-add the printer: Settings > Bluetooth & devices > Printers & scanners > Add device.
If automatic detection fails, click "Add manually" and enter the printer's IP address or hostname.

Scenario 2: Print jobs stuck in queue.

net stop spooler
del /Q /F /S "%systemroot%\System32\spool\PRINTERS\*.*"
net start spooler

This stops the spooler, deletes all pending jobs, and restarts the service. It resolves about 90% of stuck queue issues — it's the classic fix for a reason.

Scenario 3: Garbled output or unexpected text on printed pages.

This is a known issue with USB dual-mode printers in Windows 11 where IPP protocol messages leak into the print output. Kind of bizarre when you first see it. The fix is to disable the IPP protocol for that printer and force USB-only communication:

Open Device Manager.
Find the printer under "Print queues" or "Universal Serial Bus devices."
Uninstall the IPP-class device if a duplicate entry exists.
Reinstall using only the manufacturer's USB driver.

Scenario 4: Network printer intermittently offline.

ping printer-hostname
Test-NetConnection -ComputerName printer-ip -Port 9100

If the printer responds to ping but port 9100 (raw printing) is blocked, check the firewall on the printer itself or any network firewall between the client and the printer. Also verify the printer has a static IP or a DHCP reservation — printers that get dynamic addresses frequently "disappear" when their lease expires. This one catches people off guard more often than you'd expect.

5. BitLocker Recovery Lockouts

Why BitLocker Recovery Gets Triggered

BitLocker recovery lockouts are one of the most stressful helpdesk tickets because the user is completely locked out of their machine. I've seen whole departments grind to a halt over this. BitLocker's Trusted Platform Module (TPM) validates the boot chain on every startup, and if anything changes, it demands the 48-digit recovery key. Common triggers include:

Windows Updates that modify the boot manager or boot configuration data (BCD).
BIOS/UEFI firmware updates that change the Secure Boot configuration.
Hardware changes such as replacing the motherboard, adding RAM, or connecting to a docking station.
Secure Boot policy changes — enabling or disabling Secure Boot in the BIOS.
TPM firmware updates or TPM resets.

Recovery Key Retrieval Methods

The recovery key can be stored in multiple locations depending on your organization's setup:

1. Microsoft Entra ID (Azure AD):

Azure Portal > Microsoft Entra ID > Devices > Search for device > BitLocker keys

2. Active Directory Domain Services (on-premises):

Get-ADObject -Filter {objectclass -eq "msFVE-RecoveryInformation"} -SearchBase "CN=ComputerName,OU=Computers,DC=domain,DC=com" -Properties msFVE-RecoveryPassword | Select-Object -Property msFVE-RecoveryPassword

3. Microsoft Intune / Endpoint Manager:

Intune Admin Center > Devices > Search device > Recovery keys

4. User's Microsoft Account: If the device is personal or hybrid-joined, the key may be stored at account.microsoft.com/devices/recoverykey.

Preventing Future BitLocker Lockouts

The best approach is to suspend BitLocker before performing actions that change the boot configuration:

Suspend-BitLocker -MountPoint "C:" -RebootCount 1

This suspends protection for exactly one reboot cycle. Use -RebootCount 3 for firmware updates that may require multiple restarts. Configure this as part of your BIOS update and Windows Update deployment scripts to prevent mass lockout events.

For organizations using SCCM/ConfigMgr or Intune, enable the "Suspend BitLocker during task sequence" option in your update deployment profiles. Also, make sure all recovery keys are being escrowed to either Active Directory or Entra ID — run this audit PowerShell command across your fleet:

$BitLockerInfo = Get-BitLockerVolume -MountPoint "C:"
if ($BitLockerInfo.KeyProtector.KeyProtectorType -notcontains "RecoveryPassword") {
    Write-Warning "No recovery password protector found on C: drive!"
} else {
    $BitLockerInfo.KeyProtector | Where-Object {$_.KeyProtectorType -eq "RecoveryPassword"} | 
    Select-Object KeyProtectorId, RecoveryPassword
}

6. Driver Issues and Device Compatibility

The Windows 11 25H2 Driver Landscape

Windows 11 25H2 introduced several driver-related changes that affect helpdesk operations. The OS now supports Wi-Fi 7 enterprise access points, which is great for organizations deploying modern wireless infrastructure, but it also means older Wi-Fi adapters may need updated drivers to coexist properly with new access points.

Quick Machine Recovery, a new feature in 25H2, automatically attempts to recover from driver-related boot failures by reverting the offending driver. While this reduces the number of "my PC won't start" tickets, it can also confuse users who see their devices reboot unexpectedly during startup. So expect a different kind of ticket instead.

Systematic Driver Troubleshooting

Step 1: Identify the problematic device. Open Device Manager and look for devices with yellow exclamation marks:

devmgmt.msc

Right-click any flagged device, select Properties, and note the error code on the General tab. Here are the common codes:

Code 10: Device cannot start. The driver is loaded but not functioning.
Code 28: No driver installed for this device.
Code 31: Device isn't working properly because Windows can't load the required drivers.
Code 43: Windows has stopped this device because it has reported problems. Common with USB and GPU devices.
Code 52: Windows can't verify the digital signature of the driver. Often caused by unsigned or tampered driver files.

Step 2: Check for driver updates via PowerShell.

Get-WindowsDriver -Online | Where-Object {$_.Date -lt (Get-Date).AddYears(-2)} | 
Select-Object ClassName, ProviderName, Date, Version | Format-Table -AutoSize

This lists all drivers older than two years — prime candidates for updating.

Step 3: Reinstall the driver cleanly. For persistent issues, especially with GPU drivers:

Download the latest driver from the manufacturer's website.
Open Device Manager, right-click the device, and select "Uninstall device." Check "Attempt to remove the driver for this device."
Restart the computer.
Install the freshly downloaded driver.

Step 4: Use PnPUtil for advanced driver management.

pnputil /enum-drivers
pnputil /delete-driver oem42.inf /uninstall

PnPUtil lets you enumerate all third-party drivers in the driver store and remove specific ones cleanly. It's particularly useful when multiple driver versions are conflicting with each other.

7. System File Corruption: The DISM and SFC Deep Dive

When and Why System Files Get Corrupted

System file corruption is an underlying cause of many Windows 11 problems — from random application crashes to failed updates to performance degradation. Corruption commonly happens after:

Interrupted Windows updates (power loss during installation is the classic one).
Malware infections that modify system binaries.
Disk sector failures on aging storage devices.
Aggressive third-party "optimization" tools that delete files Windows actually needs.

The Correct Order of Operations

Here's something a lot of techs get wrong: many run SFC first, but that's backwards. The proper sequence is:

1. DISM first: DISM repairs the Windows component store (WinSxS), which is the source repository that SFC uses to replace corrupted files. If the component store itself is corrupt, SFC will fail every time.

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

CheckHealth reports whether corruption is detected (fast — takes seconds). ScanHealth performs a deeper scan (slower, a few minutes). RestoreHealth actually repairs the component store by downloading good copies from Windows Update (can take 15-30 minutes, so plan accordingly).

2. SFC second: Once DISM has restored a healthy component store, SFC can properly scan and replace corrupted system files:

sfc /scannow

SFC checks all protected system files and replaces corrupted versions with the correct ones from the component store. Review the log at C:\Windows\Logs\CBS\CBS.log for the details.

3. CHKDSK if disk issues are suspected:

chkdsk C: /f /r /x

The /f flag fixes errors, /r locates bad sectors and recovers readable information, and /x forces the volume to dismount first. This will require a restart for the boot volume.

When SFC and DISM Can't Fix the Problem

If repeated runs of DISM and SFC report corruption they can't repair, you've got two options:

Option 1: In-place upgrade repair. Download the Windows 11 ISO from Microsoft, mount it, and run Setup.exe. Choose "Keep personal files and apps." This replaces all system files while preserving user data and applications. It's the least disruptive repair option and honestly works more often than people expect.

Option 2: Reset this PC (keep files).

Settings > System > Recovery > Reset this PC > Keep my files

This reinstalls Windows while preserving user files but removes all installed applications. More disruptive, but faster than a full reinstall. Use this when the in-place upgrade also fails.

8. Remote Troubleshooting Tips and Tools

PowerShell Remoting for Helpdesk Efficiency

Many of the commands and procedures in this guide can be executed remotely using PowerShell Remoting, which saves both you and the user a lot of time:

# Enable remoting on the target machine (run once, requires admin)
Enable-PSRemoting -Force

# Connect to a remote machine
Enter-PSSession -ComputerName DESKTOP-ABC123

# Run a command on multiple machines simultaneously
Invoke-Command -ComputerName PC1, PC2, PC3 -ScriptBlock {
    Get-BitLockerVolume -MountPoint "C:" | Select-Object MountPoint, VolumeStatus, EncryptionPercentage
}

For organizations using Microsoft Intune, the Troubleshooting + support pane in the Intune Admin Center provides a helpdesk dashboard that shows device compliance status, installed apps, policy assignments, and recent device actions — all without needing direct access to the machine.

Quick Machine Recovery in Windows 11 25H2

Windows 11 25H2 introduced Quick Machine Recovery, a feature that lets IT administrators remotely push targeted fixes to devices that can't boot. This works through the Windows Recovery Environment and requires:

The device to have network connectivity during WinRE (wired Ethernet or known Wi-Fi).
The remediation script to be published via Windows Remediation Service.
The policy to be configured via Group Policy or Intune.

This is genuinely a game-changer for helpdesk teams dealing with mass boot failures caused by bad updates or driver issues. Instead of physically touching each affected device, you can push a fix that runs before the OS loads. If you haven't set this up yet, I'd strongly recommend prioritizing it.

9. Building a Helpdesk Troubleshooting Decision Tree

When a Windows 11 issue comes in, use this mental framework to triage and resolve it efficiently:

Can the user boot to the desktop?
- No → BitLocker recovery? Boot failure? BSOD loop? Follow sections 2 or 5.
- Yes → Continue to step 2.
Did the issue start after an update?
- Yes → Check the KB article for known issues. Consider uninstalling the update. Follow section 1.
- No → Continue to step 3.
Is the issue performance-related?
- Yes → Check Task Manager, startup apps, disk health, and system files. Follow section 3.
- No → Continue to step 4.
Is it a specific device or application?
- Device (printer, USB, display) → Follow sections 4 or 6.
- Application → Check Event Viewer for application errors, reinstall the app, or repair system files per section 7.
Is the issue intermittent?
- Yes → Set up Performance Monitor or Reliability Monitor to capture data over time.
- No → Proceed with the specific troubleshooting workflow for the symptom.

10. Essential PowerShell Commands Every Helpdesk Tech Should Know

To wrap things up, here's a reference list of PowerShell commands that cover the most common helpdesk scenarios. I keep these bookmarked and use them almost daily:

# System Information
Get-ComputerInfo | Select-Object OsName, OsVersion, OsBuildNumber, WindowsProductName

# Uptime (useful for the classic "have you restarted?" conversations)
(Get-Date) - (Get-CimInstance Win32_OperatingSystem).LastBootUpTime

# Installed Updates
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

# Disk Space
Get-Volume | Select-Object DriveLetter, FileSystemLabel, @{N="SizeGB";E={[math]::Round($_.Size/1GB,2)}}, @{N="FreeGB";E={[math]::Round($_.SizeRemaining/1GB,2)}}

# Running Services
Get-Service | Where-Object {$_.Status -eq "Running"} | Sort-Object DisplayName

# Network Configuration
Get-NetIPConfiguration | Select-Object InterfaceAlias, IPv4Address, IPv4DefaultGateway, DnsServer

# Event Log Errors (last 24 hours)
Get-WinEvent -FilterHashtable @{LogName="System"; Level=2; StartTime=(Get-Date).AddHours(-24)} | Select-Object TimeCreated, Id, Message -First 20

# Installed Software
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | 
Select-Object DisplayName, DisplayVersion, Publisher, InstallDate | Sort-Object DisplayName

# Group Policy Results
gpresult /h C:\Temp\GPReport.html
Start-Process C:\Temp\GPReport.html

# Pending Reboot Check
$RebootPending = Test-Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending"
$WindowsUpdate = Test-Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired"
Write-Output "CBS Reboot Pending: $RebootPending | WU Reboot Required: $WindowsUpdate"

Conclusion: Becoming a More Effective Windows 11 Helpdesk Professional

Windows 11 troubleshooting isn't about memorizing every possible error code or update KB number — it's about having a systematic approach and knowing where to look. The workflows in this guide cover the vast majority of tickets you'll encounter on a typical helpdesk, from the January 2026 update disasters to the eternal printer woes that just refuse to go away.

Here are the key takeaways worth remembering:

Always run DISM before SFC — the order matters because SFC depends on a healthy component store.
Defer updates by 7-14 days in production environments to let early adopters find the bugs first.
Suspend BitLocker before BIOS updates to prevent mass lockout events.
Check for V3/V4 printer driver deprecation when printer issues arise after 2026 updates.
Use Quick Machine Recovery in Windows 11 25H2 for remote remediation of boot failures.
Document everything — update your internal knowledge base with the specific fixes that worked in your environment.

The best helpdesk professionals aren't the ones who never encounter problems — they're the ones who resolve them faster because they've got a proven, repeatable methodology. This guide is your starting point. Adapt it to your environment, expand it with your own findings, and share it with your team.