STEP-BY-STEP GUIDE

Troubleshoot 173 in AMD Software: Adrenalin Edition

What to do first

Record 173, verify the affected product and environment, correct the confirmed prerequisite, and retry once under the same conditions.

This is a general troubleshooting guide, not an announcement of a current outage.

Affected products and symptoms

Product
AMD Software: Adrenalin Edition
Versions and conditions
Windows 10 / 11, AMD Radeon Graphics
Error codes and identifiers
173

Symptoms

  • The operation fails with 173.
  • The same failure is reproducible in AMD Software: Adrenalin Edition.

Causes and conditions

The official article identifies a product, compatibility, storage, update, network, file, or configuration condition that must be resolved before retrying.

Before you start

  • Close applications and record the exact PC or GPU model, Windows build, current driver version, and complete error.
  • For a laptop or branded PC, check its model support page and obtain a recovery OEM driver before making changes.

Precautions

  • Use signed GPU or PC-maker packages, not unofficial drivers, individual DLL downloads, or registry tools.
  • Do not open a laptop or bulk-remove a healthy multi-GPU configuration that includes integrated graphics.

Tools and official pages used in this guide

AMD Software: Adrenalin Edition troubleshooting sequence: Check device detection; Separate CPU branding from GPU detection; Separate installation and conflict issues; Select the next check from the device list; Retry only after detection; Escalate as hardware when appropriate; Retry only after Windows identifies the GPU; Compare before and after hardware inspection
Procedure overview created by FaultNote. Read the precautions and full instructions before changing settings. Read the full steps

Step-by-step instructions

  1. 01

    Check device detection

    #

    Right-click Start, open Device Manager, and expand Display adapters. If only Microsoft Basic Display Adapter appears or a yellow warning is listed under Other devices, resolve that condition before retrying error 173.

    Record the complete code, AMD Software version, and GPU name from the same session. If the code changes, stop using this guide and move to the official article for the new code.

  2. 02

    Separate CPU branding from GPU detection

    #

    An AMD CPU can be paired with Intel or NVIDIA graphics. Inspect every Display adapters entry and compare with the physical GPU model. For an unknown device, record the status code and hardware IDs.

    Distinguish a previously detected GPU that disappeared from a PC that never had AMD graphics. For switchable or external graphics, check OEM power and connection requirements. Do not force a different model INF onto an undetected device.

  3. 03

    Separate installation and conflict issues

    #

    For a desktop, power down, unplug it, and follow the product manual to check card seating, auxiliary power, and display cabling. Do not open a warranty-covered laptop; record the Device status code for any warning.

    On an OEM PC, check the model support page before choosing AMD's generic package. Switchable graphics, integrated GPUs, and handhelds may require an OEM build, so preserve the current version and recovery package.

  4. 04

    Select the next check from the device list

    #

    If an AMD name has a warning, inspect the complete status code. If only Basic Display Adapter or an unknown device appears, identify the vendor through hardware IDs. If no entry could be the add-in GPU, inspect power and connections according to the manual before more downloads. These are three different meanings of missing detection.

    An old GPU in hidden devices is not necessarily evidence of a current connection. Record list changes after replacement or external-GPU connection. Do not uninstall every device indiscriminately. A display driven by integrated graphics does not confirm detection of an add-in GPU.

  5. 05

    Retry only after detection

    #

    Restart Windows and verify the actual AMD GPU name appears in Device Manager. Run AMD Software Installer only then; success means error 173 is gone and driver installation completes.

    Close games, recording, GPU monitoring, and other installers. Wait for completion or a specific new code; temporary display flicker can occur, so do not power off during setup.

    Check before continuing

    The official page or signed package for AMD error 173 guidance opens and its product/version conditions match this device.

  6. 06

    Escalate as hardware when appropriate

    #

    If the GPU never appears in firmware or Device Manager, stop reinstalling drivers and give the card or PC maker the model, power configuration, and device status.

    After restart, open Device Manager > Display adapters > target GPU > Properties > Driver and verify provider/version. If it is not the intended state, preserve Install.log instead of repeatedly rerunning setup.

    Check before continuing

    Decision: If the GPU never appears in firmware or Device Manager, stop reinstalling drivers and give the card or PC maker the model, power configuration, and device status. After restart, open Device Manager > Display adapters > target GPU > Properties > Driver and verify provider/version. If it is not the intended state, preserve Install.log instead of repeatedly rerunning setup.

  7. 07

    Retry only after Windows identifies the GPU

    #

    Once Windows identifies AMD graphics, retry the supported package once. If 173 changes to 182 or 175, detection has progressed to a compatibility problem; follow that code instead.

    If the GPU remains absent, stop repeating installer removal. Give the OEM the connection state, device error and PC model. Follow the product manual for hardware inspection.

    Check before continuing

    Once Windows identifies AMD graphics, retry the supported package once. If 173 changes to 182 or 175, detection has progressed to a compatibility problem; follow that code instead.

  8. 08

    Compare before and after hardware inspection

    #

    For connection inspection, shut down normally and power off, then follow the product manual. Do not change slots or power cables while operating. For sealed devices or laptops that cannot be opened, report model and detection state to the OEM. Another slot or PC is an optional test only when compatible equipment exists.

    After restart, inspect changes in Windows first. If detection returns but 173 remains, report tool version and GPU to AMD. A changed code can indicate progress to another stage; retain it rather than calling every result unchanged. Do not decide on GPU replacement or OS reset from 173 alone.

Check the result

  • 173 no longer appears and the operation completes.
  • The selected version and settings remain after restart.
  • A second test shows no new display, input, save, or synchronization problem.

If the problem continues

  • Restore reversible settings from the notes and escalate without deleting user data.
  • Prefer the PC maker or administrator procedure for OEM drivers and managed networks.
  • Protect account names, tokens, and save contents before sharing logs.

Scope of this guide

Troubleshooting guide — A general diagnostic guide based on official support. It does not claim a current incident or a version-specific fix.

Frequently asked questions

Can error 173 occur when only Microsoft Basic Display Adapter appears?

Yes. The installer may not identify supported AMD hardware, so inspect hardware IDs and Device status first.

Should I ignore a yellow warning and install anyway?

No. Record and resolve its Device Manager code first, then rerun the installer as AMD directs.

Does Basic Display Adapter establish that the GPU is AMD?

No. Identify it through hardware IDs, PC specifications and the GPU model before choosing a package.

Does a GPU in hidden devices prove a working connection?

No. Historical device information may remain. Check current status, connection-related changes and hardware IDs.

Official sources and dates

Source publication or resolution date: Not specified. Sources checked: 2026-10-13. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.

Related troubleshooting guides

AMD Radeon / Adrenalin errors and troubleshooting →

AMD, Intel and NVIDIA driver installation errors →

Graphics driver and display problems →

Related how-to guides and comparisons

← Search English guides