# WIN10 22H2 on FW13 AMD Ryzen 5, missing HW Drivers

**URL:** <https://community.frame.work/t/win10-22h2-on-fw13-amd-ryzen-5-missing-hw-drivers/60360>\
**Category:** Community Support\
**Tags:** other-issues, amd-7040\
**Created:** [November 12, 2024, 5:57pm UTC](https://community.frame.work/t/win10-22h2-on-fw13-amd-ryzen-5-missing-hw-drivers/60360 "2024-11-12T17:57:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mark4](https://avatars.discourse-cdn.com/v4/letter/m/77aa72/32.png) [@mark4](https://community.frame.work/u/mark4)\
**Post date:** [November 12, 2024, 5:57pm UTC](https://community.frame.work/t/win10-22h2-on-fw13-amd-ryzen-5-missing-hw-drivers/60360/1 "2024-11-12T17:57:08Z")

</div>

Hello Everybody,

I am currently setting up my newly aquired FW13 AMD with WIN10. After basic installation and installing the FW13 drivers package, It works flawless but I have discovered unknown devices in the device manager.

See:

 ![overview](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/d/f/df6e9157b915bee229a0e4c8789e494186670db7.png)

The corresponding HW IDs (from top):  
(1) PCI\VEN\_1022&DEV\_14EC&SUBSYS\_0006F111&REV\_00  
(2) PCI\VEN\_1022&DEV\_14EC&SUBSYS\_0006F111&REV\_00  
(3) PCI\VEN\_1022&DEV\_15C7&SUBSYS\_0006F111&REV\_00  
(4) ACPI\VEN\_AMDI&DEV\_0102  
(5) ACPI\VEN\_AMDI&DEV\_0052  
(6) PCI\VEN\_1022&DEV\_1669&SUBSYS\_0006F111&REV\_00  
(7) PCI\VEN\_1022&DEV\_1668&SUBSYS\_0006F111&REV\_00

Google does not give me any further insight, apart from AMD beeing the vendor.

What are these devices and is there any significant drawback from leaving the machine “as is”?

Thank you very much for your support and kind regards.  
mark

---

<div class="post-metadata">

**Author:** ![DHowett](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/dhowett/32/1990_2.png) [@DHowett](https://community.frame.work/u/DHowett)\
**Post date:** [November 12, 2024, 6:23pm UTC](https://community.frame.work/t/win10-22h2-on-fw13-amd-ryzen-5-missing-hw-drivers/60360/2 "2024-11-12T18:23:07Z")

</div>

Windows 10 is not officially supported on any Framework Laptop except for the original 11th Generation Intel Core 13”.

---

<div class="post-metadata">

**Author:** ![mark4](https://avatars.discourse-cdn.com/v4/letter/m/77aa72/32.png) [@mark4](https://community.frame.work/u/mark4)\
**Post date:** [November 12, 2024, 8:21pm UTC](https://community.frame.work/t/win10-22h2-on-fw13-amd-ryzen-5-missing-hw-drivers/60360/3 "2024-11-12T20:21:29Z")

</div>

My fault! Thanks for pointing this out. Back into the rabbit hole of setting up a Win11/Ubuntu24 dualboot ;-)…

---

<div class="post-metadata">

**Author:** ![Kenny\_Lewis](https://avatars.discourse-cdn.com/v4/letter/k/c0e974/32.png) [@Kenny\_Lewis](https://community.frame.work/u/Kenny_Lewis)\
**Post date:** [November 13, 2024, 11:39am UTC](https://community.frame.work/t/win10-22h2-on-fw13-amd-ryzen-5-missing-hw-drivers/60360/4 "2024-11-13T11:39:27Z")

</div>

> [@mark4](#):
>
> What are these devices and is there any significant drawback from leaving the machine “as is”?

I have misc items in `lspci` in Linux, I don’t think there’s a drawback beyond Framework not supporting Win10 (same as Framework not supporting me in the flavour of Linux I use).

K3n.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/1X/64c81a89f963ddb07633887baceb642a4b056046.png) [@system](https://community.frame.work/u/system)\
**Post date:** [May 12, 2025, 11:39am UTC](https://community.frame.work/t/win10-22h2-on-fw13-amd-ryzen-5-missing-hw-drivers/60360/5 "2025-05-12T11:39:44Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.