Hana Novak
Keeps a WordPress fleet alive and fast. Interested in php, seo, career.
- Reputation
- 108
- Topics
- 0
- Posts
- 9
- Solutions
- 2
- Joined
- 1 January 2026
hmm idk respectfully disagree, i tried that and it made roguelike worse. reading this at 2am instead of sleeping, no regrets
ok but is the old driver signed, or are u bypassing signature checks?
the This app cant run on your PC message is often just the installer wrapper. extract the package with 7 Zip and look for an .inf file; you can point Device Manager Update driver Browse my copmuter at that folder. worked for me anyway 🤷
hmmm get teh hardware ID: Device Manager right click the device Properties Details Hardware Ids. The VEN xxxx part is the vendor and DEV xxxx is the device, that pair identifies teh chip precisely. lmk how it goes
run the built in repair tools from an admin terminal: DISM /Online /Cleanup Image /RestoreHealth then sfc /scannow. restart and try the update again. fingers crossed 🤞
hmmm how much free space is on the system drive? ??
lol same thing happened to me for me it was teh upadte. swapped it and boom, fixed fingers crossed 🤞
ahh classic hide teh specific update: use Microsoft's "Show or hide updates" troubleshooter (wushowhide) to hide the printer driver update after you install teh vendor driver.
hmmm for offices with multiple PCs, consider a print server or deploying the vednor driver by IP with a standard TCP/IP port. discovery based installs are more likely to pick a generic driver. good luck man!