-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Desktops
- Business PCs, Workstations and Point of Sale Systems
- Searching drivers for HP Thin Client
Create an account on the HP Community to personalize your profile and ask a question
02-05-2024 03:09 PM
Hello. I would like to know if drivers are available for Windows XP (32-bit) or Windows 7 (32-bit) for these thin client models: HP T620 Plus, HP T730? I know these are outdated operating systems, but I really need drivers. Perhaps they were once available and have now been hidden by HP? Or was it not there in the first place? Somebody knows?
02-05-2024 04:10 PM
Hi:
No XP drivers were ever released for either model.
I have a t630 and it used to have W7 embedded 32-bit drivers on the support page and now there are only W10 drivers.
I assume that was the same for the t620.
This reputable 3rd party driver website has the W7 32-bit drivers for the t620. They will work on the regular W7 OS.
HP t620 Flexible Thin Client drivers (driverscollection.com)
I don't know for sure if there were ever W7 drivers released for the t730.
I highly doubt it though.
02-06-2024 06:00 AM - edited 02-08-2024 12:37 PM
Oh, apparently you can still select Windows 7 Embedded on the driver page, although initially it shows that only Windows 10 is available. They should work with Windows 7 Ultimate, right? Unfortunately, only 64-bit drivers are available for the T730 😞
02-06-2024 06:14 AM
I used the W7 x64 Embedded drivers on my HP t630 I had installed W7 Pro on, and they worked just fine.
So, I see no reason why the W7 Embedded 32-bit drivers wouldn't work just as well.
Then I took the free upgrade to W10 (which you can no longer do).
Then I updated it to W11 but somewhere during last year, a W11 22H2 update messed with the embedded AMD graphics.
I couldn't fix it and went back to W10.