Newscast

Microsoft provides the tool for HP Smart bug on Windows 10 and 11 servers

By Nik

January 09, 2024

Last month, people online started to complain that their computer systems were automatically installing HP’s Smart app for printers, even though there was no printer connected to their PCs. This issue became widespread, and shortly after, Microsoft confirmed it and said that almost all versions of Windows were affected by the bug.

Since HP’s app was installed, many initially thought that HP company might be responsible for this bug. However, after looking into it further, Microsoft confirmed that this was not the case and that the problem was not caused by an update on HP’s part.

A couple of weeks later, Microsoft solved the problem with a tool. The company explained that this tool is meant to help users and administrators solve this issue, It will check your printer information and restore any previously downloaded model information and icons. The tool will also remove the ‘HP LaserJet M101-M106 model information, icons, and application associations from printers that do not match this name and model. This tool will also uninstall the HP Smart application if incorrect metadata is found, if there are no HP printers or HP printer drivers installed, and also if the application was installed after Nov 25th, 2023.

The tool can be downloaded from the Microsoft Download Center.

If your system is affected, download the file that matches your system’s architecture and run it as an Administrator. Microsoft suggests using the elevated Command Prompt (run as administrator).

To use the tool click Start, type cmd, right-click Command Prompt, and then select Run as Administrator. In the opened command prompt windows, type the following:

cd /d c:\temp and then press Enter. (Keep in mind that the downloaded files have to be located in the C:\temp directory.) Type the name of the file that suits your PC’s architecture (example: PrintMetadataTroubleshooterX64.exe) and then press Enter.

If your system is affected by this bug, you will receive the message: Troubleshooter completed successfully.